Repository navigation
feat: clarify routing attribution and add host preflight - #40
Conversation
◈ PR Lens
Architecture 11 components touched across 4 lanes. Play the interactive walkthrough Inside the changed components — 3 viewsComponent view — Evidence inspection and preflight Read-only capture inspection, preflight diagnosis, and drift evaluation modules. Component view — Schema v3 model routing and qualification Schema v3 model routing with explicit evidence level checks and objective binding. Component view — Plugin and packaging validation CI validation, packaging checks for schema v3, and isolated installation testing. Data flow
Follow each request, response and payload The other flows — 1 sequence
View
Tip Add 🪧 More tips
Thanks for using PR Lens! It's built by Coldtea, free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
Summary
Clarify what Guildhall can verify before users pay for routing studies. Add a bundled read-only preflight and explicit task-owned Claude/Codex capture importers. Routing schema v3 separates configuration evidence from observed model/effort, binds qualification to objective, and supports an explicitly selected configuration lane while preserving the stronger setup default.
Closes #36; addresses #37 finding4. Stacked on #39. All manifests advance to 0.12.0.
The inspected Codex runtime exposes configuration, not executed identity. A complete owned app-server capture can support the configuration lane; the desktop collaboration result alone cannot. Documentation explains that limitation and never silently substitutes CLI workers. Native-Claude concrete model observations remain distinct from effort and provider attestation.
Validation
104 tests passed, covering missing/mixed attribution, wrong worker/session, interruption/replay, reported substitution, alias drift, explicit evidence levels and objective binding. Native/portable validators and ten isolated installations passed, including installed synthetic capture import after source removal. Local version-specific Codex schemas were inspected without model calls.
No live host/profile qualification or routing activation is claimed. See the decision record and installed host-evidence guide for scope and migration.