Repository navigation
ci: no workflow runs the pm-stack aggregator test suite — aggregator PRs merge with no test signal #1579
Description
Problem
No GitHub Actions workflow runs the pm-stack aggregator test suite (pm-stack/aggregator, bun test, 301 tests). A search of .github/workflows/ (2026-10-28) finds no workflow referencing pm-stack/aggregator; PRs touching only pm-stack/aggregator/** get just nix ci (flake evaluation + treefmt), Auto Assign, and CodeRabbit.
Evidence: PR #1572 (fix for #1485) stated "aggregator bun tests via CI on this PR", but its only checks were Nix flake evaluation, treefmt, Auto Assign, and CodeRabbit — the suite had to be run manually on the laptop (301 pass) before merge. A merged aggregator regression would have no CI signal.
Acceptance
- A workflow runs
bun install && bun test(and ideallybunx tsc --noEmit) forpm-stack/aggregatoron PRs touchingpm-stack/**(path-filtered so other PRs are unaffected). - The check appears on an aggregator PR and passes on current main.
- Failing aggregator tests block merge for aggregator-touching PRs (required check or documented equivalent).
Found by: queue worker lane B while completing task 1639 / PR #1572.
Acceptance criteria
- A GitHub Actions workflow runs the pm-stack aggregator test suite (
bun install && bun testinpm-stack/aggregator;bunx tsc --noEmitincluded or its omission explicitly justified) on PRs touchingpm-stack/**, path-filtered so unrelated PRs are unaffected. - The check appears on an aggregator-touching PR and passes on current main.
- A failing aggregator test blocks merge for aggregator-touching PRs (required check or a documented equivalent).
- The suite's 301 tests pass under the new workflow on its first run.
Metadata
Metadata
Assignees
Labels
Package/app: aggregator (pm-stack in this repo)pm-stack (Pad/Grist) in developing-today/codeCI/CD pipelines, workflows, and build automation (area)Small: expected under 2 hours of workCI/CD pipelines, workflows, and build automationIntake review done: acceptance criteria, links, and normalized labels addedOrdinary priority (the default)Filed or worked by the queue/worker pilot
Activity
developing-today commentedon Oct 28, 2026
CODE-617
dezren39 commentedon Oct 28, 2026
🤖 Intake review — fleet monitor, 2026-10-27 run
## Acceptancesection; the appended criteria restate it under the standard heading without changing its substance.pm-stack/**, bun setup matching the repo's existing toolchain pins, run on PR + merge-group events.34 remaining items
dezren39 commentedon Nov 2, 2026
agent-note:v1
event: parked
task: 5023 (repo-health-code-pilot, repo-worker-code — OpenChamber scheduled lane)
state: Parked for 20 minutes and ending this launch. Freshly verified #1579 OPEN, PR #4025 OPEN at 4a46dae, and workflow run 41356090312 still QUEUED; its test job has not started. Laptop worktree /home/user/git/fleet/5023 is clean at the PR head; no files changed this shift.
resume: Recheck PR #4025 and run 41356090312 fresh. Merge only after the required workflow verdict is available; if it fails, distinguish already-proven main baselines #3835/#4023.
Merge pull request #4025 from developing-today/queue/5023-1579-aggreg…
dezren39 commentedon Nov 2, 2026
🤖 Agent note · done — workflow merged (task 5023, Lane B queue worker)
ceba688aef342395af6abe740a9b57266b281450. Thepm-aggregator-testsworkflow now runs the pm-stack aggregator suite in GitHub Actions. Closing this issue as delivered.main's own code (PR ci: run pm-stack aggregator bun tests in GitHub Actions (#1579) #4025 changes only the workflow file, so it cannot cause them):slice-3 routes > dns + sessions + pages routes serve— already tracked as aggregator: slice3 registry test fails on clean main — no claude-code record via fixture path #3835 (fails on clean main).hub renders > service detail: full metrics, chart, reads, conflicts— newly filed as aggregator: 'hub renders > service detail' test fails in CI on main #4091 with the run evidence.4a46daef5completed, no findings.