PM stack docs: one live-vs-fixture-vs-absent matrix, generated from provenance

Part of epic #1184 (PM stack coherence review, 2026-10-26).

The docs contradict each other about what is live vs fixture. Evidence: aggregator/README.md claims comments read live and nothing is fixture-backed when the stack is up, while program.ts gaps/next and live.ts say GitHub comment projection is fixture-backed and the projector is dead by config, and the top-level README Phase-2 table presents all layers as running.

Acceptance:

README, aggregator README, and /program agree facet-by-facet.
One capability matrix (per facet: live source, fallback, deployed?) names the projector and Pad honestly.
A doc check or generation step from config/provenance is documented so the matrix cannot silently re-diverge.

Acceptance criteria

README, aggregator README, and /program agree facet-by-facet on what is live, fixture-backed, or absent.
One capability matrix (per facet: live source, fallback, deployed?) names the comment projector and Pad honestly.
A doc check or generation step from config/provenance is documented so the matrix cannot silently re-diverge.

CODE-334

Intake review — fleet monitor

Liveness: Verified still live at intake (2026-10-28): issue is open and unheld, and a merged-PR search for #1200 returned only unrelated text matches (no PR title or fix reference resolves this item). Part of epic #1184 (PM stack coherence review, 2026-10-26); sibling batch #1210–#1222 was enriched in the previous monitor run.

Notes: Docs-only, but it is the item that keeps the rest of the epic honest: the matrix generated from provenance prevents the two READMEs and /program from re-diverging silently.

Risks: Scope creep across the pm-stack pages is the main risk for this batch; the acceptance criteria above (converted from the issue's original Acceptance list) bound the work. CI on the aggregator's render/derive tests is the verification surface.

Suggested approach: Take the acceptance criteria in order; keep the JSON twins in lockstep with the HTML pages, per the batch convention.

Labels normalised this pass: source/human (coherence-review filer), effort/m, meta/enriched; existing kind/priority/status/app labels kept.

Picked up triage in queue task 2475; checking current main and ownership.

Done (documentation half): PR #4172 merged (merge commit 63aed02); task 4902 completed as fixed_merged. The remaining half — verifying the matrix's deployment column against OBSERVED runtime state (the packet evidence recorded 'runtime not verified') — is enqueued as follow-up task 6104. #1200 stays open until task 6104 lands.

agent-note:v1
event: picked-up
task: 6104 (repo-health-code-pilot, OpenChamber scheduled lane)
state: claimed
verified: Fresh checks at 2026-11-02: #1200 is OPEN; PR #4172 is MERGED (63aed02), and its completion note explicitly queued task 6104 for the observed-runtime remainder. Search found no matching open implementation PR; #3960 is unrelated. No hard-stop labels.
next: inspect current main and identify authoritative pm-stack runtime status surfaces; record observations on #1200.

Runtime verification — queue task 6104 (2026-11-02):

At 06:04:56.726Z the aggregator /api/health reported Pad up (HTTP 200), projector down (1.5 s probe timeout), and Comments fixtures.
At 06:07:46.665Z the aggregator recheck reported Pad and projector up (HTTP 200), Comments live (projector), and degraded=false.
Direct checks: pm-pad was running/healthy and /api/v1/health returned ok, v0.18.1; projector /health returned ok with 8,189 items and 41,961 comments; a direct projector /comments read returned a projected issue comment. Both systemd units were active/running.
This supersedes task 4902’s earlier same-day success read (8,134 items, 41,169 comments). The brief timeout was not the final state. The matrix’s Pad deployment cell also said Compose, but current config declares the pm-pad NixOS OCI container in services.pm-apps.
The docs update is on the task branch. Matrix consistency check passes 15/15; targeted program/render tests pass 40/40; git diff --check passes.

agent-note:v1
event: done
task: 6104 (repo-health-code-pilot, OpenChamber scheduled lane)
state: pr_opened
result: PR #4221 opened with the observed-runtime and Pad deployment-cell corrections. Fresh GitHub check confirms the PR is OPEN against main; its CI test is QUEUED. Issue #1200 remains open pending the PR.
verification: matrix check 15/15; targeted program/render tests 40/40; direct runtime observations and transient recovery are recorded in the PR and matrix. Full-suite pre-merge-base failures are noted in the PR.
bookkeeping: sandbox backlog and sweep log deferred to fleet reconciliation.

Merge pull request #4221 from developing-today/queue/6104-1200-observ…

Navigation Menu

Repository navigation

PM stack docs: one live-vs-fixture-vs-absent matrix, generated from provenance #1200

Acceptance criteria

Intake review — fleet monitor

112 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

PM stack docs: one live-vs-fixture-vs-absent matrix, generated from provenance #1200

Description

Acceptance criteria

Activity

developing-today commented on Oct 27, 2026

dezren39 commented on Oct 28, 2026

Intake review — fleet monitor

dezren39 commented on Nov 1, 2026

112 remaining items

dezren39 commented on Nov 2, 2026

dezren39 commented on Nov 2, 2026

dezren39 commented on Nov 2, 2026

dezren39 commented on Nov 2, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions