# Mode: cycle-update

A scoped refresh of existing test-spec artifacts against the current feature cycle's completed tasks. Used by `existing-code` flow's per-cycle sync step.

## Inputs

- The list of task spec files in `_docs/02_tasks/done/` implemented in the current cycle
- `_docs/03_implementation/implementation_report_{feature_slug}_cycle{N}.md`

## Phases that run

- Skip Phase 1 (input data analysis)
- Skip Phase 4 (script generation)
- Run a **narrowed** Phase 2 and Phase 3 per the rules below

## Narrowed rules

1. For each new AC in the cycle's task specs, check `traceability-matrix.md`. If not covered, append one row.
2. For each new component surface exposed in the cycle (new endpoint, event, DTO field — detectable from task Scope and from diffs against `module-layout.md`), append scenarios to the relevant `blackbox-tests.md` / `performance-tests.md` / `security-tests.md` / `resilience-tests.md` / `resource-limit-tests.md` category. Reuse the existing test template shapes.
3. For each NFR declared in a cycle task spec, propagate it to the matching spec file. If the NFR conflicts with an existing spec entry, present via the Choose format.
4. Do NOT rewrite unaffected sections. Preserve existing traceability IDs.
5. Save only the files that changed, update `traceability-matrix.md` last.

## Save action

Save only the changed test artifact files under `TESTS_OUTPUT_DIR`. Update `traceability-matrix.md` last, after all per-category files are written.
