- 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.
Root cause: I ran the full unit suite at the end of every autodev
batch despite implement/SKILL.md already saying that is forbidden
(lines 33, 136, 145, 372). The skill's existing rules were buried
mid-document; coderule.mdc's general "run full suite when done"
overrode them in practice because each batch felt like a "done"
point.
Two targeted clarifications:
- .cursor/rules/coderule.mdc: add an Iterative-Skill Exception
bullet stating that when an iterative loop skill (autodev /
implement batch loop, refactor batch loop) is active, the
skill governs full-suite cadence and "done with changes"
means done with the implementation phase, not done with one
batch.
- .cursor/skills/implement/SKILL.md: hoist the per-batch / per-
task / Step-16 cadence rule into a top-of-file "READ FIRST,
EVERY BATCH" banner with an explicit anti-pattern check ("if
you catch yourself about to run pytest tests/ at end of batch,
STOP").
Co-authored-by: Cursor <cursoragent@cursor.com>
Oleksandr Bezdieniezhnykh