Production runner: wire bounded autonomous worker loop with durable worker tasks

[MrFlashAccount]

Goal

Wire /buran run to execute a bounded autonomous worker loop using the durable worker task model from #16: spawn/wait/ingest/transition to the next stage for one approved run.

Dependencies

• Depends on Production runner: add durable worker task model and completion ingestion #16 for durable worker task creation and completion ingestion.
• Likely depends on the operator control plane in Production runner: add operator control plane #19 for audit logging, safety gates, retry budgets, and stuck/next-action visibility.

Current state / evidence

• README.md positions Buran as the execution layer that turns approved work into review-ready handoffs and tracks durable local state.
• src/entrypoints/cli.js help still says the current scope is a "local runner skeleton" with no worker execution.
• src/gates/implementation-contract.js has an implementation-harness-dispatch.v1 contract, but the default adapter is implementation-harness-unavailable.v1 and fails closed.
• src/application/final-report.js still has unsupportedStageMessage(state) for stages not executed by adapters.
• Open issue Research task-level orchestration model for Buran #2 covers task-level orchestration research; this issue is the pragmatic production slice for a single run, not the full architecture model.

Scope

• Use worker tasks from Production runner: add durable worker task model and completion ingestion #16 to spawn implementation/fix/review work through configured adapters.
• Wait for or poll worker completion through the durable completion ingestion boundary, then transition deterministically to verification, internal review, fix loop, blocked, or handoff-ready states.
• Enforce bounded attempts/retries and fail-closed behavior when adapters are unavailable, completions are missing/conflicting, or policy blocks action.
• Preserve epoch/attempt history across implementation, verification failure, internal-review failure, and fix redispatch.
• Surface current worker task, blocker, and next safe action in the runner report/control-plane output.

Acceptance criteria

• Given a sufficient approved packet and an acquired/valid workspace lease, /buran run --run <run_id> ... can create a worker task, invoke a configured implementation worker/harness adapter, ingest completion, and record completed implementation evidence.
• Verification and internal review gates run only after valid implementation/fix worker completion evidence exists.
• PASS, FAIL, and BLOCKED verification/review results transition through the existing state machine deterministically.
• Failed verification or internal review can enter the existing bounded fix loop and redispatch fix work without losing prior epoch/attempt/task history.
• Missing adapter, missing completion, conflicting completion, retry exhaustion, and policy denial all fail closed with structured blockers.
• All stage transitions and task events are recorded in the registry snapshot/events and reflected in formatted runner reports.
• Tests cover happy path, blocked implementation dispatch, failed verification -> fix loop, failed internal review -> fix loop, retry exhaustion, and idempotent resume from already-recorded worker artifacts.

Non-goals

• No proof matrix or kill/restart checklist here; that belongs in Production runner: proof checklist for local e2e and restart recovery #21.
• No GitHub live transport policy here; that belongs in Production runner: harden live GitHub transport policy #18.
• No autonomous discovery of work items.
• No auto-merge or movement to Done.
• No multi-task orchestration tree beyond a single approved run.

Planning notes / questions

• Keep the adapter interface narrow enough for OpenClaw/DevHarness without coupling core Buran to one runtime.
• Decide whether verification/review adapters are injected separately or composed by the same harness adapter.
• Reuse fake adapters from Production runner: proof checklist for local e2e and restart recovery #21 tests where possible.

Suggested labels

• enhancement

[MrFlashAccount]

Closed as completed by merged PR #23 (c71a0cf).

Reconciliation evidence:

• PR Issue #15: bounded autonomous worker loop #23 wires /buran run through durable WorkerTask creation, dispatch, completion ingestion, CompletionDecision gating, verification/internal-review transitions, and bounded fix-loop redispatch.
• Merged code/docs cover the worker lifecycle in src/application/mission-phase-runner.js, src/application/fix-review-loop.js, src/gates/implementation-contract.js, src/core/ports/harness-runtime.js, docs/state-machine.md, and docs/execution-run-schema.md.
• Tests added/updated in test/runner.test.js and test/operator-status.test.js cover implementation dispatch, missing adapter fail-closed behavior, completion evidence before verification, failed verification/internal-review into fix loop, retry exhaustion, idempotent resume, and operator worker status.
• PR verification reported npm test 183/183 passing and npm run check passing.