v1.3.25 — Useful reconstruction slices

Broad reconstruction requests now start with the first useful user outcome and a short sequence of coherent working slices. Hard requirements remain binding; shared dependencies and unknowns that could change the design are distinguished from optional polish and deferred work.

• Improved journey selection, dependency ordering and evidence-linked acceptance guidance, with proportional loading and corrected-priority resume behavior.
• Added a save-first worked planning example and 14 manually assessed scenarios covering conflicting priorities, offline/file compatibility, unavailable backends, corrections and varied wording. These are same-agent, source-exposed teaching material, not a model benchmark or time-savings claim.
• Updated the usage example. Understand/future-build requests and narrow function scope retain their boundaries; a plan does not authorize implementation.

Installer, updater, integration, consent, path safety, historical fixtures and CI safeguards are unchanged. No dependency, model API, paid service, agent or scheduler is added. Validation and artifact identities are verified before publication; local denied preflights remain separately recorded limitations. Existing host sessions may need to reload the updated skill.