[wdm0006]

Adds a focused section to guarding-destructive-operations on testing recovery against the target produced by real setup and optional scheduling scaffolds.

Motivating pattern: a tool can generate tracked workflow files outside its owned state directory, then correctly refuse its own scaffold during a later rebuild. Ordinary runs and previews may never reach the destructive guard. Broadening the accepted directory is unsafe unless the destructive implementation also preserves the admitted files.

Readers get a concrete lifecycle verification sequence and a requirement to define preservation or an actionable safe recovery procedure while keeping unrelated content rejected.

Validation: both CI commands passed on Python 3.12 (62 pytest tests; 62 unittest tests); git diff --check passed. Only one existing skill changed; no registration changes are needed.