Investigate or fix fold proxy-path performance — run the added-latency gate, profile with the bench-profiler agent, and apply the move-to-snapshot-build fix pattern. Use when make bench fails, when a change touches the hot path, or when the user asks about gateway latency or allocations.
Run fold's full local merge gate in the right order and interpret failures — make check, plus the conditional gates the diff warrants (bench, conformance, helm-check, vuln, console-check, image build). Use before declaring work done, before commits, or when the user asks "is this ready" / "run the checks".
Checklist for adding state or config to fold that must survive hot reload — snapshot placement, Reload semantics, discovery merge, schema lockstep, and the reload/churn test matrix. Use when adding a config field, per-upstream setting, or any state the gateway reads per-request.
Groom fold's gap list and roadmap — README "Not implemented", docs/roadmap.md's three horizons, non-goals, deprecations on the clock, and the drift canaries that fail when a gap closes. Use when closing or widening a gap, when deciding whether something is a non-goal, or when a canary test fires.
Land a verified change in fold — branch, commit, PR title and body in the house register, the template checklist answered rather than ticked, then hand off to CI watching. Use when a change is ready to become a PR, when the user says ship it / open a PR / land this, or when work needs a branch before it grows further.
Compare a new MCP protocol revision against what fold implements and produce the gap list — what fold must change, what it may decline, and what becomes a deliberate documented gap. Use when a new revision ships, when the conformance drift workflow flags upstream movement, or when bumping the Go SDK across a protocol…
Work on fold-stdio and internal/stdiobridge — the shim that exposes a stdio MCP server over streamable HTTP so the gateway can federate servers with no network endpoint. Use when changing cmd/fold-stdio, internal/stdiobridge, the stdio compose profile, or docs/stdio.md.
Bring fold's docs in line with the working diff — map changed code to the README sections, docs/ guides, schema, and example config that track it, then fix the drift via the docs-sync agent. Use when the user asks to update docs, when the Stop hook flags code changes without doc changes, or before committing a…
Watch fold's CI after a push or tag and triage failures back to local make targets. Use immediately after any git push, when the user asks about CI status, or when a run needs diagnosing.