feat(FN-4892): complete Step 9 — document intake auto-archive heuristics

Fusion-Task-Id: FN-4892
Fusion-Task-Lineage: 6f56b468-a827-416d-ba1f-444e1326d613

.changeset/FN-4892-ghost-bug-and-duplicate-intake.md

@@ -0,0 +1,5 @@
+---
+"@runfusion/fusion": patch
+---
+
+Add intake-side auto-archive safeguards: ghost-bug preflight on triage finalize and same-agent duplicate detection at task creation. Both paths are fail-open on errors/timeouts and emit structured activity/audit events when auto-archive triggers.

docs/task-management.md

@@ -27,6 +27,24 @@ Dashboard `POST /tasks` now performs a pre-create duplicate gate using token-ove
   - `task.source.sourceMetadata.acknowledgedDuplicateIds = [...]`
 - Override creates emit activity type `task:duplicate-warning-overridden` with acknowledged IDs and scored candidate metadata.
 
+### Intake auto-archive (ghost-bug preflight + same-agent duplicate)
+
+Fusion applies two conservative intake heuristics that may auto-archive newly filed tasks before execution starts:
+
+- **Ghost-bug preflight** (triage finalize path): for bug-fix-shaped specs that cite concrete constructs/commands, Fusion probes current `main`. If all definitive probes show the cited bug does not reproduce, the task is archived as `auto-resolved-ghost-bug`.
+- **Same-agent duplicate intake** (create path): if the same `source.sourceAgentId` filed a highly similar task within 24h (threshold `0.75`), the later task is archived as `auto-resolved-duplicate` and the earliest sibling is kept.
+
+Both heuristics are **fail-open**: probe/detection errors, timeouts, or inconclusive signals do not block normal intake — the task continues in the regular flow.
+
+Activity + run-audit event types:
+
+- `task:auto-archived-ghost-bug`
+- `task:auto-archived-duplicate`
+
+These appear in task activity history; run-audit entries are emitted where run context exists (triage/engine paths). Store-only intake paths record activity without synthetic run context.
+
+Recovery is reversible: restore archived tasks via dashboard **Unarchive** or `fn_task_unarchive`.
+
 ### 2) Plan Mode (AI interview)
 
 Use the 💡 button to open planning mode: