Skip to content

chore(e2e): remove retired terminal proof helpers - #1283

Merged
steipete merged 1 commit into
mainfrom
fix/remove-retired-terminal-proof-helpers
Aug 28, 2026
Merged

chore(e2e): remove retired terminal proof helpers#1283
steipete merged 1 commit into
mainfrom
fix/remove-retired-terminal-proof-helpers

Conversation

@steipete

Copy link
Copy Markdown
Contributor

Summary

Follow-up to retiring automatic live proof: remove the unused standalone Codex generator and one-shot terminal fixture that were left behind after their planner was deleted.

This is exactly two file deletions, 307 lines removed, zero additions. There is no replacement planner, manual-tool fork, execution toggle, dependency change, or relaxation of an active security boundary.

Ownership and compatibility

Four independent cleanup passes checked reuse, simplification, efficiency, and ownership. Neither helper has a current caller, package command, test dependency, or supported manual-use contract. Historical proof documentation still records the generator's source hash; that provenance is deliberately preserved.

Historical parsing, verification, comment rendering, artifact publication, recording retraction, low-level drivers, production schema/prompt, and workflows are unchanged. OpenClaw Bay is unaffected: no lifecycle, timing, telemetry, presentation, or observer data-contract change. This is internal e2e-tool cleanup, not a user-facing feature change.

Controlled behavior proof

Exercised committed head b226be81c79f826b3a50b672e13d660691acc63c over base f72ea010c1d7fd134b1bd0826b3a707778c312bc, on macOS with Node v24.20.0.

The removed-entry-point behavior is reproduced with:

node scripts/e2e/terminal-proof-generate.mjs /tmp/retired-proof-output
node scripts/e2e/terminal-proof-once.mjs /tmp/retired-fixture-output

Controlled invocations used fresh scratch output paths, HOME/TMPDIR, and a harmless Codex marker executable on PATH. Both correctly exited 1 / MODULE_NOT_FOUND, without invoking Codex or creating the requested output. A tracked-source search found no active references outside immutable historical proof records.

The current production parser and verification/comment renderer also consumed a previously recorded real terminal decision and verification artifact. The historical recommended plan survived parsing unchanged, verification remained valid, and all five PASS markers rendered. New model output remains constrained to the fixed empty not_applicable shape. No historical command, inference, recording, upload, or publication was executed for this cleanup.

Historical input SHA-256:

  • decision: a7ee1c05499e225e08c301f75d2e9fe80b1309ebfbc6a3af2b38d4f5cc7ef108
  • verification: 53715a78327c2d426d52cb746837b33ede92959429e97ce91fc3ff308a15e7bd

These are archived inputs to the current parser/render replay, not a claim of new current-head terminal execution. The retained runtime, schema, prompts, workflows, docs, and dependencies were verified byte-unchanged from base.

Validation

  • 16 focused retirement/historical-compatibility tests passed, zero failures or skips, across workflow, prompt/schema, live-proof, historical bundle, and publication/sparse-checkout coverage.
  • Locked dependency install, all builds, static/documentation/format checks, lint, and diff checks passed.
  • Fresh isolated Codex reviews before commit and on the committed branch both reported no accepted/actionable findings at the default P0 threshold.
  • Full local pnpm run check was invoked; a complete local pass is not claimed. The baseline has an independently reproduced macOS action-ledger concurrency stall outside these deletions. Its source/tests are untouched. Hosted CI for this PR must pass before merge.

Limits: this proves removal of the standalone CLI surfaces and preservation of historical parser/render behavior. It does not claim a new live-proof lane, production publication run, deployment, or model-generation test.

Remove the orphaned generator and one-shot fixture after automatic live-proof planning was retired in #1280. Keep historical artifact compatibility and low-level drivers unchanged.
@clawsweeper

clawsweeper Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

🦞👀
ClawSweeper picked this up.

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

@clawsweeper clawsweeper Bot added P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. proof: sufficient Contributor real behavior proof is sufficient. 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 Aug 28, 2026
@clawsweeper

clawsweeper Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Codex review: needs maintainer review before merge. Reviewed August 28, 2026, 12:26 PM ET / 16:26 UTC.

ClawSweeper review

What this changes

This PR removes the unused standalone terminal-proof generator and its one-shot fixture, leaving historical proof records intact.

Merge readiness

⚠️ Ready for maintainer review - 1 item remains

Keep open: this is a focused, viable cleanup that completes the retirement introduced by #1280; no active caller or package command depends on either deleted helper.

Priority: P3
Reviewed head: b226be81c79f826b3a50b672e13d660691acc63c

Review scores

Measure Result What it means
Overall readiness 🐚 platinum hermit (4/6) A narrowly scoped deletion with source-confirmed lack of active consumers and adequate current-head terminal proof.
Proof confidence 🐚 platinum hermit (4/6) Sufficient (terminal): The PR body records the exact tested head, macOS/Node environment, removal commands, and observed MODULE_NOT_FOUND outcome without Codex invocation or output creation; it also describes focused compatibility replay of retained historical artifacts.
Patch quality 🦞 diamond lobster (5/6) No actionable review findings were identified.

Verification

Check Result Evidence
Real behavior Verified Sufficient (terminal): The PR body records the exact tested head, macOS/Node environment, removal commands, and observed MODULE_NOT_FOUND outcome without Codex invocation or output creation; it also describes focused compatibility replay of retained historical artifacts.
Evidence reviewed 6 items Exact introduced change: The verified PR-introduced delta contains only the deletion of the two named helper scripts (307 lines removed, no additions).
No active consumer: Current-main tracked-source search found the generator path only as a preserved historical SHA-256 entry; package scripts contain no command for either helper.
Current retirement contract: Current documentation says automatic review generation no longer executes or provisions live proof, while historical records and publication remain supported.
Findings None None.
Security None None.

How this fits together

ClawSweeper’s automatic live-proof execution has been retired, while the parser, publication path, and historical proof artifacts remain compatible. The deleted scripts were standalone helpers for the retired generation path and no longer feed an active workflow.

flowchart LR
A[Review decision] --> B[Retired automatic proof path]
B --> C[Standalone terminal helpers]
D[Historical proof records] --> E[Parser and publication]
C --> F[Deleted unused scripts]
E --> G[Historical compatibility retained]
Loading

Before merge

  • Complete next step (P2) - No actionable defect was found in the introduced deletion; this PR only needs normal current-head CI and maintainer landing review.
Agent review details

Security

None.

Review metrics

Metric Value Why it matters
Patch scope 2 files removed, 307 deletions, 0 additions The branch is limited to unused helper removal and does not alter production runtime, workflow, dependency, or schema files.

Technical review

Best possible solution:

Land the two deletions while retaining the documented historical-artifact parser, verification, publication, and retraction paths.

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

Not applicable as a bug reproduction: this is a deletion-only cleanup. The PR body supplies current-head terminal evidence that both retired entry points now fail before invoking Codex or creating output.

Is this the best way to solve the issue?

Yes. Deleting the two unreferenced helpers is the narrowest maintainable completion of the merged retirement, while the current parser and historical-publication compatibility tests retain the still-supported behavior.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 468dab46ff57.

Labels

Label changes:

  • add P3: This is a low-risk internal cleanup with no user-facing behavior change.
  • add proof: sufficient: Contributor real behavior proof is sufficient. The PR body records the exact tested head, macOS/Node environment, removal commands, and observed MODULE_NOT_FOUND outcome without Codex invocation or output creation; it also describes focused compatibility replay of retained historical artifacts.
  • add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🦞 diamond lobster.
  • add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (terminal): The PR body records the exact tested head, macOS/Node environment, removal commands, and observed MODULE_NOT_FOUND outcome without Codex invocation or output creation; it also describes focused compatibility replay of retained historical artifacts.

Label justifications:

  • P3: This is a low-risk internal cleanup with no user-facing behavior change.
  • rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🦞 diamond lobster.
  • status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (terminal): The PR body records the exact tested head, macOS/Node environment, removal commands, and observed MODULE_NOT_FOUND outcome without Codex invocation or output creation; it also describes focused compatibility replay of retained historical artifacts.
  • proof: sufficient: Contributor real behavior proof is sufficient. The PR body records the exact tested head, macOS/Node environment, removal commands, and observed MODULE_NOT_FOUND outcome without Codex invocation or output creation; it also describes focused compatibility replay of retained historical artifacts.

Evidence

What I checked:

Likely related people:

  • steipete: Peter Steinberger authored the original one-shot helper change and the current deletion; history also shows sustained work on this proof surface. (role: original helper author and recent area contributor; confidence: high; commits: c0af16349bfb, b226be81c79f; files: scripts/e2e/terminal-proof-generate.mjs, scripts/e2e/terminal-proof-once.mjs, docs/live-proof.md)
  • roboclaw-bot: The related merged retirement change established the current compatibility-only automatic-live-proof contract that this cleanup follows. (role: retirement-change author; confidence: medium; commits: f72ea010c1d7; files: docs/live-proof.md, test/live-proof.test.ts)

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.

@steipete
steipete merged commit ccac077 into main Aug 28, 2026
18 checks passed
@steipete
steipete deleted the fix/remove-retired-terminal-proof-helpers branch August 28, 2026 16:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. proof: sufficient Contributor real behavior proof is sufficient. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant