Diagnoses fold proxy-path latency and allocation regressions — runs the added-latency gate, profiles the hot path, and pinpoints which change put work on the per-request path. Use when make bench fails, before merging proxy-path changes, or when the user asks about gateway performance.
Reviews fold's deployment surface — the Helm chart's rendered output, Kubernetes security posture, the four Dockerfiles, and the compose stack — for what only shows up in the manifest rather than in the templates. Use after changes under deploy/, before a chart release, or when auditing how fold actually runs in a…
Audits fold's documentation surface after a feature or behavior change — README sections, docs/ guides, config schema lockstep, and the "Not implemented" gap list. Use after implementation is done, before commit.
Diagnoses an intermittent or race-detector test failure in fold — reproduces it reliably, localizes the shared state or timing assumption behind it, and names the real fix. Use when a test fails in CI and passes locally, when go test -race reports a data race, or when a test is suspected of being timing-dependent.
Reviews fold changes against the gateway's architectural invariants — pipeline order, snapshot-based reload state, audit as the single exit door, the invisibility rule, the minted error-code registry, and proxy-path allocation discipline. Use proactively after any non-trivial change to gateway/, auth/, policy/, or…
Writes and extends fold's integration tests using real MCP SDK peers behind the gateway. Use when a change needs test coverage — new gateway behavior, reload/discovery paths, policy or auth changes, or a repro for a reported bug.
Audits fold against the normative MCP specification for the pinned revision — method shapes, required fields and headers, error-code allocation, caching and intermediary rules, and deprecations on the clock. Use when a change touches wire behavior, when a new protocol revision ships, or before bumping the conformance…
Verifies a published fold release end to end from the outside — archives, checksums and their cosign signature, SBOMs, the four ghcr images, the OCI chart, and every sigstore attestation. Use after a tag's release workflow goes green, before announcing a release, or when someone asks whether a published artifact is…
Security review of fold changes against the documented threat model — inbound auth chain, deny-by-default policy, credential confinement, tenant isolation, and the trust boundaries in docs/security-model.md. Use for changes to auth/, policy/, host validation, EMA, discovery, or credential handling, and for periodic…
Run, debug, or bump the pinned MCP conformance suite for fold. Use when conformance fails locally or in CI, when the scheduled drift workflow flags upstream movement, or when deliberately bumping CONFORMANCECOMMIT / CONFORMANCEPKG.
Review, bump, or debug the vendored fold-console assets in gateway/console — the weekly bump PR, the console-check CI gate, and the manifest allowlist. Use when the console-sync workflow is red, when a bump PR needs review, or when deliberately moving CONSOLECOMMIT.
Triage a govulncheck failure, review a dependabot PR, or bump a dependency in fold — including the case where CI goes red with no commit behind it. Use when make vuln fails, when CI's vuln job is red, when a dependabot PR needs review, or when bumping the MCP SDK or the Go toolchain.
Work on fold-discovery and internal/kubediscovery — the controller that turns labeled Kubernetes Services into fold's discovery document, and the trust boundary its allowlist flags defend. Use when changing cmd/fold-discovery, internal/kubediscovery, gateway/discovery.go, or docs/discovery-controller.md.
Run fold locally and talk to it as a real MCP client — the dev stack, the repo's .mcp.json, and what to look at once it is up. Use to see a change from a client's side, to reproduce a client-reported bug, or when a test is green and the behavior still looks wrong.
Cut a fold release — verify gates, write the changelog and bump the Helm chart's appVersion, then with explicit per-step approval commit/push, watch CI, tag to trigger goreleaser, verify the published artifacts via the release-verifier agent, and refresh the conformance receipt. Use when the user asks to release…
Change fold's Helm chart safely — the three ci values shapes make helm-check renders against, the probe Host-header trap, Chart.yaml's two version lines, and the docs that track values. Use when editing anything under deploy/helm/, adding a value, or when make helm-check fails.
Drive the official MCP Inspector CLI against a locally running fold to see what a real client sees — namespacing, list merging, policy filtering, auth failures, ui:// resources. Use to reproduce a client-reported bug, to diff gateway behavior against an upstream directly, or to check a change by hand before writing…
Look up the normative MCP specification text for a method, field, header, or error code before implementing or changing it in fold. Use when a change touches wire behavior, when a reviewer asks "does the spec actually say that", or when answering a protocol question — never answer MCP protocol questions from memory.
Add, rename, or retire a fold metric, span attribute, or audit event field — the bidirectional lockstep against the packaged dashboard and both alert files, the v1 freeze on names and label sets, and the docs that track them. Use when touching gateway/metrics.go, otel.go, audit/, the Grafana dashboard, or either alert…