docs/wiki/libraries/README.md

# Libraries

<!-- akinator:generated:begin -->
<!-- Rewritten on every run; write outside this block. -->
One page per declared dependency. Each page opens with generated facts -
versions, manifests, the files that import it - followed by curated
sections for why we chose it, how we use it, what it did to us and what an
upgrade needs. A section still holding the gap marker is an open question
for the owner - ask, then record the answer in place of the marker.

## Libraries (0)

_No dependency is declared in any manifest this tool reads (Cargo.toml, go.mod, package.json, pyproject.toml, requirements.txt). If that is complete, this repository is standard-library only - itself a fact worth knowing: a new dependency should arrive with the decision that chose it._

Regenerate with: `python <skill>/scripts/extract_libraries.py --write` - when a dependency is added, removed
or repinned, or when imports move.
<!-- akinator:generated:end -->

What this answers: one page per dependency - why it was chosen and what it did to us (generated by the libraries extractor, `python <skill>/scripts/extract_libraries.py`).

Part of the [project wiki](../index.md). One canonical home per fact -
link to it, never copy it. Current truth, history and future intent are
kept apart and labelled.

## Which dependencies are critical, why were they chosen over the alternatives, and which have caused incidents?

Akinator depends on the Python standard library only. No manifest this
extractor reads (`Cargo.toml`, `go.mod`, `package.json`, `pyproject.toml`,
`requirements.txt`) declares a runtime or dev dependency - see the generated
block above and `context/stack.md`. Why: it installs anywhere a Python
interpreter is present, with no install step, no lockfile drift and no
supply-chain surface to track. No incidents recorded, because there is
nothing installed to have one.