Update demo replay validation and testing documentation

- Modified the autodev state to reflect the current testing phase and details of the new `jetson-e2e` tests.
- Enhanced the "How to Test" documentation to provide clearer instructions on the demo replay validation process, including video and tlog alignment steps.
- Updated architectural documentation to include the new demo replay operator flow and its dependencies.
- Documented the removal of deprecated auto-sync features and clarified the operator-facing UI for replay validation.
- Added new entries in the dependencies table for upcoming tasks related to the demo replay flow.

These changes improve clarity and usability for operators and developers working with the demo replay system.

.cursor/skills/plan/templates/traceability-matrix.md

@@ -0,0 +1,47 @@
+# Traceability Matrix Template
+
+Save as `DOCUMENT_DIR/tests/traceability-matrix.md`.
+
+---
+
+```markdown
+# Traceability Matrix
+
+## Acceptance Criteria Coverage
+
+| AC ID | Acceptance Criterion | Test IDs | Coverage |
+|-------|---------------------|----------|----------|
+| AC-01 | [criterion text] | FT-P-01, NFT-PERF-01 | Covered |
+| AC-02 | [criterion text] | FT-P-02, FT-N-01 | Covered |
+| AC-03 | [criterion text] | — | NOT COVERED — [reason and mitigation] |
+
+## Restrictions Coverage
+
+| Restriction ID | Restriction | Test IDs | Coverage |
+|---------------|-------------|----------|----------|
+| RESTRICT-01 | [restriction text] | FT-N-02, NFT-RES-LIM-01 | Covered |
+| RESTRICT-02 | [restriction text] | — | NOT COVERED — [reason and mitigation] |
+
+## Coverage Summary
+
+| Category | Total Items | Covered | Not Covered | Coverage % |
+|----------|-----------|---------|-------------|-----------|
+| Acceptance Criteria | [N] | [N] | [N] | [%] |
+| Restrictions | [N] | [N] | [N] | [%] |
+| **Total** | [N] | [N] | [N] | [%] |
+
+## Uncovered Items Analysis
+
+| Item | Reason Not Covered | Risk | Mitigation |
+|------|-------------------|------|-----------|
+| [AC/Restriction ID] | [why it cannot be tested at blackbox level] | [what could go wrong] | [how risk is addressed — e.g., covered by component tests in Step 5] |
+```
+
+---
+
+## Guidance Notes
+
+- Every acceptance criterion must appear in the matrix — either covered or explicitly marked as not covered with a reason.
+- Every restriction must appear in the matrix.
+- NOT COVERED items must have a reason and a mitigation strategy (e.g., "covered at component test level" or "requires real hardware").
+- Coverage percentage should be at least 75% for acceptance criteria at the blackbox test level.