Reviewer roadmap: open PR summary and merge queue

[YOMXXX]

This is a reviewer-facing summary of the current open PR backlog and a proposed roadmap to reduce review load without losing the context behind the parallel fix series.

Snapshot captured on 2026-05-25:

• Open PRs: 92
• Mergeable PRs: 68
• Conflicting PRs: 24
• Draft PRs: 11
• Non-draft mergeable third-party PRs: 58
• Review decisions recorded on open PRs: effectively none

The main bottleneck appears to be final maintainer triage/merge sequencing, not GitHub mergeability. Several PRs fix overlapping release-blocking problems, so reviewing them one-by-one without a roadmap is expensive and risks merging duplicate or conflicting fixes.

Reviewer Roadmap

Batch A — low-risk user-facing fixes to review first

These are small or narrow, mergeable, and address active breakage. They are good candidates for a first maintainer pass.

PR	Area	Why it matters	Reviewer focus
#2594	MCP launcher / Windows	Replaces sh -c MCP launcher with Node-based resolver. Helps Windows hosts where sh is absent or path handling breaks.	Confirm fallback order and child signal forwarding.
#2598	Windows hooks	Replaces fragile $SHELL -lc PATH probe with printenv-first hook prefix.	Treat as partial fix only; it does not close nested-pipe #2613 by itself.
#2592	Packaging	Adds missing transcript-watcher.cjs build target.	Check build output and package inclusion.
#2629	Provider env isolation	Strips Bedrock/Vertex/Mantle routing env vars from worker subprocess to avoid silent compression failures.	Confirm env snapshot/restore in tests and blocklist scope.
#2628	Marketplace metadata	Removes unsupported metadata.homepage field.	One-file schema cleanup.
#2630	Uninstall UX	Removes CLAUDE_CODE_DISABLE_AUTO_MEMORY on uninstall.	Confirm uninstall is idempotent and preserves unrelated settings.
#2635	server-beta startup	Initializes ModeManager and supports CLAUDE_MEM_MODES_DIR.	Confirm missing modes degrade with useful warning.
#2634	server-beta event linkage	Links tool_use events to sessions via contentSessionId.	Confirm lookup scope and idempotency behavior.

Batch B — packaging strategy decision

Several PRs address the same family: fresh installs/cache directories missing runtime dependencies, especially zod/v3.

Recommended policy:

1. Prefer fix(build): inline zod into worker / server-beta / context-generator bundles (closes #2437) #2610 as the root fix for the zod failure. Inlining pure-JS zod removes the runtime dependency from every install path.
2. Treat fix: auto-install plugin dependencies on first hook invocation #2644 as defense-in-depth only. It now handles spawnSync failures and guards on node_modules; remaining concern is that first-hook dependency install is still on the hook critical path.
3. Treat fix(build): populate plugin/node_modules during build (partial #2407) #2597 as useful for dev/marketplace-sync dependency population, not as the full fresh-install fix if fix(build): inline zod into worker / server-beta / context-generator bundles (closes #2437) #2610 lands.
4. Avoid merging multiple overlapping packaging fixes without explicitly documenting which layer is responsible for what.

Related issues: #2437, #2637, #2640, #2407, #2456.

Batch C — reliability fixes that need explicit owner decision

PR / issue	Recommendation
#2602	Good partial fix for oversized observer payload overflow. It helps #2468, but does not fully solve #2643's token/cost explosion. Review as a partial reliability improvement.
#2643	Needs a broader cost-control roadmap: diff/minimal payloads for Edit/Write, observer-session budget/reset, user-visible observer token accounting, and degraded-state reporting.
#2485	Parser recovery should distinguish empty idle output, non-empty invalid prose, and poisoned SDK session closure strings. Add preview diagnostics and reset threshold while preserving pending messages.
#2593	Likely worth landing for Windows Chroma uvx metacharacter failures, but coordinate with other Windows Chroma PRs to avoid duplicate fixes.
#2596	Bundle-size/better-auth externalization. Review only after dependency ownership is clear because it increases reliance on plugin/node_modules.
#2599	Windows PID reuse guard. Useful, but larger than Batch A; review after smaller Windows startup fixes land.

Needs split, rebase, or superseded decision

• Fix chroma-mcp orphan cleanup #2536: important Chroma orphan cleanup direction, but currently conflicting and too broad. Best path is a focused PR touching ChromaMcpManager plus targeted tests first.
• Older Windows hook/MCP launcher PRs that overlap with fix(mcp): replace sh launcher with cross-platform node -e (closes #2461) #2594, fix(hooks): replace fragile $SHELL -lc PATH probe with printenv-first pattern #2598, and Windows hooks: nested-pipe plugin-root lookup may still trigger 'printf: write error: Permission denied' after #2598 #2613 should be marked superseded or asked to rebase.
• Broad server-beta series PRs should be reviewed as an ordered stack, not as independent unrelated PRs.

Suggested Reviewer Assignments

• Release / packaging: fix(build): inline zod into worker / server-beta / context-generator bundles (closes #2437) #2610, fix: auto-install plugin dependencies on first hook invocation #2644, fix(build): populate plugin/node_modules during build (partial #2407) #2597, refactor(build): externalize better-auth from worker/server-beta bundles (closes #2584) #2596, fix(build): add transcript-watcher.cjs build target (closes #2450) #2592
• Windows runtime / hooks: fix(mcp): replace sh launcher with cross-platform node -e (closes #2461) #2594, fix(hooks): replace fragile $SHELL -lc PATH probe with printenv-first pattern #2598, Windows hooks: nested-pipe plugin-root lookup may still trigger 'printf: write error: Permission denied' after #2598 #2613, fix(windows): strip BOM from settings.json + exempt lifecycle subcommands from #2188 stdin guard #2636, fix(chroma): escape cmd.exe metacharacters in uvx args on Windows #2593
• Provider / env isolation: fix(worker): strip Bedrock/Vertex routing env from worker subprocess #2629 and follow-up retry/degraded health handling for Worker leaks CLAUDE_CODE_USE_BEDROCK + ANTHROPIC_DEFAULT_*_MODEL → 400 invalid model identifier on every compression #2620
• Observer reliability / cost: fix(observer): truncate oversized prompt fields + drop overflow from hard-stop (closes #2468) #2602, Silently burned 649M tokens on my account. Here's how I found out. #2643, v13.2.0: observer SDK responses dropped by parser as non-XML; observations table stays at 0 #2485
• Chroma lifecycle: chroma-mcp child processes leaked by worker daemon → concurrent writers crash chromadb Rust bindings #2638, Fix chroma-mcp orphan cleanup #2536, Windows Chroma duplicates
• server-beta: fix(server-beta): link tool_use events to their session via contentSessionId #2634, fix(server-beta): initialize ModeManager at startup + support CLAUDE_MEM_MODES_DIR #2635, and the mguttmann stack starting at fix: resolve 24 pre-existing TypeScript errors across 9 files #2539/feat(security): argon2id API key hashing with SHA-256 backward-compat #2542/feat(install): server-beta runtime setup, rollback, and multi-IDE injection #2544

Proposed Next Steps

1. Maintainer picks or rejects Batch A as a first low-risk merge set.
2. Maintainer chooses the packaging policy for zod/node_modules: fix(build): inline zod into worker / server-beta / context-generator bundles (closes #2437) #2610 as root fix, fix: auto-install plugin dependencies on first hook invocation #2644 as fallback, fix(build): populate plugin/node_modules during build (partial #2407) #2597 as build/dev support.
3. Reviewers mark superseded Windows/Chroma duplicate PRs to reduce noise.
4. Reliability owners split the remaining high-risk issues into focused follow-ups: cost controls, parser recovery, Chroma child lifecycle, and daemon version drift.
5. After Batch A/B, run a smoke pass covering:
   • Windows Git Bash hook startup
   • MCP search startup on Windows without sh
   • fresh plugin cache with no node_modules/zod
   • host Bedrock/Vertex env present while worker uses isolated provider config
   • server-beta generation startup with modes loaded

Related tracking issue: #2601.

[YOMXXX]

Execution update (2026-05-25)

I pushed the small reviewer-risk reducers called out in the latest review summaries:

• #2610 (fix/inline-zod-in-worker-bundle): added the missing post-build no-external-zod assertion for context-generator.cjs. Local npm run build passed; no generated bundle diffs.
• #2602 (fix/observer-prompt-truncation): handled the remaining defensive truncation edge case (tailChars === 0 / negative elision math) and rebuilt plugin/scripts/worker-service.cjs. Local npm run build passed. npm run typecheck still reports existing errors outside this PR scope.
• #2616 (feat/auto-redaction-v2): added the missing redaction-marker guidance to summary prompts, made the guidance explicit that the marker itself should not be copied into generated memory content, added a focused buildSummaryPrompt test, and rebuilt plugin/scripts/worker-service.cjs. Local npm run build and a tsx summary-prompt sanity check passed.

Current maintainer-facing status: the three PRs that still had concrete Greptile/reviewer gaps now have follow-up commits and PR comments documenting the verification. They remain mergeable from GitHub's mergeability signal.

[YOMXXX]

Follow-up status (2026-05-27): still no maintainer response after the execution update.

I posted a consolidated maintainer decision request in #2601 with a recommended first merge batch and a separate hold list:

• First merge batch: fix(build): inline zod into worker / server-beta / context-generator bundles (closes #2437) #2610, fix(observer): truncate oversized prompt fields + drop overflow from hard-stop (closes #2468) #2602, fix(mcp): replace sh launcher with cross-platform node -e (closes #2461) #2594, fix(build): add transcript-watcher.cjs build target (closes #2450) #2592, fix(supervisor): make Windows captureProcessStartToken actually return a token (closes #2578) #2599
• Then low-risk cleanup: chore(scripts): drop sync-to-marketplace.sh and harden sync-marketplace.cjs #2595, refactor(build): externalize better-auth from worker/server-beta bundles (closes #2584) #2596, chore(sqlite): unify worker DB init through MigrationRunner #2632, refactor: consolidate parseJsonArrayColumn into utils/json-utils #2633
• Hold for explicit decision: fix(chroma): escape cmd.exe metacharacters in uvx args on Windows #2593, fix(hooks): replace fragile $SHELL -lc PATH probe with printenv-first pattern #2598, fix(build): populate plugin/node_modules during build (partial #2407) #2597, feat(privacy): opt-in auto-redaction for common secret patterns #2616, feat: auto dedup-folding (S3) — opt-in fold of identical tool calls within a sliding window #2627

Link: #2601 (comment)