Skip to content

Implement part 2 of 3 of the empty bodies in specs/file/watcher.t27 (8 functions) - #4344

Closed
gHashTag wants to merge 2 commits into
masterfrom
queen-3853
Closed

gHashTag wants to merge 2 commits into
masterfrom
queen-3853

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Closes #3853

Written by a bee on queen-3853 and published by tools/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.

1 file changed, 139 insertions(+), 7 deletions(-)

🤖 Generated with Claude Code

Trinity Bee and others added 2 commits September 19, 2026 17:35
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: #3853
Turn: e025844f-725a-4065-bc3b-7277d01a254e
Ending: finished (the turn closed)
Committed: 1 path(s)
Left uncommitted: 0 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 #3853

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

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-09-20 12:43:21 UTC

Summary

Status Count
Total Open PRs 29
PRs with Failing Checks 23
PRs with All Checks Green 6
READY 2
FAILING 23
PENDING 0
NO CHECKS YET 0

These columns do not partition: 2 + 23 + 0 + 0 = 25, and there are 29 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=403499176a5d != 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).

@github-actions

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@gHashTag

Copy link
Copy Markdown
Owner Author

Closing: this is Rust, not .t27, and the parse ratchet caught it.

$ parse-ratchet on this branch
changed specs: 1; newly unparseable: 1; repaired: 0
Error: parse error in fn 'set_filter' near line 123:
  Unexpected token in expression: RParen (')') at line 123:28

Line 123 and its neighbours:

                return Ok(());
        ...
        return Err(FileError::WatcherNotFound);

.t27 has no Ok(()), no Err(E::V) and no 0..n range loop. It accepts
eight top-level forms and no others -- const, var, fn, enum, struct, test, invariant, bench -- and a spec that does not parse generates nothing, so every
test it carries stops running.

The branch is left in place. The brief is what needs fixing, not this pull
request: it names the boundary and the criteria and never says which language
the file is in, which is how a bee that writes fluent Rust ends up here. That is
being added to the shared preamble every feeder embeds.

@gHashTag gHashTag closed this Sep 20, 2026
auto-merge was automatically disabled September 20, 2026 13:40

Pull request was closed

gHashTag added a commit that referenced this pull request Sep 20, 2026
A bee filled eight empty bodies in specs/file/watcher.t27 with `return Ok(());`,
`Err(FileError::WatcherNotFound)` and `for i in 0..watchers.length`.
parse-ratchet refused the file - `Unexpected token in expression: RParen at line
123:28` - and a spec that does not parse generates nothing, so every test the
file ALREADY carried stopped running. #4344 is closed with that measurement.

The brief named the boundary, the criteria and the instruments, and never said
which language the file was in. A bee fluent in Rust writes Rust.

docs/BEE_TOOLBELT.md now opens with `## What the language accepts` - the eight
top-level forms and the five idioms reached for from elsewhere - and
tools/toolbelt.py puts that block FIRST in every issue every feeder opens.

The document's own rule bit back while writing it: a list item whose first
backtick span is a command IS one, and `tri toolbelt` tried to run `Ok(())`.
The bullets read prose-first now and `--check` is green.

And a refused pull request no longer sentences its issue: refile.py counted a
pull request in ANY state as delivery, so an issue whose only attempt was
closed unmerged could never be re-filed. OPEN and MERGED only.

Closes #4442

Co-authored-by: Claude <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.

Implement part 2 of 3 of the empty bodies in specs/file/watcher.t27 (8 functions)

1 participant