Cleanup: delete only the preview doc via --stage PREVIEW

Live testing showed `raptor delete iac-module REF --yes --force` deletes the
PUBLISHED doc when a module has both published and preview versions — so
cleanup on an in-place-update PR would delete the customer's live module.

Delete now uses `raptor delete iac-module REF --stage PREVIEW --yes`, which
targets only the preview doc (and errors if no preview exists). Dropped
--force so the usage guard stays active and a genuinely in-use preview
surfaces as a real error instead of being force-deleted; that failure is
already recorded and gates the job. README version requirement updated to
list --stage alongside --feature-branch and list-JSON provenance.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: anujhydrabadi

module-ci-action/README.md

@@ -41,13 +41,19 @@ modules live at `infra/modules/...`).
 ## Requirements
 
 - **Runner:** Ubuntu (the action installs a Linux amd64 `raptor` binary).
-- **raptor version:** the **preview** mode uses `raptor create iac-module --feature-branch`,
-  a flag that marks a preview as **unpublishable**. It is newer than the base
-  `iac-module` commands, so preview mode requires a `raptor` release that ships
-  `--feature-branch` and surfaces module git provenance (`gitRef` / `previewGitRef`) in
-  `raptor get iac-module -o json`, which cleanup's ownership check reads. Pin
-  `raptor_version` accordingly if `latest` ever lags. Publish works on any recent
-  `raptor`; cleanup safely no-ops when those provenance fields are absent.
+- **raptor version:** preview and cleanup depend on newer `raptor` capabilities:
+  - **preview** uses `raptor create iac-module --feature-branch`, a flag that marks a
+    preview as **unpublishable**.
+  - **cleanup** reads module git provenance (`gitRef` / `previewGitRef`) from
+    `raptor get iac-module -o json` for its ownership check, and deletes with
+    `raptor delete iac-module --stage PREVIEW`, which targets **only** the preview doc
+    (so a module that has both a published and a preview version never loses its live
+    published doc).
+
+  These require a `raptor` release that ships all three (`--feature-branch`, row-level
+  provenance in the list JSON, and `delete --stage`). Pin `raptor_version` if `latest`
+  ever lags. Publish works on any recent `raptor`; cleanup safely no-ops when the
+  provenance fields are absent.
 
 ## Inputs
 

module-ci-action/action.yml

@@ -381,7 +381,11 @@ runs:
           fi
 
           echo "Deleting preview for ${REF} (owned by this PR, owning commit=${OWNER_SHA})..."
-          if ! raptor delete iac-module "$REF" --yes --force; then
+          # --stage PREVIEW targets ONLY the preview doc; without it a REF that has
+          # both a published and a preview doc would delete the live published
+          # module. Keep the usage guard (no --force) so a genuinely in-use preview
+          # surfaces as a real error rather than being force-deleted.
+          if ! raptor delete iac-module "$REF" --stage PREVIEW --yes; then
             echo "::error::Failed to delete preview for ${REF}"
             echo "${REF} (cleanup)" >> "$FAILURES"
           fi