fix(routing): verify handoffs before model comparisons and retain normal-work feedback

[GrillerGeek]

Truncated reference reads can otherwise be graded as model failures and consume a whole study budget. Add bounded input manifests and host-visible chunk checks, require manifests before new live study claims, and stop later claims after invalid delivery. Invalid/unknown live inputs are excluded before grading and prevent comparison export; original outcomes, grades and usage remain intact.

4 of 4; depends on #49, #48 and #47. Targets routing/dynamic-setup so this diff contains the final step. Review/merge #47 → #48 → #49 → this PR; retarget to main when preceding branches merge. Final package version: 0.17.3.

• Check complete, omitted, truncated, duplicated and changed chunks; recover only missing material within cumulative read budgets without worker replay.
• Record normal-work outcomes, trustworthy observations and normalized usage without duplicate runs, extra graders, training or automatic policy updates. Correlate task/host/policy/worker; preserve unknown allowance and cost.
• Keep Codex/Claude Dynamic activation independent of benchmarks, while advanced qualified routing retains its existing improvement gate.
• Validation: 178 offline tests passed on Python 3.12 and 3.14; native validator (19 agents), portable/generated checks, both skill validations and whitespace passed. Isolated native Codex/Claude installs and pinned skills 1.5.25 independent installs passed source-removal checks; first three PRs have green CI.

No paid model/Jev calls, study reruns, personal activation or marketplace changes. Supplied visible-read records establish delivery only within their evidence scope; they cannot prove comprehension or authenticate fabricated source labels. Hosts without visibility report unknown.

Full verification: docs/reviews/2026-09-29-dynamic-routing-verification.md.

[coldtea-pr-lens]

◈ PR Lens

🟢 +2 new · 🟠 ~8 changed · 🔴 -0 removed · 2 flows · 24 files · commit 148c9af

Architecture

10 components touched across 3 lanes.

Play the interactive walkthrough

Inside the changed components — 2 views

Component view — Bounded input delivery and study guardrails

Chunking reference materials, host-visible verification, budgeted recovery, and study runner guards.

Component view — Local feedback summarization and usage correlation

Correlating test results, observed host settings, and token meters to detect model substitution locally.

Data flow

Verifying input delivery and recovering missing chunks · Recording local feedback and detecting substitution

Follow each request, response and payload

The other flows — 1 sequence

Recording local feedback and detecting substitution

View

• Architecture lens
• Data flow lens
• Expand every detail

Tip

Run npx skills add coldteadotai/pr-lens, then tell your coding agent: "Diagram the change you just made with PR Lens and attach it to the pull request."

🪧 More tips

• Run npx @coldtea/pr-lens-cli analyze --base origin/main on a branch, then npx @coldtea/pr-lens-cli render .pr-lens/graph.json. Same lenses, your own model key, before the pull request exists
• Untick Architecture lens or Data flow lens under View to hide a diagram, or tick Expand every detail to open every section. The comment redraws in a few seconds
• Click the link under each diagram to open it on a canvas you can zoom, pan and step through
• The diagrams are links. Click one to open it on the canvas, then press W or click play to walk through the change
• Open a diagram on the canvas, then press W or click play to walk through the change one step at a time
• The CLI's render reads .github/pr-lens.yml and applies your renames, exclusions and lane pins at draw time
• Set github.comment.collapsed: true in .github/pr-lens.yml to fold the comment behind one View architecture and data flow row. Drawing still runs as before
• Set github.draw: on-demand in .github/pr-lens.yml and PR Lens stops drawing pull requests on its own. Comment @pr-lens draw on a pull request when you want that one drawn
• Add .github/workflows/pr-lens.yml with coldteadotai/pr-lens/packages/action@v0 and your model provider's key as its api-key to run PR Lens from your own CI. Any /chat/completions endpoint works
• Push a commit and the drawing stays, with a note that it is out of date. Tick Redraw in the note to draw the new head
• Switch GitHub to dark mode and the diagrams follow. The moving dots are this pull request's data in motion

---

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.

❤️ Share

• X
• Bluesky
• Mastodon
• Reddit
• LinkedIn