[AZ-263] [AZ-264] [AZ-265] Decompose: layout, helpers epic, replay epic

Decompose Step 1 + Step 1.5 + new cycle-1 epics:

- Step 1 (Bootstrap): AZ-263 spec at _docs/02_tasks/todo/. Single
  top-level Python package src/gps_denied_onboard/ + nested
  components/ subpackage per user feedback (replaces earlier
  src/gps_denied/ + sibling src/components/ split).
- Step 1.5 (Module Layout): _docs/02_document/module-layout.md is
  the file-ownership map consumed by /implement Step 4. Covers all
  14 components + cross-cuttings (_types, config, logging,
  fdr_client, helpers x8, frame_source, clock, runtime_root,
  cli/replay, healthcheck), 5-layer layering, and the Build-Time
  Exclusion Map for all 4 binaries (airborne, research,
  operator-tooling, replay-cli).
- New epic AZ-264 (E-CC-HELPERS): re-homes the 8 shared helpers
  from per-component child-issues into a single cross-cutting
  epic per the decompose skill cross-cutting rule. R14
  (LightGlue circular dep) is structurally prevented because
  both C2.5 and C3 import gps_denied_onboard.helpers.lightglue_runtime.
- New epic AZ-265 (E-DEMO-REPLAY): offline replay mode (video +
  tlog -> per-tick coordinate stream). 8 child tasks, 27-32 pts.
  Reuses C8 FcAdapter via TlogReplayFcAdapter strategy + new
  VideoFileFrameSource + JsonlReplaySink + compose_replay
  composition root + gps-denied-replay CLI + auto-sync via IMU
  take-off detection (per how_to_test.md). NO ROS dependency.
- Plan Final report at FINAL_report.md.
- _autodev_state.md updated with handoff notes for Step 2
  execution in a fresh chat (~290 MCP calls expected; epic
  ordering documented).

Step 2 task PLAN approved (97 implementation tasks across 18
epics) but EXECUTION deferred per user choice to a fresh chat.

Co-authored-by: Cursor <cursoragent@cursor.com>

_docs/_autodev_state.md

@@ -2,12 +2,42 @@
 
 ## Current Step
 flow: greenfield
-step: 3
-name: Plan
+step: 6
+name: Decompose
 status: in_progress
 sub_step:
-  phase: 21
-  name: plan-step6-epics-local-draft
-  detail: "Step 5 complete; Step 6 epics.md drafted locally (18 epics, 2054 lines, chunked write per new large-file-writes rule); awaiting user decision on Jira push"
+  phase: 3
+  name: decompose-step2-task-decomposition
+  detail: |
+    Step 1 (Bootstrap) and Step 1.5 (Module Layout) approved by user. Step 2 task PLAN approved
+    (97 implementation tasks across 18 epics — see chat plan table). Two new epics created during
+    Step 2 prep: AZ-264 (E-CC-HELPERS) re-homes the 8 shared helpers per the cross-cutting rule;
+    AZ-265 (E-DEMO-REPLAY) adds offline replay mode (video + tlog → JSONL per-tick coordinate
+    stream; subprocess-shaped UI integration; no ROS dependency). epics.md and module-layout.md
+    updated to reflect both new epics. Per user's choice (option D), Step 2 EXECUTION
+    (~290 MCP calls to write specs + create tickets + rename files) is deferred to a fresh chat.
+    Resume in fresh chat by reading this state file + epics.md + module-layout.md, then
+    iterate epic-by-epic in dependency order: AZ-245, AZ-246, AZ-247, AZ-264, AZ-248, AZ-249,
+    AZ-250, AZ-251, AZ-252, AZ-253, AZ-254, AZ-255, AZ-256, AZ-257, AZ-258, AZ-259, AZ-260,
+    AZ-261, AZ-265 (replay tasks last; depend on every C1–C5 epic).
 retry_count: 0
 cycle: 1
+tracker: jira
+
+## Resume notes (fresh chat handoff)
+
+When resuming Step 2 execution in a fresh chat, the agent should:
+
+1. Read `_docs/_autodev_state.md` (this file).
+2. Read `_docs/02_document/epics.md` (canonical E-* ↔ AZ-NN map; rows 17–21).
+3. Read `_docs/02_document/module-layout.md` (file-ownership map for the implement skill).
+4. Read `_docs/02_tasks/todo/AZ-263_initial_structure.md` (already-completed bootstrap task spec).
+5. Replay any leftovers in `_docs/_process_leftovers/` per `tracker.mdc`.
+6. Begin Step 2 execution one epic at a time, in the order listed above. Per-epic
+   per-task workflow: write `todo/[##]_[short_name].md` → create Jira ticket parented to
+   the right epic → rename file to `todo/[AZ-NN]_[short_name].md` → update Tracker/Epic
+   fields inside the file → repeat. Brief progress note after each epic completes.
+7. After all 19 epics' tasks are written, run Step 4 (Cross-Verification) to produce
+   `_docs/02_tasks/_dependencies_table.md` and resolve any cross-task dependency drift.
+8. Then auto-chain to Step 3 (Blackbox Test Tasks) for E-BBT (AZ-262) per the
+   user's earlier choice to defer test-spec Phase 4 to the Decompose pass.