fix(audit): restore adopted durable tiers

CLAUDE.md

@@ -111,14 +111,15 @@ caller; it exists only as test infrastructure (`polylogue-enium`).
 `TopologyEdgeStatus` = unresolved/resolved/repaired/**quarantined**
 (cycle-break).
 
-### The five tiers (durability is the axis)
+### The six tiers (durability is the axis)
 
 | Tier | durability | holds |
 | --- | --- | --- |
 | `source.db` | durable | raw acquired bytes (`raw_sessions`), artifact taxonomy, blob/GC substrate (`blob_refs`, `gc_generations`), hook events, sidecars |
 | `index.db` | **rebuildable** | the whole parsed tree, FTS, `session_links`, cost tables, and all materialized insights |
 | `embeddings.db` | rebuildable | `vec0` virtual table (Voyage 1024-dim), meta, status |
 | `user.db` | **durable, irreplaceable** | unified `assertions`, settings/context receipts, immutable annotation schemas + batch provenance |
+| `audit.db` | **durable, append-only authority** | mutation previews, authorizations, attempts, receipts, and continuity heads |
 | `ops.db` | disposable | ingest cursors, attempts, `convergence_debt`, cursor-lag samples, daemon events, embed catch-up runs |
 
 `user.db` is a **single unified `assertions` table** keyed by a closed
@@ -186,8 +187,8 @@ snapshot reference check) to bridge the acquire-blob → commit-row window.
 
 Two evolution regimes, enforced by `devtools lab policy schema-versioning`:
 
-- **Durable tiers** (`source.db`, `user.db`): explicit **additive** numbered SQL
-  migrations under `storage/sqlite/migrations/{source,user}/NNN_*.sql`, one
+- **Durable tiers** (`source.db`, `user.db`, `audit.db`): explicit **additive** numbered SQL
+  migrations under `storage/sqlite/migrations/{source,user,audit}/NNN_*.sql`, one
   `PRAGMA user_version` step at a time, behind a **verified backup manifest**.
   Destructive durable changes need a copy-forward design + explicit consent.
 - **Derived tiers** (`index.db`, `embeddings.db`): no migration *chain*, but not

devtools/render_cli_output_schemas.py

@@ -24,6 +24,7 @@
 from devtools.command_catalog import control_plane_command
 from devtools.render_support import write_if_changed
 from polylogue.archive.query.metadata import terminal_query_cli_surfaces, terminal_query_source_list
+from polylogue.cli.commands.maintenance._migrate_tier import MigrateTierResultPayload
 from polylogue.operations.action_contracts import ActionAffordanceListPayload
 from polylogue.surfaces.payloads import (
     ArchiveDebtListPayload,
@@ -259,6 +260,16 @@ class CliOutputSchema:
             "MCP action_affordances",
         ),
     ),
+    CliOutputSchema(
+        name="migrate-tier-result",
+        title="Migrate Tier Result",
+        description=(
+            "Result from `polylogue ops maintenance migrate-tier --output-format json`, including durable "
+            "adoption and restore receipt references."
+        ),
+        model=MigrateTierResultPayload,
+        surfaces=("polylogue ops maintenance migrate-tier --output-format json",),
+    ),
     CliOutputSchema(
         name="machine-error",
         title="Machine Error Envelope",

devtools/validation_lane_catalog_contracts.py

@@ -281,6 +281,7 @@
             "mutate-clear-corrections",
             "mutate-delete-session",
             "mutate-session-excision",
+            "mutate-session-lifecycle-request",
             "mutate-identity-reset",
         ),
         tags=("contract", "mutation", "operation-executor"),

devtools/verify_schema_upgrade_lane.py

@@ -5,7 +5,7 @@
 
 Polylogue has two schema-evolution regimes:
 
-* Durable tiers (``source.db`` and ``user.db``) may use explicit additive SQL
+* Durable tiers (``source.db``, ``user.db``, and ``audit.db``) may use explicit additive SQL
   migrations with a backup gate.
 * Derived/rebuildable tiers (``index.db`` and ``embeddings.db``) do not use
   migration chains. They are rebuilt or blue-green replaced from durable source
@@ -86,7 +86,7 @@
 ROOT = _get_root()
 STORAGE_SQLITE_DIR = ROOT / "polylogue" / "storage" / "sqlite"
 MIGRATIONS_DIR = STORAGE_SQLITE_DIR / "migrations"
-ALLOWED_MIGRATION_TIERS = {"source", "user"}
+ALLOWED_MIGRATION_TIERS = {"source", "user", "audit"}
 
 # Upgrade-shaped helper name patterns. Matched against ``def <name>``
 # at the top level of any module under ``polylogue/storage/sqlite/``.
@@ -345,7 +345,8 @@ def main(argv: list[str] | None = None) -> int:
     helpers = _collect_upgrade_helpers()
     invalid_migrations = _invalid_migration_paths()
     durable_change_train_reports = {
-        tier.value: durable_change_train_policy_report(tier) for tier in (ArchiveTier.SOURCE, ArchiveTier.USER)
+        tier.value: durable_change_train_policy_report(tier)
+        for tier in (ArchiveTier.SOURCE, ArchiveTier.USER, ArchiveTier.AUDIT)
     }
     durable_migration_collisions = durable_migration_collision_report(_durable_migration_claims_on_disk())
     delta_report = index_delta_declaration_report(INDEX_SCHEMA_VERSION)

docs/cli-reference.md

@@ -801,6 +801,7 @@ The schema files live under `docs/schemas/cli-output/`.
 | `session-neighbor-candidate` | `SessionNeighborCandidatePayload` | `polylogue read --view neighbors --format json` |
 | `mutation-result` | `MutationResultPayload` | `polylogue find <query> then delete --dry-run`<br>`polylogue find <query> then delete --yes`<br>`MCP mutation tools`<br>`daemon mutation endpoints` |
 | `action-affordance-list` | `ActionAffordanceListPayload` | `polylogue config action-affordances`<br>`GET /api/action-affordances`<br>`MCP action_affordances` |
+| `migrate-tier-result` | `MigrateTierResultPayload` | `polylogue ops maintenance migrate-tier --output-format json` |
 | `machine-error` | `MachineErrorPayload` | `polylogue * --machine (error path)` |
 | `machine-success` | `MachineSuccessPayload` | `polylogue * --machine (success path)` |
 | `query-error` | `QueryErrorPayload` | `GET /api/sessions?query=... (error path)`<br>`daemon query/read error responses`<br>`MCP query/read error responses` |

docs/internals.md

@@ -86,9 +86,9 @@ Polylogue has two schema-evolution regimes, keyed by tier durability.
 
 - Tier version constants under `storage/sqlite/archive_tiers/` are the
   authority. The canonical fresh schema is described directly by each tier DDL.
-- **Durable tiers** (`source.db`, `user.db`) may use explicit additive
+- **Durable tiers** (`source.db`, `user.db`, `audit.db`) may use explicit additive
   migrations. Migration SQL lives under
-  `storage/sqlite/migrations/{source,user}/NNN_name.sql`, advances
+  `storage/sqlite/migrations/{source,user,audit}/NNN_name.sql`, advances
   `PRAGMA user_version` one step at a time, and requires a verified backup
   manifest containing the affected tier before it runs. Verification restores
   the backup into scratch, checks every included SQLite tier and referenced
@@ -685,10 +685,11 @@ rebuilds or blue-green-replaces the tier from durable source/user evidence.
 Files that are not configured archive paths are not classified or handled by
 the archive runtime.
 
-For **durable tiers** (`source.db`, `user.db`) the boundary is different, because
-`user.db` holds irreplaceable human assertions that cannot be rebuilt from
-source. These tiers use explicit *additive* numbered SQL migrations under
-`storage/sqlite/migrations/{source,user}/NNN_*.sql`, applied one `PRAGMA
+For **durable tiers** (`source.db`, `user.db`, `audit.db`) the boundary is different, because
+`user.db` holds irreplaceable human assertions and `audit.db` holds immutable
+mutation authority and receipt evidence; neither can be rebuilt from source.
+These tiers use explicit *additive* numbered SQL migrations under
+`storage/sqlite/migrations/{source,user,audit}/NNN_*.sql`, applied one `PRAGMA
 user_version` step at a time by `migration_runner.py` behind a **verified backup
 manifest** for the affected tier. Additive means `CREATE TABLE`/`CREATE INDEX`/
 `ADD COLUMN`/bounded backfill; destructive durable-tier changes require a

docs/maintenance.md

@@ -728,8 +728,8 @@ polylogue ops diagnostics workload --json | jq .fts_trigger_state.all_present
 
 If FTS remains non-ready after daemon convergence, the underlying issue is
 structural (missing columns, corrupted index file, or a broken write path).
-Stop the daemon, restore from backup or rebuild the affected index tier, and
-open an issue with the probe output attached.
+Stop the daemon, restore or rebuild the affected index tier, and open an issue
+with the probe output attached.
 
 ### Inspecting a raw-authority census
 

docs/plans/mutation-census.yaml

@@ -61,6 +61,14 @@ rows:
     adapters:
       - polylogue.cli.commands.excise.excise_command
 
+  - operation: mutate-session-lifecycle-request
+    spec_name: mutate-session-lifecycle-request
+    status: executor-routed
+    actuator: polylogue.operations.mutation_actuators.SessionLifecycleRequestActuator
+    surfaces: [cli]
+    adapters:
+      - polylogue.cli.commands.excise.excise_command (--mode mirror/primary)
+
   - operation: mutate-identity-reset
     spec_name: mutate-identity-reset
     status: executor-routed

docs/schemas/cli-output/README.md

@@ -30,6 +30,7 @@ devtools render cli-output-schemas --check # CI sync check
 | [`session-neighbor-candidate.schema.json`](./session-neighbor-candidate.schema.json) | `polylogue read --view neighbors --format json` | `SessionNeighborCandidatePayload` |
 | [`mutation-result.schema.json`](./mutation-result.schema.json) | `polylogue find <query> then delete --dry-run`<br>`polylogue find <query> then delete --yes`<br>`MCP mutation tools`<br>`daemon mutation endpoints` | `MutationResultPayload` |
 | [`action-affordance-list.schema.json`](./action-affordance-list.schema.json) | `polylogue config action-affordances`<br>`GET /api/action-affordances`<br>`MCP action_affordances` | `ActionAffordanceListPayload` |
+| [`migrate-tier-result.schema.json`](./migrate-tier-result.schema.json) | `polylogue ops maintenance migrate-tier --output-format json` | `MigrateTierResultPayload` |
 | [`machine-error.schema.json`](./machine-error.schema.json) | `polylogue * --machine (error path)` | `MachineErrorPayload` |
 | [`machine-success.schema.json`](./machine-success.schema.json) | `polylogue * --machine (success path)` | `MachineSuccessPayload` |
 | [`query-error.schema.json`](./query-error.schema.json) | `GET /api/sessions?query=... (error path)`<br>`daemon query/read error responses`<br>`MCP query/read error responses` | `QueryErrorPayload` |