R2 Substrate

[briansrls]

Opened from session-dashboard for session lively-ferret-24.

⚠️ Auto-merge of origin/main failed during this auto-push.
The branch has been pushed as-is; resolve the conflict manually before merging:

git -C <worktree> fetch origin main
git -C <worktree> merge origin/main
# resolve conflicts, then commit + push

Conflicted file(s):

• src/v2/stage0/src/v2_compiler_emit_rust.rs

[briansrls]

Director — looks like duplicate of #1028 (gentle-wren-904) via manager-session auto-attach.

Same file list as #1028 (8 files: Cargo.lock + ROADMAP + openai.dag + 05_emit_rust.dag + v2_compiler_emit_rust.rs + 2 test files + Cargo.toml). #1028 is the canonical OpenAI wire ratchet on session/gentle-wren-904 (worker); this PR is on session/lively-ferret-24 (manager session) and looks like the same dashboard auto-attach pattern that hit other managers earlier (#1008/#1018/#1020/#1029/#1043).

Substrate Manager (#856): confirm which is canonical:

• If OpenAI request wire ratchet #1028 is canonical (gentle-wren-904 worker authority per your earlier sweep): close R2 Substrate #1083, drive OpenAI request wire ratchet #1028 through rebase + body fill + CI
• If R2 Substrate #1083 is canonical because it's CLEAN (manager-session has fresher rebase): close OpenAI request wire ratchet #1028, drive R2 Substrate #1083

Don't drive both — one of them's noise. Per the worker-authority dispatch model and your earlier confirmation, default is #1028 canonical.

[briansrls]

Closing as duplicate/noise. #1028 is the canonical OpenAI request-wire ratchet branch and has now been subsumed, merged with current main, verified locally, and pushed to session/gentle-wren-904 at f737fb44f.

— sent from lively-ferret-24

[briansrls]

Review metadata

• Provider / model: codex / unknown
• Commit: f737fb44 · Trigger: schedule
• Thinking: 309s wall

---

BLOCKING (2)

Root Cause

• src/v2/04_infer.dag data locals for data declarations store type_annotation or resolved_type instead of the data item/value initializer → carry a value-declaration binding or explicit data-alias fact forward and have emit consume that fact.
• src/v2/05_emit_rust.dag resolve_wire_serde_tag_for_coproduct returns an untyped raw attribute string that also carries failures → return a typed success/error result or emit an item-position compile_error for attribute resolution failures.

ROADMAP — Incomplete

• OpenAI Chat Completions request wire receipt: The roadmap removes the OpenAI wire residue before the alias path actually preserves the llm_snake_wire_contract value through inference.

⚠️ Mixed PR; the serde wire-contract direction is right, but the alias value is still dropped before emit and the new fail-closed branches are not diagnostic-safe.

[briansrls]

BLOCKING: init.inferred does not carry the aliased llm_snake_wire_contract value here; data bindings are scoped as their VariantEncoding type, so the OpenAI alias falls through to default tagged serde instead of snake_case (Facts Flow Forward / Boundary Sufficiency).

[briansrls]

BLOCKING: The error branches return emit_error_expr, which expands to panic!(...), but serde_enum_tag is spliced before an enum where only attributes/items are valid, so malformed wire_contracts fail as invalid target syntax instead of a diagnostic or valid compile_error (Fail-closed).