aggregator: actions.test.ts fails on main — applied snooze never lands in the Snoozed strip ('Snoozed by you (1)' missing)

Problem

pm-stack/aggregator test suite fails on clean main @ d39e6111 (verified twice, 2026-10-28, laptop):

bun test → 302 pass / 1 fail (303 tests)
Failing: test/actions.test.ts — "attention action controls (design+impl(aggregator): triage actions on /attention - acknowledge, snooze, escalate, answer - orchestrator-mediated #1152/impl(aggregator): session actions from /sessions and /attention - poke, answer, stop - keeper/orchestrator-mediated #1156) > pending + applied states render as badges; applied snooze lands in the Snoozed strip"
actions.test.ts:335: expect(html).toContain("Snoozed by you (1)") — the rendered /attention HTML contains the pending/acknowledged badges (⏳ acknowledge requested, ✓ acknowledged both pass) but no Snoozed strip for an applied snooze action (verb: "snooze", state: "applied", appliedAt: NOW-1h, payload.until: NOW+24h, object orch:gone_item).

Evidence

Reproduced identically on the untouched laptop primary clone at d39e6111 and in a fresh worktree of the same commit — not caused by any in-flight change (found while testing queue task 1896 / aggregator: roadmap Horizon dates are never validated — month 13 invents a Q5 lane and an 'undefined 2026' month, month 00 a Q0 lane, and ymdLabel throws on them #1628, whose diff does not touch attention/actions code; that branch shows the same 1 fail atop its 6 new passing tests).
The two neighbouring assertions in the same test (pending badge, applied ack badge) pass, so the render path generally works; the applied-snooze → Snoozed-strip step specifically does not fire for this fixture.

Acceptance

The named test passes on main without weakening its assertions, OR the test is shown to be date/fixture-sensitive and is pinned to a deterministic clock with a comment saying so.
Full aggregator suite green: bun test in pm-stack/aggregator → 0 fail.

Found by: queue worker lane C (task 1896) pre-existing-failure check, 2026-10-28.

Acceptance criteria

The named actions.test.ts test ("pending + applied states render as badges; applied snooze lands in the Snoozed strip") passes on main without weakening its assertions, OR it is shown to be date/fixture-sensitive and pinned to a deterministic clock with an explanatory comment.
Full aggregator suite green: bun test in pm-stack/aggregator reports 0 failures.

Intake review

Related: The failing test covers the attention action controls from design+impl(aggregator): triage actions on /attention - acknowledge, snooze, escalate, answer - orchestrator-mediated #1152 / impl(aggregator): session actions from /sessions and /attention - poke, answer, stop - keeper/orchestrator-mediated #1156. Found by queue worker lane C (task 1896) while testing aggregator: roadmap Horizon dates are never validated — month 13 invents a Q5 lane and an 'undefined 2026' month, month 00 a Q0 lane, and ymdLabel throws on them #1628; that diff does not touch attention/actions code.
Notes: Verified still live this run: no merged PR since the filing touches the aggregator attention/actions render path (today's aggregator merges are aggregator: anchor OpenCode Go resets to each workspace paragraph (#1626) #1717 for aggregator: OpenCode Go reset dates are paired by section position, not by workspace — one missing or extra 'monthly reset' line shifts both workspaces' resets #1626 and aggregator: clock proposal expiry from proposal.at, not delegation updatedAt (#1623) #1714 for aggregator: proposal expiry is clocked from the delegation's updatedAt, not the proposal's draft time — a 72h-old proposal stays approvable, a 1h-old one reads expired #1623). Reproduction is already documented twice on clean main @ d39e611.
Risks: The fixture uses relative times (appliedAt NOW-1h, until NOW+24h); if the strip render has an unstated freshness window, this may be a clock-sensitivity bug rather than a render bug — the acceptance covers both outcomes.
Suggested approach: Trace the applied-snooze branch in the /attention render for the fixture shape first; if the render is correct, pin the test clock and say why in a comment.

agent-note:v1 — state=claimed; task=2627; worker=repo-worker-code; origin=openchamber-scheduled-lane; at=2026-11-01T05:07:00Z; triage=#1682 against current main; no hard-stop labels or open competing PR found; next=reproduce the reported test on current main and route a scoped small-fix packet if still failing.

agent-note:v1 — state=handed-off; task=2627; worker=repo-worker-code; origin=openchamber-scheduled-lane; at=2026-11-01T05:09:39Z; verdict=confirmed on current main 79bfc34 by the targeted actions.test.ts run (0 pass, 1 fail at line 335; expected Snoozed by you (1) missing); follow-up=small_fix task 5036 queued with scope and target/full-suite tests; issue remains open; no competing open PR found.

agent-note:v1 — state=done; task=2627; worker=repo-worker-code; origin=openchamber-scheduled-lane; at=2026-11-01T05:10:47Z; outcome=triaged; evidence=current main 79bfc34 targeted test fails at actions.test.ts:335 with missing Snoozed by you (1); follow-up=task 5036 queued; issue remains open with queue/queued for the follow-up.

🤖 Agent note · picked up

Agent: queue worker (repo-worker-code), lane D shift
Session / ID: task 5036
Found via: queue claim
Task: Fixing the actions.test.ts failure on main for aggregator: actions.test.ts fails on main — applied snooze never lands in the Snoozed strip ('Snoozed by you (1)' missing) #1682: an applied snooze never lands in the Snoozed strip ("Snoozed by you (1)" missing).
Expectation: effort/s — done = failing test reproduces, root cause fixed, aggregator tests green, PR open.
Links: task 5036

🤖 Agent note · done

Agent: queue worker (repo-worker-code), lane D shift
Session / ID: task 5036
Found via: queue claim
Task: Already fixed on current main — closing with two-point evidence rather than manufacturing a change. The failing test from this issue ("pending + applied states render as badges; applied snooze lands in the Snoozed strip", test/actions.test.ts) was run at both ends of today's main history on the laptop:
- At 79bfc34 (the commit triage task 2627 confirmed against this morning): fails — 14 pass / 1 fail, the failure is exactly this test.
- At current main 8540505: passes — actions.test.ts 16/16 standalone (twice) and passing inside full-suite runs (899 pass overall; the only full-suite failures are unrelated, nondeterministic slice-3/hook-timeout flakes under laptop load). pm-stack/aggregator/src/actions.ts changed between the two commits among today's merges.
Expectation: aggregator: actions.test.ts fails on main — applied snooze never lands in the Snoozed strip ('Snoozed by you (1)' missing) #1682 closes as already-fixed upstream. If the snooze strip regresses again, the repro is deterministic at the test level: bun test test/actions.test.ts in pm-stack/aggregator.
Links: task 5036 · triage task 2627

Navigation Menu

Repository navigation

aggregator: actions.test.ts fails on main — applied snooze never lands in the Snoozed strip ('Snoozed by you (1)' missing) #1682

Problem

Evidence

Acceptance

Acceptance criteria

Intake review

1 remaining item

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

aggregator: actions.test.ts fails on main — applied snooze never lands in the Snoozed strip ('Snoozed by you (1)' missing) #1682

Description

Problem

Evidence

Acceptance

Acceptance criteria

Activity

dezren39 commented on Oct 28, 2026

Intake review

dezren39 commented on Nov 1, 2026

1 remaining item

dezren39 commented on Nov 1, 2026

dezren39 commented on Nov 1, 2026

dezren39 commented on Nov 1, 2026

dezren39 commented on Nov 1, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions