Finalize artifact workflow documentation

docs/internal/adapters.md

@@ -52,6 +52,12 @@ range, but an unselected integration is neither initialized nor validated by
 runner composition. Each selected stage retains its own fail-fast configuration
 and input validation.
 
+`session plan` is outside production adapter composition. It performs
+resume validation and models selected transitions against cloned manifest
+state without constructing or invoking stage-execution adapters. The shared
+command configuration loader may still use object storage to retrieve a missing
+remote session file before planning begins.
+
 Notarius is composed only when extraction is enabled; the extract stage owns
 prepared reference resolution, receipt, bundle, and configured-lane policy.
 The adapter validates the ordered selector/absolute-path pairs and is the sole

docs/internal/artifacts.md

@@ -54,12 +54,14 @@ kind and prepared filename vocabulary.
 Configured definitions are always registered. Without an explicit selection,
 the effective analyze set contains enabled definitions. With `--artifacts`, the
 exact named configured definitions become the effective set for that invocation,
-regardless of their `enabled` value; dependencies are not added implicitly.
-Availability is separate from executability. Configured outputs, including
-non-executable prerequisites, become available only when the versioned analyze
-state identifies a current result whose source, contract, canonical configured
-path, size, and checksum match a confined no-follow regular file. An incidental
-canonical file and a legacy aggregate analyze output are unavailable.
+regardless of their `enabled` value. The effective-set resolver itself does not
+expand dependencies; the analyze work planner closes those targets over their
+configured prerequisite graph. Availability is separate from executability.
+Configured outputs, including non-executable prerequisites, become available
+only when the versioned analyze state identifies a current result whose source,
+contract, canonical configured path, size, and checksum match a confined
+no-follow regular file. An incidental canonical file and a legacy aggregate
+analyze output are unavailable.
 Extraction entries are registered from configuration and become available only
 after compatible extraction evidence is hydrated.
 

docs/internal/manifest.md

@@ -189,9 +189,11 @@ cannot contain outputs.
 When an already-succeeded stage is skipped, the invocation run manifest records
 the `skip` action and reason. The session manifest deliberately retains its
 existing succeeded record because it remains the cross-invocation progress
-authority. Stages with a resume validator, currently extraction, may reject an
-otherwise eligible skip when the recorded durable result is obsolete; the
-runner marks it stale and executes it.
+authority. Extraction and analyze have resume validators and may reject an
+otherwise eligible skip when their selected durable evidence is obsolete; the
+runner marks the aggregate record stale and executes it. Analyze's validator
+can still accept a partial selection when only unrelated artifact records are
+stale.
 
 Session manifest is the authoritative stage-progress ledger across invocations.
 Run manifest is invocation-scoped audit state.

docs/internal/overview.md

@@ -43,6 +43,14 @@ Narratio-level contracts; external transport and SDK details remain in
 adapters. The normative rules for these relationships remain in
 [Architecture](../policy/architecture.md).
 
+Pipeline execution and `session plan` share the same inclusive contiguous-range
+model. Planning clones session state and applies selected-stage transitions and
+resume validation in memory; it does not create invocation state or initialize
+stage-execution adapters. Command configuration loading can still retrieve a
+missing session file through configured remote storage. Analyze planning
+additionally exposes the artifact closure's targets, prerequisite rebuilds,
+execution order, and current reuse.
+
 ## Pipeline Stage Set
 
 The implemented canonical order is:

docs/internal/stage-analyze.md

@@ -31,7 +31,9 @@ Supported source families:
   executable, completes successfully with no outputs and records explanatory
   metadata. This is not an explicit self-skip: both manifests record success,
   satisfy publish's prerequisite, and an ordinary later run reuses the result
-  until forced.
+  while the effective set remains empty. Enabling or selecting an artifact
+  later makes missing versioned evidence non-resumable and schedules it without
+  requiring force.
 - builds a runtime artifact catalog containing built-ins, configured artifacts,
   and configured extraction lanes. Extraction availability is hydrated only
   from compatible successful extraction evidence.