Skip to content

Expose screenplay baseline admit and check #351

Closed

Description

@woksin

Screenplay decision 0070 (Cratis/Screenplay#686) adds a committed release baseline, .screenplay/release-baseline.json (published schema Documentation/screenplay/release-baseline-v1.schema.json), written only by screenplay baseline admit and checked by screenplay baseline check (exit 1 on a changed/missing baselined event revision, 2 when unreadable).

Per decision 0070, the Cratis CLI baseline check is the CI gate for edits made outside MCP, and baseline admit is the deliberate release step. Expose both through cratis screenplay (bundled tool) with the same exit codes, and document running admit in a release job.

Status

State: Done — Released in v3.60.0 (PR #357).
Branch: cli-esm-v16 (#357)
Scope: cratis screenplay baseline admit|check delegating to a public Screenplay entry point.
Delivered: Nothing yet.
Remaining: To be confirmed.
Follow-ups: None.

Activity

  1. self-assigned this
    on Oct 13, 2026
  2. woksin commented on Oct 13, 2026

    @woksin
    CollaboratorAuthor

    Blocked on Cratis/Screenplay#720: Screenplay 4.153.0 ships screenplay baseline admit|check, but the state loading, recovery-journal refusal and atomic sidecar write it uses are internal to Cratis.Screenplay.Mcp. The CLI will delegate to a public root-aware entry point rather than re-implement that path.

  3. github-actions commented on Oct 13, 2026

    @github-actions
    Contributor

    Closed by release v3.60.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions