spec-synclisted

Hard rule: **A change confirmed in conversation must not remain only in the conversation.** If user-confirmed intent that affects future collaboration or acceptance is not written back to the source of truth in this session, the next session cannot even see that the user changed their mind—intent that was never persisted cannot be recovered. ## The decision test (the only test for whether to sync) > If the next session or another agent read only the current source of truth, would it continue toward an outcome the user has rejected, violate a new constraint, or judge completion against stale criteria? If so, the change must be synced. - Only changes the user has **already confirmed** belong in the spec; your own inferences and ideas still under discussion do not. - Before deciding, read the current source of truth at most once to compare. Do not turn this into research. ## Write-back rules 1. Use the current source of truth already designated by the project—the document named by the project guide. 2. If none is designated, designate an existing Issue / PRD / ADR / status document as the current spec; **do not copy it into a second document**. If there are multiple candidates or none is obvious, ask the user to choose. 3. If nothing exists and the work genuinely spans sessions, is shared by multiple people, or would be costly to get wrong, ask whether the user wants a minimal spec (below). The user decides whether to create one; do not create one for work that can be complet