Why a deno subprocess spawned by discovery produced no usable output.

• permission-denied — the CLI was run without --allow-run=deno. Decoding and encoding still work; only discovery is unavailable.
• not-spawned — the process could not be started at all, e.g. no deno on PATH.
• minimum-dependency-age — the requested version is younger than the consuming project's minimumDependencyAge, so the graph refused to resolve. Nothing about the invocation was wrong.
• exited-non-zero — anything else the tool rejected: unknown package, network failure, syntax error in a local entrypoint.
• graph-incomplete — the tool succeeded, but the module graph it printed carries an error, so it was never walked. deno info exits 0 in this case, which would otherwise read as a graph that simply contains nothing.
• timed-out — the tool said nothing for TOOL_TIMEOUT and was killed. A stalled fetch inside deno doc has no deadline of its own, so without this the CLI waits forever with a blank screen.