Release v7.7.0

Summary

Event modeling on Cratis projects is now model-first. Once a repository has opted in, agents work in the Screenplay .play model, through the Screenplay MCP server and Stage rendering. They write code only for infrastructure, clients, adapters, Screenplay code attachments, and anything Stage cannot render yet. A repository opts in by committing a model under its model root, or by setting a model root explicitly. Otherwise agents stay code-first and offer a model once, and the code-level skills stay as they are.

Added

• Ten Screenplay method skills, which you install with the cratis/screenplay profile:

  • cratis-screenplay-modeling-lifecycle: phases, gates, verdicts and the model-first decision.
  • cratis-screenplay-toolchain: versions, tools and diagnostics.
  • cratis-screenplay-discovery
  • cratis-screenplay-slice-design
  • cratis-screenplay-streams-and-consistency
  • cratis-screenplay-automations-and-translations
  • cratis-screenplay-scenario-coverage
  • cratis-screenplay-model-review
  • cratis-screenplay-legacy-extraction
  • cratis-screenplay-render-and-gap-fill

  The skills adapt event modeling practice: workshop and interview guidance, scenario and review checklists, and gates between phases.

• cratis-application-slice-conformance checks hand-written or gap-filled slice code against its contract, element by element and spec by spec. It installs with cratis/specifications/dotnet.

• Three agents for model-level work: Screenplay Modeler, Screenplay Reviewer (read-only) and Screenplay Renderer. They use your session's model.

• cratis-arc-react-page maps Screenplay screens, forms and queries to Arc React pages, and traces every field on screen to its source.

Changed

• cratis-screenplay-event-modeling is now the entry point. It holds the model-first decision and routes to the method skills. (#493)
• The language skills now state, at Screenplay 4.64.0, which compiler admits reactions, clocks and captures, and what binds and what renders. The MCP guidance covers identity-preserving edits, the source-map view and the whenAppendedEvent label. (#434)
• cratis-stage-rendering-and-sandbox describes cratis render on Stage 4.24.
• Contract-first agents:
  • The planner, coordinator, orchestrator and code reviewer choose the model level when a repository has opted in.
  • The slice implementer, backend developer, spec writer and frontend developer start from the contract.
  • The spec writer seeds prior state with _scenario.Given. (#492)
• The rules, prompts and code-level skills find the contract first, and route model-level work back to Screenplay when a model covers it.
• The specification skills take their list of specs from the contract and cover read-model lifecycles, and the reactor skill covers repeated delivery.

Fixed

• Translation has one meaning across rules, skills and prompts: outside data becomes your own facts. (#490)
• The Screenplay skills no longer say that reactions, clocks and captures never bind, and the overdue-invoice example now uses a clock trigger. (#491)