From 4881cd47f8908ad99d7f0761fc4333cbe3fbdc02 Mon Sep 17 00:00:00 2001 From: Trinity Bee Date: Wed, 23 Sep 2026 17:40:41 +0000 Subject: [PATCH 1/2] salvage(queen-2532): commit what the turn left uncommitted 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: #2532 Turn: 5608e45d-f424-49a9-93c7-fcdf8008040f Ending: finished (the turn closed) Committed: 1 path(s) Left uncommitted: 0 path(s) outside the declared boundary --- specs/jit/jit.t27 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/specs/jit/jit.t27 b/specs/jit/jit.t27 index 2070d20db7..f0f0fd18ea 100644 --- a/specs/jit/jit.t27 +++ b/specs/jit/jit.t27 @@ -496,7 +496,7 @@ pub fn init(allocator: *anyopaque, max_cache_size: usize) Self { /// Get or compile bind function for dimension /// Returns cached function if available, compiles new otherwise - pub fn get_bind(self: *Self, dimension: usize) ?*JitVsaFn { + pub fn get_bind(self: *Self, dimension: usize) *?JitVsaFn { // Check cache for existing function var i : usize = 0; while (i < self.cache_size) { @@ -516,7 +516,7 @@ pub fn init(allocator: *anyopaque, max_cache_size: usize) Self { } /// Get or compile bundle function for dimension - pub fn get_bundle(self: *Self, dimension: usize) ?*JitSimilarityFn { + pub fn get_bundle(self: *Self, dimension: usize) *?JitSimilarityFn { // Similar to get_bind but for bundle operation if (!self.compiler.compile_bundle(dimension)) { return null; From 5f6981f99ea234d694a1cee933aa52f9e4684e1b Mon Sep 17 00:00:00 2001 From: "queen-publisher[bot]" Date: Wed, 23 Sep 2026 18:27:02 +0000 Subject: [PATCH 2/2] 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 #2532 Co-Authored-By: Claude Opus 5 --- ...oved-by-two-events-in-one-file-jit-t27-has-func.md | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 docs/now/2026-09-23-published-the-ratchet-moved-by-two-events-in-one-file-jit-t27-has-func.md diff --git a/docs/now/2026-09-23-published-the-ratchet-moved-by-two-events-in-one-file-jit-t27-has-func.md b/docs/now/2026-09-23-published-the-ratchet-moved-by-two-events-in-one-file-jit-t27-has-func.md new file mode 100644 index 0000000000..fc80e7f7d7 --- /dev/null +++ b/docs/now/2026-09-23-published-the-ratchet-moved-by-two-events-in-one-file-jit-t27-has-func.md @@ -0,0 +1,11 @@ +# NOW -- The ratchet moved by two events in one file: jit.t27 has function-pointer return types (published 2026-09-23) + +## A bee's work on #2532, published from `queen-2532` (Closes #2532) + +- The branch changes 1 file(s): `specs/jit/jit.t27`. +- `git diff --stat origin/master...queen-2532` reads: 1 file changed, 2 insertions(+), 2 deletions(-) +- This entry is written by the publisher, not by the bee. 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. +- What this entry does NOT establish: that the work is correct. The gates on the + pull request judge that, and they are the same gates every other change meets.