Programmatic use
Every report is a decoded Schema value, not a loose object, so a failure is structured data you can act on rather than a string you have to parse. loadShowca...
| Import | What you get |
|---|---|
foldcase | the Showcase type; runShowcase, runShowcases, suiteOf, suiteExitCode, formatSuite; the ShowcaseReport / SuiteReport Schemas; SerializedError and serializeError |
foldcase/cli | discoverShowcaseFiles, loadShowcasesFromFiles, runCatalog, runSuiteFromFiles, docsFromFiles; ShowcaseModuleError and loadFailureReason; the LoadedShowcase / CatalogLoad types |
foldcase/mcp | FoldcaseMcpServer, the launchable stdio server Layer, and makeFoldcaseMcpServer over your own catalog Layer |
foldcase/mcp/catalog | the FoldcaseCatalog service (.layer, .layerFromShowcases), makeCatalog, loadCatalogFromDir, and the listing / load-report / error Schemas |
foldcase/mcp/tools | FoldcaseToolkit, FoldcaseHandlers, makeHandlers |
foldcase/reports | the --json documents as Schemas — TestDocument, DocsDocument, InitDocument — plus CoverageReport, StaleDoc, ComponentGap and the report Schemas they carry, so a consumer decodes a document with the Schema that produced it |
Every report is a decoded Schema value, not a loose object, so a failure is structured
data you can act on rather than a string you have to parse. loadShowcasesFromFiles
returns { loaded, showcases, failures } and never fails — loaded pairs each Showcase
with its file, showcases drops the file for surfaces that only run records — so you
decide what an unloadable file means for your surface.
Last updated Aug 4, 2026