Skip to content

Adopt two orphaned PRs whose sessions are gone: #8938 (inference endpoint binding, mergeable, never ran checks) and #9051 (reach fold endpoint projection, CONFLICTING, operator-paused) - #9204

Closed
gunbai-bot[bot] wants to merge 4 commits into
mainfrom
receipt/9196-planted

Conversation

@gunbai-bot

@gunbai-bot gunbai-bot Bot commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Auto-opened by session-dashboard for session loyal-dove-837.
Pushing to receipt/9196-planted 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 added 4 commits August 25, 2026 15:56
…_semantics_witness

The field was added to TypeEnv by #8952 and its hand-maintained callers in this bin were never
updated, because nothing compiles them: witnesses.yml builds two of fifteen bins, the Rust suite
left CI 2026-07-11, clippy 2026-07-08, and the compile-clean gate went with the floor cut. So main
has been red at 'cargo check -p v1-compiler' with no required phase that could notice.

All six sites already set the sibling source_visible_names to an empty map -- these are synthetic
envs, not module envs -- so the empty map is the established value at this shape rather than a
choice made here.

MEASURED, same command and same base, discriminating both ways:
  origin/main            cargo check -p v1-compiler --bins -> exit 101, 6 x E0063
  origin/main + this fix cargo check -p v1-compiler --bins -> exit 0, Finished

The --bins scope also measures the other twelve unbuilt binaries: all of them compile. The class
is thirteen unguarded bins, of which exactly one had gone stale.
…e to prove the new all-binary-targets step fails while the floor still publishes its ledger
@gunbai-bot

gunbai-bot Bot commented Aug 25, 2026

Copy link
Copy Markdown
Contributor Author

Closing immediately — this branch is a DELIBERATELY BROKEN measurement fixture, not proposed work. It was auto-attached by the dashboard when I pushed the branch; it must never be merged or reviewed.

It carries one planted mutation (one authored_import_names field removed from infer_semantics_witness) to serve as the discriminating control for the new all-binary-targets standing in #9196: it proves the new step FAILS and names the binary, while the required floor still reaches and PUBLISHES its ledger — i.e. that the guard is not a second preparation mask.

The receipt is being taken via workflow_dispatch on the branch (run 32873753939), which needs no PR. The branch is deleted once the run reports.

— sent from loyal-dove-837

@gunbai-bot gunbai-bot Bot closed this Aug 25, 2026
@gunbai-bot
gunbai-bot Bot deleted the receipt/9196-planted branch August 25, 2026 17:43
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