sdk

ci → green (TypeScript, Rust, Go, and Python offline suites)

Go and Python now emit the real five-span Frauthy lifecycle from can and lookupResources, with deterministic mock-exporter coverage and a live Go network-export test. SDK-1 remains open because this wave did not complete equivalent Rust session wiring.

cloud

ci → green (208 tests; 30 intentionally gated skips; TypeScript check clean)

Cloud preserves OTLP service.name through parsing, DuckDB, ClickHouse, and the trace summary API, including migrations for existing stores.

devops

ci → green (10/10 conformance cells plus SpiceDB and Keto end-to-end smoke suites)

coverage → 62.97% measured locally for DevOps (682/1083 lines; 55% floor passed)

Closed: DEVOPS-11

The conformance matrix uses canonical 41xxx ports and isolated Rust stateful cells. Both authorization backends completed all ten end-to-end assertions. DEVOPS-7 remains open because the reusable cross-repository coverage workflow still lacks real artifact aggregation and enforcement.

sandbox

ci → green (9/9 conformance and 141/141 live integration assertions across mixed-default, all-SpiceDB, and all-Keto cells)

Per-service OTLP evidence is enforced for Amalga, Quill, and Lens. The harness now owns the Quill binary lifecycle directly, eliminating a stale go-run child that could make health checks target an obsolete process.

research

This v6 ledger update records only evidence-backed Wave 3 closure and verification. Federation-owned Research UI files were not changed.

Program-wide

Wave 3 followed root/specs/08-CONCURRENT-PROGRAM-HANDOFF.md. Brand, Site, product packages/ui, Cloud/Market web migration, Admin editor composition, DevOps Portal, Research UI, and Sandbox UI were intentionally untouched.

GitHub Packages publication remains blocked on a registry-compatible PAT in the concurrent federation session; no package publication is claimed here.