Target stale tracker repair by the open-state join key

[vaibhav4046]

Live failure reproduced

Exact production SHA 14911dcc566a472a8d40dc3369e378f0c2406fae passed the release gate but Auto benchmark scored 6/8. Both REVIEW cases had all required facts but only a GitHub receipt; the independent Linear tracker receipt was missing.

Root cause

The first receipt contains both the completed incident identifier and the tracker identifier. The evidence-derived second-hop query sent both back to hybrid retrieval, allowing the incident identifier to dominate the provider-scoped Linear repair.

Fix

• detect stale/open-tracker questions generically
• extract record identifiers only from first-hop sentences that independently assert the tracker remains open
• prioritize that tracker-state identifier in the bounded second hop
• suppress unrelated record IDs from the same receipt for this repair only
• keep ordinary multi-hop identifier expansion unchanged

No fixture identifier or expected answer is hard-coded.

Validation

New regression tests reproduce the exact two-ID receipt shape seen in production. Full CI is required before merge.

[vercel]

Deployment failed for project queueproof with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/vaibhav4046s-projects?upgradeToPro=build-rate-limit