API Coverage

Automated public export coverage for reference docs.

This page records the coverage policy that keeps handwritten reference pages aligned with public package exports.

Scope

The coverage check treats every package entry in package.json#exports as a public import path. It uses the TypeScript compiler to enumerate symbols exported from those entrypoints, then verifies that the mapped reference docs mention each import path and exported symbol.

Internal source-file exports are outside this check unless they are re-exported by a package entrypoint.

Current Coverage

PackagePublic entrypointsPublic exportsReference coverage
@anvia/core19250Core
@anvia/openai117OpenAI Provider
@anvia/gemini113Gemini Provider
@anvia/anthropic14Anthropic Provider
@anvia/mistral110Mistral Provider
@anvia/fastembed16FastEmbed
@anvia/transformers16Transformers
@anvia/chroma14Chroma
@anvia/pgvector16pgvector
@anvia/qdrant15Qdrant
@anvia/langfuse16Langfuse
@anvia/otel13OpenTelemetry
@anvia/studio161Studio

The check must report:

TOTAL_MISSING_ENTRYPOINTS=0 TOTAL_MISSING_EXPORTS=0

Re-run Check

Run this from the repository root:

pnpm docs:reference-check

pnpm docs:typecheck also runs the same check before MDX generation and TypeScript validation.

Documentation Standard

Each practical reference page should document the public surface with:

RequirementExpected content
Import sourcePackage or subpath imports, such as @anvia/core/memory
SignatureTypeScript class, function, interface, type, or constant shape
PurposeWhat the primitive owns or represents
Return behaviorResolved value, emitted events, side effects, or type-only behavior
Notable errorsValidation, provider, transport, persistence, or capability failures
ExampleMinimal code showing ordinary use when the primitive is runtime-facing
Related docsGuides or cookbook entries for workflow-oriented usage