loadout-ai 0.7.0 → 0.9.0

package/docs/REPOSITORY_STABILIZATION.md

@@ -1,190 +0,0 @@
-# Repository stabilization record
-
-Status date: 2026-07-19. This document records evidence gathered while consolidating
-the repository. `MASTER_PLAN.md` is the only active plan; this is an audit record, not
-a second backlog.
-
-## Starting synchronization inventory
-
-The investigation fetched all visible branches and tags before making cleanup
-decisions. The starting GitHub default was `main` at
-`189cb7a0e918860fc37bb92639126b93b387abec` (`v0.3.2`).
-
-| Local branch/worktree                             | Starting head | Tracking state                                              | Starting disposition                        |
-| ------------------------------------------------- | ------------- | ----------------------------------------------------------- | ------------------------------------------- |
-| `codex/readme-truth`, `/tmp/loadout-readme-truth` | `ee8d548`     | 29 ahead of `origin/main`, clean                            | Preserve and integrate                      |
-| `dev/nitish`, user checkout                       | `69b8fe7`     | one ahead of `origin/dev/nitish`; untracked `.superpowers/` | Preserve user state and safety requirements |
-| local `main`                                      | `d2a11d8`     | 101 behind `origin/main`                                    | Fast-forward after integration              |
-| local `develop`, `dev/amartya`, `dev/viraj`       | `d2a11d8`     | stale or merged                                             | Remove after final-main verification        |
-
-No local commit was treated as remote merely because it existed in a worktree.
-
-## Failure ledger
-
-| Failure                                                                                           | Reproduction/evidence                                                                                                                                                                                                                                                                                                                                            | Root cause/classification                                                                   | Resolution/status                                                                                                                                                                    |
-| ------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Risky setup preview omitted `--approve-risk`                                                      | Prepared risky catalog plan printed an incomplete rerun command                                                                                                                                                                                                                                                                                                  | Product guidance defect                                                                     | Fixed in `1f62a1b`; regression test derives guidance from the prepared plan                                                                                                          |
-| Unknown command ran default onboarding                                                            | Unknown positional top-level command reached the root action                                                                                                                                                                                                                                                                                                     | CLI routing defect                                                                          | Fixed in `1f62a1b`; unknown commands fail non-zero while bare invocation remains valid                                                                                               |
-| Explicit rollback could erase later user changes                                                  | Persisted snapshots recorded only pre-mutation bytes                                                                                                                                                                                                                                                                                                             | Product data-safety defect                                                                  | Fixed in `1f62a1b`; committed post-state is checked before user-requested rollback                                                                                                   |
-| Dashboard and special-file rollback bypasses                                                      | Default dashboard restore omitted the guard; nested FIFOs/sockets/devices were skipped                                                                                                                                                                                                                                                                           | Product data-safety defect                                                                  | Fixed in `6fd1a2c`; dashboard and unsupported-entry regressions pass                                                                                                                 |
-| `dev/nitish` adoption preview covered only `SKILL.md` while ownership covered the whole directory | Deletion review traced preview through apply and `recordInstall`; auxiliary drift, cloned-plan forgery, and review over-attribution were reproducible                                                                                                                                                                                                            | Product ownership/integrity defect; valuable safety intent existed only on the stale branch | Fixed in the current architecture by `186daa0`, `09e0e0c`, `3f2cafe`, and `10d6109`; focused and full verification pass                                                              |
-| Fresh-clone live Stable rollback refused on `state.json`                                          | `npm run check:live -- --stable-install` installed four pinned packages, then refused the Stable snapshot because later state differed                                                                                                                                                                                                                           | Product transaction-boundary defect plus invalid non-LIFO evidence-flow ordering            | `5f8e38e` records profile state inside the catalog transaction and rolls Stable back before unrelated fixture transactions; exact state and managed-root drift checks remain enabled |
-| Windows snapshot-root test used a POSIX fixture                                                   | CI run `29502017220` executed at `41b53e0`; Windows reported “absolute normalized path” before the test's expected “filesystem root” message                                                                                                                                                                                                                     | Test portability defect, not a runtime rollback failure                                     | `c5fe192` changed the fixture to the host filesystem root; rerun `29502324100` passed                                                                                                |
-| Recent GitHub CI and discovery runs did not start                                                 | Earlier blocked runs plus CI runs [`29691581581`](https://github.com/VirajMishra1/loadout/actions/runs/29691581581) and [`29692535521`](https://github.com/VirajMishra1/loadout/actions/runs/29692535521) have no executed steps; both CI annotations say the job was not started because recent account payments failed or the spending limit must be increased | GitHub account billing/spending-limit condition                                             | External failure; no product-test result was produced                                                                                                                                |
-| `loadout-ai@0.3.2` unavailable                                                                    | npm registry version list ends at `0.3.1`; bounded live evidence records the same result                                                                                                                                                                                                                                                                         | Package publication                                                                         | Not verified; publish and test the exact tarball externally                                                                                                                          |
-| `main` protection unavailable                                                                     | GitHub branch-protection endpoint returns 404                                                                                                                                                                                                                                                                                                                    | Repository setting/authorization                                                            | Absent or not observable; requires owner decision                                                                                                                                    |
-
-Internal failed-transaction recovery deliberately restores the pre-mutation snapshot
-without the later-drift guard. The guard applies to user-requested CLI, dashboard, and
-runtime-tool rollback. Legacy snapshots fail closed for those explicit paths.
-
-## Recent Viraj commits and GitHub Actions
-
-The recent Viraj changes were inspected as code and exercised locally; commit messages
-were not used as proof.
-
-| Commit    | Implemented area                                                                                     | Main/Actions evidence                                                                                                                                                                       |
-| --------- | ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `817c38f` | Public-beta CLI, package, credential, catalog, and release foundation                                | In `main`; CI run `29486160804` passed                                                                                                                                                      |
-| `9798f1c` | Continuous discovery, generated catalog evidence, and snapshot hardening                             | In `main`; CI run `29491118338` passed                                                                                                                                                      |
-| `6994d4e` | Candidate intelligence, signed catalog release, locking, and transaction hardening                   | In `main`; CI run `29497632211` passed                                                                                                                                                      |
-| `41b53e0` | Stable profile, daily autopilot, and release workflow                                                | In `main`; CI run `29502017220` failed on the Windows-only test fixture described above                                                                                                     |
-| `c5fe192` | Host-portable snapshot root guard test                                                               | In `main`; CI rerun `29502324100` passed                                                                                                                                                    |
-| `4e93f5d` | Cross-platform release-matrix documentation                                                          | In `main`; CI run `29502646004` passed                                                                                                                                                      |
-| `05e52a4` | Expanded Stable profile and reviewed Graphify recipe                                                 | In `main`; CI run `29505093720` passed                                                                                                                                                      |
-| `f7f53fa` | Release-work documentation clarification                                                             | In `main`; CI run `29505532691` was cancelled after a newer push; no product failure was produced                                                                                           |
-| `e35b8ff` | Upgrade, health-score, benchmark-campaign, and discovery foundation                                  | In `main`; CI run `29508916710` passed                                                                                                                                                      |
-| `3cb5505` | Trust, intelligence, benchmark, import, and skill-security systems                                   | In `main`; CI run `29520771134` passed                                                                                                                                                      |
-| `8e80ab4` | npm beta metadata and package-smoke adjustment                                                       | In `main`; CI run `29522705571` passed                                                                                                                                                      |
-| `1fe9890` | Codex Desktop installation detection                                                                 | In `main`; CI run `29524710934` and discovery run `29557150915` passed                                                                                                                      |
-| `e4e469e` | Credential-aware setup, Maximum quarantine, and managed update scoping                               | In `main`; CI run `29583273859` passed                                                                                                                                                      |
-| `ebb8133` | Unit-level Power quarantine and onboarding rewrite                                                   | In `main`; CI run `29585379546` passed                                                                                                                                                      |
-| `88466ef` | npm `0.2.0` verification documentation                                                               | In `main`; CI run `29586111523` passed                                                                                                                                                      |
-| `cf406e8` | Safe Stable/profile setup reruns                                                                     | In `main`; CI run `29588415904` passed                                                                                                                                                      |
-| `a016c0f` | Exact managed-profile reconciliation                                                                 | In `main`; CI run `29590309101` passed                                                                                                                                                      |
-| `33225ef` | Large rollback-snapshot validation                                                                   | In `main`; CI run `29591059217` passed                                                                                                                                                      |
-| `15f36e3` | Pinned Graphify generated fallback                                                                   | In `main`; CI run `29591567247` passed                                                                                                                                                      |
-| `16b8a7e` | Beginner and advanced CLI routing                                                                    | In `main`; covered by current CLI tests                                                                                                                                                     |
-| `31cb755` | Saved-profile updates and complete uninstall                                                         | In `main`; its CI job never started because of billing                                                                                                                                      |
-| `56ab3af` | Separation of model API keys from service credentials                                                | In `main`; its CI job never started because of billing                                                                                                                                      |
-| `189cb7a` | Recursively empty skill-directory recovery                                                           | In `main`; its CI job never started because of billing                                                                                                                                      |
-| `e74ba16` | Consolidated README truth, lifecycle hardening, safety fixes, adoption integrity, and cleanup record | Integrated into remote `main`; CI run [`29692535521`](https://github.com/VirajMishra1/loadout/actions/runs/29692535521) failed before steps because of the billing/spending-limit condition |
-| `5f8e38e` | Transactional installed-profile state and valid live Stable rollback ordering                        | Integrated into remote `main`; verified again from a fresh clone                                                                                                                            |
-
-Earlier green runs prove their own commits only. They do not prove later commits that
-GitHub never executed. Current local verification and future post-integration Actions
-must remain separately reported.
-
-## Branch cleanup observations during consolidation
-
-At the 2026-07-19 consolidation checkpoint, there was one merged PR:
-[#1](https://github.com/VirajMishra1/loadout/pull/1), `dev/nitish` into `develop`,
-merged as `69594f2`; its recorded Linux, macOS, and Windows Node 20/22 jobs passed.
-The authenticated query at that checkpoint returned no open PRs.
-
-| Branch                                    | Unique work relative to starting `origin/main`                                                                                                    | Final result                                                                     |
-| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
-| `codex/readme-truth`                      | README evidence, adapter/product-flow coverage, release hardening, safety fixes, and consolidation                                                | Integrated into `main`; local and remote branch deleted                          |
-| `dev/nitish`                              | Its one real adoption-integrity gap is fully reimplemented and tested by `186daa0`, `09e0e0c`, `3f2cafe`, and `10d6109`; no valuable work remains | Local and remote branch deleted; unrelated `.superpowers/` preserved and ignored |
-| `codex/cli-ux-polish`                     | None; tip `31cb755` is in main                                                                                                                    | Local and remote branch deleted                                                  |
-| `codex/fix-large-snapshot-validation`     | None; tip `33225ef` is in main                                                                                                                    | Local and remote branch deleted                                                  |
-| `codex/fix-profile-reconciliation`        | None; tip `a016c0f` is in main                                                                                                                    | Local and remote branch deleted                                                  |
-| `codex/fix-stable-rerun`                  | None; tip `cf406e8` is in main                                                                                                                    | Local and remote branch deleted                                                  |
-| `codex/harden-graphify-generated-install` | None; tip `15f36e3` is in main                                                                                                                    | Local and remote branch deleted                                                  |
-| `dev/amartya`                             | Integrated through `6161c48` and later follow-ups                                                                                                 | Local and remote branch deleted                                                  |
-| `dev/viraj`                               | Old main ancestor                                                                                                                                 | Local and remote branch deleted                                                  |
-| `develop`                                 | Old integration ancestor                                                                                                                          | Local and remote branch deleted                                                  |
-
-Cleanup completed only after the integrated work reached remote `main` and the open-PR
-list was empty. At that checkpoint, Git exposed only local `main`, `origin/main`, and
-the retained release tags. The `/tmp/loadout-readme-truth` worktree had been removed.
-The user's untracked `.superpowers/` directory remained present and ignored by
-`.gitignore`; no user artifact was deleted.
-
-## Planning and dead-file consolidation
-
-`MASTER_PLAN.md` is authoritative because Viraj created it, maintained it across the
-project history, linked it from README, and explicitly labeled its top section as the
-active list. The removed files were unreferenced or self-described historical plans
-whose implementation/status had moved elsewhere.
-
-| Removed file                                         | Evidence for deletion                                   | Preserved outcome                                            |
-| ---------------------------------------------------- | ------------------------------------------------------- | ------------------------------------------------------------ |
-| `NITISH_MASTER_PLAN.md`                              | Unreferenced; stale `dev/nitish`/`develop` policy       | Durable safety work is in the master plan and implementation |
-| `SIMPLE_PLAN.md`                                     | Duplicate summary that named `MASTER_PLAN.md` canonical | README retains the user-facing summary                       |
-| `docs/plans/2026-07-18-release-0.3.md`               | Completed code plan with stale merge/publish boxes      | External publication remains explicit in the master plan     |
-| `docs/superpowers/plans/2026-07-18-cli-ux-polish.md` | Implemented on main; stale commit/verify boxes          | Founder testing remains explicit in the master plan          |
-| README truth implementation plan and design          | Implemented, reviewed, and encoded by tests/evidence    | Current status is in the master plan and release evidence    |
-
-Operational contracts such as `docs/TESTING.md`, `docs/FEATURE_TEST_MATRIX.md`,
-`docs/RELEASE_REVIEW.md`, policy documents, and machine-readable evidence remain.
-
-## README research and redesign evidence
-
-The redesign research is recorded at immutable commits rather than mutable default
-branches:
-
-| Repository | Immutable README reference                                                                                      |
-| ---------- | --------------------------------------------------------------------------------------------------------------- |
-| Ponytail   | [`16f2980`](https://github.com/DietrichGebert/ponytail/blob/16f29800fd2681bdf24f3eb4ccffe38be3baec6b/README.md) |
-| uv         | [`1535a67`](https://github.com/astral-sh/uv/blob/1535a6767e5ebd77eac2ace0f6cf1a3edc5f681c/README.md)            |
-| bat        | [`7895139`](https://github.com/sharkdp/bat/blob/78951393e29bfd2f2a45f4326b9d2bb5e737dd2a/README.md)             |
-| fzf        | [`b163463`](https://github.com/junegunn/fzf/blob/b163463079e6254b8582b05acefcf187ec160d9b/README.md)            |
-| ripgrep    | [`227381d`](https://github.com/BurntSushi/ripgrep/blob/227381db0ee83dfa4341f1e27ff9617c0f5ad992/README.md)      |
-| mise       | [`126e775`](https://github.com/jdx/mise/blob/126e7755cc22e36c3d206b650de613951146b5e3/README.md)                |
-| Gum        | [`716d8b5`](https://github.com/charmbracelet/gum/blob/716d8b5d0221558f944b5a078dbbcca8572534fb/README.md)       |
-| Starship   | [`8f28dfc`](https://github.com/starship/starship/blob/8f28dfcb1ca3242fba00a3cf98c10ee24605c3ed/README.md)       |
-
-`docs/README_RESEARCH.md` records the adopted principles and rejected patterns. The
-front page should present the bounded product journey and link to evidence, not repeat
-an exhaustive manual. In particular, the complete adapter table belongs in
-`docs/FEATURE_TEST_MATRIX.md`, not on the front page. A compact front-page support
-summary must continue to distinguish configured target paths and disposable
-filesystem tests from unverified native-agent recognition and execution.
-
-## Dated external observations before the README redesign
-
-These observations were captured on 2026-07-19 before README-redesign work began.
-They are a historical checkpoint, not claims about repository state when this document
-is later read.
-
-- GitHub repository: the private fork was `reddynitish/loadout`; its default branch
-  was `main` at `18757d4`. The earlier `VirajMishra1/loadout` observations in this
-  record describe the upstream repository at the time of consolidation.
-- Branches and PRs: `codex/readme-redesign` was the local work branch; the
-  authenticated check found no open pull requests in the fork at that time.
-- npm: the registry exposed versions through `0.3.1`; `0.3.2` was not verified as
-  published.
-- GitHub Actions: fork CI run
-  [`29704170975`](https://github.com/reddynitish/loadout/actions/runs/29704170975) passed
-  for `main` at `18757d4`. The upstream billing-blocked runs above were historical
-  evidence only and did not describe the fork's CI capability.
-- Branch protection: the authenticated protection endpoint returned HTTP 403 stating
-  that the private repository requires GitHub Pro or public visibility for the
-  feature. Protection was unavailable under the observed repository plan; this was
-  not a product-runtime result.
-- Native application consumption of every configured adapter path was unverified;
-  disposable filesystem lifecycle evidence did not establish native-host support.
-
-## Local verification after consolidation
-
-On 2026-07-19, `npm run verify:full` completed successfully on macOS with Node 25.4.0:
-
-- formatting, lint, type checking, build, catalog/discovery evidence, README claims,
-  and release claims passed;
-- 112 Vitest files passed with 589 tests passing and one intentionally skipped;
-- CLI and README product flows passed;
-- packaged CLI smoke passed;
-- the 1,000-skill scan benchmark passed at 240.5 ms p95 across seven CLI runs; and
-- both desktop Chromium and mobile Chromium dashboard tests passed.
-
-The fresh-clone live Stable gate also installed four pinned packages and completed
-state and filesystem rollback assertions at `5f8e38e`. An initially considered
-state-ignore fix was rejected during independent review because restoring an old
-registry while leaving later package files could orphan installations. The final fix
-keeps exact `state.json` and managed-root drift protection, includes installed-profile
-state in transaction post-evidence, and uses strict LIFO ordering in the live flow.
-
-An npm dry-run contained 137 entries, included this record and `MASTER_PLAN.md`, and
-excluded every deleted plan. These local results do not substitute for GitHub Actions,
-the unpublished `0.3.2` npm tarball, native-host acceptance, or branch protection.

package/docs/SAFE_UPDATE_DEMO.md

@@ -1,25 +0,0 @@
-# Safe update demonstration
-
-Loadout treats an update as a reviewable filesystem transaction; it never runs
-repository scripts, hooks, package-manager lifecycle commands, or MCP servers.
-
-The regression demo uses only the inert local repositories in
-`tests/fixtures/update-safety`:
-
-1. `benign-v1` to `benign-v2` is a documentation-only skill update. Loadout
-   copies it, validates the copied `SKILL.md`, and records the new commit.
-2. `risky-v2` adds a hook-shaped shell file and an external domain. Static
-   inspection marks it as requiring explicit approval. Without that approval,
-   Loadout writes review metadata to its quarantine directory and leaves the
-   installed files and state untouched.
-3. A simulated post-copy static verification failure restores the exact
-   transaction snapshot, including the previous skill bytes and install state.
-
-Run the evidence locally:
-
-```bash
-npm test -- --reporter=verbose tests/update-safety-demo.test.ts
-```
-
-The hook fixture contains a marker command solely to prove that inspection does
-not execute it. The test asserts that the marker is absent.

package/docs/SCHEMA_DECISIONS.md

@@ -1,25 +0,0 @@
-# Runtime schema decision
-
-Loadout treats catalog JSON, shared manifests and lockfiles, persisted install
-state, and inter-module install plans as untrusted data. `src/shared/schemas.ts`
-is the single runtime-validation boundary for those structures. It uses Zod so
-the parsed output has inferred TypeScript types as well as a path-aware runtime
-error for the CLI and tests.
-
-The schemas intentionally model identifiers, source provenance, agent IDs,
-component kinds, hashes, and safety levels. They do not define fields for MCP
-environment values, API keys, tokens, or other secret values. MCP environment
-values remain in their agent-owned configuration and are only summarized using
-counts/names elsewhere in the product.
-
-Compatibility and failure handling:
-
-- New manifest, lockfile, and state writers always emit schema version 1.
-- Lockfiles produced before `generatedAt` existed remain readable as the
-  explicit legacy value `unknown`; newly written lockfiles always include the
-  timestamp.
-- Unknown catalog and policy fields are retained where required for existing
-  portable-export secret scanning. They are never interpreted as executable
-  configuration by the schema layer.
-- Invalid data fails before install, audit, or update processing with the exact
-  field path (for example, `installs.0.targetAgents.0`).

package/docs/SUBMISSION_COPY.md

@@ -1,90 +0,0 @@
-# Devpost submission copy
-
-Edit this in your own voice before submitting. Replace the video placeholder and
-check every link while signed out.
-
-## Project name
-
-Loadout
-
-## Tagline
-
-One CLI to discover, install, update, and undo the best extensions for your AI coding
-agents.
-
-## Category
-
-Developer Tools
-
-## Short category and project answer
-
-We are building for the Developer Tools category. Loadout is a local CLI that finds,
-screens, installs, updates, and rolls back skills, MCP servers, and runtime tools
-across Codex, Claude Code, Cursor, and other coding agents, with project-aware
-recommendations and a daily read-only discovery feed.
-
-## Project description
-
-Improving an AI coding agent still means hunting through GitHub, Reddit, X, and
-bookmarks, then copying files into several different agent directories. A week later,
-you may not remember where a skill came from, whether a better option has appeared,
-or how to remove it safely.
-
-Loadout turns that mess into one local CLI. Stable installs a bounded 30-skill daily
-setup from four pinned public sources. Power prepares a broader toolkit. Maximum
-keeps thousands of screened skill copies in a disabled local library, then recommends
-a focused active set for the current project. Custom mode installs one exact package
-without replacing the rest of your setup.
-
-Every change is previewed first. Loadout records source and version ownership, checks
-for collisions and risky files, protects user edits, and creates a rollback snapshot
-before it changes managed files. MCP servers and executable tools remain separate,
-explicit choices. The normal skill workflow does not require an OpenAI or Anthropic
-API key.
-
-The bundled catalog credits 53 pinned public repositories. A generated discovery
-snapshot currently watches 240 repositories, including 216 candidates that have not
-been promoted into the catalog. Loadout treats popularity as a reason to inspect a
-project, not proof that it is safe or useful.
-
-We built Loadout with Codex and GPT-5.6 during OpenAI Build Week. We used Codex for
-architecture, implementation, repository research, threat modelling, cross-platform
-work, and the founder testing loop. Real tests on Codex and Claude Code exposed bugs
-in rollback history, update performance, project activation, MCP configuration,
-runtime-tool inventory, and adopted-skill removal. Each reproducible failure became a
-regression test. The current release passes 632 tests, packaged CLI journeys, public
-CI, and a 1,000-skill performance gate.
-
-Loadout is published on npm and the code is public. The dashboard was deliberately
-removed because it duplicated the CLI and made the product harder to understand. The
-result is the product we wanted to use ourselves: one command-line control layer for
-the extensions around every AI coding agent.
-
-## Links
-
-- GitHub: https://github.com/VirajMishra1/loadout
-- npm: https://www.npmjs.com/package/loadout-ai
-- Release: https://github.com/VirajMishra1/loadout/releases/tag/v0.5.9
-- Demo: https://www.youtube.com/watch?v=opNqJKX7xMw
-
-## Judge testing path
-
-```bash
-npm install --global loadout-ai@0.5.9
-loadout --version
-loadout guide
-loadout setup --mode stable
-```
-
-The Stable command previews first. It changes nothing until the reviewer approves
-the plan. The README and user test guide cover rollback, Maximum, project
-recommendations, MCP recipes, Graphify, discovery, and complete uninstall.
-
-## Final fields to verify
-
-- Category is Developer Tools.
-- All three teammates appear on the Devpost submission.
-- The public YouTube URL works while signed out.
-- The Codex `/feedback` session ID is present.
-- The GitHub, npm, and video links are correct.
-- The submission is submitted, not saved as a draft.

package/docs/TEAM_POLICY.md

@@ -1,18 +0,0 @@
-# Team policy and audit schema
-
-A shared Loadout is a versioned declarative manifest plus a signed catalog reference;
-it never contains credentials or private repository names by default. Team policy has
-four independent controls:
-
-- allowlist: package IDs/repository identities eligible for planning;
-- denylist: identities, domains, component types, or risk findings that block;
-- required approvals: roles required for risky changes; and
-- audit events: timestamp, actor label, manifest/catalog hashes, decision, and reason.
-
-The serverless/local MVP stores policy in a project-controlled JSON file and validates
-it before a plan. There is no hidden admin override. A later hosted product can add
-identity and retention without changing the portable policy semantics.
-
-The current manifest implementation enforces package/repository allowlists and
-denylists before synchronization, alongside the existing blocked-domain and
-blocked-command rules. Violations are included in the dry-run plan and stop apply.