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

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

• Eggs appear after the PR passes real-behavior proof. It is here for vibes, not verdicts: it does not change labels, ratings, merge decisions, or automation.
• The shell reacts to review momentum: open follow-up work warms it up, re-review makes it wobble, and a clean final review lets it hatch.
• Hatchable usually means sufficient real-behavior proof, no blocking P0/P1/P2 findings, no security attention needed, and clean correctness.
• The hatch is seeded from this repository and PR number, so the same PR keeps the same creature; the reviewed head SHA can only change safe visual details.
• Rarity is just collectible sparkle: 🥚 common, 🌱 uncommon, 💎 rare, ✨ glimmer, and 🌈 legendary.

Best possible solution:

Merge the nav-only docs change if a maintainer agrees the Native Codex plugins guide should be discoverable beside the bundled Codex harness guide, with no runtime changes.

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

Not applicable: this is a docs navigation PR, not a runtime bug report. Source inspection and the PR diff are enough to review the requested placement change.

Is this the best way to solve the issue?

Yes, conditionally: moving the guide-style page next to the base Codex harness guide is a narrow maintainable docs change. Because the maintainer label is present, the final placement decision should come from a maintainer.

Label justifications:

• P3: This is a low-risk documentation navigation cleanup with no runtime behavior change.

Acceptance criteria:

• python -c 'import json,pathlib; json.loads(pathlib.Path("docs/docs.json").read_text())'
• git diff --check

What I checked:

• Protected label: The provided live PR context shows the maintainer label, which this cleanup workflow must leave open for explicit maintainer handling.
• Current navigation: Current main places plugins/codex-native-plugins under the Reference tab's Codex harness group, while the Capabilities bundled plugin guides group already contains the adjacent Codex harness guide. Public docs: docs/docs.json. (docs/docs.json:1703, 5c9a8f33b312)
• PR diff: The PR head moves the native Codex plugins page into Capabilities > Bundled plugin guides and removes it from the Reference > Codex harness group without touching runtime code. Public docs: docs/docs.json. (docs/docs.json:1206, e5776ad760e5)
• Page classification: The Native Codex plugins page is written as a setup/quickstart guide used after the base Codex harness is working, supporting placement near bundled plugin guides rather than only reference pages. Public docs: docs/plugins/codex-native-plugins.md. (docs/plugins/codex-native-plugins.md:18, 5c9a8f33b312)
• Docs JSON check: The current docs navigation file parses as JSON; the PR body reports the same parse check and git diff --check for the branch. Public docs: docs/docs.json. (docs/docs.json:1, 5c9a8f33b312)
• Feature history: Recent Codex native plugin documentation and command work is tied to commit 9b97e1e, which updated the Codex harness and native plugin docs. Public docs: docs/plugins/codex-native-plugins.md. (docs/plugins/codex-native-plugins.md, 9b97e1ef2fd2)

Likely related people:

• kevinslin: Commit 9b97e1e added recent Codex plugin management docs and touched both the Codex harness and Native Codex plugins pages, so this person is the strongest routing candidate for the page placement. (role: recent Codex native plugin contributor; confidence: high; commits: 9b97e1ef2fd2; files: docs/plugins/codex-native-plugins.md, docs/plugins/codex-harness.md, extensions/codex/src/command-plugins-management.ts)
• Ayaan Zaidi: Current-line blame for the docs navigation groups involved in this move points to commit 1f794d2, which carries the current docs/docs.json structure in this checkout. (role: docs navigation contributor; confidence: medium; commits: 1f794d2816d1; files: docs/docs.json)

Codex review notes: model gpt-5.5, reasoning high; reviewed against 5c9a8f33b312.