chore: sync directive drafter integrations with latest releases

[rlippmann]

Summary

• sync the Python and TypeScript Directive Drafter integrations with the latest released dependency floors
• remove source_input= from automated fallback parsing in the Python fallback integrations
• add focused docs and tests covering the experimental structurally validated fallback path and compound-directive rejection behavior

Why

The released Directive Drafter and core behavior changed in ways these integrations needed to reflect. This updates the repo to consume the current released contract without reintroducing source-aware semantic acceptance in the automated fallback path.

Example metadata

• Enforcement point: host-side runtime enforcement in example integrations and starter apps
• Domain: repository maintenance / integration correctness
• Technology/runtime: Python, TypeScript, Open WebUI, LiteLLM, Next.js, Node
• Example type: repository maintenance
• Does this use directive drafter? should normally be no: yes, in the affected optional drafter integrations only
• Does this derive state from model output? must be no for primary examples: no; Context Compiler remains the authority layer and fallback output is only structurally validated before possible handoff

Checklist

• Repository scaffolding / governance change
• One primary enforcement point
• Explicit authoritative state
• No model-derived state mutation
• Adversarial stub or equivalent test
• Observable runtime behavior change
• Domain vocabulary is natural
• Framework is secondary to the enforcement point
• Docs updated
• Tests/smoke checks added where practical

Notes

• Python dependency floor updates: context-compiler>=0.8.3 retained and context-compiler-directive-drafter>=0.1.2 applied where the drafter-backed integrations require it.
• TypeScript dependency updates were limited to the two with_drafter starter apps that actually consume @rlippmann/context-compiler-directive-drafter, which now target ^0.1.2.
• Focused tests now lock in the released compound-directive behavior: local clarify response, no authoritative state mutation, and no downstream model call.