Repository navigation
Aggregator: wire Pad as a real source (notes on items) or remove the planning-notes feature #1202
Description
Part of epic #1184 (PM stack coherence review, 2026-10-26).
Pad is not integrated: planning notes exist only in fixtures. Evidence: source.ts has no Pad facet and live.ts never sets BoardItem.notes; the only notes are fixtures.ts:135 pointing at http://127.0.0.1:7777/. A deployed layer (Pad 7777) contributes nothing while item pages reserve an empty 'Planning notes' section in production.
Acceptance:
- A live item with a Pad plan shows it with a reachable (non-loopback) URL, or the section is deleted and Pad is recorded as standalone in the docs.
- Pad outage degrades per the degraded-facet rules.
- /health includes Pad.
Acceptance criteria
- A live item with a Pad plan shows it with a reachable (non-loopback) URL — or the 'Planning notes' section is deleted and Pad is recorded as standalone in the docs.
- A Pad outage degrades per the degraded-facet rules.
- /health includes the Pad facet.
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 addedOrdinary priority (the default)Filed directly by a humanQueue packet kind: verify, reproduce, and route this item
Activity
developing-today commentedon Oct 27, 2026
CODE-336
dezren39 commentedon Oct 28, 2026
Intake review — fleet monitor
Liveness: Verified still live at intake (2026-10-28): issue is open and unheld, and a merged-PR search for
#1202returned 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: Deliberately either/or: wiring Pad in or removing the dead section are both acceptable outcomes; leaving the fixture-only section in production is not. /health inclusion applies on the wire-in path.
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.17 remaining items
dezren39 commentedon Nov 3, 2026
agent-note:v1
state: triaged (coverage pass)
Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 40 (priority/normal). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
Found via: coverage pass 2026-11-03
dezren39 commentedon Nov 3, 2026
agent-note:v1
task: 7654
state: picked_up
lane: code-e (direct)
summary: Triage of #1202 (wire Pad as a real aggregator source or remove the planning-notes feature) started by queue task 7654. Verifying the packet's evidence claims against current main before posting the verdict.
dezren39 commentedon Nov 3, 2026
agent-note:v1
task: 7654
state: triaged — already handled, closing
lane: code-e (direct)
verdict: The removal branch of this either/or issue was implemented and merged in PR #3946 (queue task 4906); this issue stayed open only because that PR carried no closing keyword. Closing with evidence.
Evidence (current main d4d7834, 2026-11-03; PR #3946 MERGED 2026-11-02T15:46:40Z, commit 05d90f1 verified an ancestor of origin/main):
If Drew later wants Pad wired in as a real source after all, that is a new feature issue — this one is resolved by the removal it offered as the alternative.