protocol

ci → green (verified run 29380436925: strict Rust, seven-crate publication dry-run, CLI, canonical type contract, live SpiceDB/Keto/OIDC/Jaeger integration, and both mandatory coverage ratchets)

coverage → Rust 75.07% remote / 69.72% floor / 80% target; TS CLI 47.65% remote / 21.51% floor / 70% target (next CLI floor 23.51%)

Closed: PROTO-9

Commit e270ec5 completes Level 2 platform initialization with interactive prompts and deterministic flags for name, slug, provider, store, domain proof method, and visibility; it generates the authorization schema, compiler target, domain-registration helper, typed configuration, package metadata, and a versioned workspace platform registry.

Level 3 app initialization resolves a named platform from an ancestor or explicit registry, generates only app-owned configuration and auth integration, and enforces access with session.can against the registered platform resource. Missing and unknown platforms fail closed without creating partial projects.

DNS and well-known ownership proofs are wired through the generated domain helper and persisted by the domains command. An end-to-end generated Keto platform schema compiles outside the Protocol checkout after correcting compiler schema-path resolution to the invoking project directory.

Sixty-five CLI tests with 272 assertions cover defaults, custom flags, registry preservation and resolution, generated-project compilation, DNS proof persistence, minimal app ownership, and fail-closed behavior. All workspace targets, strict Clippy, formatting, canonical type-contract tests, seven-crate packaging, coverage gates, and live backend suites pass.

Program-wide

Wave 14 stayed within root/specs/08-CONCURRENT-PROGRAM-HANDOFF.md. Only Protocol CLI code, tests, documentation, its gap checklist, and this Research ledger event changed; no UI-owned surface, product packages/ui, Portal, registry publication, release tag, or concurrent UI branch was touched.