Skip to content

bootstrap: delete the dead watch command; frontier --watch is the hot reload (Closes #10238) - #10240

Merged
gHashTag merged 1 commit into
masterfrom
claude/10238-delete-dead-watch
Oct 18, 2026
Merged

gHashTag merged 1 commit into
masterfrom
claude/10238-delete-dead-watch

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Closes #10238. Epic #8095 (hot reload), ledger #8737. Step 3 of the change-only inner loop.

What

Deletes the dead watch subcommand: the Watch variant, both dispatch arms (the sync and the async main) and run_watch with its two inner helpers. 106 hand-written lines lost, 0 gained.

Why

Read from the code, the command could not do what its name says:

  • Its rerun branch (a file changed) prints the changed files, sleeps and continues before the suite call, so a save reruns nothing. Only the first scan ran the suite.
  • That call is ./bootstrap/target/release/t27c suite. bootstrap/ is a workspace member, so the binary is ./target/release/t27c; on a normal checkout it fails with "suite error".
  • It hashed whole files over specs/ and compiler/ (a directory that does not exist) and reran the whole suite.

Nothing in the tree names it (no script, workflow, skill or tri action); tri hot watch runs frontier --watch (specs/verified/watch.t27, #8737 H5), which is the real hot reload.

Verified on the Railway lab

  • cargo build --release -p t27c -j 6: builds clean.
  • The old command now exits 2 (clap: unknown subcommand) and --help no longer lists it.
  • t27c frontier --list on the unchanged tree: 0 differing lines against the base binary (frontier: reused 1394 of 2227 (626 permille); rebuild: spec 52 closure 135 toolchain 29 config 0 verdict 153 missing 464).
  • bootstrap/src/test_report.rs is untouched.
  • Local gates (foreign-budget, own-language) pass on the commit.

🤖 Generated with Claude Code

… reload (Closes #10238)

The old watch command printed the changed files, slept and continued before
its suite call, so a save never reran anything, and the one run it made called
a hard-coded ./bootstrap/target/release/t27c (bootstrap/ is a workspace
member, the binary is ./target/release/t27c). Nothing in the tree calls it;
`tri hot watch` runs the frontier --watch loop (specs/verified/watch.t27).
Removes the Watch variant, both dispatch arms and run_watch: 106 hand-written
lines lost, none gained. Measured on the Railway lab: the old command now
exits 2, and the frontier --list output on the unchanged tree is
byte-identical to the base binary's (reused 1394 of 2227).

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-18 05:17:21 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 48
PRs with All Checks Green 2
READY 0
FAILING 48
PENDING 0
NO CHECKS YET 0

These columns do not partition: 0 + 48 + 0 + 0 = 48, and there are 50 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=0f8c66b9ed0e != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

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.

Delete the dead 't27c watch' command: it never reruns and hard-codes a wrong binary path (#8095 hot reload, step 3)

1 participant