Skip to content

Release v0.5.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 06 Sep 21:34
v0.5.0
72e7156
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Thirteen Chronicle and CLI skills now ship as canonical content. Ten were migrated from the legacy corpus and re-verified against Chronicle 16.45.2 and Cratis CLI 2.4.0 source; three were authored for journeys the corpus did not cover at all. Verification changed the guidance in several places, so the migrated skills are corrections rather than copies.

Added

  • Chronicle read model, projection, reducer, and reactor skills, on public-chronicle (#177)
  • Chronicle event modeling, event model diagram, and event type migration skills, on public-chronicle (#177)
  • A Chronicle namespace multi-tenancy skill, on public-chronicle-multi-tenancy (#177)
  • A cratis CLI operations skill covering contexts, connection resolution, machine-readable output, and the authorization discipline for replay, retry, and quarantine clearing, on public-cratis-cli (#177)
  • A Chronicle compliance skill covering [PII], [ComplianceDetails], compliance subjects, IPIIManager erasure and what crypto-shredding does to reads and writes, event redaction and revision, and IReadModels.Release, on public-chronicle-compliance (#177)
  • A browser Workbench skill covering screens, mutating operations, and the facts that decide whether to expose it, on public-chronicle-web-workbench (#177)
  • A terminal Workbench skill covering views, key bindings, the command palette, and its mutating actions, on public-cratis-cli-terminal-workbench (#177)
  • A Chronicle kernel tracing skill for contributors, on engineering-chronicle (#177)

Changed

  • public-chronicle, public-chronicle-compliance, public-chronicle-multi-tenancy, public-chronicle-web-workbench, public-cratis-cli, public-cratis-cli-terminal-workbench, and engineering-chronicle move to preview-source-candidate and list their targets, so selecting one now installs content rather than reporting a gap (#177)

Fixed

  • Reducer guidance no longer shows a non-nullable current-state parameter; that shape now throws at registration rather than being skipped (#177)
  • Reactor guidance no longer references ReactorSideEffect, which does not exist in Chronicle; EventForEventSourceId is the real per-event metadata carrier, and its reactor support shipped long ago rather than being upcoming (#177)
  • [OnceOnly] is documented as replay exclusion rather than per-event-source deduplication, so side effects are still required to be idempotent (#177)
  • Reactor guidance no longer states a two-parameter limit, and [Reactor] is documented without the isActive argument it does not have (#177)
  • Read model guidance attributes [ReadModel], [Path], and the Observe extensions to Arc rather than Chronicle, requires ISubject<...> rather than a concrete subject type on query methods, and points single-document reads at ObserveSingle and ObserveById (#177)
  • Projection guidance drops the removed [FromEventSequence] attribute, puts UsingKey and its siblings on the per-event builder where they live, and writes ConstantKey as the property initializer it is (#177)
  • Multi-tenancy guidance names IEventStoreNamespaceResolver as the real contract, states that registration selects a single resolver rather than a priority chain, and stops asserting an automatic TenantNamespaceResolver that is not a Chronicle type (#177)
  • Compliance guidance records rationale with [ComplianceDetails], because a string passed to [PII] is never read, and documents no [NotAudited] attribute, which Chronicle does not have (#177)

Security

  • The browser Workbench skill records that its application bundle is served anonymously by design, that disabling the API silently disables the Workbench, that the UI applies no personal-data masking, and which mutating operations have no confirmation dialog (#177)
  • The CLI skill records that confirmation prompts are skipped whenever stdout is not a terminal, so destructive commands auto-confirm in pipelines and agent harnesses, and that several mutating commands never prompt at all (#177)
  • All three newly authored targets are excluded from public evaluation pending an effect assessment; none is added to the approved set (#177)

🤖 Generated with Claude Code

https://claude.ai/code/session_016mnTtTtUVTZSPoVFS5yCz6

Assets 2
Loading