[loopx-agent]

An opted-in Yardstick work turn can now use committed measurements of distinct candidates under the same declared Goal scope. A proxy reversal appears only when the proxy measured the same pair. The compact context preserves the authored reason and adds an advisory comparison cue. Detailed context retains source references, the exact comparison conditions, and the existing acceptance boundary.

This is the mainline proposal for #8250. Main now includes both the scoped Yardstick owner from #8202 and the paired-finding writer from #8207. The proposal contains one commit on that base.

Validation

• On the proposed head, 24 Python and seven Yardstick TypeScript cases passed. The control-plane typecheck, all five direct premerge checks, and 19 selected checks passed.
• The synthetic SQLite CLI journey records a measured proxy reversal, reads the same cue in ordinary work, carries out a different representation under the same acceptance, observes followthrough at periodic review, and confirms that disabling Yardstick removes the cue while retaining measurement readback.
• The implementation reuses the existing Yardstick and Explore owners and changes the agent's advisory context. Live model adoption and benchmark score effects require separate qualification.

[mergify]

This pull request has merge conflicts with main and cannot be merged
until they are resolved. Please rebase or merge the base branch, @loopx-agent.

Choose the remote for the base repository, not an out-of-date fork.
For a fork clone, first inspect git remote -v; upstream must point
to https://github.com/loopx-project/loopx.git. If it is absent, add it
with git remote add upstream https://github.com/loopx-project/loopx.git.
Then run:

git fetch upstream
git rebase upstream/main
# Resolve each conflict, git add the resolved files, then git rebase --continue.
git push --force-with-lease origin HEAD

For a same-repository clone whose origin points to
https://github.com/loopx-project/loopx.git, use origin instead of
upstream for fetch/rebase. If you prefer merging the base, use
git merge <base-remote>/main and push normally.

Keep the DCO Signed-off-by trailer on every commit when you rebase.
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

[mergify]

Hi @loopx-agent, the DCO Sign-off check did not pass. Please inspect
its details first: checkout, fetch, timeout or infrastructure errors
need their own recovery, not a rewrite of otherwise signed commits.

If the log confirms a missing Signed-off-by trailer, amend the
affected commit with git commit --amend -s; for multiple commits,
use an interactive rebase against the current base from the correct
base-repository remote and sign off each affected commit. Push the
rewritten PR branch with git push --force-with-lease origin HEAD.