Complete the first authenticated append milestone

[woksin]

User need

A Python developer needs one executable path proving that the client can authenticate, establish Chronicle state, register an event contract, and append an event.

Desired behavior

Complete the first bounded end-to-end milestone against a local Chronicle development kernel.

Acceptance evidence

• Establishes a TLS gRPC channel using explicit local-development credentials.
• Ensures one event store and then the Default namespace.
• Registers one event type with a non-empty JSON schema.
• Appends one event to event-log.
• Asserts success and the returned sequence number.
• Closes token and channel resources deterministically.
• Includes unit tests for conversion/failure behavior and an opt-in integration test with exact kernel setup instructions.
• Adds a runnable console sample and replaces the placeholder getting-started page.

Dependencies

• The generated cratis-chronicle-contracts package.
• Accepted connection-options and OAuth token-provider boundaries.

Non-goals

Projections, reducers, reactors, subscriptions, reconnect lifecycle, automatic discovery, and framework integrations.

[woksin]

Depends on Cratis/Chronicle#3806, #2, and #3.

[woksin]

Generated-contract publication dependency is now tracked explicitly in #15 and #16.

[woksin]

The generated-contract dependency is now available as a verified temporary Chronicle v16.38.2 release asset while PyPI setup proceeds:

https://github.com/Cratis/Chronicle/releases/download/v16.38.2/cratis_chronicle_contracts-16.38.2-py3-none-any.whl

A Chronicle.Python change is in verification to resolve this dependency automatically during a normal development install. The contracts-publication portion of this issue is therefore no longer a day-to-day development blocker; #2 and #3 remain the API/network prerequisites.

[woksin]

The temporary contracts dependency is now merged on main via #17. A standard development setup:

python -m pip install -e ".[dev]"

installs the SHA-256-pinned cratis-chronicle-contracts==16.38.2 release wheel automatically. CI verified this on Python 3.10, 3.11, 3.12, 3.13, and 3.14.

Generated-contract availability is no longer a development blocker. Contributors can proceed with #2, then #3, and use those boundaries for this end-to-end milestone while #15/#16 continue tracking the eventual move from the GitHub release asset to PyPI.

[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.