Update to fstack

{
  "description": "Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.",
  "included_files": [],
  "name": "principle-outcome-oriented-execution",
  "skill_md_contents": "---\r\nname: principle-outcome-oriented-execution\r\ndescription: \"Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.\"\r\nuser-invocable: false\r\ndisable-model-invocation: true\r\n---\r\n\r\n# Outcome-Oriented Execution\r\n\r\nOptimize for the intended, verifiable end state rather than preserving smooth intermediate states.\r\n\r\n**Why:** Keeping every intermediate step fully stable often creates temporary compatibility code that becomes long-lived debt. Converge on the target architecture and prove correctness at explicit verification boundaries.\r\n\r\n**Core rule:**\r\n- Prioritize end-state integrity over transitional stability\r\n- Intermediate breakage is acceptable when it is planned, scoped, and reversible\r\n- Always run final verification before declaring done\r\n\r\n**Guardrails:**\r\n- Use this for planned rewrites and migrations with explicit phase boundaries\r\n- Declare where temporary breakage is acceptable\r\n- Keep high-signal checks for actively touched areas while migrating\r\n- Require full static and runtime verification at plan completion\r\n"
}