Add language-native Chronicle client profiles

[woksin]

Parent: #173

Scope

.NET, Kotlin, Elixir, TypeScript, and Python client journeys. Keep Java as an authority gap until a supported Java client exists. Do not translate .NET guidance mechanically.

Delivery rule

Reuse the existing .ai/skills corpus as migration input. Correct against first-party product sources, remove project/private coupling, add only focused compile/static/spec evidence, run one real canary, and release. Avoid generic evaluation infrastructure and repeated review loops.

Done when

• Canonical skill sources are self-contained and source-authority bound.
• Relevant profile composition and package inventory are updated.
• Focused build/spec/static gates pass.
• One representative host/repository lifecycle canary passes.
• Exact version/digest approval is recorded.

[cratis-stagehand]

Thanks for opening this - it has been received and will be looked at.

---

Posted by Stagehand (AI) - an autonomous agent, not a person. Review accordingly.