@savvy-web/mcp 1.3.4 → 1.4.0

package/public/content/packages/tsdown-plugins/api.md

@@ -1,165 +0,0 @@
----
-id: packages/tsdown-plugins/api
-title: "@savvy-web/tsdown-plugins — API reference"
-summary: "@savvy-web/tsdown-plugins API reference: 138 documented symbols."
-tier: packages
-source: generated
-tags: [tsdown-plugins, api]
-priority: 0.4
-related: []
----
-
-# @savvy-web/tsdown-plugins — API reference
-
-## class
-
-- [`BuildCollector`](silk://packages/tsdown-plugins/api/class/buildcollector) — Stateful build-event accumulator. The write surface is synchronous so it can be called directly from tsdown's customLogger and API Extractor's messageCallback (both invoked synchronously). `snapshot` builds the immutable BuildReport the Effect render pipeline consumes.
-- [`BuildCollectorTag`](silk://packages/tsdown-plugins/api/class/buildcollectortag)
-- [`BuildReport`](silk://packages/tsdown-plugins/api/class/buildreport)
-- [`ConfigValidationError`](silk://packages/tsdown-plugins/api/class/configvalidationerror) — A savvy.build.ts or publishConfig.targets config is structurally invalid; raised before any build work.
-- [`ConfigValidator`](silk://packages/tsdown-plugins/api/class/configvalidator) — Fast-fail config validator; runs first in the bundler over the resolved config.
-- [`DiagnosticEntry`](silk://packages/tsdown-plugins/api/class/diagnosticentry) — A captured warning or error, from tsdown's logger, rolldown's onLog, or API Extractor.
-- [`EmittedFile`](silk://packages/tsdown-plugins/api/class/emittedfile) — One emitted output file with its in-memory byte size (gzip only when --verbose).
-- [`EnvironmentDetector`](silk://packages/tsdown-plugins/api/class/environmentdetector)
-- [`ExecutorResolver`](silk://packages/tsdown-plugins/api/class/executorresolver)
-- [`FormatSelector`](silk://packages/tsdown-plugins/api/class/formatselector)
-- [`MetaGenerationError`](silk://packages/tsdown-plugins/api/class/metagenerationerror) — API Extractor meta generation failed for an entry.
-- [`OutputRenderer`](silk://packages/tsdown-plugins/api/class/outputrenderer)
-- [`PassReport`](silk://packages/tsdown-plugins/api/class/passreport) — One build pass within a target group (js / dts / loose / exe / meta).
-- [`ReportTimings`](silk://packages/tsdown-plugins/api/class/reporttimings)
-- [`TargetGroupReport`](silk://packages/tsdown-plugins/api/class/targetgroupreport)
-- [`TsconfigResolver`](silk://packages/tsdown-plugins/api/class/tsconfigresolver) — Resolves a TypeScript `ParsedCommandLine` to a portable, JSON-serializable tsconfig (compilerOptions-only) for virtual TypeScript environments.
-
-## function
-
-- [`applySubdirMetaEntries`](silk://packages/tsdown-plugins/api/function/applysubdirmetaentries) — For each `outSubdir` override, point its meta entry at the isolated sub-package barrel.
-- [`buildEmittedManifest`](silk://packages/tsdown-plugins/api/function/buildemittedmanifest) — Compute the final manifest bytes for a TargetGroup (catalog resolution + standard transforms).
-- [`buildMetricsPlugin`](silk://packages/tsdown-plugins/api/function/buildmetricsplugin) — Rolldown plugin that records emitted-file metrics into the BuildCollector via writeBundle (which fires for the JS pass AND the emitDtsOnly dts pass — verified against tsdown 0.22.3), plus a defensive onLog for rolldown-level diagnostics that bypass tsdown's logger. Append it to each build pass's `plugins` array. `bytes` is taken from the in-memory chunk/asset content (no fs); `gzip` is computed only when `verbose`.
-- [`buildResolvedTsconfig`](silk://packages/tsdown-plugins/api/function/buildresolvedtsconfig) — Build the portable absolute-path tsconfig object (ported from rslib writeBundleTempConfig).
-- [`buildTargetGroups`](silk://packages/tsdown-plugins/api/function/buildtargetgroups) — Run tsdown.build() per TargetGroup. Composable so the escape hatch gets multi-group too. Each group runs TWO passes to the SAME outDir: 1. JS pass — per-module JS (`unbundle: true`, `dts: false`), with the `emitManifest` plugin and the `public/` copy. Default `clean: true` gives it a fresh outDir. 2. dts pass — bundled declarations only (`unbundle: false`, `dts: { emitDtsOnly: true }`, `clean: false`). No manifest plugin, no copy, no sourcemaps. `clean: false` is load-bearing: it must NOT wipe the JS the first pass just wrote. Why two passes: tsdown's `unbundle` maps to rolldown `output.preserveModules` for the whole build (JS and the dts plugin share it), so a single pass cannot give per-module JS + bundled dts. Per-module dts breaks type portability (TS2883); bundling the JS re-bundles workspace consumers. The split keeps per-module JS AND rolled-up, self-contained declarations.
-- [`cjsDefaultInterop`](silk://packages/tsdown-plugins/api/function/cjsdefaultinterop) — Rolldown plugin: append the CJS default-interop footer to ENTRY chunks of the `cjs` format that export a default alongside named exports. Gated tightly so it never touches the wrong chunk: - format must be `cjs` (ESM is untouched; `import().default` on ESM is already correct); - the chunk must be an ENTRY chunk — never a SHARED chunk. Shared chunks are required by entry chunks via their named bindings (e.g. `require_changesets.changesets_exports.X`); reassigning a shared chunk's `module.exports` to its own default would break those reads (many bundled vendor chunks carry an `exports.default`); - the chunk must export a `default` AND at least one named export. A default-only chunk already gets `module.exports = <default>` from rolldown, and a named-only chunk has no default to promote. The emitted footer is also self-guarded (`module.exports.default !== void 0`), so it is a runtime no-op whenever the static gate is ever too generous.
-- [`computeExeFileName`](silk://packages/tsdown-plugins/api/function/computeexefilename) — The exact filename `@tsdown/exe` emits for a SEA target, mirroring tsdown's `resolveOutputFileName`: base fileName + `-<platform>-<arch>` + `.exe` on win. Single source of truth so the manifest value never drifts from the on-disk file.
-- [`createTimer`](silk://packages/tsdown-plugins/api/function/createtimer) — Create a wall-clock timer. (Date.now is fine in runtime build code.)
-- [`createTsdownLogger`](silk://packages/tsdown-plugins/api/function/createtsdownlogger) — A tsdown `customLogger` that routes warnings/errors into the BuildCollector instead of the console. Paired with `logLevel: "silent"` in the same build config: silent suppresses tsdown's own console output while this logger still receives every message (verified against tsdown 0.22.3). info/success are dropped — file metrics come from the writeBundle plugin and timing from our timer.
-- [`defaultManifestTransform`](silk://packages/tsdown-plugins/api/function/defaultmanifesttransform) — The default `transform` applied to every package's manifest when its `savvy.build.ts` does not provide one of its own. Strips the build/dev-only fields in `NON_PUBLISHED_FIELDS` from the emitted package.json. This is the pattern nearly every package repeated by hand (inherited from rslib-builder); `defineBuild` now applies it automatically so a package needs a `transform` only when it has genuinely custom manifest work to do (e.g. silk promoting workspace deps to peerDependencies). A custom transform REPLACES this default — re-export it and call it from a custom transform to keep the stripping. `targetGroup` is accepted (so this is assignable wherever the full transform signature is expected) but unused; the strip is identical for every group. Pure: the supplied `pkg` is NOT mutated — a shallow copy with the fields removed is returned, so external callers invoking this from a custom transform keep their input intact.
-- [`deriveExportPaths`](silk://packages/tsdown-plugins/api/function/deriveexportpaths) — Map entry names to export paths using the package exports map. index maps to ".".
-- [`deriveTargetGroupOptions`](silk://packages/tsdown-plugins/api/function/derivetargetgroupoptions) — Derive the JS-pass tsdown options for one TargetGroup (per-module JS, no dts).
-- [`emitManifest`](silk://packages/tsdown-plugins/api/function/emitmanifest) — Rolldown plugin: emit the transformed package.json + LICENSE/README into the output pkg/ root.
-- [`extractEntries`](silk://packages/tsdown-plugins/api/function/extractentries)
-- [`flattenIssues`](silk://packages/tsdown-plugins/api/function/flattenissues) — Flatten a build snapshot into the aggregated, de-duplicated issues artifact. Pure.
-- [`formatTime`](silk://packages/tsdown-plugins/api/function/formattime)
-- [`generateMeta`](silk://packages/tsdown-plugins/api/function/generatemeta) — Generate the api-model meta bundle from already-emitted .d.ts. Writes tsdoc.json (idempotent), runs the extractor per entry, merges if needed, and writes the "virtual TS env" trio to outMetaDir (`<unscoped>.api.json` + the final `package.json` + a portable `tsconfig.json`), copying that trio into each localPaths dir. The api-extractor `tsdoc-metadata.json` is a published-package artifact and is written into `dtsDir` (the built pkg/), not the meta bundle.
-- [`isTargetObject`](silk://packages/tsdown-plugins/api/function/istargetobject) — True when a target value is the object form (carries registry/name/from).
-- [`nodeBuiltinDefaultInterop`](silk://packages/tsdown-plugins/api/function/nodebuiltindefaultinterop) — Rewrite a default import / default re-export of a Node built-in into the equivalent NAMESPACE form, so rolldown's CJS codegen produces correct interop. Why this exists — a rolldown 1.1.0 codegen defect (verified against the latest published rolldown 1.1.0 / tsdown 0.22.2, with no newer release to upgrade to): For a default import of an EXTERNAL Node builtin, rolldown emits a bare `require("node:x")` WITHOUT its `__toESM` interop wrapper, yet still accesses `.default` — which is `undefined` on a builtin's CJS export object, so the call throws `Cannot read properties of undefined (reading 'cwd')` at runtime. NAMED imports are unaffected (`(0, node_process.cwd)()` reads a real property), and a NAMESPACE import is handled correctly: rolldown wraps it as `node_process = __toESM(require("node:process"), 1)`, which synthesizes `.default` and copies every own property, so member access works. This transform converts the broken default form into the working namespace form BEFORE codegen, so it is immune to minification and applies identically to per-module and bundled output. rolldown exposes no Rollup-style `output.interop` knob to fix this at the output layer, which is why the correction happens here on the source. Rewrites (the two static forms that occur in practice, anchored to statement start): The namespace binding NAME carries the builtin's named exports (`NAME.cwd`, `NAME.join`, ...), which is exactly how a default import of a builtin is consumed in practice. ESM output is unaffected at runtime (a namespace import of a builtin resolves to the same members), so the plugin is safe to attach to dual builds.
-- [`normalizeBinPaths`](silk://packages/tsdown-plugins/api/function/normalizebinpaths) — FINAL guard: strip leading ./ from bin paths (npm 11.x drops ./-prefixed bins).
-- [`normalizeExeOptions`](silk://packages/tsdown-plugins/api/function/normalizeexeoptions) — Normalize `exe` (object or array) into one fully-resolved spec per binary. Pure function; structural validation (missing fileName, empty targets) lives in the config-validation layer.
-- [`normalizeLooseFiles`](silk://packages/tsdown-plugins/api/function/normalizeloosefiles) — Resolve a `looseFiles` map into normalized build descriptors. Pure (no filesystem): a missing `source` is surfaced later by tsdown's entry resolution. Throws ConfigValidationError on any structural problem so the bundler's ConfigValidator surfaces it as a typed, fast-fail config error.
-- [`normalizeMetaOptions`](silk://packages/tsdown-plugins/api/function/normalizemetaoptions) — Fill defaults so downstream code never branches on undefined.
-- [`packageJsonEntries`](silk://packages/tsdown-plugins/api/function/packagejsonentries) — Derive a tsdown `entry` record (name to source path) from a package.json.
-- [`readTsconfigJsx`](silk://packages/tsdown-plugins/api/function/readtsconfigjsx) — Read the jsx-relevant compilerOptions from a package's own tsconfig.json (best-effort; returns empty on absence or parse error).
-- [`removeDeclarationMaps`](silk://packages/tsdown-plugins/api/function/removedeclarationmaps) — Remove declaration source-map files (`.d.ts.map` / `.d.cts.map`) from a built `pkg` directory, returning the removed paths. The dts pass emits these next to each `.d.ts` (the resolved dts tsconfig sets `declarationMap: true`) because API Extractor reads them during meta generation to resolve original-source positions. But they are dead weight in a PUBLISHED package — they reference `.ts` sources the tarball does not ship — and they leak local source paths, so the prod build strips them AFTER meta generation has consumed them. The dev build keeps them (it is never published, and `savvy build --target meta` reads them). Recurses, but skips `node_modules` so it does not traverse a self-contained bundle's vendored tree — only the package's own emitted declarations carry maps worth stripping.
-- [`renderReport`](silk://packages/tsdown-plugins/api/function/renderreport)
-- [`resolveJsxConfig`](silk://packages/tsdown-plugins/api/function/resolvejsxconfig) — Resolve the effective JSX config: an explicit override wins; otherwise infer from the tsconfig values. Returns undefined when no JSX transform is needed (preserve/none).
-- [`resolveManifest`](silk://packages/tsdown-plugins/api/function/resolvemanifest) — Resolve every `catalog:`/`workspace:` specifier in a manifest to a concrete spec, delegating to workspaces-effect's CatalogResolver. The resolver discovers the workspace root from `process.cwd()` (run this from inside the target workspace) and assembles catalogs durably (inline + config-dependency hook-replay + lockfile), so no transient `.pnpm-workspace-state-v1.json` is required. Rejects with `CatalogResolutionError` on an unresolvable reference, or `CatalogAssemblyError` if the workspace catalog set cannot be assembled.
-- [`resolveNextVersions`](silk://packages/tsdown-plugins/api/function/resolvenextversions) — Resolve the next release version of every workspace package from pending changesets. Walks up from `cwd` to the monorepo root via `@manypkg/get-packages`, seeds the map with each package's CURRENT version, then overlays `newVersion` for changeset-affected packages via `@changesets/get-release-plan`. Never rejects: any failure (not a workspace, missing `.changeset/config.json`, parse error) degrades to current versions (or an empty map).
-- [`resolvePortableTsconfig`](silk://packages/tsdown-plugins/api/function/resolveportabletsconfig) — Resolves the package's effective compiler options (following `extends`) into a portable, JSON-serializable tsconfig for the meta release bundle.
-- [`resolveTargets`](silk://packages/tsdown-plugins/api/function/resolvetargets) — Resolve a `publishConfig.targets` map into the distinct groups to build and every target bound to one. Pure; throws ConfigValidationError on structurally-invalid config.
-- [`rewriteMetaVersions`](silk://packages/tsdown-plugins/api/function/rewritemetaversions) — Rewrite a meta `package.json` so the package's own `version` and any workspace-sibling dependency version reflect their NEXT release version from `versions`. Pure: returns a new object, never mutates the input. External/catalog-resolved deps (names absent from `versions`) are left as-is.
-- [`runExeBuild`](silk://packages/tsdown-plugins/api/function/runexebuild) — Compile each SEA binary via tsdown's exe mode. One tsdown build per spec.
-- [`runMetaPass`](silk://packages/tsdown-plugins/api/function/runmetapass) — Meta-pass orchestrator: derives export paths, filters bin/ entries, resolves optimistic next-versions, and calls generateMeta once per publish group.
-- [`serializeIssues`](silk://packages/tsdown-plugins/api/function/serializeissues) — Serialize the issues artifact to pretty JSON with a trailing newline.
-- [`syncPublicDir`](silk://packages/tsdown-plugins/api/function/syncpublicdir) — Mirror `sourceDir` into `targetDir`, idempotently. Replaces tsdown's built-in `copy`, whose non-recursive mkdir throws `EEXIST` when the target already exists (re-builds, `prepare`-on-install, concurrent turbo invocations). Behavior: - source absent: no-op. - target absent: copy `sourceDir` wholesale. - target present: copy only files that are new or whose bytes differ, then delete target files that no longer exist in the source and prune the directories left empty. The byte-diff keeps unchanged files (and their timestamps) untouched, so a large copied asset tree — e.g. the mcp markdown corpus — is not rewritten on every build.
-- [`transformBin`](silk://packages/tsdown-plugins/api/function/transformbin) — Rewrite bin: TS targets to bin/[command].js (string to bin/cli.js); strip leading ./ otherwise.
-- [`transformExports`](silk://packages/tsdown-plugins/api/function/transformexports) — Rewrite an exports map: TS string targets become a types/import conditions object. Each TS condition also gets a `require` entry when `dual` is `true` (uniform) or when the export key is in the `dual` Set (per-entry). The output path is derived from the export KEY via the shared entry-name function, never from the source path, so the manifest target always matches the emitted file. Export keys in `subdirExports` are built into an isolated `<key>/index.*` subdir (e.g. an RSPress `./runtime`), so their conditions gain an `/index` segment.
-- [`transformManifest`](silk://packages/tsdown-plugins/api/function/transformmanifest) — Apply the full standard manifest transform (excluding catalog resolution, done upstream).
-- [`writeIssuesArtifact`](silk://packages/tsdown-plugins/api/function/writeissuesartifact) — Write the aggregated issues artifact to `<cwd>/dist/<target>/issues.json`. Returns the path written.
-- [`writeResolvedTsconfig`](silk://packages/tsdown-plugins/api/function/writeresolvedtsconfig) — Write the resolved tsconfig to a temp file and return its absolute path.
-- [`writeTargetsBinding`](silk://packages/tsdown-plugins/api/function/writetargetsbinding) — Write the target-to-group binding to dist/prod/targets.json for the release action to consume. Returns the path.
-
-## interface
-
-- [`BuildEmittedManifestOptions`](silk://packages/tsdown-plugins/api/interface/buildemittedmanifestoptions)
-- [`BuildGroupSpec`](silk://packages/tsdown-plugins/api/interface/buildgroupspec) — A prod/dev group to build: its folder id and the resolved package name its manifest carries.
-- [`BuildIssues`](silk://packages/tsdown-plugins/api/interface/buildissues) — The aggregated build-issues artifact written to `dist/<target>/issues.json`.
-- [`BuildTargetGroupsOptions`](silk://packages/tsdown-plugins/api/interface/buildtargetgroupsoptions)
-- [`CssOptions`](silk://packages/tsdown-plugins/api/interface/cssoptions) — CSS handling for a partition's JS pass, forwarded VERBATIM to tsdown's `css` option (consumed by `@tsdown/css`). Structurally typed so tsdown-plugins takes no dependency on `@tsdown/css`. The package whose runtime is built must install `@tsdown/css`; tsdown loads it lazily.
-- [`DerivedTsdownOptions`](silk://packages/tsdown-plugins/api/interface/derivedtsdownoptions) — The JS pass: per-module JavaScript, no declarations. The build runs TWO tsdown passes per TargetGroup to the SAME outDir: - pass 1 (this) emits per-module JS (`unbundle: true`) with `dts: false` and the default `clean: true`, so it starts from a fresh outDir; - pass 2 (`DerivedDtsPassOptions`) emits ONLY bundled declarations (`unbundle: false`, `dts: { emitDtsOnly: true }`) with `clean: false`, so it must NOT wipe pass 1. We cannot do this in a single pass: tsdown's `unbundle` maps to rolldown `output.preserveModules` for the WHOLE build, and the dts plugin shares it — so one pass gives EITHER per-module JS + per-module dts OR bundled JS + bundled dts. Per-module dts breaks type portability (TS2883) when a package exports only its root entry, and bundling the JS re-bundles workspace consumers (e.g. silk re-bundling silk-effects crashes at runtime). The split keeps per-module JS (no re-bundle hazard) AND bundled, self-contained declarations (no TS2883).
-- [`DeriveOptions`](silk://packages/tsdown-plugins/api/interface/deriveoptions)
-- [`DiagnosticInput`](silk://packages/tsdown-plugins/api/interface/diagnosticinput)
-- [`EmitManifestOptions`](silk://packages/tsdown-plugins/api/interface/emitmanifestoptions)
-- [`EntryOverride`](silk://packages/tsdown-plugins/api/interface/entryoverride) — One entry partition built with its own format + bundling posture, layered into the SAME outDir as the base build (clean:false). Anything omitted falls back to the base build's value. `entry` is a subset of the package's entries (`entryName -> source path`).
-- [`ExeConfig`](silk://packages/tsdown-plugins/api/interface/execonfig) — One SEA binary to compile.
-- [`ExeRewrite`](silk://packages/tsdown-plugins/api/interface/exerewrite) — Describes a SEA binary the bundler compiled for this package. When present, transformManifest rewrites every `exports`/`bin` value equal to `source` to the emitted binary path and adds it to `files` so it ships in the tarball.
-- [`ExeSeaConfig`](silk://packages/tsdown-plugins/api/interface/exeseaconfig) — SEA seaConfig overrides (subset; the rest are defaulted).
-- [`ExeTarget`](silk://packages/tsdown-plugins/api/interface/exetarget) — A resolved per-platform SEA target. `platform` uses the tsdown/tsdown/exe token (win, not win32).
-- [`ExeTargetInput`](silk://packages/tsdown-plugins/api/interface/exetargetinput) — A target before nodeVersion defaulting (platform/arch only).
-- [`ExtractOptions`](silk://packages/tsdown-plugins/api/interface/extractoptions)
-- [`ExtractResult`](silk://packages/tsdown-plugins/api/interface/extractresult)
-- [`Formatter`](silk://packages/tsdown-plugins/api/interface/formatter)
-- [`FormatterContext`](silk://packages/tsdown-plugins/api/interface/formattercontext)
-- [`GenerateMetaOptions`](silk://packages/tsdown-plugins/api/interface/generatemetaoptions)
-- [`JsxConfig`](silk://packages/tsdown-plugins/api/interface/jsxconfig) — Resolved JSX transform settings, mirroring the subset of rolldown's JsxOptions the bundler forwards.
-- [`LooseFileSpec`](silk://packages/tsdown-plugins/api/interface/loosefilespec) — One standalone bundled output file, declared by its literal output filename.
-- [`MetaOptions`](silk://packages/tsdown-plugins/api/interface/metaoptions) — The `meta` field on defineBuild. Absent means no api-model generation.
-- [`MetaResult`](silk://packages/tsdown-plugins/api/interface/metaresult)
-- [`NextVersions`](silk://packages/tsdown-plugins/api/interface/nextversions) — Result of resolving next release versions for a workspace.
-- [`NormalizedExe`](silk://packages/tsdown-plugins/api/interface/normalizedexe) — Fully-resolved SEA binary spec (no optionals).
-- [`NormalizedLooseFile`](silk://packages/tsdown-plugins/api/interface/normalizedloosefile) — A loose file resolved to a concrete build descriptor.
-- [`NormalizedMeta`](silk://packages/tsdown-plugins/api/interface/normalizedmeta) — Fully-resolved meta options (no optionals).
-- [`PackageJsonEntriesOptions`](silk://packages/tsdown-plugins/api/interface/packagejsonentriesoptions)
-- [`PackageJsonLike`](silk://packages/tsdown-plugins/api/interface/packagejsonlike)
-- [`PkgOsCpu`](silk://packages/tsdown-plugins/api/interface/pkgoscpu) — The package's own os/cpu fields, used to infer a single platform target.
-- [`PlainDiagnostic`](silk://packages/tsdown-plugins/api/interface/plaindiagnostic) — A diagnostic flattened to a plain JSON object (only defined fields are present).
-- [`PortableTsconfig`](silk://packages/tsdown-plugins/api/interface/portabletsconfig) — Portable, JSON-serializable tsconfig.json (compilerOptions-only).
-- [`PublishTargetObject`](silk://packages/tsdown-plugins/api/interface/publishtargetobject) — A single object-form publish target. Uses `from` XOR `name` (never both).
-- [`RenderedOutput`](silk://packages/tsdown-plugins/api/interface/renderedoutput)
-- [`RenderReportOptions`](silk://packages/tsdown-plugins/api/interface/renderreportoptions)
-- [`ResolvedCompilerOptions`](silk://packages/tsdown-plugins/api/interface/resolvedcompileroptions) — Compiler options with enum values converted to their string equivalents.
-- [`ResolvedGroup`](silk://packages/tsdown-plugins/api/interface/resolvedgroup) — A distinct byte-variant build group (one per distinct resolved name).
-- [`ResolvedTarget`](silk://packages/tsdown-plugins/api/interface/resolvedtarget) — A resolved registry target (one per `publishConfig.targets` key).
-- [`ResolvedTsconfig`](silk://packages/tsdown-plugins/api/interface/resolvedtsconfig)
-- [`ResolvedTsconfigOptions`](silk://packages/tsdown-plugins/api/interface/resolvedtsconfigoptions)
-- [`RunExeBuildOptions`](silk://packages/tsdown-plugins/api/interface/runexebuildoptions) — Options for compiling SEA binaries.
-- [`RunMetaPassOptions`](silk://packages/tsdown-plugins/api/interface/runmetapassoptions) — Options for the meta-pass orchestrator.
-- [`TargetGroupRef`](silk://packages/tsdown-plugins/api/interface/targetgroupref)
-- [`TargetResolution`](silk://packages/tsdown-plugins/api/interface/targetresolution) — The full resolution of `publishConfig.targets`: the distinct groups to build, and every target bound to one.
-- [`Timer`](silk://packages/tsdown-plugins/api/interface/timer)
-- [`TransformManifestOptions`](silk://packages/tsdown-plugins/api/interface/transformmanifestoptions)
-- [`TsconfigJsx`](silk://packages/tsdown-plugins/api/interface/tsconfigjsx) — The jsx-relevant slice of a tsconfig's compilerOptions.
-- [`TsdocOptions`](silk://packages/tsdown-plugins/api/interface/tsdocoptions) — TSDoc / doc-warning configuration. suppressWarnings is doc functionality, so it lives here.
-- [`TsdocTagDefinition`](silk://packages/tsdown-plugins/api/interface/tsdoctagdefinition) — A single TSDoc tag definition (parity with api-extractor's TSDoc config).
-- [`TsdownLogger`](silk://packages/tsdown-plugins/api/interface/tsdownlogger) — Structural match for tsdown's Logger interface (tsdown 0.22.x).
-- [`ValidationInput`](silk://packages/tsdown-plugins/api/interface/validationinput) — The normalized facts the validator checks, assembled by the bundler before any build work.
-- [`WarningSuppressionRule`](silk://packages/tsdown-plugins/api/interface/warningsuppressionrule) — An api-extractor message-suppression rule. messageId is exact-matched; pattern (regex or substring) is AND-matched against the text.
-
-## type
-
-- [`BuildFormat`](silk://packages/tsdown-plugins/api/type/buildformat) — An output module format the build can emit.
-- [`BuildPlatform`](silk://packages/tsdown-plugins/api/type/buildplatform) — Bundling platform for the JS pass. Defaults to "node". Use "browser" for web runtime partitions.
-- [`DualExports`](silk://packages/tsdown-plugins/api/type/dualexports) — Which exports get a CJS `require` condition. `true`/`false` apply uniformly to every TS export; a Set marks ONLY the listed export keys (e.g. "./changesets/markdownlint") as dual — used by per-entry format overrides.
-- [`Environment`](silk://packages/tsdown-plugins/api/type/environment)
-- [`ExeBuild`](silk://packages/tsdown-plugins/api/type/exebuild) — A minimal structural type for tsdown's build, kept loose so this package keeps no tsdown runtime dep (interface-only).
-- [`Executor`](silk://packages/tsdown-plugins/api/type/executor)
-- [`Json`](silk://packages/tsdown-plugins/api/type/json)
-- [`LooseFiles`](silk://packages/tsdown-plugins/api/type/loosefiles) — Map of literal output filename to its source (bare string) or a `{ source, format }` spec.
-- [`OutputFormat`](silk://packages/tsdown-plugins/api/type/outputformat)
-- [`PassKind`](silk://packages/tsdown-plugins/api/type/passkind)
-- [`PublishTargets`](silk://packages/tsdown-plugins/api/type/publishtargets) — The `publishConfig.targets` map, keyed by target id (`npm`, `github`, or a custom key).
-- [`PublishTargetValue`](silk://packages/tsdown-plugins/api/type/publishtargetvalue) — A `publishConfig.targets` value: `true` (well-known registry, base name), a string (name override), or an object.
-- [`TargetGroupId`](silk://packages/tsdown-plugins/api/type/targetgroupid) — A build group id: "dev" or any prod byte-variant id (e.g. "npm", "github", a custom key).
-- [`TsdownBuild`](silk://packages/tsdown-plugins/api/type/tsdownbuild) — Signature compatible with tsdown's `build(inlineConfig)`.
-
-## variable
-
-- [`CiAnnotationsFormatter`](silk://packages/tsdown-plugins/api/variable/ciannotationsformatter)
-- [`ConfigValidatorLive`](silk://packages/tsdown-plugins/api/variable/configvalidatorlive) — Live ConfigValidator: wraps the synchronous rule set, surfacing ConfigValidationError as a typed Effect failure.
-- [`DEFAULT_EXE_NODE_VERSION`](silk://packages/tsdown-plugins/api/variable/default_exe_node_version) — Default Node runtime embedded in the SEA (parity with the vitest-agent reference).
-- [`EnvironmentDetectorLive`](silk://packages/tsdown-plugins/api/variable/environmentdetectorlive)
-- [`ExecutorResolverLive`](silk://packages/tsdown-plugins/api/variable/executorresolverlive)
-- [`FormatSelectorLive`](silk://packages/tsdown-plugins/api/variable/formatselectorlive)
-- [`JsonFormatter`](silk://packages/tsdown-plugins/api/variable/jsonformatter)
-- [`MarkdownFormatter`](silk://packages/tsdown-plugins/api/variable/markdownformatter)
-- [`OutputRendererLive`](silk://packages/tsdown-plugins/api/variable/outputrendererlive)
-- [`ReportPipelineLive`](silk://packages/tsdown-plugins/api/variable/reportpipelinelive)
-- [`SilentFormatter`](silk://packages/tsdown-plugins/api/variable/silentformatter)
-- [`TerminalFormatter`](silk://packages/tsdown-plugins/api/variable/terminalformatter)

package/public/content/standards/api-model-pipeline.md

@@ -1,64 +0,0 @@
----
-id: standards/api-model-pipeline
-title: API Extractor as docs source of truth
-summary: How package API surfaces become generated silk://packages/<pkg>/api docs via API Extractor models.
-tier: standards
-source: hand
-tags: [api, build]
-priority: 0.5
-related: [packages/mcp/resource-taxonomy]
----
-
-## Rule
-
-Package API-reference docs are **generated** from Microsoft API Extractor models,
-not hand-written. Do not edit generated docs directly — changes are overwritten on
-the next build.
-
-### Pipeline
-
-1. A library package built by `@savvy-web/bundler` emits a model by default; the
-   `meta` option in its `savvy.build.ts` controls it (`false` opts out).
-2. `build:prod` emits `<unscoped>.api.json` (a Microsoft API Extractor model file).
-3. The `api-extractor-llms` library renders that model into LLM-lean
-   markdown.
-4. The rendered docs appear in the MCP resource layer under
-   `silk://packages/<pkg>/api/<kind>/<name>`.
-5. The `silk://catalog` lists these entries marked `(generated)`.
-
-Generated docs carry a provenance marker indicating they must not be hand-edited.
-
-### Coverage scope
-
-Only public API surfaces are included. Internal and `@internal`-tagged members are
-excluded. Quality tracks TSDoc coverage: undocumented public members degrade the
-model and produce sparse rendered output.
-
-## Why
-
-Hand-written API docs drift from code. Generating docs from the type surface and
-TSDoc comments keeps them accurate by construction: a renamed export, a removed
-parameter, or a new option surfaces automatically in the next build. The API
-Extractor model format is the standard Microsoft toolchain for TypeScript API
-management, making the pipeline compatible with upstream tooling.
-
-## Examples
-
-A package `@savvy-web/silk-effects` built by `@savvy-web/bundler` emits
-`silk-effects.api.json` on its prod build. The renderer produces entries such as:
-
-```text
-silk://packages/silk-effects/api/class/SilkPublishability
-silk://packages/silk-effects/api/namespace/Changesets
-silk://packages/silk-effects/api/class/ChangesetConfig
-```
-
-These appear in `silk://catalog` as `(generated)` entries alongside hand-authored
-docs.
-
-## See also
-
-The resource taxonomy that governs where generated and hand-authored docs live is at
-`silk://packages/mcp/resource-taxonomy`. The `api-extractor-llms` library
-is the renderer; the `@savvy-web/bundler` build tool emits the model via its
-`meta` option.

package/public/content/standards/catalog-usage.md

@@ -1,48 +0,0 @@
----
-id: standards/catalog-usage
-title: Catalog usage
-summary: Load when adding or pinning a dependency in a Silk Suite package.
-tier: standards
-source: hand
-tags: [catalog, dependencies]
-priority: 0.8
-related: [standards/publishability]
----
-
-## Rule
-
-Pin dependencies through the named catalogs that `@savvy-web/pnpm-plugin-silk`
-merges into `pnpm-workspace.yaml` during `pnpm install`. Use `catalog:silk` for
-direct `dependencies` and `devDependencies`; use `catalog:silkPeers` for
-`peerDependencies`. Do not hard-code version strings for catalog-managed packages.
-
-## Why
-
-`catalog:silk` carries current/latest pinned versions; `catalog:silkPeers` carries
-wider permissive ranges so a consuming package does not force its users to upgrade
-in lockstep. Centralizing versions in the plugin keeps every repo in the ecosystem
-on one coordinated set, and lets security overrides for transitive CVEs land
-without per-repo edits.
-
-The 26 Effect ecosystem packages are updated together as one batch to preserve
-cross-package compatibility. For `@effect/*` packages (all at `0.x`), `silkPeers`
-uses `>=` floor-only ranges rather than `^` caret ranges, because `^0.x.y`
-restricts to patch-only and would not overlap with the `silk` pinned version one
-minor ahead. For `effect` itself (at `3.x`) the standard `^` caret works.
-
-## Examples
-
-```json
-{
-  "devDependencies": { "typescript": "catalog:silk", "vitest": "catalog:silk" },
-  "peerDependencies": { "typescript": "catalog:silkPeers" }
-}
-```
-
-To override a catalog entry locally, add it under `catalogs.silk` in
-`pnpm-workspace.yaml`; the local value wins and the plugin prints a warning so the
-divergence is visible. Remove the local entry to revert to the Silk default.
-
-## See also
-
-Publishability and registry targets are at `silk://standards/publishability`.

package/public/content/standards/changeset-discipline.md

@@ -1,52 +0,0 @@
----
-id: standards/changeset-discipline
-title: Changeset discipline
-summary: Load when deciding whether a branch needs a changeset and how to author one.
-tier: standards
-source: hand
-tags: [changeset, release]
-priority: 0.8
-related: [packages/silk-effects/, standards/publishability]
----
-
-## Rule
-
-Every branch that changes a publishable package's runtime behavior, public API, or
-shipped output ships a changeset that describes the change in user-facing terms.
-Changes that do not affect what a consumer installs — AI context files, design
-docs, internal tests, trivial config — do not get a changeset. The Silk ecosystem
-formats changelogs through `@savvy-web/changesets`, a section-aware formatter that
-categorizes entries with `h2`/`h3` headings (Features, Bug Fixes, Breaking Changes,
-and the rest of the 13 valid headings) and enriches them with PR links and
-contributor attribution.
-
-## Why
-
-A changeset is release documentation, not a commit log. It answers "what changed
-for someone consuming this package" one level above the diff. Reconciling the
-changeset set against the branch diff before merge keeps the `.changeset/`
-directory an accurate description of the pending release: stale entries that name
-packages no longer touched are removed, and missing entries for shipped work are
-added. Pure dependency bumps follow a one-package-per-changeset, one-dependency-
-changeset-per-package convention so the changelog reads cleanly.
-
-A config is detected as Silk (versus vanilla changesets) when its `changelog`
-field references `@savvy-web/changesets`; Silk mode is what enables the
-section-aware pipeline and the ignore-aware publishability rules.
-
-## Examples
-
-A `feat` that adds a public export needs a `minor` changeset under a Features
-heading. A `fix` that corrects shipped behavior needs a `patch` changeset under
-Bug Fixes. A branch that only edits `CLAUDE.md` and `.claude/design/` needs no
-changeset. A breaking signature change needs a `major` changeset under Breaking
-Changes.
-
-## See also
-
-Authoring and reconciliation are handled by the changeset skills — the
-`changeset-create` skill reconciles changesets against the branch diff, and the
-`changeset-style` skill carries the full format spec (the 13 headings and rules
-CSH001–CSH005). The publishability rules that decide which packages a changeset
-may name live at `silk://standards/publishability`; the config reader and the
-fixed/ignore groups it exposes are documented at `silk://packages/silk-effects/`.

package/public/content/standards/changeset-format.md

@@ -1,132 +0,0 @@
----
-id: standards/changeset-format
-title: Changeset file format (CSH001–CSH005)
-summary: The YAML frontmatter, 13 valid section headings, and CSH001–CSH005 structural rules for changesets.
-tier: standards
-source: hand
-tags: [changeset]
-priority: 0.5
-related: [standards/changeset-discipline]
----
-
-## Rule
-
-Every changeset file (`.changeset/*.md`) starts with YAML frontmatter declaring the
-affected packages and bump levels, followed by body content organized under one or
-more of the 13 valid `##` section headings.
-
-### Frontmatter shape
-
-```yaml
----
-"@savvy-web/package-name": patch | minor | major
----
-```
-
-Multiple packages list one line each:
-
-```yaml
----
-"@savvy-web/package-a": minor
-"@savvy-web/package-b": patch
----
-```
-
-### Bump type guide
-
-| Bump | Use for |
-| :--- | :--- |
-| `patch` | Bug fixes, docs, internal refactoring, tests, CI/build changes |
-| `minor` | New features, new exports, non-breaking additions |
-| `major` | Removed exports, changed signatures, breaking behavior changes |
-
-### 13 valid section headings
-
-All `##` headings must exactly match one of these (case-sensitive):
-
-| Priority | Heading | Use for |
-| :--- | :--- | :--- |
-| 1 | Breaking Changes | Backward-incompatible changes |
-| 2 | Features | New functionality |
-| 3 | Bug Fixes | Bug corrections |
-| 4 | Performance | Performance improvements |
-| 5 | Documentation | Documentation changes |
-| 6 | Refactoring | Code restructuring |
-| 7 | Tests | Test additions or modifications |
-| 8 | Build System | Build configuration changes |
-| 9 | CI | Continuous integration changes |
-| 10 | Dependencies | Dependency updates |
-| 11 | Maintenance | General maintenance |
-| 12 | Reverts | Reverted changes |
-| 13 | Other | Uncategorized changes |
-
-### Structural rules (CSH001–CSH005)
-
-| Rule | Description |
-| :--- | :--- |
-| **CSH001** | No `#` (h1) headings anywhere in the body. No heading depth skips (e.g., jumping from `##` directly to `####`). |
-| **CSH002** | All `##` headings must exactly match one of the 13 valid categories. |
-| **CSH003** | No empty sections. Code fences must include a language identifier. No empty list items. |
-| **CSH004** | No content before the first `##` heading (YAML frontmatter is not "content"). |
-| **CSH005** | A `## Dependencies` section containing a table must use the 5-column schema (Dependency, Type, Action, From, To). |
-
-**CSH005 dependency table schema:**
-
-```markdown
-| Dependency | Type        | Action  | From   | To     |
-| :--------- | :---------- | :------ | :----- | :----- |
-| effect     | dependency  | updated | 3.18.0 | 3.19.1 |
-```
-
-Valid **Type** values: `dependency`, `devDependency`, `peerDependency`,
-`optionalDependency`, `workspace`, `config`.
-
-Valid **Action** values: `added`, `updated`, `removed`. Use `—` (em dash) for From
-when adding, or for To when removing.
-
-## Why
-
-The section-aware format makes changelogs scannable by category. Structural rules
-are enforced by remark-lint pre-validation (and markdownlint in-editor); violations
-fail CI. The 13 headings map to conventional commit types so tooling can correlate
-commits to changelog entries.
-
-## Examples
-
-**Minimal valid changeset (Simple tier):**
-
-```markdown
----
-"@savvy-web/foo": patch
----
-
-## Bug Fixes
-
-- Corrects off-by-one error in pagination helper.
-```
-
-**Multi-section with dependency table (Structured tier):**
-
-```markdown
----
-"@savvy-web/foo": minor
----
-
-## Features
-
-- Adds `suppressWarnings` option to `ApiModelOptions`.
-
-## Dependencies
-
-| Dependency | Type        | Action  | From   | To     |
-| :--------- | :---------- | :------ | :----- | :----- |
-| effect     | dependency  | updated | 3.18.0 | 3.19.1 |
-```
-
-## See also
-
-The discipline rules governing when a changeset is required are at
-`silk://standards/changeset-discipline`. The `changeset-style` Claude Code skill
-carries worked examples for all three content-depth tiers. The `changeset-check`
-skill validates files against CSH001–CSH005 via `savvy changeset lint` (or
-`savvy changeset validate-file <file>` for a single file).

package/public/content/standards/commit-contract.md

@@ -1,58 +0,0 @@
----
-id: standards/commit-contract
-title: Silk commit contract
-summary: Load when composing any conventional commit, amending, squashing, or opening a PR.
-tier: standards
-source: hand
-tags: [commit, dco, tdd]
-priority: 0.8
-related: [standards/changeset-discipline]
----
-
-## Rule
-
-Commits follow `type(scope): subject`, with an optional body, optional `Closes #N`
-trailers, and a mandatory DCO `Signed-off-by` trailer as the last line. The
-`@savvy-web/commitlint` Silk preset enforces this through the `commit-msg` husky
-hook; violations reject the commit.
-
-**Type enum** (one lowercase identifier): `ai`, `build`, `chore`, `ci`, `docs`,
-`feat`, `fix`, `perf`, `refactor`, `release`, `revert`, `style`, `tdd`, `test`.
-Do not invent types.
-
-**Subject:** imperative mood ("add", not "added"/"adds"); lowercase first letter
-after the colon; the full header at most 100 characters; no trailing period; no
-markdown.
-
-**Body** (optional): explain what changed conceptually and why, one level above
-the diff. Each paragraph or bullet is one continuous line — do not soft-wrap.
-No markdown headers, numbered lists, code fences, links, bold, or italic. Name
-the concept that changed, not every file. For dependency updates list only direct
-deps, never transitive lockfile entries. Skip routine AI-context and config tweaks.
-
-## Why
-
-`tdd` commits require a structured scope `goalId:state` matching
-`^\d+:(spike|red|green|refactor)$` — for example `tdd(42:red)` or `tdd(7:green)`.
-The scope ties a commit to a TDD goal and its phase, so a bare `tdd` or
-`tdd(red)` is rejected. The DCO signoff is the Developer Certificate of Origin
-attestation; its exact `Signed-off-by: Full Name <email>` form is required
-verbatim, using the committer's real name and git email. When `commit.gpgsign`
-is true, confirm the signing agent is responsive rather than silently producing
-an unsigned commit.
-
-## Examples
-
-Good: `feat(auth): add JWT refresh token rotation`. Bad: `feat: Updated the auth
-flow` (past tense, capitalized, vague).
-
-A TDD green-phase commit: `tdd(14:green): implement scope validator for tdd commits`.
-
-A fix that closes an issue carries `Closes #87` above the signoff. Any of
-`Closes`, `Fixes`, or `Resolves` followed by `#N` is accepted, one trailer per
-issue.
-
-## See also
-
-The commit-create skill carries the full pre-commit checklist and worked examples.
-Release documentation discipline lives at `silk://standards/changeset-discipline`.

package/public/content/standards/dependency-conventions.md

@@ -1,82 +0,0 @@
----
-id: standards/dependency-conventions
-title: Dependency conventions
-summary: When to use catalog:silk vs catalog:silkPeers, and how the pnpm-plugin-silk config dependency pins versions.
-tier: standards
-source: hand
-tags: [dependencies, catalog]
-priority: 0.5
-related: [standards/catalog-usage]
----
-
-## Rule
-
-All Silk Suite packages pin dependencies through the named catalogs provided by
-`@savvy-web/pnpm-plugin-silk`:
-
-- Use `catalog:silk` for `dependencies` and `devDependencies` (current pinned versions).
-- Use `catalog:silkPeers` for `peerDependencies` (permissive ranges).
-
-Do not hard-code version strings for catalog-managed packages.
-
-### How the plugin works
-
-`@savvy-web/pnpm-plugin-silk` is installed as a pnpm config dependency:
-
-```yaml
-configDependencies:
-  "@savvy-web/pnpm-plugin-silk": "0.3.0+sha512-..."
-```
-
-During `pnpm install` the plugin merges its catalog definitions, security overrides,
-and build configuration into the consuming repo's `pnpm-workspace.yaml`. The merge
-is non-destructive — local definitions always take precedence, and divergences are
-printed as warnings.
-
-The plugin ships:
-
-- `catalog:silk` — current/latest pinned versions for direct use
-- `catalog:silkPeers` — permissive ranges for peer declarations
-- `silkOverrides` — centralized CVE fixes propagated to all consumers
-- Shared `onlyBuiltDependencies`, `publicHoistPattern`, and `peerDependencyRules`
-
-### Effect ecosystem note
-
-The 26 `@effect/*` packages are updated together as one batch to preserve
-cross-package compatibility. For `@effect/*` packages (all at `0.x`),
-`catalog:silkPeers` uses `>=` floor-only ranges rather than `^` caret ranges,
-because `^0.x.y` restricts to patch-only and would not overlap with the `silk`
-pinned version one minor ahead. For `effect` itself (at `3.x`) the standard `^`
-caret works.
-
-## Why
-
-Centralizing versions in the plugin keeps every repo in the ecosystem on one
-coordinated set and lets security overrides for transitive CVEs land without
-per-repo edits. The dual-catalog strategy balances two needs: direct consumers get a
-predictable pinned version; peer consumers stay compatible with a wider range of
-host environments without forcing lockstep upgrades.
-
-## Examples
-
-```json
-{
-  "devDependencies": {
-    "typescript": "catalog:silk",
-    "vitest": "catalog:silk"
-  },
-  "peerDependencies": {
-    "typescript": "catalog:silkPeers"
-  }
-}
-```
-
-To override a catalog entry for a single repo, add it under `catalogs.silk` in
-`pnpm-workspace.yaml`; the local value wins and the plugin prints a warning. Remove
-the local entry to revert to the Silk default.
-
-## See also
-
-Detailed catalog usage rules (including when to add a local override) are at
-`silk://standards/catalog-usage`. Publishability and registry targets that determine
-which packages enter the release pipeline are at `silk://standards/publishability`.