docs: add scripts directory index#97250
Conversation
|
Codex review: needs maintainer review before merge. Reviewed June 27, 2026, 10:13 AM ET / 14:13 UTC. Summary PR surface: Docs +75. Total +75 across 1 file. Reproducibility: not applicable. this is a documentation/discoverability PR, not a runtime bug. Source inspection verifies current main lacks Review metrics: none identified. Stored data model Root-cause cluster Members:
Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything. Merge readiness Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch. Rank-up moves:
Next step before merge
Security Review detailsBest possible solution: Land the narrow scripts README after ordinary maintainer docs review, and leave any script relocation or taxonomy change in the canonical broader issue until maintainers approve a compatibility plan. Do we have a high-confidence way to reproduce the issue? Not applicable: this is a documentation/discoverability PR, not a runtime bug. Source inspection verifies current main lacks Is this the best way to solve the issue? Yes for the index slice: adding a root scripts README is the narrowest maintainable docs path and avoids the compatibility risk of moving script paths. It intentionally does not solve the broader scripts reorganization request. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning high; reviewed against 5ccfc97b319e. Label changesLabel justifications:
Evidence reviewedPR surface: Docs +75. Total +75 across 1 file. View PR surface stats
What I checked:
Likely related people:
What the crustacean ranks mean
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. How this review workflow works
|
|
@clawsweeper re-review |
|
🦞🧹 I asked ClawSweeper to review this item again. |
|
@clawsweeper re-review |
What Problem This Solves
Fixes the low-risk documentation/index portion of #59728 by adding a discoverable
scripts/README.mdfor the currentscripts/directory.The issue also proposes a wholesale scripts directory reorganization. This PR intentionally does not move or rename scripts because those paths are referenced by
package.json, GitHub Actions, docs, and maintainer runbooks. Any relocation still needs a maintainer-approved taxonomy and compatibility plan.Why This Change Was Made
The existing
scripts/directory has many entry points but no local index for contributors or agents to quickly find the right wrapper. This adds a small README that documents:scripts/AGENTS.mdand the public scripts docsUser Impact
Contributors can find existing script wrappers faster before adding new tooling or running broad commands. Maintainers get a safer first step toward #59728 without changing any script paths, package scripts, workflows, lockfiles, or generated files.
Evidence
Claim proved: this PR is docs-only and adds a
scripts/README.mdindex for the existing flatscripts/layout. It does not move, rename, or regroup scripts, and it does not changepackage.json, GitHub Actions, lockfiles, generated files, or runtime behavior.Commands / artifacts:
pnpm docs:listgit diff --check HEAD~1 HEAD -- scripts/README.mdcheck-docspassed on this PR: https://github.com/openclaw/openclaw/actions/runs/28290280970/job/83821022006Copied terminal output:
Duplicate PR preflight:
gh search prs --repo openclaw/openclaw --state open --match title,body -- 59728returned no open PRsgh search prs --repo openclaw/openclaw --state open --match title,body -- "scripts README"returned no open PRsgh issue view 59728 --repo openclaw/openclawconfirmed Scripts: Organize 150+ files in scripts/ directory by function with README index #59728 is still openResult: the docs index renders as Markdown, docs discovery still lists successfully, whitespace checks pass, and scoped CI docs validation is green.
Not tested / proof gaps: no runtime, script execution, script relocation, package-script rewiring, or workflow behavior was tested because this PR intentionally does not change those surfaces. The broader #59728 directory reorganization still needs a maintainer-approved taxonomy and compatibility plan before implementation.