Best possible solution:

Land this narrow CI-restoration patch after the assigned maintainer is satisfied with exact-head CI, keeping the production attach CLI and gateway contracts unchanged.

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

Yes. I did not run local checks in this read-only review, but current source shows docs/cli/attach.md missing from docs/docs_map.md and the gateway params type as unknown while the test recorder stores object params.

Is this the best way to solve the issue?

Yes. The patch keeps the production gateway contract unchanged, narrows only the test recorder boundary, and refreshes the generated docs-map entry for an existing page; widening or changing runtime types would be the wrong layer for this CI-only failure.

AGENTS.md: found and applied where relevant.

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

Label changes:

• add P2: This fixes a normal-priority CI/docs/test-type regression with limited blast radius and no runtime behavior change.
• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: Real behavior proof is not required for this maintainer-labeled docs-map/test-type CI repair with no runtime behavior change; PR-body commands and GitHub checks are still useful validation.

Label justifications:

• P2: This fixes a normal-priority CI/docs/test-type regression with limited blast radius and no runtime behavior change.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: Real behavior proof is not required for this maintainer-labeled docs-map/test-type CI repair with no runtime behavior change; PR-body commands and GitHub checks are still useful validation.

PR surface:

Tests +8, Docs +5. Total +13 across 2 files.

What I checked:

• Repository policy read: Read full root AGENTS.md and scoped docs/AGENTS.md; the protected-label rule, review-depth rule, docs generated-map guidance, and read-only validation constraint were applied. (AGENTS.md:1, f8769559aecc)
• Gateway contract is unknown params: Current main defines both GatewayRequestFunction and CallGatewayBaseOptions.params as unknown, so tests that record params as object data need an explicit boundary check or narrowing. (src/gateway/call.ts:63, f8769559aecc)
• Patch narrows the test recorder boundary: PR head adds gatewayParams(params: unknown) and uses it before storing params in the attach action test recorder, matching the existing unknown gateway-call boundary without changing runtime code. (src/cli/attach-cli.action.test.ts:15, 2fdb73067fe0)
• Docs map omission matches generated-map contract: docs/cli/attach.md exists on current main, docs/docs_map.md omits it between approvals and backup, and PR head adds the expected /cli/attach route with no headings. (docs/docs_map.md:1248, 2fdb73067fe0)
• Relevant PR checks are green on head: GitHub reports PR head check-docs, check-test-types, and check-prod-types completed successfully; this supports the stated CI restoration without relying only on the PR body. (2fdb73067fe0)
• Feature provenance: Merged PR feat(cli): openclaw attach — launch an external harness bound to a gateway session #96454 introduced the attach CLI, attach action tests, and attach docs page that this PR repairs. (src/cli/attach-cli.action.test.ts:1, 6df7db9f9e49)

Likely related people:

• steipete: Live PR metadata assigns this PR to steipete, the PR carries the protected maintainer label, and CONTRIBUTING.md lists steipete as a repository maintainer, so final merge handling likely routes there. (role: assigned maintainer / likely follow-up owner; confidence: high; commits: 2fdb73067fe0; files: docs/docs_map.md, src/cli/attach-cli.action.test.ts)
• anagnorisis2peripeteia: Merge commit 6df7db9f9e49c574bd12f2443869319a5661db89 and PR metadata for feat(cli): openclaw attach — launch an external harness bound to a gateway session #96454 show this author introduced the attach CLI, attach docs page, and attach action tests now being repaired. (role: introduced attach CLI surface; confidence: high; commits: 6df7db9f9e49, f984f9087d2f; files: src/cli/attach-cli.ts, src/cli/attach-cli.action.test.ts, docs/cli/attach.md)
• obviyus: PR metadata for feat(cli): openclaw attach — launch an external harness bound to a gateway session #96454 shows an additional attach CLI commit by obviyus, making them relevant to the merged attach behavior even though this cleanup PR is narrower. (role: adjacent contributor in merged attach PR; confidence: medium; commits: fcf060472605; files: src/cli/attach-cli.ts)
• Peter Lindsey: git blame on scripts/generate-docs-map.mjs ties the generated docs map contract and check behavior to commit 2205bf9d2463f51b21590663a2a4cfeb70d21675. (role: generated docs map area contributor; confidence: medium; commits: 2205bf9d2463; files: scripts/generate-docs-map.mjs, docs/docs_map.md)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

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.

• 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.