Skip to content

Port gHashTag/BrowserOS:trios/agent-server/apps/server/src/tools/clade-improve-tool.ts (TypeScript, 1 function) to specs - #7063

Open
gHashTag wants to merge 4 commits into
masterfrom
queen-5806
Open

gHashTag wants to merge 4 commits into
masterfrom
queen-5806

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 6, 2026

Copy link
Copy Markdown
Owner

Closes #5806

Written by a bee on queen-5806 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, 47 insertions(+)

🤖 Generated with Claude Code

Trinity Bee and others added 3 commits October 3, 2026 20:52
New spec at specs/port/browseros/trios/agent-server/apps/server/src/tools/
clade-improve-tool.t27, porting trios/agent-server/apps/server/src/tools/
clade-improve-tool.ts (gHashTag/BrowserOS at 928e1624a50e, 73 lines).

Ported as decisions: runCli_allowed (the allowlist gate - exact match
against the three subcommands, so nothing else spawns the CLI whatever it
holds), runCli_verdict (exit 1 refusal before any spawn), runCli_refusal
(the constant prefix of the refusal message, gated on the allowlist), and
runCli_error_detail (stderr wins over message, empty stderr falls back).
The zod schemas, defineToolWithCategory, logger, response.text, the
default export array, and the execFileSync spawn itself stay with the
runtime: runCli keeps its name with an undefined body that no test calls.
Template-literal interpolation (lines 19 and 32) is named as unportable
rather than faked.

Six tests; parse OK, typecheck OK (0 errors, 0 warnings), test-report
6/6 pass, no not-yet-implemented markers in generated Zig.

Closes #5806
- Add runCli function with CladeCommand enum
- Port decision logic for command validation and execution
- Add comprehensive tests for all commands and error cases
- Replace execFileSync logic with pure function returns

Closes #5806
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 #5806

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

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-06 20:06:06 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 50
PRs with All Checks Green 0
READY 0
FAILING 50
PENDING 0
NO CHECKS YET 0

Seal Status

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

This was referenced Oct 6, 2026
This was referenced Oct 6, 2026
@gHashTag
gHashTag enabled auto-merge (squash) October 7, 2026 07:23
@gHashTag
gHashTag disabled auto-merge October 7, 2026 07:32
…5806, #7573)

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

github-actions Bot commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-07 18:34:19 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 48
PRs with All Checks Green 2
READY 1
FAILING 48
PENDING 0
NO CHECKS YET 0

These columns do not partition: 1 + 48 + 0 + 0 = 49, and there are 50 open PRs. A PR is being counted twice or not at all.

Seal Status

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

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants