@msn-control/liftoff 0.6.1 → 0.7.0

package/docs/cli-reference.md

@@ -24,8 +24,9 @@ plan -> init or migrate -> validate and doctor -> update -> dev and infra helper
 | `liftoff migrate <source>` | Creates a new sibling scaffold and filtered source copy without changing the source |
 | `liftoff validate [project]` | Validates manifest identity, durable files, workload metadata, and framework markers |
 | `liftoff doctor [project]` | Runs read-only workload-derived project and workstation diagnostics |
-| `liftoff update [project]` | Reports drift and, in an interactive terminal, explains impact and asks before applying |
-| `liftoff update --apply` | Applies safe changes, preserves unforced conflicts, and records the resulting manifest |
+| `liftoff update [project]` | Applies safe managed drift immediately, preserves unforced conflicts and orphans, and records the resulting manifest |
+| `liftoff update --check` | Reports drift without preflight or mutation; exits 0 when clean and 2 when drift exists |
+| `liftoff update --force` | Applies safe changes and overwrites only the exact guarded conflicts reported by update |
 | `liftoff dev` | Prints workload-appropriate local development commands; it does not execute them |
 | `liftoff infra` | Prints OpenTofu guidance for API workloads and reports infrastructure as not applicable for Power Apps |
 | `liftoff patterns` | Lists GenAI patterns |
@@ -64,30 +65,46 @@ Consent options are documented in [safety and consent](safety-and-consent.md).
 
 ```bash
 liftoff update
+liftoff update --force
 liftoff update --json
-liftoff update --apply
-liftoff update --apply --force
+liftoff update --check
+liftoff update --check --json
 ```
 
-With interactive input and output, plain `liftoff update` first reports drift
-and its impact. Safe managed changes use a default-No confirmation. Local or
-user-owned conflicts are listed separately and require another default-No
-confirmation before replacement. Liftoff collects both decisions before any
-preflight or write.
+Plain `liftoff update` is imperative and prompt-free. It applies safe new,
+missing, untouched-upgrade, clean-move, and recorded-state changes in
+interactive terminals, redirected streams, and automation. Local or user-owned
+conflicts are skipped and reported. Orphans are reported without deletion.
 
-With redirected input or output, plain update remains a read-only check and
-prints the explicit apply command. `--json` also remains prompt-free and
-read-only unless combined with `--apply`. Explicit `--apply` and
-`--apply --force` bypass prompts for automation.
+Use `--check` whenever no project bytes may change. Human check mode prints each
+drift state and recommends plain update for safe changes or a reviewed
+`--force` invocation for conflicts. `--check --force` is invalid because check
+mode never authorizes writes.
 
-The impact summary identifies affected dependency definitions, but update does
-not install dependencies. Orphans are reported without deletion. Transaction
-snapshots restore a failed update, but Liftoff retains no backup after a
-successful overwrite; commit or copy local work first.
+`--json` selects output format, not safety. `liftoff update --json` applies safe
+changes and emits the versioned apply result. `liftoff update --check --json`
+is the read-only automation gate.
 
-`--force` is valid only with `--apply`. It overwrites reported file conflicts;
-it does not permit workload, API stack, GenAI pattern, framework, selected
-agent, or user-supplied Power Apps starter identity changes.
+Update never installs dependencies. Transaction snapshots restore a failed
+update, but Liftoff retains no backup after a successful overwrite; commit or
+copy local work before using `--force`. Force does not permit workload, API
+stack, GenAI pattern, framework, selected-agent, or user-supplied Power Apps
+starter identity changes, and it cannot bypass project-boundary, symlink,
+structural-collision, or manifest guards.
+
+### Migration from 0.6.x
+
+The `--apply` flag was removed in 0.7.0. These are historical 0.6.x commands,
+not current syntax:
+
+| Historical 0.6.x command | 0.7.0 replacement |
+| --- | --- |
+| `liftoff update` when used as a read-only check | `liftoff update --check` |
+| `liftoff update --apply` | `liftoff update` |
+| `liftoff update --apply --force` | `liftoff update --force` |
+
+Invoking removed syntax fails during argument parsing, before project discovery
+or filesystem access.
 
 ## JSON and exit codes
 
@@ -97,15 +114,18 @@ Machine-readable maintenance contracts bypass decorative presentation:
 liftoff validate --json
 liftoff doctor --json
 liftoff update --json
+liftoff update --check --json
 ```
 
 Each JSON object has a top-level numeric `schemaVersion`.
+Operational warnings, such as a dirty-worktree warning before JSON apply, are
+written to stderr so stdout remains one parseable JSON object.
 
 Exit codes:
 
 - `0`: success or a clean check.
 - `1`: invalid input, unsafe state, or command failure.
-- `2`: a read-only check or declined interactive update found drift.
+- `2`: explicit update check mode found drift.
 
 Raw installer, framework, and dependency child stdout and stderr are forwarded
 unchanged.

package/docs/configuration-and-manifests.md

@@ -67,10 +67,9 @@ Readers support schemas v2, v3, and v4:
 - V3 normalizes flat GenAI or API identity plus framework and agent metadata.
 - V4 represents the discriminated workload model, including Power Apps.
 
-A non-interactive or JSON check, or a declined interactive update, leaves an
-old manifest byte-for-byte unchanged. A successful explicit or interactively
-accepted apply writes v4 only after the file transaction succeeds. Skipped
-conflicts retain their recorded hashes.
+`liftoff update --check`, including `--check --json`, leaves an old manifest
+byte-for-byte unchanged. A successful plain update writes v4 only after the
+file transaction succeeds. Skipped conflicts retain their recorded hashes.
 
 ## Artifact ownership
 

package/docs/existing-repositories.md

@@ -64,15 +64,15 @@ Use:
 
 ```bash
 liftoff validate
+liftoff update --check
 liftoff update
-liftoff update --apply
 ```
 
-In an interactive terminal, plain update reports drift and impact, then asks
-with a default of No before applying safe managed changes. Local or user-owned
-conflicts require a separate default-No overwrite decision. Redirected and
-JSON checks remain read-only and prompt-free; use `--apply` for explicit
-automation consent.
+Use `--check` first when the invocation must be read-only. Plain update applies
+safe managed changes immediately and without prompting in terminals and
+automation, while preserving conflicts and orphans. Review every reported
+conflict and commit or copy local work before choosing `liftoff update --force`.
+For CI drift gates, use `liftoff update --check --json`.
 
 ## Existing non-Liftoff application
 

package/docs/safety-and-consent.md

@@ -8,7 +8,7 @@ project dependencies. No one permission implies another.
 | Flag | Authorizes | Does not authorize |
 | --- | --- | --- |
 | `--yes` | Project defaults and plan confirmation | File replacement, machine installs, or project dependencies |
-| `--force` | Only listed and validated regular-file replacements | Manifest guards, symlinks, structural collisions, tools, dependencies, or non-empty migration targets |
+| `--force` | During init, listed regular-file replacements; during update, exact reported conflicts | Manifest guards, symlinks, structural collisions, tools, dependencies, or non-empty migration targets |
 | `--install-tools` | Allowlisted workstation installation commands | Project decisions, overwrites, or project dependencies |
 | `--install-dependencies` | Locked project-local dependency commands after a successful merge | Machine tools, project decisions, or overwrites |
 
@@ -50,11 +50,10 @@ Individual project files use temporary-file replacement. Initialization keeps
 backups for replaced files and records created files and directories. A handled
 merge failure restores or removes those entries in reverse order.
 
-An accepted interactive update or `liftoff update --apply` preflights all
-affected paths and applies generated file, move, delete, and manifest mutations
-as one rollback-capable transaction. Schema upgrades are committed only after
-the other mutations succeed. A corrected retry converges from the restored
-state.
+Plain `liftoff update` preflights all affected paths and applies generated file,
+move, delete, and manifest mutations as one rollback-capable transaction.
+Schema upgrades are committed only after the other mutations succeed. A
+corrected retry converges from the restored state.
 
 If automatic rollback itself cannot safely restore a path because another
 process changed it, Liftoff reports the incomplete rollback rather than
@@ -65,24 +64,25 @@ does not retain them as backups after success.
 
 ## Update ownership
 
-Plain `liftoff update` always reports drift before any write:
+Update mode is selected explicitly rather than from terminal interactivity:
 
 - Clean generated files remain unchanged.
-- In an interactive terminal, new, missing, untouched-upgrade, clean-move, and
-  recorded-state changes are summarized and offered through a default-No
-  confirmation.
-- With redirected input or output, or with `--json`, update remains a
-  prompt-free read-only check unless `--apply` is explicitly supplied.
+- Plain `liftoff update` immediately applies safe new, missing,
+  untouched-upgrade, clean-move, and recorded-state changes without prompting,
+  including with redirected input or output.
+- `liftoff update --check` is read-only and performs no preflight or mutation.
+- `liftoff update --json` applies safe changes and returns an apply result;
+  `liftoff update --check --json` is the read-only machine drift gate.
 - Developer edits that also differ from the current template are conflicts.
-- Safe-update consent does not authorize conflicts. Interactive conflicts are
-  listed by portable relative path and require a separate default-No overwrite
-  confirmation; automation uses `--apply --force`.
+- Default update skips conflicts and lists them by portable relative path.
+  After reviewing every listed overwrite, `liftoff update --force` extends the
+  transaction only to those guarded conflicts.
 - Orphans are reported and left on disk for manual review.
 - Dependency definitions may be updated, but update never installs
   dependencies.
 
-All interactive decisions are collected before preflight or mutation.
-Declining the safe update changes nothing and leaves drift exit code 2.
+`--force` cannot be combined with `--check` and cannot weaken project-boundary,
+symlink, collision, manifest, or transaction guards.
 
 Power Apps reconciliation reads only the packaged immutable starter. It does
 not fetch the upstream repository. Workload kind and user-edited starter
@@ -98,6 +98,23 @@ does not claim framework-owned files in durable artifact hashes.
 One-time seed content is also omitted from durable hashes so it can follow its
 own lifecycle after generation.
 
+## Telemetry boundary
+
+Liftoff sends only a recognized command name, CLI version, and zero/nonzero
+outcome after a command completes. It creates no persistent installation or
+session identifier and sends no arguments, paths, project data, errors, timing,
+or host details.
+
+Telemetry is enabled by default after a one-time disclosure. Set
+`LIFTOFF_TELEMETRY=0` or `DO_NOT_TRACK=1` to disable it; `CI=true` disables it
+automatically. Delivery is one bounded HTTPS attempt and cannot change command
+output or exit status.
+
+Azure necessarily handles a source network address while routing HTTPS, but
+Liftoff does not include it in the event, derive geolocation from it, or persist
+it in the product telemetry table. See [telemetry and privacy](telemetry.md) for
+the exact fields, Azure boundary, OpenTofu deployment, and 180-day retention.
+
 ## Credentials and external actions
 
 Generated files contain configuration boundaries, not real credentials.

package/docs/spec-workflows-and-agents.md

@@ -88,5 +88,6 @@ invoke `/create-code-app`. The plugin's connector and deployment skills remain
 available for post-creation work.
 
 Changing the valid plugin preference in `liftoff.config.json` is reconciled by
-`liftoff update`; it updates generated guidance and manifest intent without
-creating API or infrastructure artifacts.
+plain `liftoff update`; it immediately updates generated guidance and manifest
+intent without creating API or infrastructure artifacts. Use
+`liftoff update --check` to inspect that drift without writing.

package/docs/telemetry.md

@@ -0,0 +1,168 @@
+# Telemetry and privacy
+
+Liftoff collects a small aggregate event to understand which CLI commands are
+useful and whether they exit with zero or nonzero status. Telemetry is enabled
+by default, disclosed before the first eligible command, and never required for
+the CLI to work. It creates no persistent installation or session identifier.
+
+## Event contract
+
+Each recognized command can send at most one event after it finishes:
+
+```json
+{
+  "schemaVersion": 1,
+  "event": "command_executed",
+  "command": "infra:plan",
+  "cliVersion": "0.6.1",
+  "outcome": "success"
+}
+```
+
+`outcome` is `success` for exit code zero and `failure` for every nonzero exit
+code. It is an exit-status class, not an error diagnosis. Help requests are
+recorded as `help`, and rejected input that never resolves to a recognized
+command is not recorded.
+
+Liftoff does **not** send:
+
+- An installation, user, device, or session identifier.
+- A client timestamp or duration.
+- Arguments, flags, paths, project names, config values, manifests, or generated
+  content.
+- Error text, stack traces, operating-system details, Node.js version, cloud,
+  workload, region, or environment choices.
+- A source IP address or derived location in the event.
+
+Liftoff creates no telemetry queue and stores no event locally. Its only local
+telemetry state is a numeric disclosure version in the platform configuration
+directory.
+
+## Disable telemetry
+
+Set either variable before running Liftoff:
+
+```bash
+export LIFTOFF_TELEMETRY=0
+export DO_NOT_TRACK=1
+```
+
+On PowerShell:
+
+```powershell
+$env:LIFTOFF_TELEMETRY = "0"
+$env:DO_NOT_TRACK = "1"
+```
+
+Telemetry is also disabled when `CI=true`. Disabled runs do not show the notice,
+create telemetry state, or initialize network transport.
+
+## Delivery and failure behavior
+
+The CLI makes one HTTPS request after command completion with a maximum
+one-second delivery budget. It does not retry, buffer, read a response body, or
+report telemetry failures. Offline use, command output, JSON stdout, and the
+original exit status remain unchanged when the service is unavailable.
+
+## Azure processing and retention
+
+The public endpoint is a strict-schema plain Node.js service in Azure Container
+Apps. It counts streamed bytes before parsing, rejects unknown or additional
+fields, and adds server-side `TimeGenerated`. A managed identity then writes only
+these Liftoff-defined columns through an Azure Monitor data collection rule:
+
+```text
+TimeGenerated, EventName, SchemaVersion, Command, CliVersion, Outcome
+```
+
+Azure Monitor adds standard workspace system columns after the data collection
+rule transformation. Those platform columns contain tenant, type, item, and
+billing metadata; they are not additional Liftoff event fields and are not
+populated from the request body, source IP, or derived geolocation.
+
+Azure networking necessarily handles the source network address while routing
+HTTPS. Liftoff does not copy that address into the event, derive geolocation
+from it, forward it to the data collection rule, or configure the product
+workspace to persist Container Apps ingress or console telemetry. The Container
+Apps environment has persistent platform logs disabled, and the gateway has no
+Application Insights connection string or instrumentation key.
+
+Accepted events are stored in `LiftoffCommandEvents_CL` in the operator-selected
+Azure region for 180 days of analytics and total retention, with no additional
+long-term retention. Query access uses Microsoft Entra ID and Azure RBAC.
+Aggregate counts are directional because a public, unauthenticated endpoint can
+receive forged events.
+
+## Operator deployment boundary
+
+Production telemetry resources are created and managed in the fixed resource
+group `rg-liftoff-prod`. OpenTofu owns the group, applies deletion protection,
+and deploys ACR Basic, a commit-pinned ACR build task, a Container Apps
+environment, one warm Container App replica, managed identity, workspace,
+custom table, data collection endpoint, and data collection rule.
+
+The registry contains only the already-public gateway image. Administrator
+credentials and anonymous pull are disabled; the Container App uses its
+resource-scoped `AcrPull` identity. A full public Git commit SHA identifies the
+build tag; the running Container App is pinned to the resolved `sha256` manifest
+digest, never a branch, `latest`, or tag-only reference.
+
+OpenTofu state storage remains in a separate enforced Azure Network Security
+Perimeter. Its explicit operator IPv4 `/32` CIDRs live only in ignored local
+inputs, and Entra authentication plus storage-scoped RBAC remain required. The
+Container App needs no Function host/deployment storage, package blob, or Azure
+Files share.
+
+The gateway uses the smallest Container Apps Consumption allocation: 0.25 vCPU,
+0.5 GiB, one minimum replica, and five maximum replicas. Keeping one replica
+ready prevents scale-to-zero cold starts from consuming the client's one-second
+delivery budget. It adds reduced idle compute cost plus ACR Basic cost.
+
+From the repository root, operators build and validate with:
+
+```bash
+npm ci --prefix services/telemetry-ingest
+npm run check --prefix services/telemetry-ingest
+npm run package --prefix services/telemetry-ingest
+npm run smoke:container --prefix services/telemetry-ingest
+tofu -chdir=infrastructure/opentofu/telemetry fmt -check
+tofu -chdir=infrastructure/opentofu/telemetry init -backend=false
+tofu -chdir=infrastructure/opentofu/telemetry validate
+```
+
+Real environments must use access-controlled remote state and Entra
+authentication. Before apply, review the subscription, region, unique resource
+suffix, full public source revision, immutable image digest,
+`rg-liftoff-prod` deletion protection, ACR administrator and anonymous-access
+disablement, managed-identity roles, one-to-five replica bounds, disabled
+persistent platform logs, six-column schema, 180-day retention, ingestion
+quota, and state perimeter rules. Operator CIDRs live only in ignored local
+inputs. If the operator IP changes, update and apply the bootstrap access rule
+through the Azure control plane before retrying backend access. Use the same
+reviewed production variable file for every plan, apply, and emergency
+disablement so region, image revision, and quota inputs cannot fall back to
+defaults.
+Every infrastructure lifecycle action uses `tofu`; Liftoff does not use Bicep,
+`azd`, Terraform CLI, or ad hoc Azure resource commands for this service.
+
+Standard GitHub-hosted runners run static validation only. They do not plan or
+apply production because their dynamic networks are not admitted to the
+perimeter.
+
+After apply, operators must verify the registry identity boundary, one ready
+replica, sub-second endpoint response, synthetic allowlisted event, six
+Liftoff-defined columns, expected Azure system columns, server time, retention,
+and absence of request, IP, geolocation, Container Apps platform/console, or
+Application Insights records before compiling the endpoint into a Liftoff
+release.
+
+The final production architecture contains no Function App, FC1 plan, product
+storage, OneDeploy action, or production storage-perimeter association.
+
+For emergency disablement, apply the OpenTofu configuration with
+`ingestion_enabled=false`, then publish a patch with client delivery disabled.
+Rollback preserves `rg-liftoff-prod`; do not destroy the protected production
+resource group.
+
+Normal `liftoff` commands never authenticate to Azure, read OpenTofu state, or
+deploy telemetry infrastructure.

package/docs/troubleshooting.md

@@ -67,15 +67,13 @@ hand-edited unsafe path.
 
 ## Update reports conflicts or orphans
 
-In an interactive terminal, `liftoff update` shows an impact summary and asks
-before applying safe managed changes. The default answer is No.
-
-- Local or user-owned conflicts are listed separately and require their own
-  default-No overwrite confirmation.
-- With redirected input or output, review the report and apply safe changes
-  with `liftoff update --apply`.
-- For prompt-free conflict replacement, use `liftoff update --apply --force`
-  only after reviewing every listed path.
+`liftoff update` applies safe managed changes immediately and skips conflicts.
+
+- Use `liftoff update --check` for a read-only human report or
+  `liftoff update --check --json` for an automation drift gate.
+- Local or user-owned conflicts remain untouched by default.
+- Use `liftoff update --force` only after reviewing every listed path and
+  deciding that each overwrite is intended.
 - Orphans are never deleted automatically.
 - Update reports dependency-definition impact but does not install
   dependencies.

package/docs/workloads.md

@@ -126,3 +126,7 @@ created the application.
 workload. It does not convert among GenAI, API, and Power Apps or change an API
 stack, GenAI pattern, or user-supplied starter identity. Initialize a fresh
 project or use a supported migration flow instead.
+
+Plain update applies safe changes immediately for every workload. Use
+`liftoff update --check` for read-only inspection and review all reported
+conflicts before using `liftoff update --force`; orphans remain untouched.

package/package.json

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

package/dist/update-impact.d.ts

@@ -1,23 +0,0 @@
-import type { ReconcileEntry } from './reconcile.js';
-export declare const dependencyDefinitionLogicalNames: readonly ["backend-pyproject", "function-worker-requirements", "node-backend-package", "node-backend-lock", "go-backend-module", "go-backend-checksums", "frontend-package", "frontend-lock", "power-apps-package", "power-apps-lock"];
-export interface UpdateImpact {
-    readonly creates: readonly string[];
-    readonly restores: readonly string[];
-    readonly replacements: readonly string[];
-    readonly moves: readonly string[];
-    readonly recordedStateRefreshes: readonly string[];
-    readonly conflicts: readonly string[];
-    readonly managedPathsRemoved: readonly string[];
-    readonly managedPathsRemovedOnOverwrite: readonly string[];
-    readonly orphansPreserved: readonly string[];
-    readonly dependencyDefinitions: readonly string[];
-    readonly safeActionCount: number;
-    readonly localOrUserOwnedFilesAtRisk: number;
-    readonly manifestWillUpdate: boolean;
-    readonly installsDependencies: false;
-    readonly deletesOrphans: false;
-    readonly retainsBackupAfterSuccess: false;
-    readonly hasSafeActions: boolean;
-    readonly hasActionableChanges: boolean;
-}
-export declare function buildUpdateImpact(entries: readonly ReconcileEntry[]): UpdateImpact;

package/dist/update-impact.js

@@ -1,127 +0,0 @@
-import { manifestDisplayPath } from './file-system.js';
-export const dependencyDefinitionLogicalNames = Object.freeze([
-    'backend-pyproject',
-    'function-worker-requirements',
-    'node-backend-package',
-    'node-backend-lock',
-    'go-backend-module',
-    'go-backend-checksums',
-    'frontend-package',
-    'frontend-lock',
-    'power-apps-package',
-    'power-apps-lock'
-]);
-const dependencyDefinitionLogicalNameSet = new Set(dependencyDefinitionLogicalNames);
-function comparePortable(left, right) {
-    return left < right ? -1 : left > right ? 1 : 0;
-}
-function displayEntry(entry) {
-    const current = manifestDisplayPath(entry.pathParts);
-    return entry.previousPathParts
-        ? `${manifestDisplayPath(entry.previousPathParts)} => ${current}`
-        : current;
-}
-function freezeSorted(values) {
-    return Object.freeze(values.sort(comparePortable));
-}
-function isActionable(entry) {
-    return entry.status !== 'orphan' &&
-        (entry.status !== 'unchanged' || entry.refreshHash === true);
-}
-export function buildUpdateImpact(entries) {
-    const creates = [];
-    const restores = [];
-    const replacements = [];
-    const moves = [];
-    const recordedStateRefreshes = [];
-    const conflicts = [];
-    const managedPathsRemoved = [];
-    const managedPathsRemovedOnOverwrite = [];
-    const orphansPreserved = [];
-    const dependencyDefinitions = [];
-    for (const entry of entries) {
-        switch (entry.status) {
-            case 'new':
-                creates.push(manifestDisplayPath(entry.pathParts));
-                break;
-            case 'missing':
-                restores.push(manifestDisplayPath(entry.pathParts));
-                break;
-            case 'upgrade':
-                replacements.push(manifestDisplayPath(entry.pathParts));
-                break;
-            case 'moved':
-                if (entry.cleanMove) {
-                    moves.push(displayEntry(entry));
-                    if (entry.previousPathParts) {
-                        managedPathsRemoved.push(manifestDisplayPath(entry.previousPathParts));
-                    }
-                }
-                else {
-                    if (entry.sourceModified && entry.previousPathParts) {
-                        conflicts.push(manifestDisplayPath(entry.previousPathParts));
-                    }
-                    if (entry.destinationOccupied && !entry.destinationMatches) {
-                        conflicts.push(manifestDisplayPath(entry.pathParts));
-                    }
-                    if (entry.previousPathParts) {
-                        managedPathsRemovedOnOverwrite.push(manifestDisplayPath(entry.previousPathParts));
-                    }
-                }
-                break;
-            case 'conflict':
-                conflicts.push(manifestDisplayPath(entry.pathParts));
-                break;
-            case 'orphan':
-                orphansPreserved.push(manifestDisplayPath(entry.pathParts));
-                break;
-            case 'unchanged':
-                if (entry.refreshHash) {
-                    recordedStateRefreshes.push(manifestDisplayPath(entry.pathParts));
-                }
-                break;
-        }
-        if (isActionable(entry) &&
-            dependencyDefinitionLogicalNameSet.has(entry.logicalName)) {
-            dependencyDefinitions.push(manifestDisplayPath(entry.pathParts));
-        }
-    }
-    const frozenCreates = freezeSorted(creates);
-    const frozenRestores = freezeSorted(restores);
-    const frozenReplacements = freezeSorted(replacements);
-    const frozenMoves = freezeSorted(moves);
-    const frozenRefreshes = freezeSorted(recordedStateRefreshes);
-    const frozenConflicts = freezeSorted(conflicts);
-    const frozenManagedPaths = freezeSorted(managedPathsRemoved);
-    const frozenManagedOverwritePaths = freezeSorted(managedPathsRemovedOnOverwrite);
-    const frozenOrphans = freezeSorted(orphansPreserved);
-    const frozenDependencyDefinitions = freezeSorted(dependencyDefinitions);
-    const safeActionCount = frozenCreates.length +
-        frozenRestores.length +
-        frozenReplacements.length +
-        frozenMoves.length +
-        frozenRefreshes.length;
-    const hasSafeActions = safeActionCount > 0;
-    const hasActionableChanges = hasSafeActions || frozenConflicts.length > 0;
-    return Object.freeze({
-        creates: frozenCreates,
-        restores: frozenRestores,
-        replacements: frozenReplacements,
-        moves: frozenMoves,
-        recordedStateRefreshes: frozenRefreshes,
-        conflicts: frozenConflicts,
-        managedPathsRemoved: frozenManagedPaths,
-        managedPathsRemovedOnOverwrite: frozenManagedOverwritePaths,
-        orphansPreserved: frozenOrphans,
-        dependencyDefinitions: frozenDependencyDefinitions,
-        safeActionCount,
-        localOrUserOwnedFilesAtRisk: frozenConflicts.length,
-        manifestWillUpdate: hasActionableChanges,
-        installsDependencies: false,
-        deletesOrphans: false,
-        retainsBackupAfterSuccess: false,
-        hasSafeActions,
-        hasActionableChanges
-    });
-}
-//# sourceMappingURL=update-impact.js.map

package/dist/update-impact.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"update-impact.js","sourceRoot":"","sources":["../src/update-impact.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,mBAAmB,EAAE,MAAM,kBAAkB,CAAC;AAGvD,MAAM,CAAC,MAAM,gCAAgC,GAAG,MAAM,CAAC,MAAM,CAAC;IAC5D,mBAAmB;IACnB,8BAA8B;IAC9B,sBAAsB;IACtB,mBAAmB;IACnB,mBAAmB;IACnB,sBAAsB;IACtB,kBAAkB;IAClB,eAAe;IACf,oBAAoB;IACpB,iBAAiB;CACT,CAAC,CAAC;AAEZ,MAAM,kCAAkC,GAAG,IAAI,GAAG,CAChD,gCAAgC,CACjC,CAAC;AAuBF,SAAS,eAAe,CAAC,IAAY,EAAE,KAAa;IAClD,OAAO,IAAI,GAAG,KAAK,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,IAAI,GAAG,KAAK,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;AAClD,CAAC;AAED,SAAS,YAAY,CAAC,KAAqB;IACzC,MAAM,OAAO,GAAG,mBAAmB,CAAC,KAAK,CAAC,SAAS,CAAC,CAAC;IACrD,OAAO,KAAK,CAAC,iBAAiB;QAC5B,CAAC,CAAC,GAAG,mBAAmB,CAAC,KAAK,CAAC,iBAAiB,CAAC,OAAO,OAAO,EAAE;QACjE,CAAC,CAAC,OAAO,CAAC;AACd,CAAC;AAED,SAAS,YAAY,CAAC,MAAgB;IACpC,OAAO,MAAM,CAAC,MAAM,CAAC,MAAM,CAAC,IAAI,CAAC,eAAe,CAAC,CAAC,CAAC;AACrD,CAAC;AAED,SAAS,YAAY,CAAC,KAAqB;IACzC,OAAO,KAAK,CAAC,MAAM,KAAK,QAAQ;QAC9B,CAAC,KAAK,CAAC,MAAM,KAAK,WAAW,IAAI,KAAK,CAAC,WAAW,KAAK,IAAI,CAAC,CAAC;AACjE,CAAC;AAED,MAAM,UAAU,iBAAiB,CAAC,OAAkC;IAClE,MAAM,OAAO,GAAa,EAAE,CAAC;IAC7B,MAAM,QAAQ,GAAa,EAAE,CAAC;IAC9B,MAAM,YAAY,GAAa,EAAE,CAAC;IAClC,MAAM,KAAK,GAAa,EAAE,CAAC;IAC3B,MAAM,sBAAsB,GAAa,EAAE,CAAC;IAC5C,MAAM,SAAS,GAAa,EAAE,CAAC;IAC/B,MAAM,mBAAmB,GAAa,EAAE,CAAC;IACzC,MAAM,8BAA8B,GAAa,EAAE,CAAC;IACpD,MAAM,gBAAgB,GAAa,EAAE,CAAC;IACtC,MAAM,qBAAqB,GAAa,EAAE,CAAC;IAE3C,KAAK,MAAM,KAAK,IAAI,OAAO,EAAE,CAAC;QAC5B,QAAQ,KAAK,CAAC,MAAM,EAAE,CAAC;YACrB,KAAK,KAAK;gBACR,OAAO,CAAC,IAAI,CAAC,mBAAmB,CAAC,KAAK,CAAC,SAAS,CAAC,CAAC,CAAC;gBACnD,MAAM;YACR,KAAK,SAAS;gBACZ,QAAQ,CAAC,IAAI,CAAC,mBAAmB,CAAC,KAAK,CAAC,SAAS,CAAC,CAAC,CAAC;gBACpD,MAAM;YACR,KAAK,SAAS;gBACZ,YAAY,CAAC,IAAI,CAAC,mBAAmB,CAAC,KAAK,CAAC,SAAS,CAAC,CAAC,CAAC;gBACxD,MAAM;YACR,KAAK,OAAO;gBACV,IAAI,KAAK,CAAC,SAAS,EAAE,CAAC;oBACpB,KAAK,CAAC,IAAI,CAAC,YAAY,CAAC,KAAK,CAAC,CAAC,CAAC;oBAChC,IAAI,KAAK,CAAC,iBAAiB,EAAE,CAAC;wBAC5B,mBAAmB,CAAC,IAAI,CAAC,mBAAmB,CAAC,KAAK,CAAC,iBAAiB,CAAC,CAAC,CAAC;oBACzE,CAAC;gBACH,CAAC;qBAAM,CAAC;oBACN,IAAI,KAAK,CAAC,cAAc,IAAI,KAAK,CAAC,iBAAiB,EAAE,CAAC;wBACpD,SAAS,CAAC,IAAI,CAAC,mBAAmB,CAAC,KAAK,CAAC,iBAAiB,CAAC,CAAC,CAAC;oBAC/D,CAAC;oBACD,IAAI,KAAK,CAAC,mBAAmB,IAAI,CAAC,KAAK,CAAC,kBAAkB,EAAE,CAAC;wBAC3D,SAAS,CAAC,IAAI,CAAC,mBAAmB,CAAC,KAAK,CAAC,SAAS,CAAC,CAAC,CAAC;oBACvD,CAAC;oBACD,IAAI,KAAK,CAAC,iBAAiB,EAAE,CAAC;wBAC5B,8BAA8B,CAAC,IAAI,CACjC,mBAAmB,CAAC,KAAK,CAAC,iBAAiB,CAAC,CAC7C,CAAC;oBACJ,CAAC;gBACH,CAAC;gBACD,MAAM;YACR,KAAK,UAAU;gBACb,SAAS,CAAC,IAAI,CAAC,mBAAmB,CAAC,KAAK,CAAC,SAAS,CAAC,CAAC,CAAC;gBACrD,MAAM;YACR,KAAK,QAAQ;gBACX,gBAAgB,CAAC,IAAI,CAAC,mBAAmB,CAAC,KAAK,CAAC,SAAS,CAAC,CAAC,CAAC;gBAC5D,MAAM;YACR,KAAK,WAAW;gBACd,IAAI,KAAK,CAAC,WAAW,EAAE,CAAC;oBACtB,sBAAsB,CAAC,IAAI,CAAC,mBAAmB,CAAC,KAAK,CAAC,SAAS,CAAC,CAAC,CAAC;gBACpE,CAAC;gBACD,MAAM;QACV,CAAC;QAED,IACE,YAAY,CAAC,KAAK,CAAC;YACnB,kCAAkC,CAAC,GAAG,CAAC,KAAK,CAAC,WAAW,CAAC,EACzD,CAAC;YACD,qBAAqB,CAAC,IAAI,CAAC,mBAAmB,CAAC,KAAK,CAAC,SAAS,CAAC,CAAC,CAAC;QACnE,CAAC;IACH,CAAC;IAED,MAAM,aAAa,GAAG,YAAY,CAAC,OAAO,CAAC,CAAC;IAC5C,MAAM,cAAc,GAAG,YAAY,CAAC,QAAQ,CAAC,CAAC;IAC9C,MAAM,kBAAkB,GAAG,YAAY,CAAC,YAAY,CAAC,CAAC;IACtD,MAAM,WAAW,GAAG,YAAY,CAAC,KAAK,CAAC,CAAC;IACxC,MAAM,eAAe,GAAG,YAAY,CAAC,sBAAsB,CAAC,CAAC;IAC7D,MAAM,eAAe,GAAG,YAAY,CAAC,SAAS,CAAC,CAAC;IAChD,MAAM,kBAAkB,GAAG,YAAY,CAAC,mBAAmB,CAAC,CAAC;IAC7D,MAAM,2BAA2B,GAAG,YAAY,CAAC,8BAA8B,CAAC,CAAC;IACjF,MAAM,aAAa,GAAG,YAAY,CAAC,gBAAgB,CAAC,CAAC;IACrD,MAAM,2BAA2B,GAAG,YAAY,CAAC,qBAAqB,CAAC,CAAC;IACxE,MAAM,eAAe,GACnB,aAAa,CAAC,MAAM;QACpB,cAAc,CAAC,MAAM;QACrB,kBAAkB,CAAC,MAAM;QACzB,WAAW,CAAC,MAAM;QAClB,eAAe,CAAC,MAAM,CAAC;IACzB,MAAM,cAAc,GAAG,eAAe,GAAG,CAAC,CAAC;IAC3C,MAAM,oBAAoB,GAAG,cAAc,IAAI,eAAe,CAAC,MAAM,GAAG,CAAC,CAAC;IAE1E,OAAO,MAAM,CAAC,MAAM,CAAC;QACnB,OAAO,EAAE,aAAa;QACtB,QAAQ,EAAE,cAAc;QACxB,YAAY,EAAE,kBAAkB;QAChC,KAAK,EAAE,WAAW;QAClB,sBAAsB,EAAE,eAAe;QACvC,SAAS,EAAE,eAAe;QAC1B,mBAAmB,EAAE,kBAAkB;QACvC,8BAA8B,EAAE,2BAA2B;QAC3D,gBAAgB,EAAE,aAAa;QAC/B,qBAAqB,EAAE,2BAA2B;QAClD,eAAe;QACf,2BAA2B,EAAE,eAAe,CAAC,MAAM;QACnD,kBAAkB,EAAE,oBAAoB;QACxC,oBAAoB,EAAE,KAAK;QAC3B,cAAc,EAAE,KAAK;QACrB,yBAAyB,EAAE,KAAK;QAChC,cAAc;QACd,oBAAoB;KACrB,CAAC,CAAC;AACL,CAAC"}