pm-stack: make Project #4 auditable — scheduled export of fields, views, item counts, status/area distribution

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

Project #4 is unauditable with normal tooling. Evidence: the sandbox gh token lacks read:project scope, so Project fields/views/counts cannot be enumerated directly, and there is no committed export or snapshot. The only machine-readable copy rides inside the fleet feed via a siloed collector token, and that pipeline has already failed silently once (PR #992: projects section omitted under the systemd unit).

Acceptance:

An auditor with only repo access can state Project Bump build/buck/preludes/buck2-prelude from 3a02ea3 to 9530656 #4's fields, views, total items and counts by Status/Area/repo from an artifact <=24h old.
An empty or absent projects section raises a visible signal (empty-section alarm) instead of silently omitting.
The export is scheduled/recurring, not a one-off snapshot.

Acceptance criteria

An auditor with only repo access can state Project Bump build/buck/preludes/buck2-prelude from 3a02ea3 to 9530656 #4's fields, views, total items, and counts by Status/Area/repo from an artifact ≤24h old.
An empty or absent projects section raises a visible signal (empty-section alarm) instead of silently omitting.
The export is scheduled/recurring, not a one-off snapshot.

CODE-352

Intake review

Related: epic #1184; PR #992 is the cited silent-failure precedent (projects section omitted under the systemd unit). Siblings #1220 (coverage report) and #1226 (Needs-Drew queue) both consume this export.
Notes: the sandbox gh token lacks read:project scope (per the body), so the export must ride the collector-token pipeline that already feeds the fleet feed — the alarm half is as important as the export half. No merged PR references this issue (checked this run).
Risks: another silent omission is the exact failure being fixed; land the empty-section alarm with or before the export.
Suggested approach: add the scheduled export beside the existing projects collector, plus a section-presence check in the aggregator that surfaces loudly.

🤖 Agent note · filed

Agent: fleet monitor
Session / ID: repo-fleet-monitor run 2026-10-28 02:19 CDT
Found via: monitor reconciliation
Task: Intake enrichment (protocol §5): acceptance-criteria section appended, labels normalized, this review posted.
Expectation: effort as labelled; done when the acceptance criteria above are met.

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-f
Session / ID: task 7668
Found via: queue claim
Task: Handed off to the opencode execution lane (prior handoff lease expired unbound, where applicable); the laptop claimant launches the bound opencode session, which drives task 7668 to its terminal state.
Expectation: effort m; done = worked per the task packet at current main, verified terminal state.
Links: issue pm-stack: make Project #4 auditable — scheduled export of fields, views, item counts, status/area distribution #1218

🤖 Agent note · handed off

Agent: fleet monitor (repo-fleet-monitor)
Session / ID: task 7668
Found via: monitor reconciliation
Task: Claim-eviction repair: the queue task for this issue is queued and unclaimed (its previous claim's lease expired without a complete/park/block), but the issue labels still said claimed. Labels reset to the truth: queue/queued + status/needs-triage. Checkpoint stage on the task: handed_off.
Expectation: a queue lane re-claims the task and resumes from the checkpoint stage named in the task progress.

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-j
Session / ID: task 7668
Found via: queue claim
Task: Re-handed task 7668 (triage of issue pm-stack: make Project #4 auditable — scheduled export of fields, views, item counts, status/area distribution #1218) to the opencode execution lane; the laptop claimant launches the bound opencode session to triage issue pm-stack: make Project #4 auditable — scheduled export of fields, views, item counts, status/area distribution #1218 at current main. Flag: task 7668 is at attempt 9 of 12 after repeated handoffs — if the claimant does not launch, this task risks hitting its attempt cap unworked.
Expectation: claimant session posts a verified triage verdict on issue pm-stack: make Project #4 auditable — scheduled export of fields, views, item counts, status/area distribution #1218 and drives task 7668 to a terminal state.
Links: issue pm-stack: make Project #4 auditable — scheduled export of fields, views, item counts, status/area distribution #1218

Task 7668 was launched and bound to OpenCode session ses_e5e5c5cfca8ffe1s289CBDhmI5 by opencode-claimant. It is executing as repo-worker-code with the issue acceptance and current project-scope blocker in its prompt.

Fresh triage verdict — work remains (2026-11-03)

CONFIRMED live at current main 7a8500417188465deea72339db81fcf1a92c8448. GitHub still reports #1218 OPEN (last updated 2026-11-03T22:59:39Z). I did not close it.

Project-scope blocker verified, not assumed: gh project view 4 --owner developing-today --format json fails with missing required scopes [read:project]. I therefore cannot claim direct Project Bump build/buck/preludes/buck2-prelude from 3a02ea3 to 9530656 #4 enumeration or verify its actual current fields, views, or item counts.
Current main still lacks the requested audit: pm-stack/aggregator/src/projects.ts (PROJECT_QUERY, lines 24–52) reads title/number/url and items/fieldValues, but not Project field definitions or views. collect-fleet-feed.ts omits projects when the token is missing, the GraphQL read fails, or the result is empty; src/watchdog.ts has no Project-audit diagnosis for an absent/empty section. The recurring collector itself exists (fleet-feed-collector.timer, five-minute cadence, doc/fleet-schedule-registry.md:234), but that does not make the requested audit available today.
Existing scoped route: PR pm-stack: publish auditable Project #4 snapshot (#1218) #3995, opened from implementation task 4948, is still OPEN and unmerged (head a41fb76c4bb9952feaac447288005370eee062df; mergeable currently UNKNOWN). Its diff adds Project fields/views, total and Status/Area/repo distributions to the scheduled feed, plus absent/empty/stale watchdog diagnosis. No duplicate implementation packet was enqueued because this existing PR already covers the scoped fix.

Blocker and ordering: first refresh/reconcile and review PR #3995 against current main, resolve any required checks/review, then merge. After deployment, verify a repo-readable feed artifact generated within 24 hours contains fields, views, total items and Status/Area/repo counts, and that missing/empty projects data raises a visible alarm. Keep #1218 open until that evidence is observed; then close it.

Navigation Menu

Repository navigation

pm-stack: make Project #4 auditable — scheduled export of fields, views, item counts, status/area distribution #1218

Acceptance criteria

Intake review

25 remaining items

Fresh triage verdict — work remains (2026-11-03)

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

pm-stack: make Project #4 auditable — scheduled export of fields, views, item counts, status/area distribution #1218

Description

Acceptance criteria

Activity

developing-today commented on Oct 27, 2026

dezren39 commented on Oct 28, 2026

Intake review

25 remaining items

dezren39 commented on Nov 3, 2026

dezren39 commented on Nov 3, 2026

dezren39 commented on Nov 3, 2026

dezren39 commented on Nov 3, 2026

dezren39 commented on Nov 3, 2026

Fresh triage verdict — work remains (2026-11-03)

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions