Plan the PromptKit 0.8 upgrade

docs/roadmap/future.md

@@ -15,34 +15,11 @@ is warranted.
 
 ### 1. Upgrade To PromptKit v0.8.0
 
-- Upgrade the PromptKit dependency and follow the upstream v0.8.0 release
-  guide, including its now-active `repair_attempts` behavior and compatibility
-  checks for prompt definitions, prepared execution, validation results,
-  capacity accounting, error adaptation, debug data, and cumulative token
-  usage.
-- Use PromptKit's bounded repair loop for eligible structural output failures.
-  A repair must resend the immutable original prompt followed by the latest
-  defective assistant response and one bounded user correction message. It
-  must not accumulate the history of every defective candidate.
-- Review every maintained LLM prompt's structural repair budget. Prefer a
-  small positive budget where a corrected structured response can be useful,
-  while retaining zero where a second call would be inappropriate or where
-  observational evidence does not justify it.
-- Keep PromptKit repair attempts distinct from Notarius stage retries.
-  PromptKit repairs a response that fails its deterministic `basic`, `json`, or
-  `json_schema` contract within one stage attempt; Notarius may later retry a
-  complete stage candidate after application validation. Document and test the
-  multiplicative maximum provider-call cost created by both configured
-  budgets, including PromptKit repair calls made by any LLM-backed validators.
-  Attribute generation count, token usage, latency, and failure provenance to
-  the producer, validator, PromptKit repair, and Notarius correction layers so
-  operators can explain the actual cost of a run.
-- Treat exhaustion of PromptKit structural repair as the absence of a usable
-  structured candidate. The default terminal policy is to fail the run after
-  the applicable Notarius stage-attempt budget is also exhausted. A future
-  configurable alternative may reject the affected stage or lane where the
-  pipeline can represent that outcome, but it must never accept undecodable or
-  structurally invalid output merely with a warning.
+This item has been promoted to the standalone
+[PromptKit v0.8.0 Upgrade](promptkit-v0.8.md) roadmap. That document owns the
+release-by-release compatibility review, adopted features, structured-repair
+policy, target integration boundary, acceptance criteria, and settled design
+decisions.
 
 ### 2. Feedback-Aware Stage Validation Retries
 
@@ -245,8 +222,7 @@ The implemented source-backed core and initial D&D registry adoption are
 described by [Module Internals](../internal/modules.md#semantic-reconciliation)
 and
 [D&D Module Internals](../internal/dnd.md#semantic-registry-reconciliation).
-The [Semantic Reconciliation Roadmap](semantic-reconciliation.md) retains the
-original feature scope; the sections below keep broader extensions deferred.
+The sections below keep broader extensions deferred.
 
 ### Large-Collection Semantic Reconciliation