# feat\(pi\): support repository review guides · PR \#23836 · pingdotgg/t3code [View on GitCafe](https://git.cafe/pingdotgg/t3code/pull/23836) Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code) Visibility: public State: open Source repository: Unavailable fork Source branch: t3code/pi-guide-stack-context Target branch: main Head commit: b422699b73c4fde2a7dfd03fbc781e50734da8ed [Discussion and reviews](https://git.cafe/pingdotgg/t3code/pull/23836) [Commits](https://git.cafe/pingdotgg/t3code/pull/23836/commits?format=markdown) [Files changed](https://git.cafe/pingdotgg/t3code/pull/23836/diffs?format=markdown) ## Description --- Pi currently rejects repository review guides. Prepare complete Git evidence on demand in the host, then let Pi investigate the checkout with native read, grep, find and ls. Evidence is pinned to verified commits and split into bounded text chunks with lossless offsets. Startup overrides inherited project trust, partial clones retain normal lazy fetching, and neighbor comparisons use their merge base to exclude unrelated main drift. Preparation failures identify the failed step and preserve their cause. Evidence over 64 MiB, or a neighbor without a merge base, fails preparation rather than producing a partial guide. Validation: `check:changed` passed 33 tests and 20 affected package typechecks. Native Pi 1.4 reconstructed 164,765 payload bytes exactly, blocked three project-trust execution probes, and closed its processes on cancellation. The diagnostic follow-up also exercised the actual Git driver's output-limit error and a filesystem failure. Native file reads keep normal server-user access; this adds no filesystem sandbox. The deterministic native fixture does not establish real-model guide quality. Windows and minimum-version execution were not tested; native find lacked fd in the offline fixture. Prepared for Wout by gpt-6.1-sol in Codex through T3 Code.