[loopx-agent]

Quota and native Turn convey admitted work through separate layouts and repeated interpretation. This C1 candidate composes one complete input before capture and moves real consumers onto shared typed owners, preserving original requirements, evidence, recovery and settlement identity.

Author work remains unfinished; this proposal stays Draft. Signed-complete material staging, remaining caller/writer cutover, historical-reader retirement and actual single-session outcome/full-cost qualification are still open.

Current integration

Head 95deaab4118fe4e0c2d8a0d28aa3c982f6cdb14d integrates main ccf6aacc5f9f711293bda832a4523a6386ca1bb1, including the existing progressive-material planner, generic capture selectors, request settlement, recovery output guidance and exact Todo-record reuse. The original C1 branch and semantic owners are retained.

• Native scope/planning/encoding reuse one typed boundary. Sources needing no edits keep one RPC; material or reference edits apply to the original Python values before capture. Signed-complete inputs retain their full fallback pending migration.
• Generic selected-read continuations retain their selection digest. Replan reader commands bind the original capture before expanding diagnostic references, fixing valid generated reads being refused against that immutable source.
• Ordinary work missing Task/request identity again fails as a contract error. Unbound controller replans and valid request-scoped work retain their distinct handling.
• Host transport preparation is localized within the existing adapter. A misplaced execution-fence decorator introduced during that extraction was caught by real busy-request regressions and corrected before publication. The complete execution entry holds the original lane fence. Premerge now automatically runs the existing public-entry fence module for execution-boundary edits, including quick validation.
• Paired RFCs and their existing ledger distinguish delivered integration, failed intermediate revisions and remaining qualification. No budget or acceptance floor is raised.

Validation and limits

• 163 TypeScript cases pass, with control-plane typecheck and configured mypy. 232 focused Python cases pass: 216 executor, settlement/recovery, real File/SQLite request/replan and native-overhead cases; seven public-entry fence cases; nine premerge-selection cases. Four direct complete-Goal/missing-work regressions also pass.
• Frozen initial integration reproduces the extra native RPC and original-capture replan-hash failures. The unchanged public-entry fence oracle fails on frozen fc4763098 and passes after correction. Busy requests retain their identity, wait while occupied, and execute/settle once after restart.
• A wider 37-module run stopped at three failures with 1,364 passed / 53 environment skips. Its follow-through stopped at three failures with 843 passed. Those failures were traced to layout/helper migrations, missing-work classification and the introduced fence-placement error. They remain failed historical cohorts; the final focused passes do not relabel either whole cohort as passed. Native/model environment skips do not qualify installed behavior.
• Final source premerge passes seven direct and 19 selected checks, including the actual public-entry fence tests, with zero failures or manual holds. Public/private scans, DCO, bilingual checks, and scoped Ruff pass. Remote CI is not queried or awaited. This proposal is not merge readiness.

The qualification ledger retains the versioned evidence. The earlier wheel and original-quota byte/call tables at d410e297 are historical, including 25,862 > 13,000. They are not measurements of this head. No new wheel, installed App, actual model decisions, tokens/cache, billing, latency or accepted long-horizon outcomes are qualified here.

Continue in the existing C1/C2 work on signed-complete progressive material and discoverable same-capture recovery selectors, with sufficient/insufficient brief, unfinished first read, repeated compaction new-Turn behavior and nested-output truncation despite valid JSON. Selector availability or instruction wording alone does not prove adoption. The original-quota single-session comparison remains the primary acceptance gate; the two-session controller experiment remains separate.

[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]

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]

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]

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]

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