Skip to content

ci(t27os): make t27os on every PR touching the OS specs (Closes #11788) - #12330

Merged
gHashTag merged 2 commits into
masterfrom
ci-t27os-app
Oct 25, 2026
Merged

ci(t27os): make t27os on every PR touching the OS specs (Closes #11788)#12330
gHashTag merged 2 commits into
masterfrom
ci-t27os-app

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 25, 2026

Copy link
Copy Markdown
Collaborator

Closes #11788 (the second requirement: "make t27os must run in CI on every PR touching specs/t27os/ -- today the app target can rot silently on master (it did)").

What

  • .github/workflows/t27os.yml: on every PR touching specs/t27os/**, Makefile, specs/tri/t27b/libm.t27 or specs/tri/t27b/libm_plan.t27, build T27OS.app and t27os-pty on an arm64 runner (macos-14), assert both products exist and are signed, upload the app as an artifact.
  • tools/policy/foreign-exceptions.txt: the workflow's path listed under the owner's approval.

Owner approval (quoted, per the Only-t27 rule)

"разрешаю! owner-approved-foreign!" -- the owner, 2026-10-23, in the working session, said three times the same day in direct response to the blocked CI-workflow and gen-zig-stub slices; plus the standing rule of 2026-10-06 ("add the label yourself and do the foreign part", recorded in foreign-exceptions.txt #6446/#6887 entries).

The label owner-approved-foreign is applied to this pull request on that authorization. The local lefthook reads master's copy of the exceptions list (#7371: "a branch cannot list itself"), so the branch and its two commits were created through the GitHub API; the canonical gate is this PR's own own-language check, which reads the label.

Evidence

The app builds green from this exact tree today (build 7216 on the authoring machine, make t27os exit 0, both products signed ad hoc).

@gHashTag
ci(t27os): list the workflow under the owner-approved-foreign entry (C…
7b02b2e 
…loses #11788)
@gHashTag
ci(t27os): make t27os on every PR touching the OS specs (Closes #11788)
2fa1f9f 
The app target rotted silently on master once -- glass_window.t27
refused to lower for two days while every spec gate stayed green,
because no gate built the product. This workflow builds T27OS.app and
t27os-pty on an arm64 runner for every pull request that touches the OS
specs, the trig/libm plans they pull in, or the Makefile, asserts both
products exist and are signed, and uploads the app as an artifact.

Foreign by the Only-t27 rule; the owner approved it directly:
'razreshayu! owner-approved-foreign!' (2026-10-23, in session, three
times), and the path is listed in foreign-exceptions.txt in the base
commit of this PR.
@gHashTag gHashTag added the owner-approved-foreign Owner-approved exception to the only-t27 rule: hand-written foreign code allowed in this PR label Oct 25, 2026
This was referenced Oct 25, 2026
Merged
Merged
Merged
Merged
@github-actions

github-actions Bot commented Oct 25, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-25 07:22:21 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 24
PRs with All Checks Green 26
READY 13
FAILING 24
PENDING 0
NO CHECKS YET 0

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

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=55c0f1b1b32d != 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).

This was referenced Oct 25, 2026
Merged
Merged
Merged
Merged
Merged
Merged
Merged
@tri-claw

tri-claw Bot commented Oct 25, 2026

Copy link
Copy Markdown

Summary by t27-bees

This PR adds a CI workflow to build the T27OS app on PRs touching the OS specs and related files, preventing silent rot on master. It also registers the workflow in the foreign-exceptions list with owner approval.

Worth a look

  • .github/workflows/t27os.yml:7 — T27OS_BUILD=$(git rev-list --count HEAD) uses the PR branch's commit count as the build number. This changes on every push to the PR and resets if the branch is rebased, so the build number isn't stable or monotonic across the PR's lifetime.
  • .github/workflows/t27os.yml:6 — The workflow only triggers on pull_request events. The issue notes the app "can rot silently on master (it did)"; without a push trigger for master (or a workflow_dispatch), regressions merged to master won't be caught until the next PR touches the watched paths.
  • .github/workflows/t27os.yml:15 — codesign -dv … | grep -q Signature relies on the string "Signature" appearing in codesign -dv output. For ad-hoc signed binaries the line reads Signature=adhoc; if the output format changes or the ad-hoc signature line is worded differently, the check could pass incorrectly or fail spuriously.
  • .github/workflows/t27os.yml:13-14 — The test -x checks verify the files exist and are executable, but don't validate they're Mach-O binaries for arm64 (the runner is arm64, but a cross-build or lipo artifact could slip through).
  • tools/policy/foreign-exceptions.txt:493-498 — The exception entry cites owner approval for the workflow, but the workflow itself is the only foreign code added; the exception is self-referential and doesn't cover any generated or downstream artifacts the workflow might produce.

Read: 2 files, +32 -0, the whole diff. Head 2fa1f9f. Model: openai-compatible/nvidia/nemotron-3-ultra-550b-a55b. Commands: @t27-bees review | summary | help | pause | resume. Free for every repository.

@github-actions github-actions Bot mentioned this pull request Oct 25, 2026
Merged
@gHashTag
gHashTag merged commit 78bda9d into master Oct 25, 2026
29 of 34 checks passed
gHashTag added a commit that referenced this pull request Oct 25, 2026
@gHashTag @claude
chore(census): re-bless for t27os.yml, which arrived on master with t…
1bd978b 
…he ledgers un-moved (Refs #12296, Refs #11788)

The census moved because #12330 added .github/workflows/t27os.yml on master
and did not re-bless: workflow files read 67 -> 68, jobs 96 -> 97, run: steps
329 -> 331, runner-named shells 308 -> 310. Written by tri census pin --bless,
checked by tri census pin --gate (rc 0). Data only, no code.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This was referenced Oct 25, 2026
Closed
Merged
Closed
Closed
gHashTag added a commit that referenced this pull request Oct 25, 2026
@gHashTag @claude
chore(census): re-bless the workflow pins, 67 -> 68 files, 96 -> 97 j…
a5f442d 
…obs, 329 -> 331 run steps (Closes #12355)

Which numbers moved and why: workflow files read 67 -> 68 (quiet and shell), jobs 96 -> 97,
run: steps 329 -> 331 and "the runner does" 308 -> 310 (shell). All four are the one workflow file
.github/workflows/t27os.yml that #12330 (78bda9d) added: one file, one job, two run steps. That
commit did not re-bless, so the cli-tri step "No census moved without saying so" has been red on every
PR since, including PRs that touch no workflow (#12346 run 40175925028). The fetches pin did not move.
Blessed with the tool, not by hand.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
gHashTag added a commit that referenced this pull request Oct 25, 2026
@gHashTag
claw(gates): t27os joins the gate inventory; re-seal the wave-drifted…
3e542b0 
… specs; re-bless the census

gate-topology's claw-drift step failed on every open PR because #12330
landed .github/workflows/t27os.yml without its row in specs/claw/gates.t27
-- a workflow file cannot land without its row, and the row cannot outlive
its file. t27os joins at its alphabetical place (68 rows, class blocking,
event pull_request), COUNT 67 -> 68, loops and census pins follow, the
negative control in coverage_report_carries_every_class moves to the now
unprinted n=62, and gen/c/claw/gates.c is t27c gen-c output of the spec.
The exact CI harness (cc + ls *.yml | claw-audit) passes locally: 'matrix
is current', exit 0. 24/24 under t27c test-report and 24/24 under t27b.

spec-guards found 8 stale gen hashes (JitSemantics, PackedVsa, TriBuilder
x aliases) -- gen output drifted under the merged compiler wave while the
seals stayed; re-sealed from the same tree, check_seal_currency reports
zero stale. cli-tri's census (workflow files read 67 -> 68, quiet.txt and
shell.txt) is re-blessed with a docs/now note saying so -- the 68th
workflow file is the t27os gate this lane asked for.
gHashTag added a commit that referenced this pull request Oct 25, 2026
@gHashTag @claude
chore(census): re-bless the workflow pins, 67 -> 68 files, 96 -> 97 j…
833c30b 
…obs, 329 -> 331 run steps (Closes #12355) (#12357)

Which numbers moved and why: workflow files read 67 -> 68 (quiet and shell), jobs 96 -> 97,
run: steps 329 -> 331 and "the runner does" 308 -> 310 (shell). All four are the one workflow file
.github/workflows/t27os.yml that #12330 (78bda9d) added: one file, one job, two run steps. That
commit did not re-bless, so the cli-tri step "No census moved without saying so" has been red on every
PR since, including PRs that touch no workflow (#12346 run 40175925028). The fetches pin did not move.
Blessed with the tool, not by hand.

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
This was referenced Oct 25, 2026
Open
Merged
Closed
Merged
This was referenced Oct 25, 2026
Merged
Merged
Closed
gHashTag added a commit that referenced this pull request Oct 25, 2026
@gHashTag @claude
ci(gate-topology): classify t27os.yml as not merge-critical, ceiling …
bd3fd64 
…stays 24 (Refs #12358) (#12404)

t27os.yml (added by #12330) was in neither list, so the unclassified
count rose to 25 against a ceiling of 24 and gate-topology went red on
every pull request. One entry in NOT_MERGE_CRITICAL with its reason;
MAX_UNCLASSIFIED is unchanged. The checker now prints CLEAN with 24
unread at a ceiling of 24.

A doubled empty comment line is dropped in the same file, so the
foreign-line budget (lines added <= lines deleted) holds. Owner
approved this hand edit (owner-approved-foreign), 2026-10-25.

Refs #12358

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
@gHashTag gHashTag mentioned this pull request Oct 25, 2026
Merged
gHashTag added a commit that referenced this pull request Oct 25, 2026
@gHashTag @claude
claw: add the t27os workflow row to the gate inventory, 68 rows (Closes
1b1a27d 
#12417) (#12421)

The gate-topology claw drift step failed with DIR-ONLY t27os: the workflow
file t27os.yml landed in #12330 but specs/claw/gates.t27 had no row for it.

Row added in alphabetical place after t27o-release: class 0 (no
continue-on-error), events "pull_request" (len 12), name len 5. The parallel
arrays, every 0..67 loop and the [67] types move to 68; the census is now
63 blocking + 3 soft + 2 reporting; the coverage tests and the last-row index
tests follow. gates_pins loops widened to 68. gen/c/claw/gates.c regenerated
(only the count, the new row and the census test name differ) and both seals
re-saved with the master-built compiler. Workflow file names and NAMES now
match one to one (68 = 68).

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
gHashTag added a commit that referenced this pull request Oct 25, 2026
@gHashTag
spec(t27os): version digits from the release constants; seal the 35 n…
70e3073 
…ever-sealed specs (Closes #12372) (#12373)

* spec(t27os): track the version digits by the release constants; seal the 35 never-sealed specs (Closes #12372)

plist_main's test asserted the hard-coded digits '0.1.1' while release.t27
carries VERSION_PATCH=3 -- the version moved and the test kept reading the
old digit, failing on master under BOTH backends (invisible in the reference
until #5980 let an import-carrying module compile). The test now reads the
digits from version_major/minor/patch of current_version(), the same
constants the plist is built from, so a bump never breaks it silently again.
1/1 under t27c test-report and 1/1 under t27b.

The sweep that found it also measured the whole family: 70/70 specs green
under the reference (100% each) -- the first time every t27os spec runs
under t27c -- and 69/70 under t27b (1016/1017 tests; hdmi_grab_main's
[*:0]const u8 is a t27b construct gap, #6198 territory). The 35 specs that
could not be sealed while the reference refused them -- glass_window,
pty_server, profile_host, keys_host and 31 more -- carry their gen seals
now (data only: .trinity/seals/*.t27os_*.json); every seal verifies and
check_seal_currency reports zero stale t27os entries.

* claw(gates): t27os joins the gate inventory; re-seal the wave-drifted specs; re-bless the census

gate-topology's claw-drift step failed on every open PR because #12330
landed .github/workflows/t27os.yml without its row in specs/claw/gates.t27
-- a workflow file cannot land without its row, and the row cannot outlive
its file. t27os joins at its alphabetical place (68 rows, class blocking,
event pull_request), COUNT 67 -> 68, loops and census pins follow, the
negative control in coverage_report_carries_every_class moves to the now
unprinted n=62, and gen/c/claw/gates.c is t27c gen-c output of the spec.
The exact CI harness (cc + ls *.yml | claw-audit) passes locally: 'matrix
is current', exit 0. 24/24 under t27c test-report and 24/24 under t27b.

spec-guards found 8 stale gen hashes (JitSemantics, PackedVsa, TriBuilder
x aliases) -- gen output drifted under the merged compiler wave while the
seals stayed; re-sealed from the same tree, check_seal_currency reports
zero stale. cli-tri's census (workflow files read 67 -> 68, quiet.txt and
shell.txt) is re-blessed with a docs/now note saying so -- the 68th
workflow file is the t27os gate this lane asked for.
@gHashTag
gHashTag deleted the ci-t27os-app branch October 26, 2026 03:42
gHashTag added a commit that referenced this pull request Oct 26, 2026
@gHashTag @claude
fix(gen-verilog): a cast to a wider integer widens the Verilog expres…
a151a9c 
…sion (Closes #12296) (#12338)

* fix(gen-verilog): a cast to a wider integer widens the Verilog expression (Closes #12296)

The ExprCast arm of gen_verilog_expr printed the operand of `x as u64`
verbatim. Verilog sizes an expression to its widest operand, so
`(a as u64) + (b as u64) > (lim as u64)` over u32 inputs stayed a 32-bit
add and wrapped, while the interpreter (test-report runs zig) computed it
at 64 bits: t27c test-report said 42 of 42 and vvp failed
mem_access_past_the_page_traps on the WASM cell.

A cast to a wider integer target now emits an explicit extension:
zero-extending `{{(W-N){1'b0}}, op}` for an unsigned operand,
sign-extending `{{(W-N){($signed(op) < 0)}}, op}` for a signed one,
wrapped in `$signed(...)` for a signed target. The enclosing expression is
then sized by the cast target, so sums and comparisons run at the widened
width. Literal, unknown-width, float and 32-bit-plus signed-composite
operands keep their old forms.

Also: unit tests test_verilog_cast_width_correct (adds the u32 -> u64 sum
and an i32 -> i64 case), test_verilog_cast_no_as_keyword and
accepts_valid_cast_as_control follow the new text; the corpus spec
specs/fpga/w5_cast_widen.t27 with its icarus baseline is the regression
witness; tools/elab_baseline.txt gains the row `w5_cast_widen 0` (the
ratchet reads specs/fpga by directory); bootstrap/stage0/FROZEN_HASH moves
with compiler.rs.

Refs #9367

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

* chore(seal): FROZEN_HASH regenerated for the merged compiler.rs (Refs #12296, Refs #9367)

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

* chore(census): re-bless for t27os.yml, which arrived on master with the ledgers un-moved (Refs #12296, Refs #11788)

The census moved because #12330 added .github/workflows/t27os.yml on master
and did not re-bless: workflow files read 67 -> 68, jobs 96 -> 97, run: steps
329 -> 331, runner-named shells 308 -> 310. Written by tri census pin --bless,
checked by tri census pin --gate (rc 0). Data only, no code.

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

* chore(seal): re-seal 235 seal files whose Verilog moved with the cast-widening fix (Refs #12296, Refs #9367)

The emitter now extends a cast to a wider integer explicitly, so the
Verilog of 220 specs (235 seal files with their twins) changed. In every
one of them gen_hash_verilog is the only generated hash that moved;
gen_hash_zig, gen_hash_rust and gen_hash_c are unchanged. The re-seal also
refreshes built_by and, where it had gone stale, the test_runner hash.
Written by tri seals drift --fix plus t27c seal specs/t27f/face.t27 --save
(that one aborts in a build with overflow checks, array_size - 1 at
compiler.rs:15134 on master, so the binary was built with
CARGO_PROFILE_DEV_OVERFLOW_CHECKS=false, which matches the release build).

The four stale seals that master already carries (GitDiff, git_GitDiff,
TriBuilder, pipeline_TriBuilder: specs/git/diff.t27 and
specs/tri/pipeline/builder.t27 changed after sealing) are left alone;
#12348 and #12350 own them.

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

* chore(seal): re-seal the three specs whose Verilog moved after merging master (Refs #12296, Refs #9367)

Merging origin/master (27 commits) conflicted in three seal files:
fpga_wasm_opcodes, t27f_a11y_mirror and t27os_T27osAgentParts. Each
took master's version and was re-sealed with the cast-widening emitter,
so only gen_hash_verilog (plus built_by and sealed_at) differs from
master. Six seals that my earlier re-seal had written against the older
spec (JitSemantics, PackedVsa, TriBuilder and their twins) are restored
to master's versions: master moved those specs and re-sealed them, and
its seals already match the emitter output.

tri seals drift: 0 specs moved. check_seal_coverage: OK, no gen-drift and
no stale. check_seal_currency: 0 stale. tri census pin --gate: PASS.
compiler.rs is still 40 added / 40 deleted against master and matches
bootstrap/stage0/FROZEN_HASH.

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

* chore(seal): re-seal analog raw_writer and sar_switch after merging master (Refs #12296, Refs #9367)

Merging ten more commits of origin/master conflicted in two seal files,
analog_AnalogRawWriter and analog_AnalogSarSwitch. Each took master's
version and was re-sealed with the cast-widening emitter, so only
gen_hash_verilog (plus built_by and sealed_at) differs from master.

tri seals drift lists nothing else of mine. The remaining stale pair,
StorageKv and storage_StorageKv, comes from master: specs/storage/kv.t27
changed there after it was sealed, and this branch touches neither file.
compiler.rs is still 40 added / 40 deleted against master and matches
bootstrap/stage0/FROZEN_HASH.

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

* chore(seal): re-seal analog mos_table after merging master (Refs #12296, Refs #9367)

Merging nine more commits of origin/master conflicted in one seal file,
analog_AnalogMosTable. It took master's version and was re-sealed with
the cast-widening emitter, so only gen_hash_verilog (plus built_by and
sealed_at) differs from master.

tri seals drift lists nothing else of mine. The remaining stale pair,
StorageKv and storage_StorageKv, comes from master: specs/storage/kv.t27
changed there after it was sealed (fix: #12386), and this branch touches
neither file. compiler.rs is still 40 added / 40 deleted against master
and matches bootstrap/stage0/FROZEN_HASH.

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

* chore(seal): re-seal t27f frame_render after merging master (Refs #12296, Refs #9367)

Merging b1a5857 of origin/master conflicted in one seal file,
t27f_frame_render. It took master's version and was re-sealed with the
cast-widening emitter, so only gen_hash_verilog (plus built_by and
sealed_at) differs from master.

tri seals drift listed nothing else. compiler.rs is still 40 added /
40 deleted against master and matches bootstrap/stage0/FROZEN_HASH.

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

* chore(seal): re-seal t27os provider_profile after merging master (Refs #12296, Refs #9367)

Master's b1a5857 brought in the provider_profile spec with a seal made
by the master emitter. Its gen_hash_verilog moves with the cast-widening
emitter, so it was re-sealed; only gen_hash_verilog (plus built_by and
sealed_at) differs from master.

The FpgaHdmiGrab seal is left alone: it was sealed on 2026-10-20 and its
spec_hash no longer matches hdmi_grab.t27 on master itself, which this
branch does not touch. compiler.rs is still 40 added / 40 deleted against
master and matches bootstrap/stage0/FROZEN_HASH.

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

* chore(seal): re-seal four specs after merging master (Refs #12296, Refs #9367)

Merging origin/master into the branch conflicted in three seal files
(analog_AnalogSarComparator, analog_AnalogSarComparatorQ,
t27os_T27osAgentParts). The master versions were taken and the specs
re-sealed with the cast-widening emitter. tri seals drift also listed
t27os/hot_reload, whose only moved hash is gen_hash_verilog.

Against master only gen_hash_verilog (plus built_by and sealed_at, and the
nested import spec_hash of sar_comparator_q and agent_parts) differs.
The doctor, glass_window, lab_publish, pty_server and receipt_name seals
moved in every hash, so they are master's stale seals and are left alone.

compiler.rs is still 40 added / 40 deleted against master and matches
bootstrap/stage0/FROZEN_HASH.

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

* chore(seal): re-seal analog sar_comparator after the second master merge (Refs #12296, Refs #9367)

Master's 0fd2a8c changed specs/analog/sar_comparator.t27 and re-sealed
it. The merge kept this branch's older seal; master's file was restored
and re-sealed with the cast-widening emitter. Against master only
gen_hash_verilog (plus built_by and sealed_at) differs, and tri seals
drift lists nothing else.

compiler.rs is still 40 added / 40 deleted against master and matches
bootstrap/stage0/FROZEN_HASH.

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

* merge: resolve seal artefacts and FROZEN_HASH to master's version

* chore(seal): re-freeze compiler.rs and re-seal three wasm specs after merging master (Refs #12296, Refs #9367)

Merging origin/master (853a782, with the BRAM-shape emitter change of
#12297) conflicted in bootstrap/stage0/FROZEN_HASH and in the seals of
fpga/wasm_board_ax7203, fpga/wasm_opcodes and tri/t27b/wasm. The merged
compiler.rs hash is recorded in FROZEN_HASH again, and the three seals
were taken from master and re-saved with the merged emitter.

Against master only gen_hash_verilog (plus built_by and sealed_at) differs
in those seals, and tri seals drift lists nothing else.

compiler.rs is still 40 added / 40 deleted against master.

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

* chore(seal): re-seal t27f spec_graph_fold and spec_graph_view after merging master (Refs #12296, Refs #9367)

The branch on the remote had taken two master merges while this branch was
being fixed. After integrating both, tri seals drift lists four specs. Two
of them (t27f/spec_graph_fold and t27f/spec_graph_view) moved only in
gen_hash_verilog, which is the cast-widening emitter, and are re-sealed
here. The other two (crons/t27os-night-loop and t27os/hive_feed_acceptance)
moved in every hash including spec_hash, so they are master's stale seals
and are left alone.

compiler.rs is still 40 added / 40 deleted against master and matches
bootstrap/stage0/FROZEN_HASH.

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

* chore(seal): re-seal four specs after merging master (Refs #12296, Refs #9367)

Merging origin/master (8384eb9) conflicted only in four t27os seals.
Earlier merges on this branch had kept stale copies of twelve files that
master had since rewritten (wasm_board_ax7203, wasm_opcodes, the fpga
verilog and workflow files, the night-loop spec, the census ledgers). This
merge takes master's side, so the PR differs from master again only in
compiler.rs, its frozen hash, w5_cast_widen and the seals.

tri seals drift then lists six specs. Four moved only in gen_hash_verilog,
which is the cast-widening emitter, and are re-sealed here: fpga/wasm_board_ax7203,
fpga/wasm_opcodes, t27os/release, t27os/statusbar. The other two
(crons/t27os-night-loop and t27os/hive_feed_acceptance) moved in every hash
including spec_hash, so they are master's stale seals and are left alone.

compiler.rs is still 40 added / 40 deleted against master and matches
bootstrap/stage0/FROZEN_HASH.

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

* chore(seal): re-seal claw merge_judge and pr_tools after merging master (Refs #12296, Refs #9367)

Master (6b9fa51) re-sealed claw/merge_judge and claw/pr_tools. Both moved
only in gen_hash_verilog under this branch's cast-widening emitter, so they
are re-sealed here. tri seals drift now lists only crons/t27os-night-loop
and t27os/hive_feed_acceptance, which are master's stale seals (every hash
moved, including spec_hash) and are left alone.

compiler.rs is still 40 added / 40 deleted against master and matches
bootstrap/stage0/FROZEN_HASH.

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

* chore(seal): re-seal t27f scene after merging master (Refs #12296, Refs #9367)

Merging origin/master (9a6e4e7) was clean with -X theirs. The PR differs
from master only in compiler.rs, its frozen hash, w5_cast_widen and the
seals. tri seals drift lists eight specs: specs/t27f/scene moved only in
gen_hash_verilog (the cast-widening emitter) and is re-sealed here. The
other seven (crons/t27os-night-loop, t27f/a11y_mirror, t27f/hud,
t27f/work_graph, t27os/hive_feed_acceptance, t27os/lab_legs,
tri/t27b/wasm) moved in spec_hash too, so master's spec changed without a
re-seal; they are master's stale seals and are left alone.

compiler.rs is still 40 added / 40 deleted against master and matches
bootstrap/stage0/FROZEN_HASH.

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

---------

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
@gHashTag gHashTag mentioned this pull request Oct 31, 2026
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

owner-approved-foreign Owner-approved exception to the only-t27 rule: hand-written foreign code allowed in this PR

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

t27b: glass_window.t27 fails on master -- type mismatch (expected f64, found a pointer) blocks make t27os

1 participant

@gHashTag