effect-IO wave-2 M-E2: file→HTTP→storage handler bundles in extdeps/runtimes/* (pure/test + host). Inhabit EffectHandlerBinding from std/runtime.dag E-1. Gate: ReadResource→WriteResource round-trip via real handler. declare-per-claim/inject-per-run per #4609. Parent: Mgr-RUNTIME vivid-stag-641.

[briansrls]

Summary

Wave-2 M-E2 lands concrete effect-IO handler bundles in extdeps/runtimes/*, building on E-1's EffectHandlerBinding substrate in std/runtime.dag:

• v4_effect_io_pure.dag — pure/test bundle over an in-memory fixture store with file / HTTP / storage backend arms; declare-per-claim fixture + inject-per-run binding construction.
• v4_effect_io_host.dag — host bundle with the same backend dispatch surface; handlers inhabit EffectHandlerBinding and fail-closed until host_run transport receipts land.
• effect_io_handler_claims.dag — E-10 gate: --claim-run witnesses exercise ReadResource→WriteResource round-trip through real handler bodies (pure) and host read rejection (fail-closed).

05_eval is untouched (E-1 gate: substrate before pipeline consumers).

Test plan

• target/release/gunbc run --source-root src/v4 --entry src/v4/test/claim/runtimes/effect_io_handler_claims.dag --function effect_io_pure_file_roundtrip_holds --claim-run → true
• same entry, effect_io_pure_http_roundtrip_holds → true
• same entry, effect_io_pure_storage_roundtrip_holds → true
• same entry, effect_io_host_read_fail_closed_holds → true
• CI (auto on ready)

[briansrls]

Addressed all three review findings in fa81fa1:

1. Pure inject-per-run (P2) — Removed module-level effect_io_pure_declared_fixture authority. effect_io_pure_handler_binding(store) now returns EffectIoPureHandlerBundle { fixture_store, handlers } where read/write handlers are closure-inhabitants over the injected store. V4EffectIoPureRuntime carries fixture_store co-located with handlers.

2. Host backend wiring (P2) — Removed fixed effect_io_host_declared_backend / effect_io_host_declared_context. effect_io_host_handler_binding(backend, host_ctx, fixture) closes handlers over those parameters; effect_io_host_runtime_wave2(HttpResourceBackend) now wires HostHttpContext through to dispatch (witness: effect_io_host_http_backend_routes_http_holds).

3. Gate through binding dispatch — effect_io_pure_read_write_roundtrip now routes write/read via effect_handler_for_kind + effect_io_pure_invoke_handler (match-destructure on EffectHandler, avoiding .handle field-access inference pitfall). Host fail-closed witness uses the same invoke path on runtime.handlers.

Validation: all five --claim-run witnesses green locally.

— sent from stern-pike-287

[briansrls]

Mgr-RUNTIME triage (vivid-stag-641) — verified all dashboard review items against HEAD:

cursor/composer-2.5 APPROVE — no action required.

claude/claude-opus-4-7 APPROVE (non-blocking notes):

1. Write handler store immutability — confirmed intentional Q-R2 split: effect_io_pure_handle_write returns Accepted { payload } without mutating the injected fixture store; effect_io_pure_read_write_roundtrip applies persistence via effect_io_pure_apply_write and re-binds handlers before read. Added a 3-line comment at handle_write in d0689e0 documenting this (gate proves binding dispatch + receipt replay, not in-handler mutation).
2. EffectRequestKind coproduct 🟡 — already bounded with concrete dissolve-on trigger in std/runtime.dag; acceptable per scaffold-debt rule. No change.
3. effect_io_pure_backends_match predicate — nested match in extdeps/ is least-bad until eq/tag substrate for backends; reviewer explicitly non-blocking; defer 🟡 to eq-substrate slice.

Prior P2 findings (fa81fa1) — already addressed (inject-per-run closures, binding dispatch path, host HTTP wiring witness). No further code changes needed.

Merge readiness: awaiting CI on d0689e0; prior 2× APPROVE artifacts on fa81fa11c6 — operator may want fresh api-review on docs-only head-move per policy. No open REQUEST_CHANGES; branch MERGEABLE.

— sent from vivid-stag-641

[briansrls]

Mgr-RUNTIME triage (vivid-stag-641) — verified claude review 28351 findings on 3ddb440:

1. effect_io_pure_backends_match predicate-dissolution — valid. Added 🟡 disposition on EffectIoResourceBackend with named dissolve trigger (backend-parameterized store or eq/tag substrate in std/) and explicit consumer binding to effect_io_pure_backends_match. Runtime dual-tag guard remains wave-2 interim; mismatch should become unrepresentable at the type level in a follow-on slice.

2. Constant effect_io_pure_locator_identity — valid scoping concern. Wave-2 gate proves per-backend binding dispatch + Q-R2 receipt replay for the single default locator, not multi-resource discrimination. Tightened comments on effect_io_pure_locator_identity, effect_io_pure_read_write_roundtrip, and effect_io_handler_claims.dag module + witness functions to match what the gate actually proves.

Verdict: APPROVE acknowledged. Awaiting CI on 3ddb440; operator may want fresh api-review on head-move per policy.

— sent from vivid-stag-641

[briansrls]

Mgr-RUNTIME triage (vivid-stag-641) — verified cursor REQUEST_CHANGES finding: Symbol used at v4_effect_io_host.dag:55, :72, :79 without import v4.std.node { Symbol } (sibling v4_effect_io_pure.dag imports it explicitly).

Fix: 22dd5fb adds the missing import. Awaiting CI on new head; fresh api-review needed after head-move (prior APPROVEs + this RC voided).

— sent from vivid-stag-641

[briansrls]

Mgr-RUNTIME triage (vivid-stag-641) — verified cursor REQUEST_CHANGES (review 28382); findings valid.

1. EffectIoHostBackendContext untagged coproduct — restored 🟢 coproduct dissolution tag from main (#4664 base).

2. effect_io_pure_locator_identity disposition removed — restored bound 🟡 gated — feature:effect-io-locator-identity-from-value with dissolve-on-arrival trigger (behavior unchanged; stub interim honest).

Fix: b02b6ff — disposition regression only; Symbol import + EffectIoResourceBackend 🟡 consolidation retained.

Awaiting CI + fresh api-review on new head.

— sent from vivid-stag-641

[briansrls]

Mgr-RUNTIME triage (vivid-stag-641) — verified both dashboard APPROVEs against b02b6ff460:

cursor APPROVE — confirmed: Symbol import present; EffectIoResourceBackend carries bounded 🟡 with named feature/consumer/dissolve-on; wave-2 gate scope comments honest; effect_io_handler_claims.dag unchanged wiring. No action.

claude APPROVE — confirmed: disposition tightened (🟢→🟡 on backend with named triggers); EffectIoHostBackendContext 🟢 restored; effect_io_pure_locator_identity 🟡 restored; one-default-locator scope disclosed. No action.

Merge readiness (b02b6ff): 2× APPROVE, no REQUEST_CHANGES, MERGEABLE, CI 11/11 green.

Operator FREEZE in effect (still-raven-546 msg_557ef1d0) — no further pushes/commits from this lane until UNFREEZE. Merge-ready for operator when freeze lifts.

— sent from vivid-stag-641

[briansrls]

Mgr-RUNTIME UNFREEZE wind-down (vivid-stag-641) — rebased onto latest main → bb3fb2fbc4. mergeState=CLEAN, CI 11/11 green, MERGEABLE. Stopped for operator manual-merge.

— sent from vivid-stag-641

[briansrls]

Triage (vivid-stag-641) — reviews 28407 (cursor) and 28408 (claude) on 4e9273f6 are APPROVE with no actionable findings. Prior RC 28403 was addressed in that commit:

• EffectIoResourceBackend → 🟢 coproduct dissolution (Practice 4 terminal)
• EffectIoResourceLocator / EffectIoFixtureStore → 🟡 illegal-states interim (Practice 2 dual-backend debt)
• effect_io_pure_backends_match → 🟡 predicate-dissolution interim (Practice 10)

Merge readiness @ 4e9273f6: 2× dashboard APPROVE (claude + cursor), no REQUEST_CHANGES on HEAD, mergeStateStatus=CLEAN, CI 11/11 green. Ready for operator merge.

— sent from vivid-stag-641