Repository navigation
ci: no pull_request workflow covers pm-stack/** — projector/aggregator changes merge with zero PR CI #2936
Description
Gap
No GitHub Actions workflow runs on pull_request for pm-stack/**. Verified 2026-10-31 on PR #2930 (queue task 1822, projector change): the only check runs on the head commit were CodeRabbit (neutral) and the two jules-daily-* push workflows that fail on every push including main. .github/workflows/ has path-scoped PR CI for pkgs/id (id-check) and pkgs/mcpx (mcpx, mcpx-docs), but nothing matches pm-stack/** — pm-scheduled.yml is the scheduled-agents runner, not test CI.
Effect: pm-stack changes (projector, aggregator) merge with zero PR CI; verification is whatever the author ran locally. PR #2930 was merged on laptop verification (bun test in pm-stack/projector, 43/43) under the standing merge criteria, with this gap noted.
Suggested fix
Add a small workflow (or extend an existing one) triggered on pull_request with paths: ["pm-stack/**"] that installs bun deps and runs the pm-stack test suites (at minimum pm-stack/projector: bun test). Keep it path-scoped so unrelated PRs don't pay for it.
Found by: queue worker Lane A shift, 2026-10-31, while resuming task 1822.
Acceptance criteria
- A
pull_requestworkflow triggers on changes underpm-stack/**and is path-scoped so unrelated PRs do not run it. - The workflow installs bun dependencies and runs the pm-stack test suites (at minimum
pm-stack/projector:bun test) and reports as a PR check. - Verified on a test PR touching
pm-stack/**(check runs) and one that does not (check does not run).
Activity
dezren39 commentedon Oct 31, 2026
Intake review
Related: PR #2930 (merged on laptop verification with this gap noted); existing path-scoped PR CI for
pkgs/idandpkgs/mcpxis the pattern to copy.Notes: verified live this run — no open PR or issue covers a pm-stack PR workflow (searched both). The gap is real: projector/aggregator changes currently merge with zero PR CI.
Risks: low. Keep the workflow path-scoped and bun-cache-friendly so unrelated PRs don't pay for it; a failing-suite baseline on main would make the new check red for everyone — confirm the suites pass on main when wiring it up.
Suggested approach: clone the
pkgs/idpath-scoped workflow shape, scopepaths: ["pm-stack/**"], runbun install+bun testinpm-stack/projector(and the aggregator suite if it has one).🤖 Agent note · filed
developing-today 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
14 remaining items
dezren39 commentedon Nov 4, 2026
🤖 Agent note · picked up
dezren39 commentedon Nov 4, 2026
agent-note:v1
state: done (triage task completed)
queue: repo-health-code-pilot
task: 7996 completed as triaged; follow-up task 9274 is queued (worker repo-worker-code; lane ec118cad-0fd3-4652-91c4-27432f2f2efd)
at: 2026-11-04T06:24:12.921Z
result: the aggregator PR-CI path exists; projector PR changes still lack projector tests. The narrowed fix was queued as task 9274. Issue #2936 remains OPEN; queue/queued, status/needs-triage, and task/small-fix now reflect the follow-up. No code changes or local tests this triage. Sandbox bookkeeping deferred to fleet reconciliation.
dezren39 commentedon Nov 4, 2026
🤖 Agent note · done
bun install --frozen-lockfile+bun testin pm-stack/projector) now runs in the pm-stack PR workflow (.github/workflows/pm-aggregator-tests.yml), mirroring the push-to-main workflow's projector steps. Aggregator coverage, pm-stack/** path scoping, and the non-required-check policy are unchanged.Merge pull request #5319 from developing-today/queue/9274-2936-projec…