Repository navigation
PM stack: define one status taxonomy and show source-vs-derived disagreement everywhere #1198
Description
Part of epic #1184 (PM stack coherence review, 2026-10-26).
Four pages use four status vocabularies: Kaneo statuses, Grist free-Choice statuses, Project Status plus derived state, and orchestration statuses. Only /projects shows both sides of a disagreement; Board/Roadmap/Today silently pick one source. Evidence: projects.ts derivedProjectState has no derived 'In Review', so every In Review item disagrees by construction.
Acceptance:
- A canonical status set plus per-source mapping table exists in code and is rendered on /pages or /program.
- An item's canonical status is identical across pages for the same inputs (test).
- In Review no longer disagrees by construction; the derived-state model covers it.
Acceptance criteria
- A canonical status set plus a per-source mapping table exists in code and is rendered on /pages or /program.
- An item's canonical status is identical across pages for the same inputs (covered by a test).
- In Review no longer disagrees by construction; the derived-state model covers it.
- Board/Roadmap/Today show source-vs-derived disagreement instead of silently picking one source.
Metadata
Metadata
Assignees
Labels
pm-stack (Pad/Grist) in developing-today/codeMedium: expected under 1 day of workNew feature or capability requestIntake review done: acceptance criteria, links, and normalized labels addedImportant and time-sensitiveQueue or user escalation stateFiled directly by a humanQueue or user escalation stateQueue packet kind: verify, reproduce, and route this itemQueue or user escalation state
Activity
developing-today commentedon Oct 27, 2026
CODE-332
dezren39 commentedon Oct 28, 2026
Intake review
Related: Part of epic #1184 (PM stack coherence). Sibling intake batch this run: #1197, #1196, #1195.
Notes / risks: Four vocabularies plus a derived model — the mapping table is the deliverable; page changes without it will re-diverge.
Suggested approach: Start in projects.ts derivedProjectState (named in the body) and add the cross-page identity test first.
Live check: verified still open and unheld this run; a merged-PR search on this run (2026-10-28T10:35:00Z) returned no PR resolving this issue, so it remains live work. Acceptance criteria appended to the body (original text preserved verbatim above it) and labels normalized by the fleet monitor.
30 remaining items
dezren39 commentedon Nov 4, 2026
agent-note:v1
event: handed-off
task: 7217 (triage, repo-health-code-pilot; worker repo-worker-code; lane code-t)
by: repo-queue-worker lane T
Handed off to the opencode claimant (execution lane: opencode, lane-assignment row 1645). The claimant launches the bound session that drives task 7217 to its terminal state. Preserved context: a prior park recorded that the follow-up packet write was canceled and no queue follow-up exists yet; triage findings are on this issue (comment 661785... series).
dezren39 commentedon Nov 4, 2026
🤖 Agent note · handed off
opencode. Triage findings are already posted on issue PM stack: define one status taxonomy and show source-vs-derived disagreement everywhere #1198 (comment 6617858177); the remaining step is the follow-up packet enqueue (a previous local packet write was canceled, so no queue follow-up exists yet). Revalidated fresh this claim (2026-11-04T06:14Z): issue PM stack: define one status taxonomy and show source-vs-derived disagreement everywhere #1198 OPEN, no held / user/owned / do-not-merge / do-not-auto-edit labels; claim labels synced this note (removed queue/queued + status/needs-triage; added work/assigned, queue/claimed, status/in-progress).dezren39 commentedon Nov 4, 2026
agent-note:v1
state: picked up
task: 7217
worker: repo-worker-code
lane: 8ac61616-3815-4e7b-b33d-840a3829154a
Fresh claim at 2026-11-04: issue is OPEN; claim labels are synced and no hard-stop labels are present. Resuming the prior triage findings from comment 6617858177; verifying current main and the missing follow-up task before terminal completion.
dezren39 commentedon Nov 4, 2026
agent-note:v1
state: blocked
task: 7217
worker: repo-worker-code
lane: 8ac61616-3815-4e7b-b33d-840a3829154a
Triage revalidated against origin/main 8331a77c038ce2e59b8eec898cb81416f7728b72: #1198 remains OPEN. No matching open PR exists; the merged #1206 canonical work-item projection is distinct. Partial disagreement handling exists in the Project/per-item views, but the shared status contract remains incomplete: BoardStatus is open-ended and RoadmapRow.status is string (aggregator/src/model.ts:147,175-183); DerivedProjectState omits In Review (src/projects.ts:306-318); Today projects board/roadmap statuses without carrying source disagreement (src/derive.ts:756-798); work-items.ts canonicalizes orchestration work only.
Verdict: keep #1198 open; implementation follow-up is needed for its four acceptance bullets (canonical taxonomy/mapping, cross-page parity test, In Review, and Board/Roadmap/Today disagreement). No code edits or tests were performed.
Blocker: the file-write request for the scoped follow-up packet was explicitly canceled, so no follow-up was enqueued. I blocked task 7217 as escalated-to-user; do not bypass via another write path. Resume after explicit approval or an approved packet submission path.
Branch/worktree: queue/7217-1198-triage-status-taxonomy at /home/user/git/fleet/7217 (based on origin/main); primary ~/git/code main was left unchanged because it is 1 ahead / 75 behind and has unrelated untracked files.