Mirror the repo-doi/workstream-dod Observable policy pages for service-dom:
read/edit view backed by GET/PUT /policy/service-dom. Add it to the Policies
nav section and the State Hub reference doc. Builds clean (62 pages).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Establish policies/service-dom.md as the service-level companion to the repo
DoI and workstream DoD. Its load-bearing Core criterion is a cheap, side-effect
free health endpoint for availability probing — satisfied by the existing
GET /state/health (DB readiness, 200/503). Served automatically at
/policy/service-dom by the existing policy router.
Add a regression test asserting /state/health returns 200 with the expected
shape, since none existed (DoM Standard criterion #4).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Proposed plan (status: proposed) for a Suggestion entity with a persisted
relevance/demand counter feeding a WSJF read-model projection. Authored during
ops-warden WP-0012 triage; tracks gated needs as relevance-accruing suggestions
rather than inert todo tasks.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Introduce credential-routing.template for Codex, Claude Code, Grok, and
llm-connect agents. Wire into agents-codex.template and claude-md.template.
Add propagate_credential_routing.py for surgical rollout without clobbering
repo-specific AGENTS.md extensions (REPO-AGENTS-EXTENSIONS marker).
Add no-op Alembic merge migration to unify the two divergent heads
(a4v5w6x7y8z9, a4v5w6x7y8z0) into a single revision.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Marks CUST-WP-0003 finished with implementation evidence after verifying the dashboard WHI card, docs, and reference navigation are already present and the hub tasks are done.
Adds preferred workplan REST/event surfaces, legacy-meter telemetry and weekly review summaries, documentation/dashboard terminology updates, dashboard API loading fixes, and close-out sync for STATE-WP-0052 and STATE-WP-0054.
Workstream 0cca23a9-9640-491a-92db-6414db891019 (slug state-wp-0053)
created with status: proposed. Six tasks T01-T06 created and their
ids backfilled into the workplan file's task frontmatter so the
consistency checker links file ↔ DB correctly.
Coordination message sent to codex (state hub message
9d4fe78d-c3c4-4a98-a430-88f9757a0c79) requesting review of scope,
owner confirmation, and a decision on whether to promote from
proposed to ready/active.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Following the CUST-WP-0045 daily-triage cutover, the activity-core
runner now writes a daily progress event with the full WSJF report
nested under detail.report. The only ways to read it today are tail
the working-memory file or curl /progress/ — neither serves the
"sit-down review" use case the triage was designed for.
Proposed dashboard page under the existing Workstreams section:
recent reports table, per-report detail with linked recommendations,
14-day pattern view, action colour cues consistent with the rest of
the dashboard. Read-only; no schema or API changes; reuses the
existing /progress/?event_type=daily_triage endpoint.
Six tasks (T01 skeleton + nav, T02 recent table, T03 detail with
links, T04 colour cues, T05 pattern view, T06 docs). Status:
proposed — awaiting review before workstream registration.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
