[loopx-agent]

A native benchmark wake already carries its saved quota decision. Previously the client used one model/tool exchange to locate the decision's reader and a second to obtain the first facts. The wake now offers a single command for the initial page. A caller who knows the fields can select them in that same exchange.

The existing lifecycle still chooses the full or delta presentation after the native session starts. The existing reader verifies the source and selected bytes and applies one output limit to the page and its navigation. Pagination, later field selection and recovery use the pinned reader; the original wake still carries a digest-bound recovery route if the result is unavailable. No new hook, notification, acknowledgement, checkpoint, guard or spend. Ordinary projection remains available.

With the native client and a local Responses fixture, cold launch and resume selected the same two Todos and recovered the same decisions. In a paired replay with #8100 and #8109, two wakes took 10 → 8 model requests, or 12 → 10 when reads yielded asynchronously. File and SQLite preflights preserved their original receipts. Two concurrent readers reconstructed the selected bytes after compaction without republishing or touching the journal; wrong scope and disabled transport were rejected. In the synchronous fixture, unique tool results fell from 8 to 6 while their total text stayed close (30,568 → 30,272 UTF-8 bytes). The primary measured benefit is avoiding two exchanges. These are local interaction counts, not hosted token savings, a production notification incident or solver score gains.

[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