clonamic-write-controllisted

# Clonamic Write Control Read-only work leaves immediately without workflow state. For writes: - clear: one chat-only development specification and approval; - material ambiguity: one work specification, approved inspection, then one development specification; - precise tiny change: one line with target, change, verification, rollback, and code. Return only when scope, authority, output, or risk materially changes; implementation detail never adds a gate. ## Approval `승인:ABC123` is a correlation code. Accept one backtick pair, fullwidth colon, whitespace, and lowercase. Plain `승인` selects the sole pending packet; multiple packets require the code. One approval covers inspect-fix-retest-apply-deploy-backup. Password, OAuth, biometric, and platform permission remain platform actions. For automation, apply [references/automation-contract.json](references/automation-contract.json). Host metadata creates only a candidate; a matching persisted claim grants authority. Claimed runs never wait conversationally. Replay is rejected, changes return `needs_authorization`, and credentials return `waiting_platform_action` without consuming the run. The write packet contains only target and change, observable output, verification, effects or credentials, rollback, and project-convention conflicts. The request defines scope: choose the smallest working change, reuse existing code, and reject adjacent work. Read [references/write-contract.md](references/write-contract.md) for non-trivia