docs(#231): add cross-reference update guidance to AGENTS.md

[fullsend-ai-coder]

When implementing a feature previously described as in progress, coming soon, or planned in the docs, authors should search for and update those stale references in the same PR. This gives the review agent a documented convention to cite when flagging stale cross-references.

---

Closes #231

Post-script verification

• Branch is not main/master (agent/231-crossref-doc-guidance)
• Secret scan passed (gitleaks — c776c248ac9a91f10998ca7107e974a6c9d76514..HEAD)
• Pre-commit hooks passed (authoritative run on runner)
• Tests ran inside sandbox

[fullsend-ai-review]

🤖 Finished Review · ❌ Failure · Started 12:57 PM UTC · Completed 12:57 PM UTC
Commit: c776c24 · View workflow run →

[guyoron1]

/fs-review

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 3:57 PM UTC · Completed 4:02 PM UTC
Commit: d8e3df7 · View workflow run →

[fullsend-ai-review]

Review — ✅ Approve

PR: docs(#231): add cross-reference update guidance to AGENTS.md
Scope: 1 file, 1 line added

Summary

Clean, well-scoped documentation change. Adds a single bullet to the "How to work in this repo" section of AGENTS.md instructing contributors to search for and update stale "in progress" / "coming soon" / "planned" references when implementing a feature.

Dimension results

Dimension	Result	Notes
Correctness	✅ No findings	Guidance is technically accurate; grep terms are reasonable search heuristics; consistent with existing co-location patterns (mint sync rules, ADR cross-update rules)
Security	✅ No findings	Docs-only, no secrets/permissions/injection patterns
Intent & coherence	✅ No findings	Precisely implements issue #231 authorization; no scope creep
Style & conventions	✅ No findings	Matches dash-space-sentence format, imperative tone, backtick usage, and punctuation of surrounding bullets
Docs currency	✅ No findings	No stale references introduced; terms are example search phrases
Cross-repo contracts	⏭ Skipped	No exported interfaces or schemas modified

Observations

The change addresses a real gap identified in the retro for PR fullsend-ai#2773, where a stale "still in progress" reference persisted through 7 review iterations. The new bullet gives both human authors and autonomous agents a concrete checklist item, and gives the review agent a documented convention to cite when flagging stale-feature-status findings.

---

Protected paths detected — this PR modifies files under one or more
protected paths. The review agent cannot approve PRs that touch these paths.
A human reviewer must approve this PR.

Protected files in this PR:

• AGENTS.md

---

Labels: PR adds documentation guidance to AGENTS.md

[guyoron1]

/fs-fix

[fullsend-ai-coder]

🤖 Finished Fix · ✅ Success · Started 5:38 PM UTC · Completed 5:42 PM UTC
Commit: d8e3df7 · View workflow run →

[fullsend-ai-coder]

🔧 Fix agent — iteration 1 (human-triggered)

No changes made. The review agent already approved PR #265 with zero findings. The human /fs-fix trigger provided no specific instruction. The PR modifies only AGENTS.md (a protected path), which requires human approval — the review agent correctly flagged this but had no code findings to address.

Disagreed (1):

1. No actionable feedback to address: The review agent approved this PR with no findings across all dimensions (correctness, security, intent & coherence, style & conventions, docs currency). The human triggered /fs-fix with no specific instruction. There are no code changes to make.

Tests: passed

_{Updated by fullsend fix agent}