Repository navigation
E2c: eth_reply.t27 -- the receipt as a unicast UDP datagram to the requester (AX7203) - #8490
Merged
Merged
Conversation
The turn ended with these files edited and never committed. Uncommitted work is invisible to the review - it reads the branch - so the attempt would have been released as empty and the next bee would have started beside this work rather than from it. This commit is not a claim that the work is correct. It is the bee's work, committed on its behalf, and it is judged exactly like any other: the adversarial reviewer reads it, the compiler runs on it, and the issue's own criteria are measured against it. Issue: #8388 Turn: bb6553d6-85bd-46d8-a548-2c85037f0f8a Ending: finished (the turn closed) Committed: 2 path(s) Left uncommitted: 1 path(s) outside the declared boundary
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 #8388 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
gHashTag
enabled auto-merge (squash)
October 10, 2026 09:27
This was referenced Oct 10, 2026
Contributor
This was referenced Oct 10, 2026
This was referenced Oct 10, 2026
gHashTag
added a commit
that referenced
this pull request
Oct 10, 2026
…st (Refs #8534) (#8535) - duplicate bodies: crc_byte/crc_step 2->3 -- third copy of the table-driven CRC32C landed with #8490 (specs/fpga/eth_reply.t27; lineage packets.t27 -> eth_beacon.t27 -> eth_rx.t27); specs are self-contained, the copy is the honest shape, the ledger records it - type conflicts: Episode, Pair, SkipList new (85->88), all from port PRs keeping upstream type names; readings written: SkipList DRIFT (generic SkipList(T) vs the concrete gen_skiplist_impl port), Episode and Pair DISTINCT (provenance record vs loop-step; fixture vs manifest vs payload) - regenerated with a fresh tri/t27c build on the Railway lab at 32b8632; tri types classified passes: 88/88 judged, 0 stale Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
gHashTag
added a commit
that referenced
this pull request
Oct 10, 2026
…observes the accept edge (#8564) * fix(fpga): trinet_node j_go test observes the strobe on the accept edge, not a cycle late (Closes #8553) j_go is registered on the accept edge (the nonblocking idiom at the top of on_clock), so the one-cycle strobe is high in exactly the cycle after on_clock(0,0,0,1,1). #8490's test opened its 100-clock observation window only after that call and counted 0 pulses. Assert the strobe right after the accept edge, then require 0 pulses in the window that follows; the sibling j_go_stays_low test already reads it this way. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * seals: reseal the #8415 FROZEN_HASH wave -- 56 seals regenerated with zig on the lab (Refs #8553) 43b810a moved FROZEN_HASH with compiler.rs, so every generated target changed bytes; every seal not regenerated since then reported [stale] -- 56 at this branch (testbenches, Ternary* ISA, TriMath/TriMeasurement/ TriBellmanFord, SpecWriter, bench_main, lsp, functions_fn_monitoring_*, and twins, including the legacy pipeline_"[]const u8".json). Each was re-sealed per the checker prescription (t27c seal <spec> --save) with zig on PATH so the test record is real, then tri seals sync-twins. The j_go test fix in the previous commit is what made fpga_TrinetNode sealable. The lab gate on this exact tree: exit 0, zero stale, zero gen-drift. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #8388
Written by a bee on
queen-8388and published bytools/queen/publish.py. The branch itself is the bee's; the second commit is the coordination entry every pull request must add, which a bee has no way to know about.🤖 Generated with Claude Code