Release v0.7.0

Summary

Adds the first real corpus content for Lens, Screenplay and Stage. All three were previously empty content gaps — nothing existed for them anywhere in .ai/skills, skills/ or engineering/, so every skill here is authored against the products' own source rather than migrated. Studio gains nothing: its repository is private, so the existing classification-only MCP safety guidance remains the only thing that can responsibly be documented.

All three products are early-stage, and the skills say so. Each one leads with the boundary a reader will otherwise walk into.

Added

• cratis-lens-browser-extension — building and side-loading the extension, the /.cratis/* routes and forwarded-identity headers an Arc application must already serve, what an identity or tenant switch actually does, and the shape of the command and query requests the popup sends (#179)
• cratis-screenplay-model-authoring — the .play file shape, the constructs the compiler accepts, the screenplay dotnet tool, and the boundary between what parses and what the executable semantic model admits (#179)
• cratis-stage-rendering-and-sandbox — the CratisRendering facade, the STAGE-ESM admission rules, the generated artifact roster, and the cratis/stage and cratis/stage-specrunner containers (#179)
• public-lens, public-screenplay and public-stage now ship content instead of a gap summary; public-modeling-screenplay-stage composes the two modeling profiles (#179)

Changed

• Lens guidance records that no store listing exists anywhere in its repository — building from source and loading unpacked is the only install path (#179)
• Lens guidance records that its command payload form receives no schema today: it reads an introspection property named schema while Arc emits payloadSchema/argumentsSchema, and its four fallback schema routes are not mapped by Arc, so every command form falls through to the empty state with no raw-JSON editor behind it (#179)
• Lens guidance records that the tenant header name, base URL and page origin have no user interface, so an application resolving tenancy any other way cannot be driven by it, and that header rules match XMLHTTPREQUEST only — the observable-query WebSocket and SSE transports carry no injected headers (#179)
• Screenplay guidance records that the screenplay tool only verifies and never writes, that an unknown construct inside a slice is a warning that silently drops its block, and that the executable semantic model admits only StateChange and StateView, so Automation and Translate slices parse and bind to nothing (#179)
• Stage guidance records that there is no rendering CLI, that the renderer needs an executable semantic model Stage ships no way to produce from .play files, that an unsupported construct blocks the whole plan rather than emitting less, that the sandbox enforces neither modeled validation nor authorization and its modeled queries deny by default, and that nothing in Stage reviews, diffs, stages or approves anything (#179)

Security

• All three targets are excluded from public evaluation with effect-assessment-required; none is added to the approved set. Catalog classification stays unclassified pending owner review (#179)