[P0][Integration] Make RuntimeBridge the production effect executor for Runtime-backed Loop runs

[wesleysimplicio]

Objective

Promote RuntimeBridge from an isolated/tested transport into the production effect path of the Simplicio Loop runner whenever the Runtime-backed profile is selected.

Today the main runner invokes Mapper and Dev CLI operators directly, while RuntimeBridge is exercised primarily by transport tests. This leaves two parallel effect paths and prevents Runtime from being the authoritative executor/evidence boundary for Runtime-backed runs.

Non-negotiable architecture

• Loop remains usable standalone without Runtime.
• When Runtime-backed execution is selected, every mutating/process effect must go through Runtime MCP or an explicitly supported native binding.
• Mapper may remain a read-only context producer.
• Dev CLI may compile plans/verification proposals, but writes/process effects in integrated mode are applied by Runtime.
• No silent direct-subprocess or direct-file fallback after Runtime selection.
• Any compatible coordinator can drive Loop; Simplicio Agent is optional.

Implementation steps

1. Add an explicit execution profile: standalone and runtime-backed.
2. Resolve profile from CLI/config/contract, never from accidental binary presence alone.
3. Instantiate one lazy RuntimeBridge per Loop Hub/session and workspace registry.
4. Add a production runner effect adapter with map/read/edit/exec/validate/checkpoint/evidence methods.
5. Translate Loop work-item identity, attempt, lease, fencing token, deadline, cancellation and write set into EffectTransaction/v1.
6. Route Dev CLI planned mutation through the Runtime adapter instead of applying it directly.
7. Route tests/build/process execution through simplicio_exec with bounded env, cwd, output and timeout.
8. Persist Runtime receipt references in operator, watcher, delivery and loop-execution receipts.
9. Prevent direct filesystem/subprocess mutation from runtime-backed runner stages with a policy guard and tests.
10. Handle Runtime unavailable, incompatible, disconnected and uncertain-effect states explicitly.
11. Keep standalone path behavior and contracts intact.
12. Expose active profile, executor identity, Runtime generation and fallback status in CLI/status/progress.
13. Add migration notes and minimum Runtime version.
14. Make the installed-package E2E release-blocking.

State and recovery

• Before effect: safe retry with the same idempotency key.
• During/after uncertain effect: reconcile; never blindly replay.
• Runtime disconnect: pause the affected lane, preserve unrelated lanes.
• Capability drift: stop before mutation and provide exact repair.
• Cancellation: honor only at Runtime safe boundaries.
• Shutdown: drain, close and verify zero owned processes.

Tests

• Standalone run without Runtime.
• Runtime-backed mechanical task with all effects through MCP.
• Semantic task coordinated by two different hosts.
• Direct mutation bypass attempt is rejected.
• Runtime missing before effect.
• Runtime crash before, during and after effect.
• Duplicate idempotency key and reconnect.
• Mapper stale context and Dev CLI rejected plan.
• Watcher validation through Runtime.
• Multi-item drain with mixed success/failure.
• Installed minimum/latest versions.

Acceptance criteria

• Runtime-backed runner has one authoritative effect adapter.
• Process trace proves no direct mutation/process bypass.
• Every effect has transaction, gate, lease/fence, validation and receipt correlation.
• Standalone Loop remains functional and separately tested.
• Runtime selection never silently downgrades.
• Uncertain effects reconcile without duplication.
• Status and final receipt name the real executor and profile.
• Runtime contract verification reaches VERIFIED only with complete evidence.
• Unit, integration, failure-injection, regression and installed E2E tests pass locally/containerized.
• p50/p95 latency, process count, tokens and RSS are measured; unavailable values are null with reason.

Relations

• Binary/capability resolution: [P0][Runtime Bridge] Resolve the canonical simplicio binary and verify MCP capabilities before effects #692
• Per-workspace concurrency: [P0][Concurrency] Replace the global RuntimeBridge lock with bounded per-workspace sessions #691
• Execution routing: [P0][Routing] Integrate worker-agent-hybrid execution decisions into the production runner #694
• Installed E2E: [P0][E2E] Prove installed Loop to Runtime MCP execution through Mapper, Dev CLI, watcher and HBP #693
• Runtime effect transaction: wesleysimplicio/simplicio-runtime#3218
• Runtime loop verification: wesleysimplicio/simplicio-runtime#3459

[wesleysimplicio]

CLAIMED

• worker: Codex
• run: 40d5b8df-7c9a-40c7-9acf-88faaab71537
• attempt: 1
• branch: agent/issue-695-runtimebridge
• base: origin/main (1181a71)
• scope: implement the RuntimeBridge production effect-executor integration slice for issue [P0][Integration] Make RuntimeBridge the production effect executor for Runtime-backed Loop runs #695 only
• goal: route Runtime-backed runner effects through one authoritative RuntimeBridge adapter while preserving standalone behavior; validate with focused tests, compile/diff checks, and live GitHub evidence
• issue: [P0][Integration] Make RuntimeBridge the production effect executor for Runtime-backed Loop runs #695

[wesleysimplicio]

Progress receipt: PR #710 merged as �9de89a2. Local evidence: py_compile, git diff --check, and 5 runtime adapter/session tests passed. Issue remains open for full runner wiring, failure injection, and installed E2E evidence.

[wesleysimplicio]

CLAIMED

• worker: Codex
• run: 47695d02-238b-4d33-a704-48704363cb06
• attempt: 1
• branch: agent/issue-695-production-effects
• base: origin/main (df9b8e3)
• scope: continue issue [P0][Integration] Make RuntimeBridge the production effect executor for Runtime-backed Loop runs #695 after merged PR feat(runtime): explicit effect adapter profiles (#695) #710; wire RuntimeEffectAdapter/RuntimeBridge into the production runner/runtime-backed execution path with explicit no-direct-mutation policy and correlated receipts, preserving standalone mode
• goal: implement and validate the remaining runner integration slice only; report exact unverified issue acceptance criteria rather than claiming full issue closure
• issue: [P0][Integration] Make RuntimeBridge the production effect executor for Runtime-backed Loop runs #695

[wesleysimplicio]

🔁 Simplicio Loop — status da execução

Campo	Valor
Estado	PLANNED
Run / attempt	47695d02-238b-4d33-a704-48704363cb06 / 1
Lease / fence	/ 1

[wesleysimplicio]

MEASURED | issue #695 runner slice

• PR #723 is merged into main.
• Merge commit: d8b45efe7c5260b1cf372c6340fa1795eb389f6c.
• Merged head: 920cef6fe2e2e01584a278898beaa0504b588186.
• Merged files: runner.py, runtime_effect_adapter.py, tests/test_runner_runtime_effects.py, tests/test_runtime_effect_adapter_transactions.py.
• Local validation: 13 focused adapter/runner/bridge tests passed; py_compile, compileall, and git diff --check passed. GitHub Actions were intentionally not used per operator instruction.
• Standalone mode remains covered; runtime-backed execution has explicit profile selection, cached per-workspace adapter/bridge, no fake/direct mutation fallback, and correlated transaction/lease/fence/gate receipts.

UNVERIFIED | remaining acceptance criteria: real collaborator integration without mocked seams; installed Runtime-backed CLI/system smoke and capability receipts; full failure-injection coverage for Runtime missing/crash/disconnect/uncertain effects and duplicate reconciliation; full regression suite (the planning-gate integration and repository check command exceeded local bounded time); p50/p95 latency, process count, token, and RSS measurements; and coverage threshold or an explicit no-infra waiver.

Issue remains OPEN until those criteria are independently evidenced.