Update AGENTS.md files across multiple modules to standardize task status update instructions and introduce a new document for Secret Leak Detection operations.

- Modified task status update instructions in AGENTS.md files to refer to corresponding sprint files as `/docs/implplan/SPRINT_*.md` instead of `docs/implplan/SPRINTS.md`.
- Added a comprehensive document for Secret Leak Detection operations detailing scope, prerequisites, rule bundle lifecycle, enabling the analyzer, policy patterns, observability, troubleshooting, and references.

docs/modules/orchestrator/AGENTS.md

@@ -11,7 +11,7 @@ The Orchestrator schedules, observes, and recovers ingestion and analysis jobs a
 
 ## How to get started
 1. Read the design summaries in ./architecture.md (quota governance, job lifecycle, dashboard feeds).
-2. Open ../../implplan/SPRINTS.md and locate stories for this component.
+2. Open sprint file `/docs/implplan/SPRINT_*.md` and locate stories for this component.
 3. Check ./TASKS.md and update status before/after work.
 4. Review ./README.md for responsibilities and ensure changes maintain determinism and offline parity.
 
@@ -27,7 +27,7 @@ The Orchestrator schedules, observes, and recovers ingestion and analysis jobs a
 - `docs/modules/platform/architecture-overview.md`
 
 ## Working Agreement
-- 1. Update task status to `DOING`/`DONE` in both `docs/implplan/SPRINTS.md` and the local `TASKS.md` when you start or finish work.
+- 1. Update task status to `DOING`/`DONE` in both correspoding sprint file `/docs/implplan/SPRINT_*.md` and the local `TASKS.md` when you start or finish work.
 - 2. Review this charter and the Required Reading documents before coding; confirm prerequisites are met.
 - 3. Keep changes deterministic (stable ordering, timestamps, hashes) and align with offline/air-gap expectations.
 - 4. Coordinate doc updates, tests, and cross-guild communication whenever contracts or workflows change.