@msn-control/liftoff 0.10.1 → 0.10.2

package/docs/safety-and-consent.md

@@ -98,11 +98,12 @@ are committed only after the other mutations succeed.
 
 Managed update may install manifest v7, policy v6, activation-contract v1,
 phase graph, compatibility metadata, credential-policy schema, setup
-integrations, and compatibility aliases. It preserves user-owned activation
-state, approvals, immutable evidence, credential policies, active OpenSpec
-changes, and bootstrap retention/disposal records. If the current activation
-identity is future, unsupported, or graph-incompatible, update and setup block
-with a remedy instead of downgrading or rewriting state.
+integrations, and forced removal of exact retired generated setup-alias entries
+from older manifests. It preserves user-owned activation state, approvals,
+immutable evidence, credential policies, active OpenSpec changes, and bootstrap
+retention/disposal records. If the current activation identity is future,
+unsupported, or graph-incompatible, update and setup block with a remedy instead
+of downgrading or rewriting state.
 
 If automatic rollback itself cannot safely restore a path because another
 process changed it, Liftoff reports the incomplete rollback rather than

package/docs/troubleshooting.md

@@ -193,8 +193,9 @@ completes, syncs, and archives the generated bootstrap seed with local baseline
 checks, then stops at explicit authority gates for commit/push, credentials,
 billed infrastructure or exceptions, final enforcement, destructive cleanup, or
 external blockers. Rerun `/liftoff-setup` to resume; verified phases are not
-repeated. `/liftoff-repository-governance` is only a compatibility alias for the
-same engine and state.
+repeated. Older generated setup aliases are retired; after review,
+`liftoff update --force` removes exact modified retired alias entries from older
+manifests.
 
 Missing licenses, runner-provisioning authority, a private Staging assignment or
 reachable network path, alert routes, parallel deployment, or sufficient canary

package/docs/workloads.md

@@ -40,7 +40,7 @@ Automation can select the neutral starting point explicitly with
 - Docker Compose and Azure OpenTofu.
 - Optional Vue frontend and pattern-specific Azure Functions workers.
 - Versioned repository-governance policy, workload context, guide, and
-  selected-agent launcher unless `none` is selected.
+  selected-agent `/liftoff-setup` integration unless `none` is selected.
 
 ### Deferred actions
 
@@ -107,7 +107,7 @@ environment, API frontend, Docker, or OpenTofu selection.
 - `liftoff.config.json`, manifest-v7 `liftoff.manifest.json`, starter provenance,
   and third-party attribution.
 - Official OpenSpec or Spec Kit output and every selected agent marker.
-- The common local governance policy and selected-agent launcher, with backend,
+- The common local governance policy and selected-agent `/liftoff-setup` integration, with backend,
   container, OpenTofu, custom deployment, and API DAST controls marked
   inapplicable.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@msn-control/liftoff",
-  "version": "0.10.1",
+  "version": "0.10.2",
   "description": "Interactive CLI for governed GenAI, API, and Power Apps code app projects.",
   "type": "module",
   "license": "GPL-3.0-only",