Description
The provisioner records ownership and uncertain mutations for preview/apply but deliberately never deletes resources. Removing a deployment therefore lacks a supported ownership-bound cleanup and remaining-custody receipt. A generic explicit cleanup contract must preserve target binding, authoritative resource identities and concurrent user changes instead of deleting by name, spec or folder membership.
Acceptance Criteria
- #1 Preview and separately explicit cleanup operate only on exact recorded target-bound owned resource identities and validated remote revisions; foreign, changed, legacy-unbound or incomplete custody remains a refusal rather than adoption
- #2 Pending intent is durable before remote mutation, lost responses and interruption retain recovery custody, and a secret-free terminal or remaining-obligation receipt distinguishes confirmed absence from unknown outcomes
- #3 Process-boundary tests exercise owned and foreign resources, concurrent modification, response loss and emitter/provisioner authority; ordinary preview/apply/release-only activation remain compatible and no tenant-wide deletion or credential substitution is introduced
Definition of Done
- #1 just check (fmt-check, lint, gen-check, env-check, docs-check, test, race, hygiene, ui-check, compose-check, helm-test, lab-check, signal-fidelity)
- #2 just gen (only if a blueprint field, construct/workload config struct, or a skill under plugins/synthkit/skills/ changed)
- #3 just dump — inventory diffed against signals/
Implementation Notes
Landed bebf4c3 (loop50 BATCH5). Follow-up SKT-0149 covers cleanup after SM disable and chart packaging. Main CI green on 1d627bf.