Repository navigation
Description
Bug: worker-poc smoke/post-update-failure.mjs fails on clean main — MemoryJournal stub doesn't handle worker.ts's SELECT step FROM journal query
Reproduced on clean origin/main @ 03d1a21eae (no local changes), laptop Node v24.21.0:
cd pkgs/id/worker-poc
node smoke/post-update-failure.mjs
# Error: unexpected SQL: SELECT step FROM journal ORDER BY step DESC LIMIT 1
# at MemoryJournal.exec (smoke/post-update-failure.mjs:37)
# at WorldObject.handle (src/worker.ts:128)Cause
pkgs/id/worker-poc/src/worker.ts:128 issues SELECT step FROM journal ORDER BY step DESC LIMIT 1 (added by 999414c "fix(worker-poc): report journal step on cold start"). The smoke's MemoryJournal.exec stub handles the SELECT step, snapshot FROM journal ... shape (worker.ts:98) and the journal INSERT, but not the SELECT step FROM journal ... shape, so it throws unexpected SQL.
Verified pre-existing: the failure reproduces identically with all local changes stashed (found during task 10764 / issue #6372, which only wires participant-validation into the smoke chain — no source or smoke-file changes). counter-smoke and participant-validation are green on the same tree.
Acceptance
MemoryJournalinsmoke/post-update-failure.mjshandles theSELECT step FROM journal ORDER BY step DESC LIMIT 1query (returns the latest step), or worker.ts's query is aligned with the shapes the stub supports.node smoke/post-update-failure.mjspasses on clean main.npm run smokein pkgs/id/worker-poc runs the full chain green.
Acceptance criteria
node smoke/post-update-failure.mjsinpkgs/id/worker-pocpasses on clean main.- The smoke's
MemoryJournalstub handles theSELECT step FROM journal ORDER BY step DESC LIMIT 1query shape thatsrc/worker.tsissues on cold start, returning the latest journaled step. - The neighbouring smokes (
counter-smoke,participant-validation) still pass, and no production behaviour insrc/worker.tschanges.
Activity
developing-today commentedon Nov 5, 2026
CODE-1891
developing-today commentedon Nov 6, 2026
Intake review
Fleet monitor intake (§5 pass), 2026-11-05 run.
origin/main@03d1a21eaeis fresh and self-contained.999414c1ab(added the cold-start step query the stub never learned).MemoryJournal.exechandles theSELECT step, snapshot …shape and the INSERT, but not theSELECT step FROM journal …shape fromworker.ts:128. This is a stub-fidelity bug in the smoke, not a worker bug.MemoryJournal.execto recognise the step-only query and return the max journaled step (or an empty result when no rows exist, matching a fresh journal), then run the full smoke chain.20 remaining items
dezren39 commentedon Nov 6, 2026
🤖 Agent note · handed off
opencode(lane row 3460, no session bound yet)dezren39 commentedon Nov 6, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 6, 2026
🤖 Agent note · handed off
opencodedezren39 commentedon Nov 6, 2026
🤖 Agent note · handed off
opencode; handing off to the opencode claimant per the worker runbook §1b — this lane does not work it directly.