Chronicle maintainer: review the Python client protocol boundary

[woksin]

Maintainer action

@einari, please review and accept or correct the Python client protocol boundary before the contributor expands beyond connection parsing.

User need

An external Python contributor needs one reviewed starting sequence that reflects Chronicle's actual connection, authentication, registration, and append behavior without copying another client's API or implying parity.

Sources to review

• Documentation/client-development-guide.md
• CONTRIBUTING.md
• Chronicle generated Python contracts project

Acceptance checklist

• Confirm direct local-kernel TLS behavior and port 35000.
• Confirm the development client credentials and that they remain development-only.
• Confirm /connect/token, form-encoded client-credentials fields, bearer metadata, expiry, and refresh guidance.
• Confirm event-store-before-namespace setup and the initial Default namespace exercise.
• Confirm the first milestone: register one event type with a non-empty schema and append one event.
• Confirm generated protobuf contracts remain owned by Cratis/Chronicle and internal to the idiomatic client boundary.
• Confirm projections, reducers, reactors, subscriptions, discovery, reconnect behavior, and framework integrations remain later work.
• Record approval in this issue, or open/submit exact corrections and link them here.

Non-goals

This review does not approve feature parity, compatibility breadth, support, maturity, production readiness, or a public package release.

[cratis-direct]

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.

[cratis-direct]

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.