What happened
PR #2761 deleted internal/scaffold/fullsend-repo/env/retro.env as part of the ADR 0055 migration, moving its environment variables into retro.yaml directly. The review agent flagged that docs/superpowers/plans/2026-05-04-retro-agent.md still contains 5 references to the deleted file at lines 22 (file structure table), 184 (task description), 197 (write instruction), 202 (git add command), and 669-670 (harness config YAML example). This was a low-severity stale-reference finding. The PR was merged without addressing it.
What could go better
Stale documentation references can mislead agents and contributors who consult plan docs for implementation context. The review agent caught this, but low-severity findings in docs are easily deprioritized. For plan documents that describe implementation details (file paths, commands), staleness is more harmful than for conceptual docs because agents may follow the instructions literally. Confidence is high — the stale references are confirmed by grep.
Proposed change
Update docs/superpowers/plans/2026-05-04-retro-agent.md to either remove the env/retro.env references or annotate them as superseded by the env.runner/env.sandbox pattern in retro.yaml. The file structure table (line 22), task 3 instructions (lines 184, 197, 202), and harness config example (lines 669-670) all need updating to reflect the current implementation.
Validation criteria
Grep for 'retro.env' in the docs directory returns zero matches. The plan doc accurately reflects the current implementation approach using env.runner/env.sandbox.
Generated by retro agent from #2761
What happened
PR #2761 deleted
internal/scaffold/fullsend-repo/env/retro.envas part of the ADR 0055 migration, moving its environment variables into retro.yaml directly. The review agent flagged thatdocs/superpowers/plans/2026-05-04-retro-agent.mdstill contains 5 references to the deleted file at lines 22 (file structure table), 184 (task description), 197 (write instruction), 202 (git add command), and 669-670 (harness config YAML example). This was a low-severity stale-reference finding. The PR was merged without addressing it.What could go better
Stale documentation references can mislead agents and contributors who consult plan docs for implementation context. The review agent caught this, but low-severity findings in docs are easily deprioritized. For plan documents that describe implementation details (file paths, commands), staleness is more harmful than for conceptual docs because agents may follow the instructions literally. Confidence is high — the stale references are confirmed by grep.
Proposed change
Update
docs/superpowers/plans/2026-05-04-retro-agent.mdto either remove theenv/retro.envreferences or annotate them as superseded by theenv.runner/env.sandboxpattern in retro.yaml. The file structure table (line 22), task 3 instructions (lines 184, 197, 202), and harness config example (lines 669-670) all need updating to reflect the current implementation.Validation criteria
Grep for 'retro.env' in the docs directory returns zero matches. The plan doc accurately reflects the current implementation approach using env.runner/env.sandbox.
Generated by retro agent from #2761