Skip to content

fix(ci): master green -- rust_convert CSE hoist, mesh crypto mismatch, stale type row (Closes #10158) - #10160

Merged
gHashTag merged 1 commit into
masterfrom
fix/master-green-10158
Oct 18, 2026
Merged

gHashTag merged 1 commit into
masterfrom
fix/master-green-10158

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Closes #10158

Master 18c98cc is red on two ratchets, so every open PR inherits red and no PR can be judged on its own change (209 open, 9 fully green; t27b-native-ratchet red on 157 of them).

What changes

  • specs/tools/t27o/rust_convert.t27: f + 1 and fq - 1 are spelled once, so t27c's optimizer no longer hoists a _cse temporary above const f (t27b: FnDecl(reference CSE hoist)). gen/rust/tools/t27o/rust_convert.rs regenerated with t27c gen-rust; seal updated.
  • specs/port/trios/crates/trios-mesh-node/src/crypto.t27: MeshKeypair_random takes the public key and digest as parameters instead of calling undefined host primitives (the jit/interpreter mismatch). New seal.
  • docs/reports/type_conflicts_classified.json, docs/TYPE_CONFLICTS.md: drop the OptimizerStepResult row (spec(ml): arena heap + file I/O contract; adamw compiles via the arena (Closes #10077) #10088 removed the second adamw definition), DRIFT 62 -> 61.

Both spec repairs are taken from draft #9637, which also carries a workflow and Python and cannot land as is. This PR is .t27, generated output, seals and ledger data only.

Evidence (Railway lab, t27c 0.5.2+0d4fe82f2, zig 0.16.0)

  • Per-spec t27c report: rust_convert 65/65, crypto 23/23, 0 vacuous. seal --verify: all hashes MATCH for both.
  • t27b build: both specs accepted. Control: master's rust_convert is refused with FnDecl(reference CSE hoist) at line 6201.
  • Control: t27c gen-rust on master's spec reproduces master's rust_convert.rs byte for byte, so the regenerated file differs only by the spec change.
  • tri types classified: OK, 108 names. tri types ratchet: CLEAN.

🤖 Generated with Claude Code

…, stale OptimizerStepResult row (Closes #10158)

Master 18c98cc was red on t27b-native-ratchet (rust_convert: ledger pass,
now blocked by FnDecl(reference CSE hoist)) and on Corpus ratchet (tri types
classified: STALE OptimizerStepResult after #10088). Every open PR inherited
both reds.

- rust_convert.t27 / crypto.t27: the .t27 repairs from draft #9637, without
  its workflow and Python; gen-rust regenerated, both sealed with zig 0.16.
- type_conflicts_classified.json + TYPE_CONFLICTS.md: drop the stale row,
  DRIFT 62 -> 61.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@gHashTag
gHashTag enabled auto-merge (squash) October 18, 2026 02:28
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-18 02:32:09 UTC

Summary

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

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

Seal Status

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

@gHashTag
gHashTag merged commit 0951ab0 into master Oct 18, 2026
26 of 29 checks passed
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.

ci: master is red on two ratchets, so every open PR inherits red

1 participant