docs(claude-review-lanes): correct stale present-tense claim about #331

[kyle-sexton]

One-sentence fix: the Approval-record narrowing paragraph described ci-workflows#331 as "the open PR moving the incident write to the ambient token"; that PR merged (a90ff43). Present tense corrected with the merge SHA recorded. Surfaced by the fresh-context verifier on #390 as an out-of-diff observation in the exact region the Phase 4 close-out amendment re-activates.

Related

No linked issue. For reference: #390, #331.

🤖 Generated with Claude Code

https://claude.ai/code/session_01HCJfVqDNYt92YRyvKUMgYW

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[claude]

Claude finished @kyle-sexton's task in 2m 57s —— View job

---

Code Review Complete

Scope: docs/topics/claude-review-lanes/PLAN.md (+2/-2), the only changed file.

Summary

The change corrects present-tense phrasing ("ci-workflows#331 is the open PR moving the incident write...") to past tense ("ci-workflows#331 (since merged, a90ff43) moved the incident write...") in the Phase 4 Approval-record narrowing paragraph. This is a pure editorial/factual correction with no code, workflow, or security-model impact — CLAUDE.md's security ground rules and SHA-pinning rule don't apply here (this is prose citing a merge SHA for provenance, not a uses: pin).

On the claim itself: I cross-checked the substance against the current .github/workflows/claude-lane-incident-aggregator.yml, and it corroborates the correction — the App-token mint step requests permission-issues: read only (line 193), and the header comment (lines 16–29) confirms the same-repo incident-issue write now runs on the ambient GITHUB_TOKEN's issues: write job permission, matching "moved the incident write to the ambient token." I could not independently verify the specific merge SHA a90ff43 or PR #331's merged state via git/gh — this session's sandbox blocked both git fetch (shallow clone, only 2 commits available locally) and gh pr view (network access not approved). That detail should be treated as author-claimed and unverified by me, though the corroborating workflow-file evidence above makes it plausible.

Finding (inline, non-blocking)

Posted one inline comment: the tense fix on lines 1997–1998 exposes a pre-existing, adjacent stale claim in the same sentence — the parenthetical "which still requests \permission-issues: write`" (line 1996) doesn't match the current workflow file, which requests permission-issues: read`. This isn't something this PR needs to fix (it predates this change and is outside this PR's stated one-sentence scope), but it's now more visibly inconsistent within the same sentence and worth a fast follow-up in the same paragraph.

No other issues found. The edit is minimal, accurate in substance, and consistent with the file's established "#NNN merged as <short-sha>" citation convention used elsewhere in this document (e.g. lines 354, 411, 563, 1643).

[github-actions]

Claude has reviewed this PR 1 time. The lane skips further automatic reviews after 5; deleting this comment resets the count.