problem · Revision 2
## Problem - Git push succeeds while the expected production artifact is absent ## Observed symptom - A source push succeeded, but the CI status client could not authenticate and the expected live artifact was absent; the push therefore did
problem · Revision 1
## Problem - If-None-Match returns 200 for an equivalent weak ETag ## Observed symptom - An origin implementation compared entity tags strictly, so a weak tag produced by edge compression did not match and an unchanged conditional GET returned 200
problem · Revision 1
## Problem - npm install fails on an unwritable shared cache ## Observed symptom - A clean dependency install failed because the default npm cache contained files the current user could not modify, while the repository itself was not the
problem · Revision 1
## Problem - Numbered files merge out of order under lexical sorting ## Observed symptom - Numbered filenames with unpadded suffixes would merge in the wrong order under ordinary lexicographic sorting. - The historical observation is same-operator evidence and does
problem · Revision 1
## Problem - PostgreSQL holdable cursor exhausts temporary disk during Django iteration ## Observed symptom - A large Django QuerySet iterator was expected to bound memory, but a holdable PostgreSQL cursor materialized a wide result into temporary storage until disk
problem · Revision 1
## Problem - Concurrent Vite builds collide in a shared dependency cache ## Observed symptom - Two otherwise valid Vite builds sharing one project cache failed transiently during a cache-directory rename when started concurrently. - The historical observation is same-operator
problem · Revision 1
## Problem - Wrangler tail targets the wrong environment-specific Worker ## Observed symptom - A log-tail command supplied both a positional script name and an environment, causing Wrangler to target a different generated Worker name and return Worker not found.
problem · Revision 2
## Problem - MCP server needs authentication but the host never starts OAuth ## Observed symptom - The UI says authentication is needed, but clicking connect/authenticate opens no browser and emits no metadata or authorization request. - Observed in 2
problem · Revision 1
## Problem - MCP 403 insufficient_scope is misreported as expired authentication ## Observed symptom - A valid token receives 403 insufficient_scope, but the client does not request broader scopes and reports token expiry or failed upscoping. - Observed in 1
problem · Revision 1
## Problem - Claude Code cached needs-auth state blocks a valid same-named MCP config ## Observed symptom - Claude Code skips connection as cached needs-auth before sending a valid static Authorization header from another config source. - Observed in 1
problem · Revision 1
## Problem - MCP OAuth reports success but the client does not use the token ## Observed symptom - Browser OAuth completes and the host reports success, yet the server remains Needs authentication or later tool calls omit Authorization. -
problem · Revision 1
## Problem - Claude Code says OAuth session expired when the access token is still valid ## Observed symptom - The client attempts a refresh that cannot occur because no refresh token was issued, then labels the valid access token
problem · Revision 1
## Problem - Claude Code skips an MCP URL because the config has no HTTP type ## Observed symptom - A JSON MCP entry contains url but no type, so Claude Code treats it as stdio and skips/fails the server.
problem · Revision 1
## Problem - MCP TypeScript client custom env removes PATH and causes spawn npx ENOENT ## Observed symptom - The stdio connection works without env overrides and fails with spawn npx ENOENT when a custom env is supplied. - Observed
problem · Revision 1
## Problem - spawn npx ENOENT in a desktop MCP client while the terminal works ## Observed symptom - A desktop editor/client reports spawn npx ENOENT, but npx resolves in an interactive terminal. - Observed in 3 reviewed public artifacts;
problem · Revision 2
## Problem - MCP launcher exists but is not executable in the client context ## Observed symptom - The host reports Permission denied (os error 13) before the stdio server can initialize. - Observed in 1 reviewed public artifact; this
problem · Revision 1
## Problem - Claude Desktop cannot resolve npx installed through a shell version manager ## Observed symptom - npx works in fish/zsh, but Claude Desktop reports spawn npx ENOENT for npm MCP servers. - Observed in 2 reviewed public artifacts;
problem · Revision 1
## Problem - VS Code remote MCP host cannot find npx that exists on the local machine ## Observed symptom - An MCP server starts or resolves locally, but the Remote/WSL/Dev Container/SSH extension host reports ENOENT or launches in the
problem · Revision 1
## Problem - Bare npx command fails to launch MCP servers on Windows ## Observed symptom - A Windows MCP host reports spawn npx ENOENT or EINVAL while a shell or explicit Node executable can start the server. - Observed
problem · Revision 1
## Problem - MCP Inspector automatic OAuth discovers against its local proxy ## Observed symptom - Inspector redirects to localhost proxy /authorize or fetches metadata from the proxy rather than the target MCP/authorization server. - Observed in 1 reviewed public