Accepted-but-unlanded pi-mono borrow B1 (requestedModel? / responseId? provider-audit fields), currently held in a local git stash (stash@{1}) — not on any branch or remote.
What it is: +291 lines across 15 files threading requestedModel? and responseId? through ProviderResponse and the agent_completed event:
src/providers/{types,claude,codex,xai,fake,fake-script,invoke}.ts
src/state/{events,schemas}.ts
docs/references/provider-contract.md
- 5 test files
Status: main's docs/comparison/08-pi-mono/SYNTHESIS.md records B1 as "accepted with naming fix" with a locked spec — but only the spec landed; the implementation lives solely in this stash (verified absent from main by the 2026-05-29 cleanup audit: git grep responseId origin/main -- src/ returns nothing).
To land it later:
- The stash base (
feat/pi-mono-borrows @ 94fafd7) is NOT an ancestor of main, so a fresh rebase against the current types.ts / schemas.ts / invoke.ts surfaces is required.
Caveat: this code lives only in a local stash on the maintainer's machine and is fragile. Consider git stash branch <name> stash@{1} to a durable branch if it will not be landed soon.
Accepted-but-unlanded pi-mono borrow B1 (
requestedModel?/responseId?provider-audit fields), currently held in a local git stash (stash@{1}) — not on any branch or remote.What it is: +291 lines across 15 files threading
requestedModel?andresponseId?throughProviderResponseand theagent_completedevent:src/providers/{types,claude,codex,xai,fake,fake-script,invoke}.tssrc/state/{events,schemas}.tsdocs/references/provider-contract.mdStatus:
main'sdocs/comparison/08-pi-mono/SYNTHESIS.mdrecords B1 as "accepted with naming fix" with a locked spec — but only the spec landed; the implementation lives solely in this stash (verified absent from main by the 2026-05-29 cleanup audit:git grep responseId origin/main -- src/returns nothing).To land it later:
feat/pi-mono-borrows @ 94fafd7) is NOT an ancestor ofmain, so a fresh rebase against the currenttypes.ts/schemas.ts/invoke.tssurfaces is required.Caveat: this code lives only in a local stash on the maintainer's machine and is fragile. Consider
git stash branch <name> stash@{1}to a durable branch if it will not be landed soon.