Forward sessions through PromptKit requests

docs/roadmap/future.md

@@ -91,31 +91,6 @@ safety checks, and deterministic application of accepted changes.
 - Add media-type validators when non-JSON artifact representations are
   introduced.
 
-## LLM Runtime Evolution
-
-### Native Session Propagation
-
-- Once upstream PromptKit exposes a direct request-level session identifier,
-  propagate the existing `StructuredCompletionRequest.SessionID` through the
-  PromptKit adapter's native session field.
-- Preserve the current `--session-id` invocation contract and its run-wide
-  propagation to every prompt-facing module and validator. Do not introduce a
-  second session configuration surface.
-- Retain session identity in checkpoint provenance so runs with different
-  sessions cannot reuse one another's LLM-derived checkpoints.
-- Define the upstream compatibility and prompt-variable transition explicitly:
-  native provider session behavior must not silently remove a `session_id`
-  prompt variable while maintained prompts still consume it.
-- Add adapter and assembled-run coverage for exact forwarding, trimming,
-  concurrent-run isolation, and unsupported-provider behavior once the
-  upstream contract is available.
-
-This work is blocked because PromptKit v0.1.0 does not expose the required
-direct request-level session field. Notarius already carries a run-scoped
-session ID through its CLI, pipeline requests, checkpoint identity, and a
-`session_id` prompt variable; that prompt-variable propagation is not native
-provider session support.
-
 ## Further Reference Evolution
 
 - Make prior-run artifacts easier to bind as references without changing the