Skip to content

feat(profiling): exercise Tokenjuice agent tool results - #362

Draft
vincentkoc wants to merge 5 commits into
mainfrom
feat/plugin-resource-tokenjuice-20260923
Draft

vincentkoc wants to merge 5 commits into
mainfrom
feat/plugin-resource-tokenjuice-20260923

Conversation

@vincentkoc

@vincentkoc vincentkoc commented Sep 22, 2026 •

Copy link
Copy Markdown
Member

What Problem This Solves

Crabpot has no workload proof for Tokenjuice's lazy tool-result middleware; Gateway catalog registration alone cannot show that the model received reduced output.

User Impact

Adds the opt-in tokenjuice-exec-status-v1 scenario: matched disabled/enabled embedded agent turns, real Git-status tool calls, a strict synthetic loopback provider and explicit resource observations. The default bundled campaign does not execute this external scenario; ordinary CI may still download other fixture sources.

Why This Change Was Made

Both cases install identical pinned source-built archive bytes and activate the ordinary OpenAI provider. Each runs one first-use turn and five warm turns in fresh sessions against the same synthetic repository with 32 modified tracked files. The fixture requests exactly one exec and checks its output in the second model request before returning a terminal marker. The control must receive raw Git output; the enabled case must receive shorter, marked output and six default statistics records. Automatic Activity recaps and utility-model selection are disabled equally; unexpected requests fail.

The middleware uses a caller-owned handle. Exact Gateway catalog observations remain scoped to the OpenAI dependency; actual model-visible output and statistics prove the target's work. Dependency activation earns no separate workload credit. Both cases use the landed shared workload, scoped-activation, cleanup and receipt owners; this change adds no second Gateway or measurement engine.

The adapter requires source-built @openclaw/tokenjuice 2026.9.5 with bundled tokenjuice 0.8.4. It rejects the same-version registry wrapper's different dependency closure. Native archive preparation and installation are outside measured Gateway phases. Source/build provenance and archive identity are separate from host/runtime qualification.

Git isolation now uses an empty ordinary file under the existing fixture root. Git for Windows rejects Node's null-device path when used as GIT_CONFIG_GLOBAL; the file is created before any Git child starts and remains inside the fixture's existing cleanup ownership. No startup deadline, cleanup guard or controller environment is changed.

The latest diagnostic change keeps status, signal, error and cleanupError unchanged. Failure text may include only eight exact known owner reasons and an unsigned 32-bit native error code; arbitrary messages, stack, arguments, environment, output and paths are excluded. This distinguishes known supervisor/adapter outcomes without claiming an internal parse or compile stage.

Within the Tokenjuice test file, unconfirmed cleanup retains the exact failed fixture root and blocks later native callbacks before invocation. Joined failures and unrelated roots still receive normal cleanup. Other test files continue; this is not whole-job fail-fast or proof of process extinction. Original minimal environments, tar-before-Git order and deadlines remain unchanged, with no inherited-environment warmup or shared command-owner modification.

Evidence

Landing held. This candidate improves failure diagnostics and test fixture ownership; it does not fix the unresolved Windows startup failure or establish closure for prior failed owners. The latest published required Windows job, at cdb4f5e, failed. The new diagnostic head is awaiting hosted qualification. Successful native readiness and authoritative cleanup, plus a validated final-head isolated workload receipt, remain required.

  • Current diagnostic candidate 18747a87f3122e7e82c8a46b416f0210e7e8514e: 35/35 focused builtin tests passed, with no failures, cancellations or skips, in 551.592 milliseconds. This includes real Git/tar setup and the new cleanup-cause privacy regression. Syntax, diff whitespace and public-data checks passed. Exact-head native review completed with one accepted P1: the unchanged Windows native owner still fails readiness/cleanup in the required fixture path. No additional defect in the diagnostic probe was reported; this is not a clean landing review.
  • A temporary, separate Windows 2025 / Node 24.20.0 job now observes the first JSON cmdlet inside the unchanged native Job owner. It runs only for this same-repository draft branch, emits fixed markers and bounded non-private diagnostics, and retains the fixture when closure is unknown. The original required fixtures keep their environment, tar-before-Git order and deadlines. The inherited outer bootstrap can warm shared state: passing would qualify only the contained sequence, not original cold-helper startup. This job must be removed after the investigation. No result from this new job is claimed yet.
  • Cleanup diagnostics additionally preserve only an allowlisted nested cause code; missing and unrecognized causes remain distinct. The original four outcome fields and all shared command-owner bytes remain unchanged. New-head hosted Windows readiness/closure and a validated final-head matched Gateway receipt remain pending. This intermediate draft update does not repair the startup failure, waive a safety or CI gate, or authorize landing.

Retained earlier evidence

  • Prior signed candidate cdb4f5e25b0f9f04528e2c37a42768192203c546 preserves the owned workload integrated onto frozen main 407299b17af54c48ffc117c2536097f6c40bcc6e, the fixture-owned Git configuration repair, and adds bounded diagnostics and test-local fixture retention/admission. All landed shared owners, Session Share's late-fault repair, existing scenarios, scheduled workflow and generated reports are preserved. The command owner, startup/cleanup budgets and environment forwarding are unchanged.
  • At prior cdb4f5e, 34/34 focused builtin Tokenjuice tests passed, no failures or skips, on Node 26.7.0/macOS in 1.555 seconds for this candidate. They cover real Git/tar setup, loopback Responses, strict outcomes, diagnostic privacy, retained uncertain roots, rejected later native admission and normal cleanup after joined failures. The broader 217-test result belongs to prior 5198b26; it is not a rerun on this diagnostic candidate.
  • Focused tests exercise actual temporary Git/tar setup and the loopback Responses fixture. Synthetic compacted unit-test output validates the observer; it is not real-plugin execution.
  • Adapter/test syntax, diff whitespace and the public-data scrub passed.
  • Independent source review of the diagnostic increment is clean. The prior cdb4f5e native review completed with exit 1 and one P1: fix Windows owner startup before admitting these native fixtures. It cites the existing hosted readiness/cleanup failure; that landing blocker is accepted and unresolved. No additional defect in the diagnostic or test-retention change was reported. The review is not claimed clean, and the retained failure does not identify an internal startup stage or establish a production root cause. ClawSweeper Revision 10 covers exact cdb4f5e with no additional code or security findings. Its before-merge requirements and Rank-up moves retain successful final-head hosted Windows tar/Git readiness and authoritative cleanup, plus a validated isolated matched-pair receipt; the draft hold remains until both are satisfied. Both requirements remain unsatisfied.
  • On exact cdb4f5e, the required Windows job failed: 604 passed, 2 failed, 27 skipped, 0 cancelled out of 633 tests, on Node 24.20.0 x64 / Windows Server 2025 (10.0.26100). Initial tar packing failed after 14.044 seconds with the unchanged four outcome fields: status: null, signal: null, error: EOWNERSTART, cleanupError: EOWNERCLEANUP. The preserved owner reasons are exactly command supervisor startup timed out and Windows helper closure was not observed; both native error codes are null. The subsequent Git test failed at native fixture admission blocked after unconfirmed cleanup in 9.344 milliseconds, before its native callback: that test did not attempt Git initialization. All three new diagnostic-privacy, uncertain-root/admission and joined-failure regressions passed. Canonical Windows bootstrap, cancellation, compiler and Job controls also passed, but they do not establish closure of the failed tar owner. The log does not identify an internal startup cause or prove process extinction. Complete log SHA-256: 2997ba8b82cc2894e0405263e8f374199b0ad074bcf0dc3d58f48aa885401612. This changed-source diagnostic run is not an unchanged CI retry or a startup repair.
  • At prior 5198b26, the required Windows job failed on Node 24.20.0 / Windows Server 2025: 601 passed, 2 failed, 27 skipped, 0 cancelled. The archive-input test failed at initial tar packing (12.046 seconds), and the real Git fixture failed at initial Git initialization (12.050 seconds). Both returned status: null, signal: null, error: EOWNERSTART, cleanupError: EOWNERCLEANUP; neither successful command readiness nor authoritative fixture-owner closure was confirmed. The complete job log SHA-256 is ddf68e1d1c13bbcedf380170ac316a6c78777cd5f093709ba9700dafe7287a59. Canonical Windows owner controls passed in that job, but those separate controls do not establish closure for these failed fixtures. The config-path correction does not repair this distinct startup failure. No unchanged CI rerun or waiver was used.
  • A bounded Windows Server 2022 / Node 24.20.0 discriminator used the unchanged command owner and original minimal environment. Original Git initialization and git --version each returned 128 with the same complete 52-byte error identifying the null-device config path as invalid. A fresh initialization changing only GIT_CONFIG_GLOBAL to an existing empty file returned 0 and produced the expected branch HEAD. All three canonical command owners joined cleanly; exact native provider release was verified. A preceding bounded probe also completed tar and Git ownership in both environment arms, without reproducing the hosted startup failure. These observations establish the config-path defect, not a fix for EOWNERSTART or EOWNERCLEANUP. They ran on Server 2022, while the failed hosted job used Server 2025; actual Git version output was unavailable because the config error also prevented git --version.
  • The retained source-built package is 466,209 bytes, SHA-256 88d4d73ef7dc7efb5bd421597257eb5bef7ee5a664d9c4aa6e8d53d8145f07b4. Its source is frozen OpenClaw 5708fd83b080a345021ce376d7e532eb38877913; all eleven recorded plugin source hashes match the planned 59a734b7358b6ccb62449b74346ff422a9e3fef7 host source. This does not relabel the historical package build as a fresh 59a build.
  • The isolated runtime attempt for prior consumer 9697f435 and the 59a host ended with native client exit 124 at the five-minute sync completion-marker guard. The client joined and the exact task-owned lease reached stopped/completed, but no runtime artifact was delivered and no canonical receipt validation ran. Controller startup and workload execution remain unknown: native artifact collection occurs only after exit 0. A successful final-head matched pair and validated receipt remain required. No current-head Gateway, full-campaign or performance qualification is claimed.

Historical proof and unresolved failures

  • At prior head 9697f435, the required Windows job failed: 599 passed, 2 failed, 27 skipped, 0 cancelled. The added archive-input test failed at initial tar packing, and the real Git fixture failed at initial Git initialization. Both command results were status: null, signal: null, error: EOWNERSTART, cleanupError: EOWNERCLEANUP; neither successful readiness nor terminal cleanup was confirmed. The completed job log SHA-256 is f2b7ee6707cd822d1971021f57f3f7bea3e26a6b9a7c9eab0f15e2cf1d168279. No unchanged CI rerun or waiver was used.

Three earlier paired runs at 04d515312cfb8691a39695a98d7b411b6f562275 and one confirmation pair at 7983100b7e01d0070c01c9e01de2e6197de1595c completed the selected workload on host 5708fd83b080a345021ce376d7e532eb38877913 with harness c029367d73b8539a36de75e94830ca36b4894831. The confirmation receipt SHA-256 is 55d3cc212df8546d554fffa5d11e847ff9326305ff2f9b7b004c3051b30bc1ee. These receipts retain their original source/runtime identities and do not qualify this integrated consumer.

At prior head 42057057a87c84e909fb84c06c2baa4a5b941fc1, the required Windows job and advisory Windows job failed during fixture tar/Git setup with EOWNERSTART and EOWNERCLEANUP, before Tokenjuice loaded. Readiness and terminal cleanup were not confirmed. The separate frozen-base main check failed in unchanged Inspector import-time bootstrap with the same startup/cleanup uncertainty; its dashboard writer was skipped. This integration does not diagnose or repair those failures, infer a leak or waive new-head checks.

Fixture Impact

  • Adds or updates fixture manifest entries
  • Updates submodule pins
  • Changes contract or smoke logic
  • Docs only

Fixture Verification

  • npm test — exact-head required Windows failed as described above; landing remains held
  • node scripts/sync-fixtures.mjs --check
  • node scripts/run-contract-smoke.mjs
  • Strict fixture smoke, if submodules were materialized
  • Focused builtin tests described above

Notes

985 added lines across seven files: adapter 385, configuration 8, tests and diagnostic fixture 524, temporary CI job 21, and docs/changelog 47. Production growth adds the strict provider fixture, native package admission and output/statistics observer while reusing the existing runner. The original diagnostic increment adds 19 production lines; this update adds one allowlisted cleanup-cause field to retain authoritative owner facts; test ownership adds no production process-control path.

Gateway process metrics exclude Git children and the mock provider; wall time includes their work. Signed matched deltas include whole-agent noise and do not allocate cost to reducer functions. One Git-status path does not establish other reducers, Codex behavior, real-provider behavior, peaks, leaks, stable budgets or in-process handle disposal. The full source inventory remains the denominator, and no complete four-scenario campaign has run on this candidate. Measured workloads use no production credentials or external services; no release or deployment is included.

@clawsweeper

clawsweeper Bot commented Sep 22, 2026 •

Copy link
Copy Markdown
Contributor

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

@clawsweeper clawsweeper Bot added P2 Normal priority bug or improvement with limited blast radius. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. labels Sep 22, 2026
@clawsweeper

clawsweeper Bot commented Sep 22, 2026 •

Copy link
Copy Markdown
Contributor

Codex review: blocked before merge. Reviewed September 24, 2026, 11:51 AM ET / 15:51 UTC (Revision 12).

ClawSweeper review

What this changes

Adds an opt-in Tokenjuice profiling workload that compares raw and compacted Git tool results across embedded agent turns, with archive checks, fixture tests, documentation, and a temporary Windows diagnostic job.

Regression provenance

Possible regression — suspected (failure trace). No predecessor PR is attributed.

Merge readiness

⛔ Blocked before merge - 6 items remain

This PR remains useful because current main has the shared scoped-activation contract but lacks the Tokenjuice workload. The added native fixtures have failed on hosted Windows, and the integrated head has no validated matched-pair receipt, so it is not ready to merge.

Priority: P2
Reviewed head: 18747a87f3122e7e82c8a46b416f0210e7e8514e

Review scores

Measure Result What it means
Overall readiness 🦐 gold shrimp (3/6) The adapter has focused validation and relevant earlier real runs, but the integrated head remains unqualified on Windows and lacks its own workload receipt.
Proof confidence 🦐 gold shrimp (3/6) Not applicable: The MEMBER-authored PR is exempt from the external-contributor proof gate. Earlier real matched pairs used different consumer identities, while this integrated head has only synthetic observer tests and no validated final-head Gateway receipt; that declared landing requirement remains unresolved. No stored-data contract changes.
Patch quality 🦐 gold shrimp (3/6) 2 actionable review findings remain.

Verification

Check Result Evidence
Real behavior Not applicable Not applicable: The MEMBER-authored PR is exempt from the external-contributor proof gate. Earlier real matched pairs used different consumer identities, while this integrated head has only synthetic observer tests and no validated final-head Gateway receipt; that declared landing requirement remains unresolved. No stored-data contract changes.
Evidence reviewed 10 items Introduced scenario: The PR configures the Tokenjuice adapter as a scoped, paired workload with a distinct Git-status seam.
Model-visible assertion: The provider checks the second model request’s tool output against the raw or compacted result.
Host dependency signal: The shared runner imports the prepared OpenClaw host’s Gateway harness; the new adapter also declares the ordinary OpenClaw agent runtime.
Findings 2 actionable findings [P1] Qualify the added native fixture setup on Windows
[P3] Remove the branch-specific diagnostic job before merge
Security None None.

How this fits together

Crabpot’s resource campaign reads configured plugin scenarios and runs their adapters against a prepared OpenClaw host. This adapter sends synthetic model requests through real Gateway agent turns and records whether Tokenjuice changes the tool result seen by the model.

flowchart LR
  A[Scenario configuration] --> B[Pinned plugin archive]
  B --> C[Gateway agent turns]
  D[Synthetic Git repository] --> C
  C --> E[Loopback model provider]
  E --> F{Raw or compacted result?}
  F --> G[Statistics and workload receipt]
Loading

Before merge

  • Qualify the added native fixture setup on Windows (P1) - The new archive test invokes the synchronous command owner to pack tar input, but required hosted Windows CI at the earlier reviewed head failed here with EOWNERSTART and EOWNERCLEANUP before the fixture could run. This setup path is unchanged at the current head, so the added tests remain unqualified. This concern was visible in the earlier review; surfacing it as a finding now is late.
  • Remove the branch-specific diagnostic job before merge (P3) - This job is gated to the PR branch name, so it becomes a dead check on main. Keep it for the investigation, then remove the job and its probe before landing.
  • Resolve merge risk (P1) - The added tar and Git fixture setup has not shown successful readiness and authoritative cleanup on hosted Windows; prior required CI observed EOWNERSTART and EOWNERCLEANUP before plugin execution.
  • Resolve merge risk (P1) - Earlier real matched-pair receipts use older source identities. The integrated final head still lacks its declared validated Gateway receipt.
  • Resolve merge risk (P1) - The temporary, branch-specific Windows diagnostic job must be removed before landing; the latest-head job failed, and its available result does not diagnose the startup cause.
  • Complete next step (P2) - Resolve and prove hosted Windows native fixture readiness and cleanup, validate the integrated final-head matched-pair receipt, and remove the temporary diagnostic job before merge.

Findings

  • [P1] Qualify the added native fixture setup on Windows — test/resource-workload-tokenjuice.test.mjs:94-96
  • [P3] Remove the branch-specific diagnostic job before merge — .github/workflows/check.yml:63-67
Agent review details

Security

None.

Review metrics

Metric Value Why it matters
Added lines production/config +393, tests/probe +524, workflow +21, docs +47 The new adapter accounts for most production growth; the diagnostic workflow is explicitly temporary.

Merge-risk options

Maintainer options:

  1. Qualify the fixture before landing (recommended)
    Establish hosted Windows command readiness and cleanup, obtain a validated final-head matched-pair receipt, and remove the temporary probe job.

Technical review

Best possible solution:

Keep the workload fixture-driven and use the shared campaign runner to verify pinned archive identity, real Gateway model-visible compaction, statistics, and owned cleanup in a qualified isolated run.

Do we have a high-confidence way to reproduce the issue?

Not applicable to the requested new workload. The earlier-head hosted Windows fixture failure is documented, but the latest diagnostic job’s failure has no readable log here to establish its cause.

Is this the best way to solve the issue?

Yes, the opt-in adapter uses Crabpot’s existing campaign and scoped-activation contracts. The solution still needs native Windows qualification and an integrated real-Gateway receipt before it can land.

Full review comments:

  • [P1] Qualify the added native fixture setup on Windows — test/resource-workload-tokenjuice.test.mjs:94-96
    The new archive test invokes the synchronous command owner to pack tar input, but required hosted Windows CI at the earlier reviewed head failed here with EOWNERSTART and EOWNERCLEANUP before the fixture could run. This setup path is unchanged at the current head, so the added tests remain unqualified. This concern was visible in the earlier review; surfacing it as a finding now is late.
    Confidence: 0.94
    Late finding: first raised on code an earlier review cycle already covered.
  • [P3] Remove the branch-specific diagnostic job before merge — .github/workflows/check.yml:63-67
    This job is gated to the PR branch name, so it becomes a dead check on main. Keep it for the investigation, then remove the job and its probe before landing.
    Confidence: 0.98

Overall correctness: patch is incorrect
Overall confidence: 0.88

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 9ceee4211b2d.

Labels

Label changes:

No label changes.

Label justifications:

  • P2: This is a bounded, opt-in profiling improvement with unresolved validation rather than a user-facing runtime regression.
  • merge-risk: 🚨 automation: The introduced native fixture tests have failed in required Windows CI, and the temporary diagnostic changes the check workflow.
  • rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦐 gold shrimp and patch quality is 🦐 gold shrimp.
  • status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: The MEMBER-authored PR is exempt from the external-contributor proof gate. Earlier real matched pairs used different consumer identities, while this integrated head has only synthetic observer tests and no validated final-head Gateway receipt; that declared landing requirement remains unresolved. No stored-data contract changes.

Evidence

What I checked:

Likely related people:

  • Vincent Koc: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)
  • Sebastien Tardif: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

Rank-up moves

Optional improvements that raise the rating; they are not merge blockers.

  • Establish successful hosted Windows tar/Git readiness and authoritative cleanup for the final head.
  • Validate a final-head isolated matched-pair Gateway receipt against the pinned host and archive.
  • Remove the temporary diagnostic workflow and probe before merge.

Rating scale

Score Internal tier Crab rank Meaning
6/6 S 🦀 challenger crab Exceptional readiness
5/6 A 🦞 diamond lobster Very strong readiness
4/6 B 🐚 platinum hermit Good normal PR; ordinary maintainer review
3/6 C 🦐 gold shrimp Useful, but confidence is limited
2/6 D 🦪 silver shellfish Proof or implementation needs work
1/6 F 🧂 unranked krab Not merge-ready
N/A NA 🌊 off-meta tidepool Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

History

Review history (11 earlier review cycles; latest 8 shown)
  • reviewed 2026-09-23T11:01:39.212Z sha 4205705 :: blocked before merge. :: none
  • reviewed 2026-09-23T12:41:15.760Z sha 9697f43 :: blocked before merge. :: none
  • reviewed 2026-09-23T13:02:13.223Z sha 9697f43 :: blocked before merge. :: none
  • reviewed 2026-09-23T14:57:09.600Z sha 5198b26 :: blocked before merge. :: none
  • reviewed 2026-09-23T15:05:04.048Z sha 5198b26 :: blocked before merge. :: none
  • reviewed 2026-09-23T15:18:59.818Z sha 5198b26 :: blocked before merge. :: none
  • reviewed 2026-09-23T15:32:35.435Z sha cdb4f5e :: blocked before merge. :: none
  • reviewed 2026-09-23T15:54:20.309Z sha cdb4f5e :: blocked before merge. :: none

@clawsweeper clawsweeper Bot added the proof: sufficient Contributor real behavior proof is sufficient. label Sep 22, 2026
@vincentkoc
vincentkoc force-pushed the fix/plugin-resource-scoped-activation-20260923 branch 2 times, most recently from f09f9b0 to 02ccb61 Compare September 23, 2026 01:29
@vincentkoc
vincentkoc force-pushed the fix/plugin-resource-scoped-activation-20260923 branch from 02ccb61 to 19bcf36 Compare September 23, 2026 10:23
Base automatically changed from fix/plugin-resource-scoped-activation-20260923 to main September 23, 2026 10:55
@clawsweeper clawsweeper Bot added the merge-risk: 🚨 automation 🚨 Merging this PR could break CI, automerge, proof capture, label sync, or automation. label Sep 23, 2026
@vincentkoc
vincentkoc force-pushed the feat/plugin-resource-tokenjuice-20260923 branch from 4205705 to 9697f43 Compare September 23, 2026 12:36
@clawsweeper clawsweeper Bot removed the proof: sufficient Contributor real behavior proof is sufficient. label Sep 23, 2026
@clawsweeper clawsweeper Bot added rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. and removed rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. labels Sep 23, 2026
@clawsweeper clawsweeper Bot added status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action. and removed status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. labels Sep 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge-risk: 🚨 automation 🚨 Merging this PR could break CI, automerge, proof capture, label sync, or automation. P2 Normal priority bug or improvement with limited blast radius. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant