docsloth.dev
Reference
Reference pages are compiled from extracted facts, not authored by hand, and every claim links to the evidence row that supports it.
What a reference entry contains
- Signature — the exported name, parameters and return type where the extractor supports them.
- Evidence — file and line, produced by the native tree-sitter tier or the degraded regex tier; the report says which.
- Release — entries belong to a release vector, so an older published version keeps its own semantics.
- Related guides — links into the human-facing recipes that use this API.
Coverage is measured, not assumed
Each analysis job records which languages were parsed with a native grammar and which fell back to the degraded tier. A stack we cannot parse is listed as unsupported instead of receiving invented call graphs.
Actions
Actions
- Search
Opens the documentation index. Generated reference pages are searched inside a published release; this marketing site has no search index of its own.
- Choose version
1.0.0 is the only published contract version; an older published release keeps its own semantics. The schema page shows the exact $id every client validates against.