Repository navigation
Open
Labels
app/pm-stackpm-stack (Pad/Grist) in developing-today/codepm-stack (Pad/Grist) in developing-today/codeeffort/mMedium: expected under 1 day of workMedium: expected under 1 day of workkind/docsDocumentation improvement or additionDocumentation improvement or additionmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels addedpriority/normalOrdinary priority (the default)Ordinary priority (the default)queue/blockedQueue or user escalation stateQueue or user escalation statequeue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queuesource/humanFiled directly by a humanFiled directly by a humanstatus/blockedQueue or user escalation stateQueue or user escalation statetask/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item
Description
Part of epic #1184 (PM stack coherence review, 2026-10-26).
The PM stack is absent from ROADMAP.md and planning/roadmaps/. Evidence: ROADMAP.md's projects table has exactly 5 projects with 5 roadmap files, none of them the PM stack, and 'PM stack' appears nowhere in planning/. The Grist roadmap is a second, drifting roadmap of record whose PM rows already contradict GitHub issue states.
Acceptance:
- ROADMAP.md projects table lists the PM stack; planning/roadmaps/pm-stack.md exists with Now/Next/Later rows all linked to issues (Now = epic epic(dashboard): PM stack coherence - single-URL, fresh data, triage-able, hierarchical #1184, pm(kaneo): install the developing.today GitHub App on dezren39/nix and connect it (org repos done 2026-10-25) #1007, impl(fleet): work-picking jobs consult the orchestrator published priorities before choosing work #911).
- planning/README.md project table is updated.
- No PM roadmap statement remains that contradicts a GitHub issue state; contradicting Grist-only PM rows are retired or marked as a mirror.
Acceptance criteria
- ROADMAP.md's projects table lists the PM stack; planning/roadmaps/pm-stack.md exists with Now/Next/Later rows all linked to issues (Now = epic epic(dashboard): PM stack coherence - single-URL, fresh data, triage-able, hierarchical #1184, pm(kaneo): install the developing.today GitHub App on dezren39/nix and connect it (org repos done 2026-10-25) #1007, impl(fleet): work-picking jobs consult the orchestrator published priorities before choosing work #911).
- planning/README.md's project table is updated.
- No PM roadmap statement remains that contradicts a GitHub issue state; contradicting Grist-only PM rows are retired or marked as a mirror.
Metadata
Metadata
Assignees
Labels
app/pm-stackpm-stack (Pad/Grist) in developing-today/codepm-stack (Pad/Grist) in developing-today/codeeffort/mMedium: expected under 1 day of workMedium: expected under 1 day of workkind/docsDocumentation improvement or additionDocumentation improvement or additionmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels addedpriority/normalOrdinary priority (the default)Ordinary priority (the default)queue/blockedQueue or user escalation stateQueue or user escalation statequeue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queuesource/humanFiled directly by a humanFiled directly by a humanstatus/blockedQueue or user escalation stateQueue or user escalation statetask/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item
Activity
developing-today commentedon Oct 27, 2026
CODE-350
dezren39 commentedon Oct 28, 2026
Intake review
Fleet-monitor intake pass (protocol §5), 2026-10-28.
Still live: verified this run — the issue is open, and a merged-PR search found no PR that explicitly resolves it (no fixes-reference; the only real merged hit in the search set, PR #1318, does not mention it). It does not merely look solved.
Related: Related: epic #1184; Now-row anchors #1007, #911.
Notes / risks: Risk: a second roadmap of record is the failure mode — the Grist contradiction sweep in the acceptance is the important part, not the new file.
Suggested approach: Suggested approach: add the ROADMAP.md row + pm-stack.md from current issue states, then diff every PM statement against GitHub and retire/mark Grist-only rows.
Labels normalized this pass (see the issue's label set); acceptance criteria appended to the body as the standard
## Acceptance criteriasection, original body preserved verbatim above it.4 remaining items
dezren39 commentedon Nov 1, 2026
🤖 Agent note · triage complete
dezren39 commentedon Nov 1, 2026
🤖 Agent note · picked up (OpenChamber scheduled lane)
dezren39 commentedon Nov 1, 2026
🤖 Agent note · blocked (OpenChamber scheduled lane)
GRIST_API_KEYis unavailable in this lane and the documented tailnet document redirects to/booton a normal unauthenticated request. The checked-in seed is not evidence of live rows.queue/4933-1216-pm-stack-roadmapat/home/user/git/fleet/4933-1216-pm-stack-roadmap; no edits made.developing-today commentedon Nov 3, 2026
agent-note:v1
state: reviewed (coverage loop-back)
Coverage pass 2026-11-03, loop-back review: this issue was re-reviewed (drift / overlap / already-handled / stale / blockers / ordering) so every open issue in the four repos is reviewed and in the system. Verdict: still live; in the system as task 4933 (small_fix, blocked, priority 50) in repo-health-code-pilot. Labels audited and synced. If it is already handled at current main, its triage closes it with evidence; if oversized, the triage files the split; blockers belong on this issue.
Found via: coverage loop-back 2026-11-03