consolidate the tests locations

docs/implplan/AGENTS.md

@@ -11,19 +11,7 @@
 - `docs/implplan` sprint template rules (see Section “Naming & Structure” below)
 - Any sprint-specific upstream docs linked from the current sprint file (e.g., crypto audit, replay runbooks, module architecture dossiers referenced in Dependencies/Prereqs sections)
 
-## Naming & Structure
-- Sprint filename format: `SPRINT_<IMPLID>_<BATCHID>_<SPRINTID>_<topic>.md` (see global charter §4.2). Normalize existing files to this format while preserving content and log the rename in Execution Log.
-- Internal template (required sections): Topic & Scope, Dependencies & Concurrency, Documentation Prerequisites, Delivery Tracker, Wave Coordination (if multi-wave), Wave Detail Snapshots, Interlocks, Upcoming Checkpoints, Action Tracker, Decisions & Risks (incl. risk table), Execution Log.
-- Status flow: `TODO → DOING → DONE/BLOCKED`. Flip status only when evidence is captured in the sprint doc.
-
-## Determinism & Metadata
-- Use UTC dates (`YYYY-MM-DD`) and include timezone labels for meetings if relevant.
-- Keep tables ordered deterministically (by task ID or due date). Avoid ad-hoc reshuffling.
-- When blocking, state the concrete dependency/document name and expected next signal/date.
-
 ## Documentation Rules
-- For any design/advisory/platform decision surfaced here, update the canonical doc under `docs/**` (architecture, ADR, product advisory, etc.) and link it from Decisions & Risks.
-- Archival: completed tasks should flow to `docs/implplan/archived/tasks.md` as per sprint guidance.
 - Avoid external URLs unless already present; prefer relative doc links.
 
 ## Advisory Handling (must do for every new advisory)