test: verify Claude issue worker end-to-end (docs-only)

[Hmbown]

Problem
Maintainer verification of the newly merged Claude issue worker (#4537): the @claude workflow must gate correctly, run once per issue, create a signed branch from main, and stop at a PR-creation link without auto-merging.

Current evidence
PR #4537 merged at 77a6649 with all checks green. The workflow has not yet processed a live maintainer comment.

Scope
Docs-only verification. First a plan-only reply, then a trivial documentation change on a signed branch.

Key files
docs/GUIDE.md

Acceptance criteria

• The authorize gate accepts an exact @claude maintainer issue comment.
• Claude replies with a plan without editing files when asked plan-only.
• A follow-up request produces a signed branch claude/issue--* from main with a PR-creation link, no automatic PR.

Verification
Workflow run logs on this issue; branch listing; commit signature verification.

Out of scope
Public contributor access, PR comments, auto-PR creation.

Related
#4537

[Hmbown]

@claude
Reply with a short implementation plan only. Do not edit files.

Plan the smallest reasonable clarification to docs/GUIDE.md that documents the doctor session-recovery diagnostic added in #4539 (read-only, filename-level, additive migration guidance).

[Hmbown]

@claude
Reply with a short implementation plan only. Do not edit files.

Same request as before, retesting reply visibility after the track_progress fix: plan the smallest reasonable clarification to docs/GUIDE.md documenting the doctor session-recovery diagnostic from #4539.

[claude]

Claude encountered an error after 1m 13s —— View job

---

Plan-only reply (no files edited)

• Read trigger comment and repo guidance (AGENTS.md, CLAUDE.md)
• Searched for the doctor session-recovery diagnostic referenced as "added in fix(doctor): diagnose recoverable legacy sessions #4539"
• Reviewed docs/GUIDE.md structure for the right insertion point
• Drafted smallest-reasonable clarification plan
• Posted plan

Verification note: I could not find evidence that a doctor session-recovery diagnostic has landed on main yet:

• No session-recovery/session recovery hits anywhere in the CLI/TUI/config crates.
• CHANGELOG.md's [Unreleased] section only lists the Solarized Light fix ([BUG] 升级到V0.9.0，日光主题失效 #4457) — no fix(doctor): diagnose recoverable legacy sessions #4539 entry.
• crates/cli/src/lib.rs doctor plumbing (Doctor(TuiPassthroughArgs), delegate_to_tui) is unchanged from what's documented today.

So #4539 appears not yet merged to this branch, or the diagnostic landed under different wording. Flagging this now rather than guessing at behavior that doesn't exist in the code yet.

Plan, conditioned on #4539 landing as described (smallest additive change, read-only/filename-level, no behavior change):

1. Insert one short paragraph in docs/GUIDE.md immediately after the existing doctor-check block (today at lines 107–121, right after the "If the doctor command reports that a rejected key came from the environment…" sentence, line 121).
2. Content of the addition (~2–3 sentences):
   • What the session-recovery diagnostic reports (read-only, filename-level check of recoverable session state).
   • That it's additive to existing doctor / doctor --json output, not a new subcommand.
   • One-line migration guidance pointer, matching the doc's existing legacy-~/.deepseek-vs-~/.codewhale framing used elsewhere in this same section.
3. No changes to CHANGELOG.md, code, or other docs — scope stays to the one clarification paragraph, per the issue's "docs-only" / "smallest reasonable clarification" framing.
4. Verification once implemented: re-read the new paragraph in context for tone/length consistency with the surrounding section; no build/test run needed for a docs-only wording change.

Before I implement: please confirm the diagnostic's actual field/flag name and exact behavior (or point me to the merged #4539 diff) so the doc addition is accurate rather than speculative. Happy to proceed on a follow-up comment once that's confirmed.

[Hmbown]

@claude
Confirmed: #4539 is merged (main commit 13221af). The diagnostic lives in crates/tui/src/main.rs as doctor_session_recovery_report / print_doctor_session_recovery_report / doctor_session_recovery_json — your search missed it because the identifiers use underscores. It reports legacy-session filename comparison only (statuses: isolated / no_legacy_sessions / migration_pending / migration_incomplete / migration_complete / scan_failed), never reads chat contents, is additive to doctor and doctor --json, and an explicit CODEWHALE_HOME suppresses ambient inspection.

Please implement your step-1/2 plan now: the one clarification paragraph in docs/GUIDE.md after the existing doctor block. Docs only; commit to your signed branch and leave the PR-creation link. Do not open a PR.

[claude]

Claude finished @Hmbown's task in 1m 13s —— View job • claude/issue-4542-20260719-0030 • Create PR ➔

---

Done

Todo list

• Read trigger comment and confirm scope (docs-only, implement prior plan)
• Re-read docs/GUIDE.md around the existing doctor-check section
• Insert the one clarification paragraph on the session-recovery diagnostic
• Verify wording accuracy against confirmed identifiers/statuses
• Commit to signed branch claude/issue-4542-20260719-0030
• Post PR-creation link (no PR opened)

Summary

Added one clarification paragraph to docs/GUIDE.md, immediately after the existing doctor-check block (following the "rejected key came from the environment" sentence). It documents the doctor / doctor --json session-recovery diagnostic from #4539:

• Confirms it's additive to existing doctor output, not a new subcommand.
• Lists the six reported statuses (isolated, no_legacy_sessions, migration_pending, migration_incomplete, migration_complete, scan_failed) and that it's a filename-level comparison only — never reads session contents.
• Ties migration_pending/migration_incomplete back to the doc's existing ~/.deepseek → ~/.codewhale migration guidance already stated a few lines above, rather than introducing new framing.
• Notes that an explicit CODEWHALE_HOME suppresses the ambient inspection.

Spot-checked crates/tui/src/main.rs and confirmed the reported status identifiers exist there, consistent with what was shared in the trigger comment.

Committed to claude/issue-4542-20260719-0030 (commit b6a9ab0). No PR opened, per instructions.

Not done

• No PR was created (out of scope per instructions — link above is for the maintainer to open one manually).
  · branch: claude/issue-4542-20260719-0030