[FIX] PR #166: command count conflict — update to 76 commands after #165 merged

[Wolfvin]

Context

PR #166 (feat(sync): per-file staleness banner — closes #66 phase-1) was written when main had 70 commands. Since then, many PRs merged including #165 (orient command). Main now has 75+ commands.

Fix Required

1. Rebase PR feat(sync): per-file staleness banner — MCP + CLI (closes #66 phase-1) #166 branch on latest main
2. Run python3 scripts/sync_command_count.py --apply — use the number it outputs, do not manually edit
3. Commit corrected counts
4. Push rebased branch

The staleness command itself is fine — only the count files need updating.

Definition of Done

• PR feat(sync): per-file staleness banner — MCP + CLI (closes #66 phase-1) #166 rebased on latest main (no conflicts)
• sync_command_count.py --apply run and docs match output
• PR feat(sync): per-file staleness banner — MCP + CLI (closes #66 phase-1) #166 is mergeable

[Wolfvin]

🔄 Taking this issue

Mengerjakan issue ini -- 2026-07-03T03:23:34Z

[Wolfvin]

PR siap review

PR: #166 — feat(sync): per-file staleness banner — MCP + CLI (closes #66 phase-1)
Branch: feat/issue-66-staleness-banner-phase1
Summary: Rebased PR #166 on latest main (which had merged orient #165, affected #142, deps-audit #162, and others since the PR was originally written). Resolved merge conflicts in mcp_server.py (merged Phase 1 staleness + Phase 4 worktree banner methods) and sync/init.py (merged worktree + pending exports). Ran sync_command_count.py --apply — command count updated from 70 to 78 (staleness + orient + deps-audit + affected are the new commands since PR #166 was written).
Tests: 45 passed (test_staleness: 41 passed, test_command_count: 4 passed), 0 failed

Definition of Done:

• PR feat(sync): per-file staleness banner — MCP + CLI (closes #66 phase-1) #166 rebased on latest main (no conflicts) — mergeable: true
• sync_command_count.py --apply run and docs match output — count is 78, all files in sync
• PR feat(sync): per-file staleness banner — MCP + CLI (closes #66 phase-1) #166 is mergeable — GitHub reports mergeable: true

Findings

Pre-existing bug on main (NOT caused by PR #166): the affected command (PR #142, already merged to main) uses -f for --filter, which conflicts with the global --format/-f flag added by codelens.py line 892. This breaks ALL CLI invocations that trigger argparse registration (e.g. codelens affected --help, codelens doctor, codelens staleness). The conflict exists on clean main — verified by checking out main and running codelens affected --help. Recommend creating a separate issue to fix this (either change affected to use --filter without -f, or add -f to the existing_option_strings check in codelens.py).