Prepare the v0.5.0 release

docs/roadmap/future.md

@@ -10,8 +10,9 @@ not as committed release dates.
 PromptKit now owns structural output repair within one completion. Notarius
 owns stage candidates, validator chains, semantic rejection policy, bounded
 feedback-aware stage retries, validation provenance, and reusable-state
-eligibility. The remaining near-term work applies those completed foundations
-to domain review and operator-facing diagnostics.
+eligibility, and the separation of actionable process warnings from quality
+diagnostics. The remaining near-term work applies those completed foundations
+to domain review and empirical evaluation.
 
 ### D&D Combat Scene Semantic Validation
 
@@ -55,33 +56,6 @@ to domain review and operator-facing diagnostics.
   the chunker or otherwise changes stage ownership or the durable chunk-plan
   contract.
 
-### Warning Signal And Presentation Reform
-
-- Audit every warning producer and representative successful runs. Ordinary
-  success producing dozens of warnings is a failed operator experience: the
-  volume obscures actionable problems and trains operators to ignore the
-  warning channel.
-- Define a small warning taxonomy that distinguishes actionable degradation,
-  incomplete validation, lossy fallback, and data-quality risk from routine
-  normalization observations or informational diagnostics. Preserve detailed
-  traceability in debug or manifest data without promoting every observation
-  to a top-level CLI warning.
-- Consider stable deduplication and aggregation by scope and reason code,
-  bounded samples plus omitted counts, and a concise CLI summary with a path to
-  detailed diagnostics. Do not suppress genuine validator execution failures
-  merely to reduce the count.
-- Decide which warnings affect process status, rejection summaries, durable run
-  receipts, or only debug output. Ensure warning ordering and aggregation are
-  deterministic across concurrent execution.
-- Establish a representative warning-volume acceptance target and human review
-  workflow before changing individual producers piecemeal. The intended result
-  is not zero warnings; it is a small set in which every surfaced warning merits
-  operator attention.
-- This work does not require an ADR unless it changes validation acceptance,
-  failure, or durable contract semantics. CLI presentation and diagnostic
-  taxonomy otherwise belong in a feature roadmap followed by updates to their
-  canonical configuration, operations, integration, and internal documents.
-
 ## Near-Term D&D Pipeline
 
 ### Evaluate Spell Extraction And Normalization