Skip to content

gates: has_at is a deliberate copy; no home path in the t27b-loop skill; 12 t27b rows (#8361) - #8375

Merged
dmitrii-f-t27 merged 1 commit into
masterfrom
fix/master-gates-8361
Oct 9, 2026
Merged

dmitrii-f-t27 merged 1 commit into
masterfrom
fix/master-gates-8361

Conversation

@dmitrii-f-t27

Copy link
Copy Markdown
Contributor

Closes #8361

Replaces #8362: one commit on current master with the issue keyword in it (L1 TRACEABILITY needs Closes/Refs #N in every commit, and a pushed branch is not rewritten), plus the t27b rows #8362 was still missing.

Description

Three gates are red on master and so on every open PR. Each change removes one cause:

Testing

python3 tools/dupe_scan.py            # no error
python3 tools/check_devhome_paths.py  # OK: 30 file(s), 38 occurrence(s), all pinned
./scripts/tri t27b ratchet --run run.json   # run 37993522616: none of the 12 is UNLISTED any more

The last command still reports differences that master made after that run (two new conformance specs, ocp_mx.t27 after an @intCast change) and eth_rx.t27, which is #8370's. This PR's own t27b-native-ratchet run on current master is the check that counts.

Review Notes

Found while working on #8370 (EthRx) and #8373 (TrinetNode), whose checks are red only for these causes.

…ll; 12 t27b rows

Closes #8361

duplicate-bodies: has_at (specs/tri/t27b/ast_walk.t27, #8258) is the body of
starts_with (source_text.t27). An import typechecks and ast_walk's 18 tests
pass, but t27c gen-rust emits the call without a `use`, and
cli/t27b/src/lower.rs mounts ast_walk.rs as its own module, so cli/t27b would
not build. One line, has_at 2.

scan: the skill read `git -C /Users/playom/t27 config --get core.hooksPath`;
every worktree shares that config, so `git config --get core.hooksPath` says
the same without a developer's home path.

t27b-native-ratchet: rows for the 12 specs the ratchet listed as UNLISTED in
run 37993522616 (t27b-native on ef75683), each as that run judged it with
the reference passing: 10 pass, base/types.t27 blocked on `type [N]T`,
math/constants.t27 blocked on `ExprCall(@Rem)` (both unimplemented).
max_not_pass 18 -> 20, the two new blocked rows; no existing row moves.
@github-actions

github-actions Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-09 21:47:05 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)=557cd271f4e3 != 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).

@dmitrii-f-t27
dmitrii-f-t27 merged commit fca3f76 into master Oct 9, 2026
29 checks passed
gHashTag added a commit that referenced this pull request Oct 10, 2026
Revive #6500 after 19 days stale. Each of the 7 mcp specs keeps a
verify_<server>_constants test (the pattern the four already-covered specs
in this directory use) and now asserts the rows only its own card holds:
TRANSPORT (http only for inngest-dev), REPO/QUALIFIED_ID split across
gHashTag/t27 and gHashTag/trinity, EXTERNAL, agent letters beyond T,
TOOLS/RESOURCES/ENV lengths, names and indexes. 89 asserted values
crosschecked against the const declarations in the same files.

Merge of origin/master picks up the fixes this branch was red on in
2026-10-06: orbitofrontal_value.t27 parse (#6861), repo-relative t27a
seals (#6861), the devhome-path scan fixes (#8375) and the dupe-bodies
ledger rows for carries_src2/sample_imm/sample_reg.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
gHashTag added a commit that referenced this pull request Oct 10, 2026
)

* Add test blocks to MCP specs for t27b coverage

Each spec now has a test block with 4 assertions that verify
basic constants. This moves these specs from pass_vacuous to
checked passes in t27b coverage.

Closes #6500

* docs: the coordination entry this branch needs to land

A pull request must add exactly one docs/now entry and a bee has no way
to know that: its brief names a boundary file and acceptance criteria,
and docs/now/ is neither. The publisher adds it rather than failing the
gate.

Closes #6500

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* t27b checked: per-spec test blocks for 7 specs in specs/tools/mcp

Revive #6500 after 19 days stale. Each of the 7 mcp specs keeps a
verify_<server>_constants test (the pattern the four already-covered specs
in this directory use) and now asserts the rows only its own card holds:
TRANSPORT (http only for inngest-dev), REPO/QUALIFIED_ID split across
gHashTag/t27 and gHashTag/trinity, EXTERNAL, agent letters beyond T,
TOOLS/RESOURCES/ENV lengths, names and indexes. 89 asserted values
crosschecked against the const declarations in the same files.

Merge of origin/master picks up the fixes this branch was red on in
2026-10-06: orbitofrontal_value.t27 parse (#6861), repo-relative t27a
seals (#6861), the devhome-path scan fixes (#8375) and the dupe-bodies
ledger rows for carries_src2/sample_imm/sample_reg.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* docs(now): the revived branch's real diff stat

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Trinity Bee <bee@trinity.local>
Co-authored-by: queen-publisher[bot] <noreply@anthropic.com>
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.

gates: duplicate-bodies, scan and t27b-native-ratchet are red on master (has_at, hw_place_before, a home path, 10 unlisted specs)

1 participant