What your healthcheck actually checks: four probe bugs in a self-hosted agent runtimeOne probe checks too hard, one too lightly, one in the wrong place, and one never receives the config you think you gave it.16 min read·soit-ai.hashnode.devSep 27
max_retries=2, one attempt: counting retries across three layers of an agent runtimeA reader's comment sent me counting. The answer was one — stacked out of three independent reasons, only one of which was on purpose.21 min read·soit-ai.hashnode.devSep 24
Your access token lifetime means two different things, depending on one database readWhy a server-side session row turns ACCESS_TOKEN_EXPIRE_MINUTES from "session length" into "revocation delay" — and the ten places our own docs have not caught up25 min read·soit-ai.hashnode.devSep 18
Three signed v1.0.0 images, one release: what attestation actually provesA registry-level walkthrough: OCI index, Sigstore bundles, a ten-minute certificate, and the manifest that ties a tag to a digest18 min read·soit-ai.hashnode.devSep 14
Five tables, four kinds of replay, and a status called in_doubtA source-level walkthrough of the run/step/tool-call ledger behind "replayable agent runs" — including the seven places it does not line up yet.18 min read·soit-ai.hashnode.devSep 10