Honor exact model identity in target-pin routing (#178) #191
No reviewers
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
P1
P2
P3
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Creatidy/scarcity-router!191
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-178-exact-target-pin"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Scope
Refs #178. Narrow qualified target pins to exact provider/model/opaque variant, rather than all resource-bound identities. Preserve authorization/quality/compatibility gates, explicit constraint intersection, existing refusal vocabulary and unchanged gateway/admit_pinned_target behavior.
Evidence
Original synthetic assertion reproduced max -> medium substitution before the fix. Regression coverage includes unbound identities, calibration/registration drift, contradictory explicit constraints, capability/profile/protocol/offline refusal and unchanged admission. Pinned unsupported-tool fixture now passes the earlier continuation gate and asserts compatibility_unsupported/tool_calls/UNSUPPORTED on the pinned resource.
Reuse existing identity keys, narrowed catalog, actual selector/resource gates and typed fixtures. No new dependency, schema/config migration, credentials, endpoint or provider calls. Existing contract docs updated.
Current Validation
Base/merge-base:
4e1d5974f2HEAD:
f78cb9d24cSanitized exact-commit make check PASS: 2693 tests, 17 skips, 589.128s; basedpyright 0 diagnostics. Complete execution record binds HEAD before/after, env -i synthetic HOME/cache/temp/runtime/minimal PATH, make check and whitespace to exit code 0. Locked uv sync --only-dev and explicit basedpyright PASS. Independent focused original tests: 61 PASS. No live provider/harness or environment-dependent acceptance claimed.
Delivery
Same owner /loop invocation 2026-10-05T12:38:32Z. Ordinal1 COMMENT (infrastructure; old HEAD); ordinal2 REQUEST_CHANGES (test gap, remediated in
f78cb9d); ordinal3 COMMENT (missing exact-HEAD full-gate artifact, now prepared). Fresh whole-PR review pending. Owner expressly authorized and required preserving synchronization mergebf61c3e; no new synchronization or history rewrite by the agent. Integration only after valid exact APPROVE and canonical currentness.