Greptile Summary

This PR makes chat.history text truncation configurable via a new gateway.webchat.chatHistoryMaxChars config field and a per-request maxChars RPC parameter, wiring the feature through the TypeBox protocol schema, the Zod config validator, the TypeScript gateway handler, and both Swift client models. The implementation is clean and well-tested — the new tests cover config-driven truncation, per-request override precedence, and boundary validation for invalid maxChars values. A prepush-ci.sh mirror script and three extension test stabilisation fixes are included as supporting changes.

Key observations:

• The core precedence logic (rpcMaxChars → configMaxChars → default) is correct and consistently applied.
• The TypeBox schema (minimum: 1, maximum: 500_000) and Zod schema (positive().max(500_000)) are aligned.
• The default is raised from 12_000 to 64_000 (5×); existing deployments will see larger history payloads without a config change — confirm this is intentional and that all consumers can handle the new ceiling.
• The has_native_swift_changes fallback in prepush-ci.sh mixes committed-history and working-tree semantics; low practical impact but slightly surprising.

Confidence Score: 5/5

Safe to merge — no P0/P1 issues found; the feature is correctly implemented and well-validated.

All remaining findings are P2 (informational / style). The default-increase observation is worth awareness but is documented and intentional. Tests cover the three key scenarios (config override, RPC override, rejection of invalid values).

No files require special attention; the default value change in src/gateway/server-methods/chat.ts is worth a quick confirmation with the team.

This is a comment left during a code review.
Path: scripts/prepush-ci.sh
Line: 44-45

Comment:
**Fallback checks working-tree changes, not committed history**

When `origin/main` is reachable but no Swift changes appear in `origin/main...HEAD`, the function falls through to `git diff --name-only --relative` (line 45), which compares the *working tree* against HEAD — not against the remote. In a typical pre-push scenario all changes are committed, so this fallback will almost never match anything useful. If the intent is just to handle the "no remote tracking branch" case, the fallback could be scoped more explicitly (e.g. `git diff --name-only HEAD~1..HEAD`) to avoid the surprising mix of committed vs. uncommitted semantics.

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: src/gateway/server-methods/chat.ts
Line: 95

Comment:
**Default raised 5× — existing deployments will see larger history responses**

The previous hardcoded limit was `12_000`; the new default is `64_000`. Any existing deployment that relies on the old ceiling will now receive responses up to 5× larger without any config change. This is likely intentional (and documented in `schema.help.ts`), but worth confirming that any downstream consumers of `chat.history` — especially the macOS client — handle the larger payload gracefully without a memory or display regression.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "feat(gateway): make chat history max cha..." | Re-trigger Greptile}