Skip to content

Release v0.8.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 06 Sep 22:42
v0.8.0
98c5e4a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Summary

Four Chronicle client profiles ship real content instead of a gap summary. This is the standalone client experience — using a Chronicle client SDK to talk to a Chronicle server from a language-native application — which is a different subject from the existing Chronicle corpus, and each skill is written from its own client's source rather than translated from the .NET one.

Added

  • cratis-chronicle-client-dotnet — connecting a standalone console, worker, or service without a host, assembly-scanning discovery, the registration wait, and the compatibility check Connect() now performs automatically. Verified against the Chronicle sources at tag v17.0.1. (#178)
  • cratis-chronicle-client-typescript — reflect-metadata and decorator setup, connection strings, @eventType(), eventLog.append, and the two conventions that decide whether a Node application works at all: handlers dispatch by camelCase method name, and artifact discovery is a runtime file glob that matches **/*.ts. Verified against Chronicle.TypeScript v4.0.0. (#178)
  • cratis-chronicle-client-kotlin — Gradle coordinates, the Spring Boot starter and its cratis.chronicle properties, @EventType classes, suspending append, ClassGraph discovery, and the blocking surface Java starts at. Verified against Chronicle.Kotlin v4.0.0. (#178)
  • cratis-chronicle-client-elixir — putting Chronicle.Client in a supervision tree, use Chronicle.Events.EventType, Chronicle.append/3 and its error tuples, reactors with @handles, model-bound read models, and waiting for the :registered lifecycle phase. Verified against Chronicle.Elixir v2.2.0, the version actually published on Hex. (#178)

Changed

  • public-chronicle-client-dotnet, -typescript, -kotlin, and -elixir move from content-gap to preview-source-candidate and now list a target. No profile composes another, so no .NET-specific Chronicle content reaches a Kotlin, TypeScript, or Elixir subscriber. (#178)
  • The product coverage catalog records what was verified: the four Chronicle client capabilities move to candidate against their named versions, and Kotlin and Elixir become current-corpus languages. (#178)
  • public-chronicle-client-java and public-chronicle-client-python are unchanged. No Chronicle Java client repository exists — the JVM client is Chronicle.Kotlin, whose Java surface the Kotlin skill covers — and Chronicle.Python carries package scaffolding with no implementation and no published package. Their notes now state the verified reason each stays a gap. (#178)

Every framework claim in these four skills cites the file and line it was verified against, in released source rather than a working checkout — three of the four local checkouts were behind their published release, one by a major version, so the released tags were fetched and read directly.

All four targets are excluded from public evaluation with effect-assessment-required, and none is added to the approved set. Capability kind, trust assessment, and source contract state stay unclassified, because classifying them is an owner decision rather than an authoring one.

🤖 Generated with Claude Code

https://claude.ai/code/session_016mnTtTtUVTZSPoVFS5yCz6

Assets 2
Loading