docs(#6): add FULLSEND.md documenting fullsend usage

[fullsend-ai-coder]

Summary

• Adds FULLSEND.md at the repository root documenting how fullsend is configured and used in this repository
• Covers all six enabled roles (triage, coder, review, fix, retro, prioritize) with triggers and descriptions
• Documents the interaction workflow and the /fs-fix-stop escape hatch

Testing

• Verified all six configured roles from .fullsend/config.yaml are referenced in the document
• No production code or CI changes — documentation only

---

Closes #6

Post-script verification

• Branch is not main/master (agent/6-add-fullsend-docs)
• Secret scan passed (gitleaks — e416f2301b7f751511265e6edc2f772e194d4c13..HEAD)
• PR body secret scan passed (gitleaks — no-git)

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 3:03 PM UTC · Completed 3:16 PM UTC

Commit: 766b0d1 · View workflow run →

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

[fullsend-ai-review]

Risk Assessment: low (1/5)

Details

Docs-only PR by a bot adding a single new markdown file (46 lines). No protected paths, no security-sensitive files, no CI or dependency changes. Issue scope perfectly matches PR size. Minimal risk across all tiers.

Previous run

Risk Assessment: low (1/5)

Details

Documentation-only PR by a known bot adding a single new markdown file (46 lines) with no protected paths, no security-sensitive files, no dependency or CI changes, and perfect alignment with the linked issue scope — all signals indicate minimal risk.

[fullsend-ai-review]

Looks good to me

Previous run

Review

Findings

Low

• [Technical documentation accuracy] FULLSEND.md:14 — The triage role trigger is described as "Issue opened or labeled", but the actual workflow (.github/workflows/fullsend.yaml) fires on issues with types [opened, edited, labeled]. The "edited" event type is omitted from the documentation, which could confuse users who see triage re-fire after editing an issue.
  Remediation: Change the trigger description for triage to "Issue opened, edited, or labeled".

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

[fullsend-ai-coder]

🤖 Finished Fix · ✅ Success · Started 3:18 PM UTC · Completed 3:21 PM UTC

Commit: 766b0d1 · View workflow run →

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

[fullsend-ai-coder]

🔧 Fix agent — iteration 1 (bot-triggered)

Fixed the triage role trigger description in FULLSEND.md to include the missing 'edited' event type, matching the actual workflow configuration.

Fixed (1):

1. Technical documentation accuracy: triage role trigger missing 'edited' event type (FULLSEND.md): Changed triage trigger description from 'Issue opened or labeled' to 'Issue opened, edited, or labeled' to match the actual workflow configuration in .github/workflows/fullsend.yaml which specifies types: [opened, edited, labeled]

Tests: passed

Next steps:

• /fs-review — request a re-review of the changes
• /fs-fix <your instruction> — run another fix pass with specific guidance
• Push commits directly — review re-runs automatically on push
  _{Updated by fullsend fix agent}

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 3:24 PM UTC · Completed 3:35 PM UTC

Commit: 2b1d489 · View workflow run →

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

Superseded by updated review