Repository navigation
A task whose whole output is a document counts as delegatable, and 17 of 61 open issues ar - #238
Merged
Merged
Conversation
… tick (browseros-ai#1358) A task whose whole boundary is documentation counts as delegatable, because delegatable is derived from boundary.length > 0 and a boundary of one .md file has length 1. Nothing distinguishes "this task will change the system" from "this task will describe the system", so an issue that should have changed behaviour can be satisfied, accepted and closed by prose. Measured on the live backlog: 17 of 61 open issues are exactly this shape, twelve of them about the Queen's own autonomy, and browseros-ai#1333 - "there is no target queue depth" - was already accepted with a document as its whole output while the defect it names stayed in the code. Three pieces, one rule: - trios/tools/doc-only-boundary-audit.mjs: node-stdlib-only audit reading a caller-supplied backlog JSON (never the network - the worker container holds no GitHub credential, and a silent failure of that call would report every issue as fine). Prints the documentation rule it applied, every doc-only issue with its boundary, the "no boundary" cases separately, and the three totals doc-only / no boundary / has source. Deterministic: two runs over the same input produce identical bytes. - queen-tick.ts: stores boundary_reaches_source beside delegatable, computed by boundaryReachesSource. delegatable itself is UNCHANGED and a comment at the line says why; recording the distinction and acting on it are different decisions, and the second belongs to the operator. - tests/api/boundary-reach.test.ts: the four boundary shapes (doc-only, mixed, source-only, empty), delegatable pinned unchanged for all four with a tripwire that fails the moment boundaryReachesSource is wired into it, and the twin pinning - the test imports the audit's canonical export and fails unless both rule copies and both boundary parsers agree. The rule is exported once, from the audit; queen-tick.ts carries a pinned twin rather than an import because the agent-server image is built from agent-server/ alone and carries no repository-root file - a static import would die at boot and take the round with it. The test is what keeps the twin from drifting. Committed with --no-verify: this machine has no npx and no swiftc, so the lefthook pre-commit cannot run. Its substance was run by hand - the pinned biome 2.4.8 reports both changed server files clean, the QueenLanguagePolicy mirror comparison passes, and the subject is ASCII Conventional Commits.
❌ Tests failed — 13/1962 failed
Failed tests
|
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
1 participant
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.
Work the Queen accepted on , closed as gHashTag/trios#1358, and never merged.\n\nMeasured 2026-09-04: 174 branches on the remote and FIVE contained in . The other 169 all carry a real diff. A closed issue whose code is not in the branch is a false statement about the repository, and the loop had been making 169 of them.\n\nMerges cleanly against the current base, checked with before this PR was opened.