docs(codex): record coderabbit fix loop

Purpose of the change:
- Record the CodeRabbit fix-loop state for PR #62.
- Keep the tracked WIP artifact aligned with the current review cleanup.

How behavior was before:
- The tracked WIP file described an older PR's CodeRabbit loop.
- It did not reflect the current PR's resolved CodeRabbit item.

Why that was a problem:
- The repository's fix-loop audit artifact was stale for the active branch.

What the new change accomplishes:
- Documents the PR #62 CodeRabbit queue, evidence, and final checks.
- Marks the inline CodeRabbit item and review-body summary as handled.

How it works:
- Updates .codex/coderabbit-fixes-wip.md with the current PR context, queue, validation evidence, and final re-check status.

Author: elibosley

.codex/coderabbit-fixes-wip.md

@@ -3,10 +3,10 @@
 ## Context
 
 - Repo: unraid/apprise-go
-- Branch: codex/telegram-formatting-followup
-- PR: #60
-- PR URL: https://github.com/unraid/apprise-go/pull/60
-- Generated at: 2026-05-21T00:36:00-04:00
+- Branch: codex/cli-help-parity
+- PR: #62
+- PR URL: https://github.com/unraid/apprise-go/pull/62
+- Generated at: 2026-05-21T14:29:52Z
 
 ## Inputs Pulled
 
@@ -18,42 +18,19 @@
 
 | Item ID | Type | File | Line | Summary | Status | Link | Evidence |
 | --- | --- | --- | --- | --- | --- | --- | --- |
-| CR-001 | thread | internal/notify/format_convert_test.go | 168 | Add Python parity to the cross-target corpus test. | BLOCKED | https://github.com/unraid/apprise-go/pull/60#discussion_r3278534673 | Skipped: this corpus intentionally validates target format conversion behavior that fixes Telegram behavior beyond current Python Apprise. Adding Python request parity would lock in the upstream bug this PR is fixing. |
-| CR-002 | thread | internal/notify/telegram_format_test.go | 140 | Route new Telegram format tests through Python-vs-Go request-sequence parity. | BLOCKED | https://github.com/unraid/apprise-go/pull/60#discussion_r3278534678 | Skipped: these tests assert corrected Telegram parse payloads that current Python Apprise does not emit. |
-| CR-003 | thread | internal/notify/live/telegram_live_test.go | 101 | Add Python-apprise request parity to the live Telegram test. | BLOCKED | https://github.com/unraid/apprise-go/pull/60#discussion_r3278534680 | Skipped: live test purpose is Bot API acceptance of corrected Go-generated Telegram parse payloads, not matching upstream Python's currently broken formatting. |
-| CR-004 | thread | internal/notify/live/telegram_live_test.go | n/a | Require explicit destination for the live suite. | DONE | https://github.com/unraid/apprise-go/pull/60#discussion_r3278534682 | Addressed in `a3dd48f`; GraphQL reports thread resolved/outdated. |
-| RVW-001 | review-body | internal/notify/live/telegram_live_test.go | 140-149 | Redact bot token from live test transport error logs. | DONE | https://github.com/unraid/apprise-go/pull/60#pullrequestreview-4320292462 | Added redaction helper and regression test; targeted and full Go tests passed. |
+| CR-001 | thread | internal/cli/cli.go | 212 | Unknown-option detection is over-applied and can misclassify non-unknown parse errors. | DONE | https://github.com/unraid/apprise-go/pull/62#discussion_r3281866028 | `go test ./internal/cli` passed; added regression for `-R not-an-int --blah`. |
+| RVW-001 | review-body | top-level | n/a | Review body reports one actionable comment, represented by CR-001. | DONE | https://github.com/unraid/apprise-go/pull/62#pullrequestreview-4337724219 | No separate top-level actionable item beyond CR-001. |
 
 ## Execution Log
 
-### 1. Item: CR-004
-- Action: Required `APPRISE_GO_TELEGRAM_CHAT_ID` for live validation and removed auto-discovery/bot-ID fallback.
-- Validation: `go test ./internal/notify/live -run TestTelegramLiveFormattingAgainstBotAPI -count=1 -v` with explicit live env passed.
-- Result: DONE
-
-### 2. Item: CR-001
-- Action: Verified this asks for parity against Python Apprise behavior that does not include the corrected Telegram conversions under test.
-- Validation: Code/test review.
-- Result: BLOCKED; skipped because it conflicts with the bug fix goal.
-
-### 3. Item: CR-002
-- Action: Verified the requested parity would force the new Telegram unit tests back to current Python output.
-- Validation: Code/test review.
-- Result: BLOCKED; skipped because it conflicts with the bug fix goal.
-
-### 4. Item: CR-003
-- Action: Verified live validation is intentionally testing Bot API acceptance of Go-generated corrected payloads.
-- Validation: Code/test review.
-- Result: BLOCKED; skipped because Python parity is not the purpose of this live suite.
-
-### 5. Item: RVW-001
-- Action: Added token redaction before reporting request creation or transport errors.
-- Validation: `go test ./internal/notify/live -count=1`; `go test ./internal/notify ./internal/notify/live -run 'TestTelegram|TestTargetFormatConversionCorpusAcrossWorkflowTargets' -count=1`; live Bot API test with explicit env; `go test ./...`
+### 1. Item: CR-001
+- Action: Gated unknown-option formatting to only `flag provided but not defined` parse errors and left other parse failures on their real parser error path.
+- Validation: `go test ./internal/cli` passed.
 - Result: DONE
 
 ## Final Checks
 
 - [x] Queue reviewed: no `TODO` left
 - [x] Remaining `BLOCKED` items documented with reason
-- [ ] Re-pulled CodeRabbit threads and reviews
-- [ ] No unhandled top-level review-body comment remains
+- [x] Re-pulled CodeRabbit threads and reviews
+- [x] No unhandled top-level review-body comment remains