docs(#5848): add CLI flag documentation sync rule to AGENTS.md

[fullsend-ai-coder]

Summary

Adds AGENTS.md guidance for keeping CLI reference documentation in sync with CLI flag changes. When modifying CLI flag help text, defaults, or behavior in internal/cli/, contributors are now instructed to update the corresponding page in docs/cli/ and search docs/guides/ for tables or descriptions referencing the same flag.

Related Issue

Closes #5848

Changes

• Added a bullet point to the "How to work in this repo" section of AGENTS.md instructing contributors to update docs/cli/ and search docs/guides/ when modifying CLI flags in internal/cli/

Testing

• make lint-md-links passes — no broken links
• No code changes; no test updates needed

Checklist

• PR title follows Conventional Commits (correct type, ! for breaking changes)
• Documentation-only change — no functional code modified

---

Closes #5848

Post-script verification

• Branch is not main/master (agent/5848-agents-cli-docs-guidance)
• Secret scan passed (gitleaks — 0251e7d777197981831f6713c44a53ca9a4e20f7..HEAD)
• PR body secret scan passed (gitleaks — no-git)

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 7:16 AM UTC · Completed 7:26 AM UTC
Commit: b74324a · View workflow run →

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[fullsend-ai-review]

Review

Findings

Medium

• [protected-path] AGENTS.md — This PR modifies AGENTS.md, a protected governance file. The change is authorized by issue AGENTS.md: add guidance to update docs/cli/ when changing CLI flag behavior #5848 and adds a single-line CLI flag documentation sync rule that is consistent with existing AGENTS.md guidance patterns. Human approval is always required for protected-path changes, regardless of context.

---

Labels: PR is a single-line documentation change to AGENTS.md governance file

[fullsend-ai-review]

See the review comment for full details.

[rh-hemartin]

/fs-fix rebase

[fullsend-ai-coder]

🤖 Finished Fix · ❌ Failure (post-script /home/runner/work/fullsend/fullsend/.fullsend/.fullsend-cache/resources/sha256/1704f826be06352c5aa727ca7a68e6bc3db1837e9743e1727323664169eefe2b/scripts/post-fix.sh failed: exit status 1) · Started 7:11 AM UTC · Completed 7:17 AM UTC

Commit: b74324a · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $1.37

[fullsend-ai-coder]

⚠️ Post-fix script failed — Secret scan blocked (exit code 1)

The fix agent completed, but the post-fix script failed before finishing.

Workflow run: https://github.com/fullsend-ai/fullsend/actions/runs/32941415827

Details:
Secret scan blocked the push. See workflow logs for details.
Please check the workflow logs for full details and retry with /fs-fix if appropriate.

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 6:52 AM UTC · Completed 7:03 AM UTC

Commit: 9ac44a5 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $3.14

[fullsend-ai-review]

Review skipped — this PR is already merged.

The /fs-review command only reviews open PRs/MRs.

_{Posted by fullsend pre-review check}

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 6:53 AM UTC · Completed 7:01 AM UTC

Commit: 9ac44a5 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $1.71

[fullsend-ai-retro]

Retro: PR #5850 — add CLI flag documentation sync rule to AGENTS.md

This PR was generated end-to-end by the agent pipeline: the retro agent on PR #5763 identified a gap (code agent updated CLI flag help text but didn't update manually-maintained docs/cli/ pages), filed #5848, and the code agent produced a correct 1-line AGENTS.md change in a single attempt. The review agent correctly flagged AGENTS.md as a protected governance file requiring human approval.

The only friction point was the fix agent's post-fix script failure. On Aug 26, a human requested /fs-fix rebase to resolve a stale branch. The fix agent (claude-opus-4-6, ~$1.37) successfully rebased and resolved the AGENTS.md merge conflict, but the post-fix gitleaks scan scanned 939 commits and detected 6 leaks — all false positives from upstream main history pulled into the scan range by the rebase. The human had to manually force-push the rebased commit and merge it the next day.

This scan-range expansion after rebase is a known bug, already tracked in #6259 and agents#318. PR #5850 provides additional evidence: the PRE_AGENT_HEAD..HEAD range included all upstream commits after the rebase, causing gitleaks detect to flag test fixtures in the main branch history. The fix proposed in agents#318 (use merge-base to compute the scan range after rebase) would have prevented this failure.

No new proposals — the workflow was otherwise clean, and the single failure is well-covered by existing issues.

[fullsend-ai-review]

Review skipped — this PR is already merged.

The /fs-review command only reviews open PRs/MRs.

_{Posted by fullsend post-review check}