Upgrade the Atomic harness to 0.9.26-alpha.5

0.9.26-alpha.5 relays a workflow stage's ask_user_question to the
session's HostInput (bastani-inc/atomic#3396). On 0.9.25 the relay
missed the request, so a stage's question never reached Decisions and
the stage waited forever. It also restores managed workflow PostgreSQL
after a shutdown (bastani-inc/atomic#3413), which is what left Planner
workflow runs non-durable, so the Planner keeps them durable with
Atomic's own database selection and no extra configuration.

The new full.test.ts case runs a workflow whose stage asks a question
through a real Atomic session: the card appears in Decisions as a
Questionnaire block and its answer reaches the stage. It times out with
no card on 0.9.25. The five builtin packages are unchanged, so
BUILTINS_OFF still turns off each one for the isolated Planner.

Assistant-workflow: inline
Assistant-model: Claude Opus 5.5
Assistant-verification: bun test failed on 0.9.25: the new workflow-stage question case timed out after 32.7s with no card
Assistant-verification: bun test passed: 1911 pass, 2 PostgreSQL skips, 0 fail; full.test.ts 16 pass with the new case
Assistant-verification: bun run types passed: all workspaces
Assistant-verification: bun run ci passed: dprint, oxlint, tokens, design contract, design record, Impeccable (no new findings)
Assistant-verification: durability check passed: a Planner workflow run with no DBOS_SYSTEM_DATABASE_URL used Atomic's managed PostgreSQL, logged no NON-DURABLY warning, and was kept after the process was killed
Assistant-verification: cross-process /workflow resume from a fresh SDK session failed: timed out on both 0.9.25 and 0.9.26-alpha.5 with persisted checkpoints
Assistant-verification: source check passed: @bastani/atomic 0.9.26-alpha.5 dist/builtin lists intercom, mcp, subagents, web-access, workflows
Co-authored-by: Alex Lavaee <lavaman131@github.com>