test: add true Open WebUI runtime loading and registration validation

[rlippmann]

Proposed enforcement point

prompt construction / host gateway behavior

Domain

Open WebUI pipe runtime validation

Runtime or framework

Open WebUI

Why existing examples do not cover it

The repository has strong import-level and fixture-style tests for the Open WebUI pipe integrations, and the README now includes better manual runtime verification guidance. However, there is still no automated validation that exercises true Open WebUI runtime loading/registration behavior.

This gap includes:

• loading the pipe into a real Open WebUI runtime
• confirming registration/import behavior in the actual runtime environment
• verifying the basic pipe path at the runtime boundary
• verifying the directive-drafter pipe path at the runtime boundary
• confirming local-only state updates vs forwarded backend requests in the real runtime

This is the main remaining runtime-validation gap after the LiteLLM Proxy runtime smoke coverage landed.

Where does this belong?

context-compiler-example-integrations

[rlippmann]

PR #56 added and validated the current non-Drafter OpenWebUI integration against a real OpenWebUI v0.9.2 runtime with Ollama.

Verified manually:

• function registration/update through the OpenWebUI Functions API
• context-compiler 0.8.3 installation from function frontmatter
• local directive updates with no downstream LLM call
• persisted authoritative state across turns
• state injection into a downstream Ollama request
• local clarification blocking
• pending clarification resolution with no

This materially reduces the runtime-validation gap for the basic pipe.

Remaining scope:

• automate the real OpenWebUI loading/registration path
• validate the Directive Drafter pipe in the real runtime
• keep cross-process/multi-worker behavior tracked separately in test: add cross-process or multi-worker runtime validation for example integrations #38