From 412e5bf450b13c11990e29b19f8aa4032b3f977a Mon Sep 17 00:00:00 2001 From: Trinity Bee Date: Wed, 23 Sep 2026 15:44:29 +0000 Subject: [PATCH 1/2] salvage(queen-2527): 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: #2527 Turn: ef258bb0-e964-4a39-8bfd-71d8f0decea1 Ending: finished (the turn closed) Committed: 1 path(s) Left uncommitted: 0 path(s) outside the declared boundary --- specs/lsp/server.t27 | 3 --- 1 file changed, 3 deletions(-) diff --git a/specs/lsp/server.t27 b/specs/lsp/server.t27 index 0779a63931..edf067d6db 100644 --- a/specs/lsp/server.t27 +++ b/specs/lsp/server.t27 @@ -9,11 +9,8 @@ module lsp-server; // Imports // ============================================================================ -use lsp-schema::Position; use lsp-schema::Range; use lsp-schema::Diagnostic; -use lsp-schema::DiagnosticSeverity; -use lsp-schema::CompletionItem; use lsp-schema::DocumentSymbol; // ============================================================================ From 3a0867279640003bd88e70f83f184bdbd5ecbf11 Mon Sep 17 00:00:00 2001 From: "queen-publisher[bot]" Date: Wed, 23 Sep 2026 15:54:53 +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 #2527 Co-Authored-By: Claude Opus 5 --- ...ort-emitted-per-use-decl-correct-fix-zero-measu.md | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 docs/now/2026-09-23-published-duplicate-import-emitted-per-use-decl-correct-fix-zero-measu.md diff --git a/docs/now/2026-09-23-published-duplicate-import-emitted-per-use-decl-correct-fix-zero-measu.md b/docs/now/2026-09-23-published-duplicate-import-emitted-per-use-decl-correct-fix-zero-measu.md new file mode 100644 index 0000000000..4d411e67b2 --- /dev/null +++ b/docs/now/2026-09-23-published-duplicate-import-emitted-per-use-decl-correct-fix-zero-measu.md @@ -0,0 +1,11 @@ +# NOW -- Duplicate @import emitted per use-decl: correct fix, zero measured gain (published 2026-09-23) + +## A bee's work on #2527, published from `queen-2527` (Closes #2527) + +- The branch changes 1 file(s): `specs/lsp/server.t27`. +- `git diff --stat origin/master...queen-2527` reads: 1 file changed, 3 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.