Plan bounded output repair

docs/roadmap/future.md

@@ -38,28 +38,8 @@ consumers.
 
 ## Ideas
 
-### Public bounded output repair
-
-Promptkit should make its bounded output-repair capability available through
-the public engine. A consumer should be able to request a limited number of
-corrective generation attempts when JSON or JSON Schema output fails content
-validation, without having to reproduce Promptkit's generation, validation,
-capacity, and result-accounting orchestration.
-
-- Repair is validation recovery, not a general provider retry, failover, or
-  backoff policy. Transport failures, cancellation, and operational schema or
-  validation errors must retain their ordinary error behavior.
-- Repair must stop after the first valid result or the configured attempt
-  bound. Exhausting the bound should preserve the final invalid result and its
-  validation diagnostics rather than inventing success.
-- Initial generation and every repair attempt must use the same resolved
-  backend, effective execution settings and presence semantics, session,
-  credential boundary, structured-output contract, and backend-capacity
-  policy.
-- Results should report the number of repair attempts and cumulative usage for
-  every model call made by the run.
-- Ordinary and prepared execution should expose coherent behavior, including
-  cancellation, frozen prepared state, error identity, and capacity lifetime.
+No ideas are currently awaiting selection. Active feature work belongs in its
+focused roadmap rather than this catalog.
 
 ## Entry Format