Close analyze checkpointing workstream

docs/internal/manifest.md

@@ -119,6 +119,8 @@ the last committed collection before constructing the active failed record.
 Newly materialized canonical bytes therefore remain incidental and cannot
 become current authority. A later ordinary run reconciles the durable records,
 reuses earlier current artifacts, and resumes with the failed or stale work.
+The same recovery applies after process interruption: the aggregate record may
+be non-successful, but every completed artifact checkpoint remains reusable.
 
 ## Remote Commit Manifest
 
@@ -151,6 +153,10 @@ establish a current immutable snapshot.
 
 Manifest replacement provides atomic visibility, not a crash- or power-loss
 durability guarantee. Callers reload after a returned save error before retrying.
+An analyze checkpoint error leaves the prior manifest as per-artifact authority.
+The runner then attempts to persist the bounded failed/stale retry collection;
+if that terminal save also fails, its error is joined with the originating
+failure and the next invocation must reconcile from the last readable manifest.
 
 ## Execution Semantics
 

docs/internal/stage-analyze.md

@@ -104,6 +104,10 @@ Supported source families:
   prerequisites remain available through the runtime catalog without invoking
   Scriptorium; newly produced prerequisites enter that catalog with the same
   contract, checksum, and size identity used for persisted current evidence.
+- before the first adapter call, checkpoints the reconciled starting collection
+  when it removed configuration records or cleared obsolete authority. After
+  each successful artifact, checkpoints the complete collection before making
+  that artifact available to the next scheduled dependent.
 - keeps adapter output in the invocation's run-local analyze directory until
   it is a safe, non-empty, bounded regular file with a calculated checksum and
   complete output contract. Canonical replacement uses the shared atomic file
@@ -146,6 +150,10 @@ Supported source families:
 - unrelated current records survive a partial failure. Old canonical bytes for
   the failed artifact and newly materialized bytes whose checkpoint fails are
   incidental, not current evidence.
+- a checkpoint failure stops the queue immediately. The in-memory retry
+  collection starts from the last successful checkpoint, marks the active
+  artifact failed without output authority, and stales its current transitive
+  dependents.
 - the runner's ordinary error path marks aggregate analyze failed, clears its
   aggregate outputs, invalidates publish and notify through the application
   dependency relation, and persists the live retry collection. Terminal-save
@@ -164,6 +172,9 @@ Supported source families:
 - output provenance and metadata are deterministic per execution.
 - a canonical file without current per-artifact manifest evidence is never
   promoted to current state.
+- an ordinary retry after interruption or partial failure reuses every valid
+  earlier checkpoint and schedules only failed, stale, missing, or otherwise
+  non-current work in dependency order.
 
 ## Related Contracts And Tests