Merge queue: dmitrii-f-t27 PRs ready (2026-10-11) #9136

Activity

1. dmitrii-f-t27 commented on Oct 11, 2026

   

   dmitrii-f-t27

   on Oct 11, 2026

   ContributorAuthor

   More actions

   @gHashTag, please merge these 13 PRs. All of them are from my fork; I cannot merge in gHashTag/t27. State checked at 2026-10-11 15:45Z against master 19ef6da00: every PR below is MERGEABLE (no conflicts), and the four required checks validate, check-linked-issue, parse-ratchet and own-language pass on its current head.

   The red checks are not required, and each one is red on master with the same findings:

   Key	Check	Master run
   A	Corpus ratchet (types: Entry/Inputs/SkillMeta)	38146939229 (master 5e5493c)
   B	coverage (queen_QueenHolds gen-drift)	38146939200 (master 5e5493c)
   C	spec-guards (queen_QueenHolds stale gen_hash_rust)	38146939153 (master 5e5493c)
   D	t27b-native-ratchet (same UNLISTED set, 0 unexpected)	38146939191 (master 5e5493c)
   E	cli-tri (census quiet 185->188, shell 305->306)	38145387223 (master a314273; path-filtered, did not run on 5e5493c)
   F	fpga-lint (eye_isi, line_bounce, xc7_primitives)	38146330915 (master 9b4338a)
   G	fpga-conformance (same NEW elab set)	38146330915 (master 9b4338a)

   #	PR	Head	Required	Red, also red on master	Closes
   1	#8842	0375bb7ee	4/4 pass	A B E	#7927
   2	#8876	b05f8e088	4/4 pass	D (same 56 UNLISTED as merge-base 337b1d4, 38133824397)	#5614
   3	#8538	cb75ec2db	4/4 pass	A B	#8536
   4	#8749	c2bd66d6d	4/4 pass	A B C D E	#8745, #8752, #8756, #8767
   5	#8771	35496172f	4/4 pass	A B C D E	#8762
   6	#8532	ea7ee772c	4/4 pass	A B C D E F G	#8530
   7	#8772	7581137f4	4/4 pass	A B C D E F G	#8770
   8	#8890	c9ab3e78d	4/4 pass	A B C D E F G	#8875, #8889
   9	#8843	d1318cd7d	4/4 pass	A B C D E	#5744
   10	#8768	4b6ee3b82	4/4 pass	A B C D E	#8765
   11	#9131	b48e46bd5	4/4 pass	A B C D E	none (Refs #8880)
   12	#8844	f042d0009	4/4 pass	A B C D E F G	#5649, #5650, #5651
   13	#9135	f6de37aee	4/4 pass	A D E F G	#8891

   Order.

   • tools/jtag: libftdi from $T27_LIBFTDI or the platform default, so B2 reads on Linux (Closes #7927) #8842, isa: S05 TRI-27 specs state the emulator fixed in gHashTag/trinity#1250 (Closes #5614) #8876 and docs(fpga): HARDWARE_SSOT records the TRI-NET node answering jobs over UDP #8538 share no files with the others. They can go in any order.
   • fix(specs): restore native JTAG verdict literals #8771 contains the head of fix(specs): restore executable policies and corpus checks #8749, so fix(specs): restore executable policies and corpus checks #8749 goes first. After fix(specs): restore executable policies and corpus checks #8749 merges, I close fix(memory): restore executable graph ingest policy #8755: its code is in fix(specs): restore executable policies and corpus checks #8749.
   • fix(fpga): eth_reply.t27 sends one frame per receipt, to the sender, with a real checksum #8532 -> fpga: the TRI-NET node's 100 Mb/s board logic in t27 (MDIO, RGMII nibbles, JTAG status) (Closes #8770) #8772 is the E2 chain from epic E2: TRI-NET node over UDP on the AX7203 (Ethernet job link instead of UART) #8327. t27b verilog: pin declarations, and the TRI-NET board top in .t27 with no hand Verilog or XDC (Closes #8889) #8890 does not depend on it at source level.
   • fix(specs): restore executable policies and corpus checks #8749, fix(specs): restore native JTAG verdict literals #8771, fix(fpga): eth_reply.t27 sends one frame per receipt, to the sender, with a real checksum #8532, fpga: the TRI-NET node's 100 Mb/s board logic in t27 (MDIO, RGMII nibbles, JTAG status) (Closes #8770) #8772, t27b verilog: pin declarations, and the TRI-NET board top in .t27 with no hand Verilog or XDC (Closes #8889) #8890, specs/policy: linked_issue_prose states what check-linked-issue reads (Closes #5744) #8843, spec(queen): claim.t27 - the round's stateOfDispatch as a card, the review valve imported (Closes #8765) #8768, Port trios-chat CR-CHAT-00: lib.rs data and decisions as lib.t27 (Refs #8880) #9131 and gen-verilog: an entry parameter named clk/rst_n/en is declared once; a void body's last call stays a statement (Closes #5649, Closes #5650, Closes #5651) #8844 each add rows to docs/reports/t27b_expectations.json. If an earlier merge makes one of them CONFLICTING, I merge master into it and re-seal with the t27c built from that tree. I do not rebase or force-push.
   • gen-verilog: an entry parameter named clk/rst_n/en is declared once; a void body's last call stays a statement (Closes #5649, Closes #5650, Closes #5651) #8844 and gen-rust: eight constructs that passed test-report now compile under rustc (Closes #8891) #9135 both change bootstrap/src/compiler.rs and bootstrap/stage0/FROZEN_HASH. The second one needs a master merge, a new FROZEN_HASH and a re-seal. gen-rust: eight constructs that passed test-report now compile under rustc (Closes #8891) #9135 also needs your approval as Architect for the FROZEN_HASH change (FROZEN.md section 5, step 2).
   • spec(queen): claim.t27 - the round's stateOfDispatch as a card, the review valve imported (Closes #8765) #8768 unblocks feat(queen): the round's claim is decided by the claim card, proven equal to the hand-written rule first (Closes #1767) trios#1768, which vendors specs/queen/claim.t27.

   Each PR has its own comment with the per-check evidence. The earlier requests in epic #8327 and in #8768 are covered by this list.

   Dmitrii Fedorov (@dmitrii-f-t27)
2. github-actions

   added

   shape-refusedClosed by the issue-shape gate (specs/policy/issue_shape.t27); a passing edit reopens itClosed by the issue-shape gate (specs/policy/issue_shape.t27); a passing edit reopens it

   on Oct 11, 2026
3. github-actions commented on Oct 11, 2026

   

   github-actionsbot

   on Oct 11, 2026 – with GitHub Actions

   Contributor

   More actions

   Closed by the issue-shape gate (specs/policy/issue_shape.t27, #7498): an issue must have the template's sections. Edit the body; an edit that passes reopens it.

   • missing: ## Boundary -- list every file this task may touch, one per line (- specs/x.t27); without it the Queen reserves nothing and no bee can take the issue
   • missing: ## User Scenarios -- at least one Given/When/Then scenario
   • missing: ## Requirements -- numbered obligations, FR-001: ... MUST ...
   • missing: ## Success Criteria -- an outcome a machine can settle: a number with a unit, a backticked file, exit 0, or a backticked command
4. github-actions

   closed this as not plannedon Oct 11, 2026