@rehearsal-db/core 0.1.0-rc.1 → 0.1.0-rc.2

package/CHANGELOG.md

@@ -5,6 +5,27 @@ a Changelog, and versions will follow Semantic Versioning after the package exis
 
 ## Unreleased
 
+## [0.1.0-rc.2] - 2026-10-09
+
+### Changed
+
+- Container-engine startup is now explicit by default. Rehearsal starts Colima only
+  when a project deliberately enables `containerRuntime.autoStartColima`, reports that
+  action, and never silently stops the shared engine.
+- Package-managed Supabase containers use Docker's non-resuming restart policy after
+  each start, preventing stopped Rehearsal stacks from waking merely because Docker or
+  Colima restarts. Exact Supabase project labels keep the change inside the selected
+  disposable target.
+- Runtime diagnostics and a new lifecycle guide explain which commands need Docker,
+  what remains running, and how to finish a low-memory local session without pruning or
+  deleting persistent data.
+
+### Fixed
+
+- A stopped Colima VM no longer restarts from a default Rehearsal configuration.
+- Independent Test Lab acceptance now reaps exact workspace-owned interactive children
+  after success, failure, interruption, and timeout.
+
 ## [0.1.0-rc.1] - 2026-10-08
 
 ### Changed
@@ -554,7 +575,8 @@ a Changelog, and versions will follow Semantic Versioning after the package exis
   publication uses short-lived trusted OIDC, and every release tag must already exist on
   protected `main`.
 
-[Unreleased]: https://github.com/Ddupasquier/rehearsal-db/compare/v0.1.0-rc.1...HEAD
+[Unreleased]: https://github.com/Ddupasquier/rehearsal-db/compare/v0.1.0-rc.2...HEAD
+[0.1.0-rc.2]: https://github.com/Ddupasquier/rehearsal-db/compare/v0.1.0-rc.1...v0.1.0-rc.2
 [0.1.0-rc.1]: https://github.com/Ddupasquier/rehearsal-db/compare/v0.1.0-beta.18...v0.1.0-rc.1
 [0.1.0-beta.18]: https://github.com/Ddupasquier/rehearsal-db/compare/v0.1.0-beta.17...v0.1.0-beta.18
 [0.1.0-beta.17]: https://github.com/Ddupasquier/rehearsal-db/compare/v0.1.0-beta.16...v0.1.0-beta.17

package/README.md

@@ -1,12 +1,39 @@
-# Rehearsal
+<p align="center">
+  <img src="https://raw.githubusercontent.com/Ddupasquier/rehearsal-db/main/docs/site/logo-mark.svg" width="104" height="104" alt="Rehearsal logo" />
+</p>
 
-[![Monthly npm downloads](https://img.shields.io/npm/dm/%40rehearsal-db%2Fcore?style=flat-square&logo=npm&logoColor=white&label=npm%20downloads&labelColor=1c2a34&color=287b5c)](https://www.npmjs.com/package/@rehearsal-db/core)
+<h1 align="center">Rehearsal</h1>
 
-[Read the documentation](https://ddupasquier.github.io/rehearsal-db/) · [View on npm](https://www.npmjs.com/package/@rehearsal-db/core) · [Report a problem](https://github.com/Ddupasquier/rehearsal-db/issues)
+<p align="center"><strong>Your migration passed on an empty database. Production will not be empty.</strong></p>
 
-Rehearsal tests PostgreSQL and Supabase migrations on your computer before you run them
-anywhere important. It restores safe test data into a disposable local database, applies
-only the migrations you approve, and runs your project's own test command.
+<p align="center">
+  <a href="https://www.npmjs.com/package/@rehearsal-db/core"><img alt="npm version" src="https://img.shields.io/npm/v/%40rehearsal-db%2Fcore?style=flat-square&logo=npm&logoColor=white&labelColor=1c2a34&color=287b5c" /></a>
+  <a href="https://www.npmjs.com/package/@rehearsal-db/core"><img alt="Monthly npm downloads" src="https://img.shields.io/npm/dm/%40rehearsal-db%2Fcore?style=flat-square&logo=npm&logoColor=white&label=downloads&labelColor=1c2a34&color=287b5c" /></a>
+  <a href="LICENSE"><img alt="MIT license" src="https://img.shields.io/npm/l/%40rehearsal-db%2Fcore?style=flat-square&labelColor=1c2a34&color=287b5c" /></a>
+  <a href="https://ddupasquier.github.io/rehearsal-db/"><img alt="Read the documentation" src="https://img.shields.io/badge/docs-read_the_guide-269fab?style=flat-square&labelColor=1c2a34" /></a>
+</p>
+
+<p align="center">
+  <a href="https://ddupasquier.github.io/rehearsal-db/">Read the documentation</a> ·
+  <a href="https://www.npmjs.com/package/@rehearsal-db/core">View on npm</a> ·
+  <a href="https://github.com/Ddupasquier/rehearsal-db/issues">Report a problem</a>
+</p>
+
+Most migration tests start with an empty database. Production does not.
+
+Existing rows, relationships, authentication identities, stored files, and migration
+history are where risky changes break. A migration can build successfully and still fail
+against the data and application behavior you actually have.
+
+**Rehearsal catches those problems before deployment.** It restores a reviewed,
+sanitized baseline into a disposable local PostgreSQL or Supabase environment, applies
+only the exact migrations you approve, and runs your application's own proof.
+
+| An empty database cannot prove…                      | Rehearsal lets you verify…                                   |
+| ---------------------------------------------------- | ------------------------------------------------------------ |
+| old rows still satisfy new constraints               | the migration against a reviewed, production-shaped copy     |
+| relationships, identities, and stored files survive  | database, Auth, and Storage behavior in one local sandbox    |
+| the application still works after the schema changes | your own tests and hands-on flows before anything is shipped |
 
 Projects with a separate publication or read-model database can declare it as a
 dependent target. Rehearsal then manages the complete isolated runtime stack.
@@ -17,7 +44,7 @@ it through a reviewed privacy policy, and retire the access again. It is never p
 `run`, `reset`, `migrate`, or application launch. Rehearsal is not a backup system or a
 production deployment tool.
 
-> Rehearsal is in public beta. Use it on a branch and keep a working backup of your
+> **Pre-1.0 safety note:** use Rehearsal on a branch and keep a working backup of your
 > project.
 
 ## What you need
@@ -37,7 +64,7 @@ your migration is intended to change.
 From your project directory:
 
 ```bash
-npm install --save-dev @rehearsal-db/core@beta
+npm install --save-dev @rehearsal-db/core
 npx rehearsal
 ```
 
@@ -145,6 +172,7 @@ Reference:
 
 - [CLI commands](docs/commands.md)
 - [Configuration](docs/configuration.md)
+- [Container runtime lifecycle](docs/runtime-lifecycle.md) — keep Docker and Supabase use on demand
 - [TypeScript types](docs/typescript.md)
 - [Baselines](docs/baselines.md)
 - [Sanitization](docs/sanitization.md)

package/dist/package.json

@@ -1,8 +1,8 @@
 {
     "name": "@rehearsal-db/core",
-    "version": "0.1.0-rc.1",
+    "version": "0.1.0-rc.2",
     "private": false,
-    "description": "Safely rehearse PostgreSQL and Supabase migrations against sanitized, production-shaped data.",
+    "description": "Catch PostgreSQL and Supabase migrations that pass on empty databases but fail on real data—before deploy.",
     "repository": {
         "type": "git",
         "url": "git+https://github.com/Ddupasquier/rehearsal-db.git"

package/dist/src/project/configuration_contract.d.mts

@@ -106,7 +106,7 @@ export declare const REHEARSAL_DEFAULTS: Readonly<{
         artifactDirectory: ".rehearsal";
     }>;
     containerRuntime: Readonly<{
-        autoStartColima: true;
+        autoStartColima: false;
     }>;
     cleanup: Readonly<{
         retainBaselineGenerations: 2;

package/dist/src/project/configuration_contract.mjs

@@ -2,7 +2,7 @@
 export const REHEARSAL_CONFIG_VERSION = 1;
 export const REHEARSAL_DEFAULTS = Object.freeze({
     baseline: Object.freeze({ artifactDirectory: ".rehearsal" }),
-    containerRuntime: Object.freeze({ autoStartColima: true }),
+    containerRuntime: Object.freeze({ autoStartColima: false }),
     cleanup: Object.freeze({ retainBaselineGenerations: 2 }),
     runtime: Object.freeze({
         applicationUrl: "http://localhost:5175",

package/dist/src/project/configuration_rendering.mjs

@@ -61,9 +61,10 @@ export default defineRehearsalConfig({
 	// After setup, run: npx rehearsal identity connect
 	// identityPolicy: "infrastructure/rehearsal/identity-policy.json",
 
-	// Reuse any running Docker-compatible engine; start Colima only when needed.
+	// Reuse any running Docker-compatible engine. Keep startup explicit so a
+	// Rehearsal command cannot wake unrelated containers after Docker was stopped.
 	containerRuntime: {
-		autoStartColima: true,
+		autoStartColima: false,
 	},
 
 	// Keep this many baseline generations, always including the active one.
@@ -166,9 +167,10 @@ export default defineRehearsalConfig({
 	// After setup, run: npx rehearsal identity connect
 	// identityPolicy: "infrastructure/rehearsal/identity-policy.json",
 
-	// Reuse any running Docker-compatible engine; start Colima only when needed.
+	// Reuse any running Docker-compatible engine. Keep startup explicit so a
+	// Rehearsal command cannot wake unrelated containers after Docker was stopped.
 	containerRuntime: {
-		autoStartColima: true,
+		autoStartColima: false,
 	},
 
 	// Keep this many baseline generations, always including the active one.

package/dist/src/runtime/plan.mjs

@@ -94,6 +94,9 @@ const resultCheck = async ({ id, label, run, remediation, }) => {
     }
 };
 const assertRuntimeConfigMatches = async ({ config, paths, }) => {
+    const startupPolicy = config.containerRuntime.autoStartColima
+        ? "Colima auto-start is enabled and may wake shared Docker containers"
+        : "container-engine startup is explicit";
     if (config.runtime.target === "postgresql") {
         if (paths.rehearsalConfig !== null || paths.supabaseWorkdir !== null) {
             throw new Error("The PostgreSQL target unexpectedly resolved Supabase paths.");
@@ -101,7 +104,7 @@ const assertRuntimeConfigMatches = async ({ config, paths, }) => {
         if (!config.postgresql) {
             throw new Error("The PostgreSQL target is missing its configuration.");
         }
-        return `isolated PostgreSQL image ${config.postgresql.image} and a loopback database port are configured`;
+        return `isolated PostgreSQL image ${config.postgresql.image} and a loopback database port are configured; ${startupPolicy}`;
     }
     if (!paths.rehearsalConfig) {
         throw new Error("The Supabase target is missing its runtime configuration.");
@@ -121,7 +124,7 @@ const assertRuntimeConfigMatches = async ({ config, paths, }) => {
     if (/\blinked\s*=\s*true\b/iu.test(source)) {
         throw new Error("Local Supabase config unexpectedly enables a linked target.");
     }
-    return "isolated Supabase project and ports match the project contract";
+    return `isolated Supabase project and ports match the project contract; ${startupPolicy}`;
 };
 const assertBaselinePermissions = async ({ paths, }) => {
     const details = await stat(paths.dataPath);

package/dist/src/targets/supabase.mjs

@@ -388,6 +388,7 @@ const resetRuntime = async () => {
                 exclude: ["edge-runtime", "logflare", "vector", "realtime"],
                 environment: serviceEnvironment,
                 autoStartColima: config.containerRuntime.autoStartColima,
+                projectId: config.runtime.projectId,
             });
             const structuralSchemaSha256 = await restoreProductionSchema(active);
             await restoreBaselineRows(active);
@@ -446,6 +447,7 @@ const startRuntime = async () => {
         exclude: ["edge-runtime", "logflare", "vector", "realtime"],
         environment: serviceEnvironment,
         autoStartColima: config.containerRuntime.autoStartColima,
+        projectId: config.runtime.projectId,
     });
     const projectRuntime = configureProjectRuntime({ environment, baseline });
     await writeRuntimeEnvironment({

package/dist/src/targets/supabase_environment.d.mts

@@ -35,11 +35,16 @@ export declare const ensureLocalContainerRuntime: ({ cwd, autoStartColima, }?: {
     cwd?: string | undefined;
     autoStartColima?: boolean;
 }) => void;
+export declare const preventOwnedSupabaseAutoRestart: ({ cwd, projectId, }: {
+    cwd?: string | undefined;
+    projectId: string;
+}) => readonly string[];
 export declare const readLocalSupabaseEnvironment: ({ cwd, workdir, environment, }?: SupabaseCommandOptions) => LocalSupabaseEnvironment;
-export declare const startLocalSupabase: ({ cwd, workdir, exclude, environment, applyMigrations, autoStartColima, }?: SupabaseCommandOptions & {
+export declare const startLocalSupabase: ({ cwd, workdir, exclude, environment, applyMigrations, autoStartColima, projectId, }?: SupabaseCommandOptions & {
     exclude?: readonly string[];
     applyMigrations?: boolean;
     autoStartColima?: boolean;
+    projectId?: string | undefined;
 }) => LocalSupabaseEnvironment;
 export declare const stopLocalSupabase: ({ cwd, workdir, environment, }?: SupabaseCommandOptions) => void;
 export declare const removeLocalSupabaseProjectResources: ({ cwd, projectId, }?: {

package/dist/src/targets/supabase_environment.mjs

@@ -90,22 +90,42 @@ export const localCommandSucceeds = (command, args, { cwd = process.cwd(), envir
     env: createCleanProcessEnvironment({ overrides: environment }),
     stdio: "ignore",
 }).status === 0;
-export const ensureLocalContainerRuntime = ({ cwd = process.cwd(), autoStartColima = true, } = {}) => {
+export const ensureLocalContainerRuntime = ({ cwd = process.cwd(), autoStartColima = false, } = {}) => {
     if (localCommandSucceeds("docker", ["info"], { cwd }))
         return;
     if (autoStartColima && localCommandSucceeds("colima", ["version"], { cwd })) {
         runLocalCommand("colima", ["start"], { cwd });
+        console.log("Started Colima because containerRuntime.autoStartColima is enabled. Rehearsal will not stop this shared Docker runtime automatically.");
     }
     if (!localCommandSucceeds("docker", ["info"], { cwd })) {
-        throw new Error("A local Docker-compatible runtime is required. Install Docker or Colima, then rerun the command.");
+        throw new Error(autoStartColima
+            ? "A local Docker-compatible runtime is required. Install Docker or Colima, then rerun the command."
+            : "A local Docker-compatible runtime is stopped or unavailable. Start Docker or Colima explicitly, or opt in with containerRuntime.autoStartColima: true.");
     }
 };
+export const preventOwnedSupabaseAutoRestart = ({ cwd = process.cwd(), projectId, }) => {
+    if (!/^[a-z0-9][a-z0-9-]{1,62}$/u.test(projectId)) {
+        throw new Error("Refusing to change container restart policies without an exact safe Supabase project id.");
+    }
+    const label = `com.supabase.cli.project=${projectId}`;
+    const containers = runLocalCommand("docker", ["ps", "--all", "--filter", `label=${label}`, "--format", "{{.ID}}"], { capture: true, cwd })
+        .split("\n")
+        .map((value) => value.trim())
+        .filter(Boolean);
+    if (containers.length) {
+        runLocalCommand("docker", ["update", "--restart=no", ...containers], {
+            capture: true,
+            cwd,
+        });
+    }
+    return Object.freeze(containers);
+};
 const withWorkdir = (args, workdir) => (workdir ? [...args, "--workdir", workdir] : [...args]);
 export const readLocalSupabaseEnvironment = ({ cwd, workdir, environment = {}, } = {}) => {
     const output = runLocalCommand("supabase", withWorkdir(["status", "-o", "env"], workdir), { capture: true, cwd, environment });
     return parseLocalSupabaseEnvironment(output);
 };
-export const startLocalSupabase = ({ cwd, workdir, exclude = [], environment = {}, applyMigrations = true, autoStartColima = true, } = {}) => {
+export const startLocalSupabase = ({ cwd, workdir, exclude = [], environment = {}, applyMigrations = true, autoStartColima = false, projectId, } = {}) => {
     ensureLocalContainerRuntime({ cwd, autoStartColima });
     const startArguments = withWorkdir(["start", ...(exclude.length ? ["--exclude", exclude.join(",")] : [])], workdir);
     runLocalCommand("supabase", startArguments, {
@@ -113,6 +133,8 @@ export const startLocalSupabase = ({ cwd, workdir, exclude = [], environment = {
         cwd,
         environment,
     });
+    if (projectId)
+        preventOwnedSupabaseAutoRestart({ cwd, projectId });
     if (applyMigrations) {
         runLocalCommand("supabase", withWorkdir(["migration", "up", "--local"], workdir), { capture: true, cwd, environment });
     }

package/docs/README.md

@@ -1,7 +1,14 @@
 # Rehearsal documentation
 
-Welcome. You do not need to read this documentation from top to bottom. Choose what you
-want to accomplish and follow that path.
+Most migration tests start with an empty database. Production does not. Existing rows,
+relationships, authentication identities, stored files, and migration history are where
+risky changes break.
+
+Rehearsal restores a reviewed, sanitized baseline into a disposable local environment,
+applies only the exact migrations you approve, and runs your application's own proof.
+
+You do not need to read this documentation from top to bottom. Choose what you want to
+accomplish and follow that path.
 
 ## Start here
 
@@ -24,6 +31,7 @@ want to accomplish and follow that path.
 
 - [CLI commands](commands.md)
 - [Configuration](configuration.md)
+- [Container runtime lifecycle](runtime-lifecycle.md)
 - [TypeScript](typescript.md)
 - [Runtime and identity policies](runtime-policies.md)
 - [Database adapters](adapters.md)

package/docs/configuration.md

@@ -4,7 +4,7 @@ An ordinary npm application install creates this file in the application root wh
 root can be identified safely:
 
 ```bash
-npm install --save-dev @rehearsal-db/core@beta
+npm install --save-dev @rehearsal-db/core
 ```
 
 The install hook detects the database type, project name, migration folder,
@@ -82,7 +82,7 @@ export default defineRehearsalConfig({
   // After setup, run: npx rehearsal identity connect
   // identityPolicy: "infrastructure/rehearsal/identity-policy.json",
   containerRuntime: {
-    autoStartColima: true,
+    autoStartColima: false,
   },
   cleanup: {
     retainBaselineGenerations: 2,
@@ -227,7 +227,7 @@ SHA-256 receipts are tracked. See
 
 ```ts
 containerRuntime: {
-  autoStartColima: true,
+  autoStartColima: false,
 },
 cleanup: {
   retainBaselineGenerations: 2,
@@ -235,9 +235,17 @@ cleanup: {
 ```
 
 Rehearsal uses whichever Docker-compatible engine already answers `docker info`. If none
-is running and `autoStartColima` is `true`, Rehearsal may run `colima start`. It respects
-the user's Colima CPU, memory, and disk settings and never changes them. Set the field to
-`false` when you prefer to start Docker or Colima yourself.
+is running and `autoStartColima` is `true`, Rehearsal may run `colima start`. This is an
+explicit opt-in because starting a shared Docker engine can also restart unrelated
+containers whose restart policy is `always` or `unless-stopped`. Rehearsal respects the
+user's Colima CPU, memory, and disk settings and never changes them. The generated default
+is `false`: start Docker or Colima yourself before a mutating command. Rehearsal never
+stops a shared container engine automatically.
+
+After each Supabase start, Rehearsal changes only the exact target's containers to
+Docker's `no` restart policy. Its database and Storage volumes remain intact,
+`rehearsal start` can resume it, and restarting Docker does not silently wake stopped
+Rehearsal stacks.
 
 `retainBaselineGenerations` controls how many immutable baseline generations survive an
 approved `rehearsal refresh` or `rehearsal cleanup`; it must be at least 1. Refresh shows

package/docs/getting-started.md

@@ -35,7 +35,7 @@ Rehearsal will use that image with downloads disabled.
 Run these commands from the directory containing your project's `package.json`:
 
 ```bash
-npm install --save-dev @rehearsal-db/core@beta
+npm install --save-dev @rehearsal-db/core
 npx rehearsal
 ```
 

package/docs/index.md

@@ -1,18 +1,37 @@
 # Rehearsal documentation
 
+## Why an empty database is not enough
+
+Most migration tests start with an empty database. Production does not.
+
+Existing rows, relationships, authentication identities, stored files, and migration
+history are where risky changes break. A migration can build successfully and still fail
+against the data and application behavior you actually have.
+
+Rehearsal catches those problems before deployment. It restores a reviewed, sanitized
+baseline into a disposable local PostgreSQL or Supabase environment, applies only the
+exact migrations you approve, and runs your application's own proof.
+
+| Empty-database tests miss…                        | Rehearsal exercises…                                      |
+| ------------------------------------------------- | --------------------------------------------------------- |
+| old rows and edge cases                           | a reviewed, production-shaped baseline                    |
+| relationships between data, identities, and files | database, Auth, and Storage in one local sandbox          |
+| whether the product still behaves correctly       | your automated proof and hands-on application walkthrough |
+
 ## Pick the path that fits today
 
 You do not need to read everything before your first rehearsal. Start with the outcome
 you want, then follow the links when a term or safety check is new.
 
-| I want to…                            | Go here                                                           |
-| ------------------------------------- | ----------------------------------------------------------------- |
-| Set up my own project                 | [Getting started](getting-started.md)                             |
-| Try Rehearsal without touching my app | [Hands-on tutorial](tutorial.md)                                  |
-| Understand what makes a copy safe     | [Baselines](baselines.md) and [Sanitization](sanitization.md)     |
-| Look up a command or setting          | [CLI commands](commands.md) and [Configuration](configuration.md) |
-| Add editor and compiler type checks   | [TypeScript](typescript.md)                                       |
-| Fix something that did not work       | [Troubleshooting](troubleshooting.md)                             |
+| I want to…                              | Go here                                                           |
+| --------------------------------------- | ----------------------------------------------------------------- |
+| Set up my own project                   | [Getting started](getting-started.md)                             |
+| Try Rehearsal without touching my app   | [Hands-on tutorial](tutorial.md)                                  |
+| Understand what makes a copy safe       | [Baselines](baselines.md) and [Sanitization](sanitization.md)     |
+| Look up a command or setting            | [CLI commands](commands.md) and [Configuration](configuration.md) |
+| Reduce Docker and Supabase resource use | [Container runtime lifecycle](runtime-lifecycle.md)               |
+| Add editor and compiler type checks     | [TypeScript](typescript.md)                                       |
+| Fix something that did not work         | [Troubleshooting](troubleshooting.md)                             |
 
 ## The short version
 

package/docs/runtime-lifecycle.md

@@ -0,0 +1,99 @@
+# Container runtime lifecycle
+
+Rehearsal uses a local Docker-compatible engine for disposable PostgreSQL and Supabase
+targets. It owns the targets it creates; it does not own the shared engine or another
+project's containers.
+
+## What starts Docker?
+
+Read-only commands such as `doctor`, `status`, `candidates`, `explain`, and `inspect` do
+not start Docker. Commands that create or resume a database—such as `start`, `reset`,
+`run`, and `open`—need an already-running engine.
+
+Generated configurations keep startup explicit:
+
+```js
+containerRuntime: {
+  autoStartColima: false,
+},
+```
+
+With the default, a stopped engine produces an actionable error. Start Docker Desktop,
+Colima, Rancher Desktop, Podman with Docker compatibility, or another supported engine,
+then repeat the command.
+
+Setting `autoStartColima: true` is an explicit convenience opt-in. If Docker is
+unavailable and the `colima` command exists, Rehearsal runs plain `colima start` and
+reports it. Rehearsal does not resize Colima and does not stop the shared engine
+automatically. Starting Docker can also wake unrelated containers that use Docker's
+`always` or `unless-stopped` restart policy.
+
+## What remains after a command?
+
+- `run` stops the application proof process but keeps the database target available for
+  hands-on testing.
+- `open` keeps the application and databases available until the application session is
+  interrupted. The database target remains available afterward.
+- `stop` stops every configured Rehearsal target in reverse dependency order and retains
+  its local data.
+- `start` resumes a stopped target, reusing compatible state.
+- `reset` recreates the target from the active immutable baseline.
+- `discard` removes the selected disposable target. It is the data-destructive runtime
+  operation and retains the immutable baseline.
+
+After Supabase starts, Rehearsal changes only containers with the exact configured
+Supabase project label to Docker's `no` restart policy. This does not remove containers
+or volumes. It prevents a later Docker restart from silently waking stopped Rehearsal
+stacks; `rehearsal start` still resumes them normally.
+
+## A low-memory daily workflow
+
+1. Start your Docker-compatible engine.
+2. Run `rehearsal run` or `rehearsal open`.
+3. When finished, run `rehearsal stop` from the project root.
+4. Check other projects before stopping the shared engine:
+
+   ```bash
+   docker ps
+   ```
+
+5. If nothing else needs Docker, stop the engine using its own command, such as
+   `colima stop`.
+
+Rehearsal intentionally does not infer that every running container belongs to it. It
+also never runs a global Docker prune. Database and Storage volumes are not deleted by
+`stop`.
+
+## Choosing PostgreSQL or Supabase
+
+Use the PostgreSQL target for migration, schema, trigger, privacy, and ordinary relational
+data checks that do not require Supabase services. It uses one database container.
+
+Use the Supabase target when the proof needs Auth, Storage, PostgREST, or the local API
+gateway. Rehearsal already excludes Realtime, Edge Runtime, Analytics/Logflare, and Vector
+from its Supabase stack. A future service-profile feature will make additional optional
+services explicit; until then, do not trade away application fidelity merely to reduce a
+container count.
+
+## Diagnosing unexpected activity
+
+Start with read-only checks:
+
+```bash
+docker context show
+docker ps --format 'table {{.Names}}\t{{.Status}}\t{{.Label "com.supabase.cli.project"}}'
+docker stats --no-stream
+colima status
+```
+
+For each container, inspect its project ownership and restart policy before taking any
+action:
+
+```bash
+docker inspect --format '{{json .Config.Labels}} {{.HostConfig.RestartPolicy.Name}}' CONTAINER
+```
+
+Do not remove anonymous volumes or old images based on names alone. Use `rehearsal
+cleanup` for package-owned baseline retention and its reviewed, opt-in image cleanup.
+Shared resource inventory and stale-environment cleanup are tracked separately; until
+that lands, stopping a configured target from its own project is the safe path.

package/docs/stability.md

@@ -26,7 +26,7 @@ file names, and undocumented package paths are not compatibility promises.
 
 ## What blocks a release candidate
 
-An issue blocks `0.1.0-rc.1` when it can cause any of the following within a supported
+An issue blocks the active release candidate when it can cause any of the following within a supported
 configuration:
 
 - data loss, credential exposure, hosted-system access, or mutation outside resources
@@ -47,12 +47,13 @@ release.
 
 1. Ship beta.18 with only stability, release-safety, upgrade, and documentation work.
 2. Freeze broad feature development on the release branch.
-3. Publish `0.1.0-rc.1` from protected `main` through the reviewed npm environment.
+3. Publish a release candidate from protected `main` through the reviewed npm environment.
 4. Run the complete Rehearsal Test Lab gate twice from clean isolated workspaces.
 5. Perform one final package-only upgrade in a real consumer. The consumer must use the
    published package rather than duplicate Rehearsal machinery.
-6. Keep the candidate available for at least seven calendar days. Restart the window if
-   a blocking package change is required.
+6. Keep the current candidate available for at least seven calendar days. Restart the
+   window if a blocking package change is required. The container-lifecycle correction
+   in `0.1.0-rc.2` restarts this observation window.
 7. Publish `0.1.0` only when no blocking issue remains and the accepted registry artifact
    matches the tested artifact exactly.
 

package/docs/troubleshooting.md

@@ -11,10 +11,10 @@ Doctor names each missing or unsafe item. If you still need help, run
 
 ## `npx rehearsal` cannot find the command
 
-Confirm you are in the project directory and install the beta locally:
+Confirm you are in the project directory and install the current release locally:
 
 ```bash
-npm install --save-dev @rehearsal-db/core@beta
+npm install --save-dev @rehearsal-db/core
 npx rehearsal --help
 ```
 

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@rehearsal-db/core",
-  "version": "0.1.0-rc.1",
+  "version": "0.1.0-rc.2",
   "private": false,
-  "description": "Safely rehearse PostgreSQL and Supabase migrations against sanitized, production-shaped data.",
+  "description": "Catch PostgreSQL and Supabase migrations that pass on empty databases but fail on real data—before deploy.",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/Ddupasquier/rehearsal-db.git"