McRitchie Studio

Agent Context

Observability epic A3 — the final slice. Extend the A1/A2 test-scope telemetry beyond the release conductor to LOCAL certs and CI. A1 shipped run_test_scope in bin/release.rb emitting kind=test_scope AgentActions via bin/agent-activity action (self-report to the open span); A2 (just shipped) tags event_slug/result_slug/duration_ms and surfaces a gradeable Test-runs band in /alex/pipeline. Now: (1) LOCAL full-suite-check — bin/full-suite-check runs test-db-reset / bin/rails test / rubocop lanes (see feature_shapes + the file). Wrap each lane's run so it self-reports a kind=test_scope AgentAction (event_slug=<lane key>, result_slug=pass|fail, duration_ms) via the SAME bin/agent-activity action verb, gated on an open activity/span, best-effort/non-fatal/inert when no span (mirror run_test_scope's guards exactly — telemetry must NEVER break a cert). Register the full-suite lanes as scopes in config/devops_test_suites.yml with stable keys (phase: build, tier: full/unit/build, host: local). This makes local cert runs gradeable like release runs — the clean, cohesive win. (2) CI — assess feasibility: GitHub Actions (.github/workflows/ci.yml) runs off-box and can't touch the local activity bus; emitting would mean POSTing a test_scope event to the board API at job start/end. JUDGMENT CALL: if this is a clean board-API POST that needs NO new CI secrets and has a sensible attribution (e.g. tied to the PR/branch), implement it; if it needs new CI secrets, a new API attribution path, or non-trivial infra decisions, DO NOT half-build it overnight — scope it as a documented follow-up task/comment instead and ship the solid full-suite-check half. Prefer a solid partial over a risky full. NO changes to bin/release.rb's run_test_scope (A1/A2 own it) beyond reusing shared helpers if cleanly extractable. Shape backend; unit + integration tiers.