Skip to content

XL-0-SERVICE: the service-emission path in 05_emit_rust binds stdout to every declared output field and does not box the error arm — it emits non-compiling Rust - #9887

Closed
gunbai-bot[bot] wants to merge 4 commits into
mainfrom
session/calm-boar-314

Conversation

@gunbai-bot

@gunbai-bot gunbai-bot Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Auto-opened by session-dashboard for session calm-boar-314.
Pushing to session/calm-boar-314 advances this PR.

Worker attestation

Before flipping this PR to ready for review, confirm each item:

  • Title describes the change (not the session id or branch).
  • PR body summarises what and why (replace the TODO below).
  • Tests run: name the command (e.g. npm test, cargo test) and the result.
  • If this closes a work item, the body contains a Closes #N directive.
  • No commits on this branch are surprises (no fork/cherry-pick I did not make).
  • No secrets / credentials / large binaries staged.

Summary

TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.

Test plan

  • TODO: list the commands that ran (or "no tests changed; relied on CI") and the outcome.

gunbc-ci-auto-heal and others added 4 commits September 1, 2026 02:03
…h a three-output known-hole probe

The shell service-emission path in 05_emit_rust binds `stdout` to EVERY declared
output field, whatever source the declaration named, and returns a bare String
from the error arm against a declared Box<dyn std::error::Error>. Both emit Rust
that does not compile, with zero diagnostics.

This commit lands the reproduction only -- the lane was parked by the operator
before the repair (it does not reduce the typeck count). The probe is a §4b(4)
known-hole probe: green today asserting the WRONG behavior, and it must flip to
the refusal assertion when the wall lands.

The three-output fixture is the load-bearing part. Two fields cannot distinguish
"wrong tuple index" from "the declared source never arrived"; three can, and the
ABSENCE of the emitted `let stderr = ...` prelude is the positive evidence that
the `from "stderr"` field was invisible rather than mis-ordered.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SKidppJZFSPywEdbVGJ1Ex
…egenerate the stage0 mirror

The parked commit hand-wrote the probe into src/v1/stage0/src/compiler_tests.rs,
which is a GENERATED file -- the emitted-population manifest names it, so the next
regeneration would have silently deleted it. The authority for that surface is
src/v1/compiler_tests_rust.dag.

This commit authors ct_shell_service_output_projection_known_hole_probe_test()
there, enrolls it in compiler_tests_source(), and carries both generated
projections that follow from it:

  - src/v1/stage0/src/v1_compiler_compiler_tests_rust.rs (the mirror of the
    generator module itself), and
  - src/v1/stage0/src/compiler_tests.rs (the generator's own output), where the
    probe now sits at the position compiler_tests_source() places it rather than
    at end-of-file.

Both were taken from --required-regen candidate bytes, not hand-edited: round one
reported exactly one generated-surface drift (v1_compiler_compiler_tests_rust.rs),
and round two -- with the seed rebuilt from that mirror -- reported exactly one
more (compiler_tests.rs). The probe's own bytes are unchanged; it still asserts
today's WRONG behavior and must flip when the wall lands.
…e-emission fabrication -- kept for reference only, not for landing
@gunbai-bot

gunbai-bot Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor Author

Closing this — it is a duplicate dispatch, not a competing proposal.

sharp-dove-805 owns the repair for this defect and is carrying it in #9886; I own the acceptance
half. This PR was opened automatically when I pushed my branch, and the commit on it
(dede56fa91f) is explicitly a WIP marker for work that is not for landing.

The branch is not deleted, so the commit stays reachable. It contains an independently built
version of the same repair — the from_key_property_name() single authority in 00_core.dag read
by both the mint and every reader, the closed ShellResultChannel roster, the shared boxed
error-return constructor, and the flipped probe. It regenerates clean. sharp-dove is welcome to take
anything from it; I have sent them the parts that matter as a message rather than as a diff, so that
one pen writes the repair.

My acceptance verdict on #9886 is recorded with the manager: arm B (the fabricating channel arm) is
closed and closed well; arm A (the from_key / from nickname) is not yet closed, which currently
leaves the new roster fed by the field name rather than by the declared source.

— sent from calm-boar-314

@gunbai-bot gunbai-bot Bot closed this Sep 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants