Prepare Notarius v0.8.1 source release

docs/roadmap/archive/remediation.md

@@ -24,7 +24,8 @@ The original finding below is retained as review context.
 ## Review Scope
 
 Reviewed implementation commits `31b48d2` through `7ac9d94` against
-[the feature roadmap](upgrade-kit.md) and [the implementation plan](implementation.md).
+[the feature roadmap](upgrade-kit.md) and the completed upgrade work recorded
+in those commits.
 The review covered configuration selection/defaults, production client wiring,
 error translation, execution observation, scheduler/debug propagation, current
 documentation, and tests. No production model calls were made.

docs/roadmap/archive/upgrade-kit.md

@@ -12,9 +12,9 @@ Adopt ConfigKit v0.4.0 and PromptKit v0.11.0 in one coordinated work set:
 Preserve application/framework boundaries and keep the two upgrades as distinct
 implementation workstreams. Neither requires a redesign of pipeline execution.
 
-This feature roadmap owns the target state and scope. The ordered work and
-stage-specific verification belong to the [implementation plan](implementation.md).
-Neither document authorizes release publication.
+This feature roadmap records the target state and scope. Its original
+implementation plan was completed and later replaced by a new work plan.
+Neither document authorized release publication.
 
 ## Current Baseline
 
@@ -249,7 +249,7 @@ new durable telemetry artifact, or add complete cost accounting.
 ### Documentation
 
 Update current documentation with the implementation, keeping canonical
-ownership under [Documentation Policy](../policy/documentation.md):
+ownership under [Documentation Policy](../../policy/documentation.md):
 
 - `docs/cli.md`: new flag on every affected command and matching help behavior.
 - `docs/config.md`: overlay terminology, directory layout, precedence, and the
@@ -296,7 +296,7 @@ retries and zero-value opt-out, and the dependency license change. PromptKit's
 catalogs are unchanged from v0.10.0; this upgrade adds no further profile-name
 migration or change to the D&D model defaults. Release preparation,
 tagging, and publication remain a separately requested task under
-[Source Releases](../release.md).
+[Source Releases](../../release.md).
 
 ## Acceptance And Verification
 
@@ -333,5 +333,5 @@ tagging, and publication remain a separately requested task under
   and the complete configuration with `--config-overlay development`.
 
 Use existing behavioral tests where possible, following
-[Testing Policy](../policy/testing.md). No live model calls or production API
+[Testing Policy](../../policy/testing.md). No live model calls or production API
 credentials are needed to validate this migration.