mathiasandClaude Opus 5
09bde6df8a
Closes #57. Consumes mcp-chassis v0.6.0 (mcp-chassis#4). Two halves of one six-day outage. The chassis fix alone would not have fixed this one. /HEALTHZ WAS A CONSTANT newHealthzHandler marshalled its body ONCE at startup and served those bytes for the process lifetime. On 2026-09-14 it reported jwt.status=degraded for six days after Authentik had recovered, because the answer was computed before Authentik was up and could never change. A health endpoint that cannot change its answer is not a health endpoint. It now evaluates readiness per request. That is also what drives recovery: the chassis resolves a pending issuer on demand, so every probe is a retry. /READYZ IS NEW, AND IT IS THE ACTUAL CONTROL Through all three occurrences the pod was 1/1 Running and readiness-green while 401ing every OAuth caller. k8s had no signal and kept routing to it. /readyz answers 503 while JWT auth is degraded, so the pod leaves the Service instead of serving guaranteed failures, and the kubelet's probe cadence becomes the retry loop — no background goroutine, no context to own. /healthz deliberately stays 200. The process is alive; a liveness probe must not restart it, because restarting does not make the IdP come back sooner. A server with no issuer configured is always ready. Making readiness depend on an issuer it was never given would pull every static-token-only MCP out of its Service — asserted, not assumed. THE RETRY-WITHOUT-THE-K8S-ISSUER FALLBACK IS GONE It existed because one unreachable issuer used to fail the whole constructor and take Authentik auth down with it. Since v0.6.0 each issuer resolves lazily and independently, so a down issuer degrades only itself. The warning it logged — "multi-issuer init failed; retrying without the k8s issuer" — was the first line of today's incident; it no longer has a reason to exist. A constructor error now means a config error, which exits non-zero rather than warning and continuing. TESTS healthz_live_test.go, written first and red (newReadyzHandler undefined, and newHealthzHandler's signature could not express a state that changes). The sharpest assertion is that readiness is evaluated TWICE for two requests — a handler that caches cannot pass it. The existing table test is ported, not weakened: same three cases, same expected statuses, only the mechanism by which state reaches the handler changed. Verified: task check EXIT=0 (lint, vet, race). The lint failure it surfaced was pre-existing and is fixed in the preceding commit. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
gitea-mcp
Streamable HTTP MCP service exposing Gitea repo operations to Claude apps.
See ~/dev/AI/infra/docs/superpowers/specs/2026-05-04-gitea-mcp-gitops-workflow-design.md.
Quickstart
task setup:hooks # installs .githooks/pre-push — runs task check before every push
task check # context sync + lint + test + vet
task build # produces bin/gitea-mcp
This repo uses Trunk-Based Development. Commit directly to main. The pre-push
hook enforces the quality gate locally; CI re-runs task check on every push.