Smoke test agent review cleanup flow

[r3dbars]

Goal

Run a tiny smoke test of the agent todo pipeline after cleaning up stale human review issues.

Change

In docs/agent-issue-orchestration.md, add one short sentence to the Safety Notes section:

After a linked PR is merged, close the issue or move it to agent done so human review stays clean.

Acceptance

• Keep this docs-only.
• Do not touch app code.
• Open a draft PR.
• The runner should move this issue to human review and post the Human Review Ready hub comment.

[r3dbars]

Codex Workpad

State: Human Review
Workspace: /Users/redbars/code/symphony-workspaces/GH-627
Branch: codex/issue-627-smoke-test-agent-review-cleanup
PR: #628

Plan

• Read the issue and required repo docs.
• Sync with origin/main.
• Implement the smallest safe change.
• Run required verification.
• Open a draft PR.

Acceptance

• Docs-only change in docs/agent-issue-orchestration.md.
• No app code touched.
• Draft PR opened for review.

Validation

• Docs-only change; inspected git diff.
• No Swift/app tests run because no app code changed.

Notes

• Runner claimed this issue at 2026-04-30T19:34:13-05:00.
• Synced with origin/main; HEAD 095b15e.
• Pushed commit 6d4831a.

Blockers

• None.

[r3dbars]

Human Review Ready

PR: #628
Packet: #628 (comment)
Branch: codex/issue-627-smoke-test-agent-review-cleanup
Change type: tests/docs only

Visuals

No UI visual required.

QA

• Transcripted QA health: passed (swift run transcripted-qa check-health)

Automated Review

Status: completed

No blocking issues found.

Residual risks/manual checks:

• Docs-only change at docs/agent-issue-orchestration.md:146; no automation enforces closing the issue or moving it to agent done.
• QA health passed, but this does not verify the GitHub label/comment workflow end to end.

Changed Files

• docs/agent-issue-orchestration.md

What To Do Next

• If this looks good, review and merge the PR.
• If it needs changes, comment your feedback on this issue or the PR, then add agent todo again. The runner will resume this issue and update the existing PR.

Issue: #627