docs(#5954): link per-repo config header to user-facing docs

[fullsend-ai-coder]

Summary

Replace the bare "ADR 0033" reference in the generated per-repo .fullsend/config.yaml header with a direct link to the published user-facing documentation at https://fullsend.sh/docs/guides/infrastructure/layered-config-reference.

Related Issue

Closes #5954

Changes

• Update perRepoConfigHeader in internal/config/config.go to replace the internal ADR citation with the published docs URL
• Add TestPerRepoConfigHeaderPointsToUserDocs regression test asserting the header links to user-facing docs and does not reference internal ADRs

Testing

• go test ./internal/config/... passes
• New test TestPerRepoConfigHeaderPointsToUserDocs added and passing
• go vet ./internal/config/... passes
• Secret scan passes

---

Closes #5954

Post-script verification

• Branch is not main/master (agent/5954-config-header-link)
• Secret scan passed (gitleaks — 900d4f429bf350a5a86701d97c08af848d48caf5..HEAD)
• PR body secret scan passed (gitleaks — no-git)

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 8:09 PM UTC · Completed 8:18 PM UTC
Commit: 7833d85 · 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

Low

• [stale-reference] .fullsend/config.yaml:5 — The repo’s own .fullsend/config.yaml still contains the old header text # See ADR 0033 for details. — the exact wording this PR removes from the perRepoConfigHeader template. After this PR, newly generated config files will have the updated header pointing to the user-facing docs, but this existing committed config file retains the stale ADR reference.
  Remediation: Update the header comment in .fullsend/config.yaml line 5 to match the new perRepoConfigHeader template.

Previous run

Looks good to me

[rh-hemartin]

/fs-fix rebase and resolve conflicts

[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:15 AM UTC · Completed 7:21 AM UTC

Commit: 7833d85 · View workflow run →

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

[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/32941698772

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 7:00 AM UTC · Completed 7:14 AM UTC

Commit: 257f41d · View workflow run →

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

[fullsend-ai-review]

Risk Assessment: moderate (2/5)

Details

Tiny documentation-only comment change replacing an ADR reference with a user-facing docs URL, elevated to moderate solely because the target files are high-churn hotspots with many recent authors and fix commits.

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 7:23 AM UTC · Completed 7:33 AM UTC

Commit: 257f41d · View workflow run →

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

[fullsend-ai-retro]

Retro: PR #5956 — link per-repo config header to user-facing docs

Workflow: Issue #5954 → triage → code agent → review → (21-day wait) → human /fs-fix rebase → fix agent failure → human force-push → re-review → merge.

Agents repo: fullsend-ai/agents@main (commit 19f8eaba9d48).

What went well

• Code agent produced correct, minimal, well-tested code on the first attempt (2 files, 8 additions, 10 deletions, regression test included). Zero rework iterations on the code itself.
• Review agent caught a real issue: the repo's own .fullsend/config.yaml:5 still contains the stale # See ADR 0033 for details. header that the PR was removing from the template. This was a genuine completeness gap in the code agent's work.
• CI passed cleanly on every push. Codecov confirmed full patch coverage.

Evidence for existing open issues

• fix(ci): post-fix gitleaks scan false-positives when fix agent merges or rebases main #6259 (post-fix gitleaks false-positives on rebase): This PR is another instance of the exact bug. The fix agent successfully rebased the branch (run 32941698772), but SCAN_RANGE used PRE_AGENT_HEAD (7833d85), which is no longer an ancestor after rebase. Gitleaks scanned 744 commits and found 6 pre-existing false-positive leaks, blocking the push. Cost: $1.15 wasted, plus the human had to manually force-push the same rebased commit the next day.
• Skip re-review when PR diff is unchanged after rebase/reopen #1356 (skip re-review when PR diff is unchanged after rebase/reopen): After the human force-pushed the rebased commit (identical diff, just rebased onto current main), the review agent ran a full re-review costing $3.82 and produced the same finding as the original review. The diff content was unchanged.
• Auto-file tracking issues for unresolved low-severity review findings #1286 (auto-file tracking issues for unresolved low-severity review findings): The review agent correctly identified the stale .fullsend/config.yaml reference as a Low-severity finding, approved the PR, and the PR was merged without addressing it. No follow-up issue was filed. The stale reference remains in the repo today.

No new proposals

All significant findings from this workflow are already covered by open issues. The workflow was clean overall — the code agent got it right on the first try, the review agent caught a real gap, and the only friction came from the known post-fix gitleaks rebase bug (#6259).