Integrate extraction lifecycle and resume validation

docs/cli.md

@@ -75,7 +75,8 @@ narratio run <session_id> [--force] [--artifacts <name[,name...]>] [...common co
 Behavior:
 
 - evaluates full stage order;
-- skips already-succeeded stages unless `--force` is set;
+- skips already-succeeded stages unless `--force` is set or a stage-specific
+  resume check finds its durable result obsolete;
 - continues interrupted or partially completed sessions by running non-succeeded stages;
 - writes session and run manifests.
 
@@ -93,6 +94,7 @@ Valid stage names:
 - `polish`
 - `normalize`
 - `trim`
+- `extract`
 - `render`
 - `analyze`
 - `publish`

docs/internal/overview.md

@@ -53,10 +53,11 @@ The implemented canonical order is:
 4. [`polish`](stage-polish.md)
 5. [`normalize`](stage-normalize.md)
 6. [`trim`](stage-trim.md)
-7. [`render`](stage-render.md)
-8. [`analyze`](stage-analyze.md)
-9. [`publish`](stage-publish.md)
-10. `notify` (placeholder)
+7. `extract`
+8. [`render`](stage-render.md)
+9. [`analyze`](stage-analyze.md)
+10. [`publish`](stage-publish.md)
+11. `notify` (placeholder)
 
 `notify` currently has optional notifier call behavior and no persisted pipeline
 outputs; its default collaborator is a no-op sender. The focused stage

docs/roadmap/implementation.md

@@ -21,7 +21,7 @@ implementation sequence.
 | Stage 3 | Complete |
 | Stage 4 | Complete |
 | Stage 5 | Complete |
-| Stage 6 | Not started |
+| Stage 6 | Complete |
 | Stage 7 | Not started |
 | Stage 8 | Not started |
 | Stage 9 | Not started |