Best possible solution:

Land the bounded command after required checks pass, preserving the replacement guard, generated docs, and no release-owned changelog edit.

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

Not applicable as a bug reproduction; this is a feature implementation PR. Source search on current main and v0.32.0 confirms there is no existing Sheets basic-filter command, and this PR is the linked implementation candidate.

Is this the best way to solve the issue?

Yes: the PR reuses existing Sheets range resolution and mutation patterns, adds dry-run and replacement confirmation behavior, and includes generated docs plus focused tests. I found no duplicate supported command path on current main or the latest release.

AGENTS.md: found and applied where relevant.

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

Label justifications:

• P2: The PR implements a bounded Sheets feature gap linked to an open request, with limited blast radius and focused tests.
• 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: Not applicable: this is a ClawSweeper bot/autofix PR, so the external-contributor real behavior proof gate does not apply.

What I checked:

• Repository policy read: AGENTS.md was read fully; its PR-review guidance applied because this was inspected read-only without changing branches or files. (AGENTS.md:37, 088198a28077)
• Current-main feature gap: Current main's Sheets command registry lists the existing Sheets subcommands and has no filter/basic-filter command surface. (internal/cmd/sheets.go:33, 088198a28077)
• Latest release feature gap: The v0.32.0 tree has no matches for SetBasicFilter, BasicFilter, basic-filter, sheets filter, or SheetsFilter under internal/docs/agents paths. (f20a26cd9e26)
• PR implementation path: The PR head validates spreadsheet/range inputs, exits before auth/API work on dry-run, resolves the range, builds SetBasicFilterRequest, and sends it through BatchUpdate. (internal/cmd/sheets_filter.go:20, 4eb708278d85)
• Replacement guard: The PR fetches basicFilter(range) metadata into the shared range catalog and refuses to replace an existing sheet filter without confirmation or --force. (internal/cmd/sheets_range_resolve.go:31, 4eb708278d85)
• Focused tests: Tests cover SetBasicFilter request shape, sheetId zero serialization, dry-run service skipping, replacement refusal, and forced replacement output. (internal/cmd/sheets_filter_test.go:17, 4eb708278d85)

Likely related people:

• steipete: Current-main blame points the Sheets command registry and shared mutation/range helpers at the release commit, while older reachable commits show steipete authored the shared mutation runner and adjacent data-validation command work; steipete also authored the PR commits that added the replacement guard and dry-run safety repair. (role: recent area contributor and likely follow-up owner; confidence: high; commits: f20a26cd9e26, a394c1c7b015, e1be268f70a6; files: internal/cmd/sheets.go, internal/cmd/sheets_mutation_helpers.go, internal/cmd/sheets_range_resolve.go)
• TheCrazyLex: GitHub commit metadata shows TheCrazyLex authored the named-range support and range resolver behavior that this new filter command reuses for named range resolution. (role: introduced adjacent behavior; confidence: medium; commits: 1da21969a825; files: internal/cmd/sheets_named_ranges.go, internal/cmd/sheets_range_resolve.go, internal/cmd/sheets.go)

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

• reviewed 2026-07-05T05:26:11.761Z sha dba7ddb :: passed. :: none
• reviewed 2026-07-06T05:41:01.230Z sha d6253e9 :: passed. :: none
• reviewed 2026-07-06T05:46:20.545Z sha 4454c21 :: needs changes before merge. :: [P3] Remove the release-owned changelog entry
• reviewed 2026-07-06T05:58:45.216Z sha 4eb7082 :: passed. :: none