@savvy-web/mcp 1.3.5 → 1.4.0

package/content/packages/bundler/api.md

@@ -1,28 +0,0 @@
----
-id: packages/bundler/api
-title: "@savvy-web/bundler — API reference"
-summary: "@savvy-web/bundler API reference: 10 documented symbols."
-tier: packages
-source: generated
-tags: [bundler, api]
-priority: 0.4
-related: []
----
-
-# @savvy-web/bundler — API reference
-
-## function
-
-- [`build`](silk://packages/bundler/api/function/build) — Sugar front door: define + run in one call, deriving `cwd`/`argv` from process globals. `cwd` is the directory of the entry script (`process.argv[1]`) — the faithful equivalent of the old `import.meta.dirname`, correct even when invoked by an explicit path from another directory. `argv` is `process.argv.slice(2)`, so `--target` and friends are read internally; the package.json build scripts stay `node savvy.build.ts --target <t>`. `overrides` merges last as the test/advanced IO seam (the same injectables as RunOptions).
-- [`defineBuild`](silk://packages/bundler/api/function/definebuild) — Normalize + validate a defineBuild config. Pure when imported; self-runs when entry (see run.ts).
-- [`parseArgs`](silk://packages/bundler/api/function/parseargs) — Parse the build CLI argv into the normalized target/flags shape.
-- [`runBuild`](silk://packages/bundler/api/function/runbuild) — Run a build from a normalized config. Pure orchestration; all IO injectable.
-
-## interface
-
-- [`BuildConfig`](silk://packages/bundler/api/interface/buildconfig)
-- [`BuildConfigInput`](silk://packages/bundler/api/interface/buildconfiginput)
-- [`BuildEntryOverride`](silk://packages/bundler/api/interface/buildentryoverride)
-- [`OutputConfig`](silk://packages/bundler/api/interface/outputconfig)
-- [`ParsedArgs`](silk://packages/bundler/api/interface/parsedargs)
-- [`RunOptions`](silk://packages/bundler/api/interface/runoptions)

package/content/packages/bundler/overview.md

@@ -1,89 +0,0 @@
----
-id: packages/bundler/overview
-title: bundler overview
-summary: Load when setting up or understanding the @savvy-web/bundler build for a Silk library package.
-tier: packages
-source: hand
-tags: [bundler, build]
-priority: 0.5
-related: [standards/catalog-usage, standards/publishability, standards/api-model-pipeline]
----
-
-## What
-
-`@savvy-web/bundler` is the tsdown-based build orchestrator for Silk Suite
-TypeScript libraries. It reads a package's `exports` field to discover entry
-points, builds dev and production outputs, emits a bundled self-contained
-`.d.ts` per public entry, and transforms the output `package.json` for
-publishing. It drives tsdown programmatically over `@savvy-web/tsdown-plugins`.
-A package opts in with a one-line self-executing `savvy.build.ts`.
-
-## API
-
-The front door is `defineBuild` (pure config normalization + validation) and
-`runBuild` (the orchestrator). A package's `savvy.build.ts` defines a config and
-self-runs when invoked directly:
-
-```typescript
-import { defineBuild, runBuild } from "@savvy-web/bundler";
-
-const config = defineBuild({
-  // format defaults to esm-only; minify defaults false (prod-only).
-});
-
-export default config;
-
-if (import.meta.main) {
-  await runBuild(config, { cwd: import.meta.dirname, argv: process.argv.slice(2) });
-}
-```
-
-Entry points come from `package.json` `exports`. `defineBuild` options include
-`format`, `jsx`, `bundle`, `overrides` (per-entry format and bundling
-partitions), `define`, `looseFiles`, `bundleNodeModules`, `plugins` (custom
-rolldown plugins), and `meta` (API-model generation — see below). Imported by
-the cli or the silk plugin, the config object is side-effect-free; run directly,
-it parses `process.argv` and builds.
-
-## Layer
-
-Build scripts invoke the file directly with Node's native type-stripping:
-
-```json
-{
-  "scripts": {
-    "build:dev": "node savvy.build.ts --target dev",
-    "build:prod": "node savvy.build.ts --target prod"
-  }
-}
-```
-
-`--target dev` writes `dist/dev/` (bundled JS, source maps, declarations, a
-transformed `package.json`). `--target prod` writes `dist/prod/<target>/` for
-each `publishConfig.targets` key, emits the API model and meta release asset, and
-strips declaration source maps from the published bytes.
-
-## Usage
-
-The output `package.json` is transformed from source by `defaultManifestTransform`:
-export paths move from `.ts` to `.js`, type conditions are added, pnpm `catalog:`
-and `workspace:` references resolve to concrete versions, and `private` is flipped
-to publish-ready based on `publishConfig.access`. This is the mechanism behind the
-convention that a source `package.json` is `private: true` while its
-`publishConfig` declares publish intent.
-
-The `meta` option is tri-state: omit it to generate the API model with default
-options on `--target prod`, pass an object to override (`localPaths`, `tsdoc`,
-`optimistic`), or pass `false` to opt out. Custom TSDoc tags are registered via
-`meta.tsdoc.tagDefinitions`. The package also ships the shared TS base config at
-`@savvy-web/bundler/tsconfig/ecma.json`, which every Silk library extends.
-
-A common pitfall: relative imports must use `.js` extensions (the ESM
-requirement), or the build reports "cannot find module".
-
-## Related
-
-The symbol-level API reference: `silk://packages/bundler/api`. Dependency
-pinning the build resolves: `silk://standards/catalog-usage`. How `private` and
-`publishConfig` decide what publishes: `silk://standards/publishability`. How the
-prod build's API model becomes generated docs: `silk://standards/api-model-pipeline`.

package/content/packages/cli/command-tree.md

@@ -1,68 +0,0 @@
----
-id: packages/cli/command-tree
-title: The savvy command tree
-summary: Load to orient on what the savvy binary does and how its command groups are organized.
-tier: packages
-source: hand
-tags: [cli]
-priority: 0.5
-related: [packages/cli/init-and-check, packages/silk/install-and-setup]
----
-
-## What
-
-`@savvy-web/cli` owns the `savvy` binary — the single command host for the Silk
-Suite's everyday dev tooling, built on `@effect/cli` + `@effect/platform-node`. It
-carries no business logic of its own: every handler imports its work from
-`@savvy-web/silk-effects`. The binary replaces three standalone bins
-(`savvy-changesets`, `savvy-commit`, `savvy-lint`) with one. It is a `fixed`
-changeset group with `@savvy-web/silk` — they always release together.
-
-## API
-
-The tree is static — no runtime discovery, no contribution manifest, no per-command
-"is the system configured" gate. Commands assume the system is set up (`savvy init`
-sets it up).
-
-```text
-savvy init        orchestrator → changeset · commit · lint init in one pass
-savvy check       orchestrator → runs all three checks
-savvy commit      hook(session-start · pre-commit-message · post-commit-verify)
-savvy changeset   lint · check · transform · validate-file · version ·
-                  config(validate) · deps(detect · regen)
-savvy lint        fmt(package-json · pnpm-workspace · yaml)
-```
-
-Each group lives under `src/commands/{commit,changeset,lint}/` and exports its
-group command plus named handlers (e.g. `runChangesetInit`). The top-level `init`
-and `check` orchestrators sequence the three tool handlers and short-circuit on
-first failure; the tool handlers are injected so the orchestration logic is
-unit-testable without a runtime. The plugin hooks and skills shell out to these
-subcommands.
-
-## Layer
-
-The runtime layer stack is assembled once in `runCli()` (`src/cli/index.ts`) as the
-union of the three source CLIs' stacks. It uses `provideMerge` (not `provide`) so
-base silk-effects services are both fed to upper services and re-exposed for
-handlers that yield those tags directly, and it hand-wires a minimal workspace
-trio (`WorkspaceRoot`, `WorkspaceDiscovery`, `PackageManagerDetector`) rather than
-the heavier `WorkspacesLive`.
-
-Because the command groups are typed with an `any` R-channel (an Effect/cli
-declaration-emit escape hatch), the type-checker cannot prove `AppLive` supplies
-every required service. The real layer-completeness gate is the **runtime smoke
-tests** that run each command, not `tsgo`. Treat them as the contract when adding a
-command that needs a new service.
-
-## Usage
-
-The `savvy` bin resolves to `src/bin/cli.ts` → `runCli()`. Tools it shells out to
-(`@biomejs/biome`, `husky`, `@commitlint/*`, `@changesets/cli`, `lint-staged`,
-`markdownlint-cli2`) are not direct deps; `@savvy-web/silk` co-installs them as
-peers and pnpm's public-hoist-pattern makes them resolvable.
-
-## Related
-
-Init and check: `silk://packages/cli/init-and-check`. Install surface:
-`silk://packages/silk/install-and-setup`.

package/content/packages/cli/init-and-check.md

@@ -1,53 +0,0 @@
----
-id: packages/cli/init-and-check
-title: savvy init and check
-summary: Load when running or wiring the savvy init/check orchestrators.
-tier: packages
-source: hand
-tags: [cli, init]
-priority: 0.5
-related: [packages/cli/command-tree, packages/silk/install-and-setup]
----
-
-## What
-
-`savvy init` and `savvy check` are the top-level orchestrators of the `savvy`
-command tree. `init` is what sets the system up — it runs the changeset, commit,
-and lint `init` handlers in one pass, seeding configs and wiring husky hooks.
-`check` runs all three checks. The rest of the tree (`commit`, `changeset`, `lint`)
-assumes `init` has already run.
-
-## API
-
-Both orchestrators sequence the three per-tool handlers and short-circuit on the
-first failure. They live at `src/commands/init.ts` and `src/commands/check.ts`. The
-per-tool handlers are injected rather than imported inline, so the orchestration
-logic — the sequencing and short-circuit — is unit-testable without standing up the
-full runtime. There is no per-tool setup or validation entry point: `savvy init`
-and `savvy check` are the only ones. The namespaced groups expose the remaining
-per-tool operations instead (`savvy changeset lint`, `savvy lint fmt`,
-`savvy commit hook ...`, and so on).
-
-## Layer
-
-`init` and `check` run on the same merged runtime stack as the rest of the tree,
-assembled once in `runCli()`. Because they orchestrate the same handlers the plugin
-hooks call, they are covered by the runtime smoke tests that gate layer
-completeness.
-
-## Usage
-
-```bash
-savvy init     # seed configs + wire husky hooks for changesets, commitlint, lint-staged
-savvy check    # run the changeset, commit, and lint checks; fail on the first violation
-```
-
-`savvy init` is what a consumer runs after installing `@savvy-web/silk`: the
-install pulls the `savvy` bin and the real tools as peers, then `init` seeds the
-configs that reference `@savvy-web/silk/*` and points the husky hooks at `savvy`
-subcommands.
-
-## Related
-
-The full command tree: `silk://packages/cli/command-tree`. The install flow that
-precedes `init`: `silk://packages/silk/install-and-setup`.

package/content/packages/github-action-builder/api/class/actionymlmissing.md

@@ -1,30 +0,0 @@
----
-id: packages/github-action-builder/api/class/actionymlmissing
-title: "ActionYmlMissing — github-action-builder class"
-summary: "Error when action.yml file is missing."
-tier: packages
-source: generated
-tags: [github-action-builder, api]
-priority: 0.3
-related: []
----
-
-# ActionYmlMissing
-
-Error when action.yml file is missing.
-
-```ts
-class ActionYmlMissing extends ActionYmlMissingBase<{
-  readonly cwd: string;
-}>
-```
-
-## Members
-
-### cwd
-
-```ts
-readonly cwd: string;
-```
-
-The working directory that was searched.

package/content/packages/github-action-builder/api/class/actionymlpatherror.md

@@ -1,48 +0,0 @@
----
-id: packages/github-action-builder/api/class/actionymlpatherror
-title: "ActionYmlPathError — github-action-builder class"
-summary: "Error when action.yml runs paths don't resolve correctly in destination."
-tier: packages
-source: generated
-tags: [github-action-builder, api]
-priority: 0.3
-related: []
----
-
-# ActionYmlPathError
-
-Error when action.yml runs paths don't resolve correctly in destination.
-
-```ts
-class ActionYmlPathError extends ActionYmlPathErrorBase<{
-  readonly entryType: string;
-  readonly specifiedPath: string;
-  readonly expectedPath: string;
-}>
-```
-
-## Members
-
-### entryType
-
-```ts
-readonly entryType: string;
-```
-
-The entry type whose path failed validation (main, pre, post).
-
-### expectedPath
-
-```ts
-readonly expectedPath: string;
-```
-
-The expected resolved path.
-
-### specifiedPath
-
-```ts
-readonly specifiedPath: string;
-```
-
-The path specified in action.yml.

package/content/packages/github-action-builder/api/class/actionymlschemaerror.md

@@ -1,45 +0,0 @@
----
-id: packages/github-action-builder/api/class/actionymlschemaerror
-title: "ActionYmlSchemaError — github-action-builder class"
-summary: "Error when action.yml fails schema validation."
-tier: packages
-source: generated
-tags: [github-action-builder, api]
-priority: 0.3
-related: []
----
-
-# ActionYmlSchemaError
-
-Error when action.yml fails schema validation.
-
-```ts
-class ActionYmlSchemaError extends ActionYmlSchemaErrorBase<{
-  readonly path: string;
-  readonly errors: ReadonlyArray<{
-    readonly path: string;
-    readonly message: string;
-  }>;
-}>
-```
-
-## Members
-
-### errors
-
-```ts
-readonly errors: ReadonlyArray<{
-    readonly path: string;
-    readonly message: string;
-  }>;
-```
-
-List of schema validation errors.
-
-### path
-
-```ts
-readonly path: string;
-```
-
-The path to the action.yml file.

package/content/packages/github-action-builder/api/class/actionymlsyntaxerror.md

@@ -1,57 +0,0 @@
----
-id: packages/github-action-builder/api/class/actionymlsyntaxerror
-title: "ActionYmlSyntaxError — github-action-builder class"
-summary: "Error when action.yml has invalid YAML syntax."
-tier: packages
-source: generated
-tags: [github-action-builder, api]
-priority: 0.3
-related: []
----
-
-# ActionYmlSyntaxError
-
-Error when action.yml has invalid YAML syntax.
-
-```ts
-class ActionYmlSyntaxError extends ActionYmlSyntaxErrorBase<{
-  readonly path: string;
-  readonly message: string;
-  readonly line?: number;
-  readonly column?: number;
-}>
-```
-
-## Members
-
-### column
-
-```ts
-readonly column?: number;
-```
-
-Column number where the error occurred, if available.
-
-### line
-
-```ts
-readonly line?: number;
-```
-
-Line number where the error occurred, if available.
-
-### message
-
-```ts
-readonly message: string;
-```
-
-The syntax error message.
-
-### path
-
-```ts
-readonly path: string;
-```
-
-The path to the action.yml file.

package/content/packages/github-action-builder/api/class/buildfailed.md

@@ -1,39 +0,0 @@
----
-id: packages/github-action-builder/api/class/buildfailed
-title: "BuildFailed — github-action-builder class"
-summary: "Error when the build process fails overall."
-tier: packages
-source: generated
-tags: [github-action-builder, api]
-priority: 0.3
-related: []
----
-
-# BuildFailed
-
-Error when the build process fails overall.
-
-```ts
-class BuildFailed extends BuildFailedBase<{
-  readonly message: string;
-  readonly failedEntries: number;
-}>
-```
-
-## Members
-
-### failedEntries
-
-```ts
-readonly failedEntries: number;
-```
-
-Number of entries that failed.
-
-### message
-
-```ts
-readonly message: string;
-```
-
-Summary message of the build failure.

package/content/packages/github-action-builder/api/class/bundlefailed.md

@@ -1,39 +0,0 @@
----
-id: packages/github-action-builder/api/class/bundlefailed
-title: "BundleFailed — github-action-builder class"
-summary: "Error when bundling with rsbuild fails."
-tier: packages
-source: generated
-tags: [github-action-builder, api]
-priority: 0.3
-related: []
----
-
-# BundleFailed
-
-Error when bundling with rsbuild fails.
-
-```ts
-class BundleFailed extends BundleFailedBase<{
-  readonly entry: string;
-  readonly cause: unknown;
-}>
-```
-
-## Members
-
-### cause
-
-```ts
-readonly cause: unknown;
-```
-
-The underlying error or error message.
-
-### entry
-
-```ts
-readonly entry: string;
-```
-
-The entry file that failed to bundle.

package/content/packages/github-action-builder/api/class/cleanerror.md

@@ -1,39 +0,0 @@
----
-id: packages/github-action-builder/api/class/cleanerror
-title: "CleanError — github-action-builder class"
-summary: "Error when cleaning the output directory fails."
-tier: packages
-source: generated
-tags: [github-action-builder, api]
-priority: 0.3
-related: []
----
-
-# CleanError
-
-Error when cleaning the output directory fails.
-
-```ts
-class CleanError extends CleanErrorBase<{
-  readonly directory: string;
-  readonly cause: unknown;
-}>
-```
-
-## Members
-
-### cause
-
-```ts
-readonly cause: unknown;
-```
-
-The underlying error or error message.
-
-### directory
-
-```ts
-readonly directory: string;
-```
-
-The directory that failed to clean.

package/content/packages/github-action-builder/api/class/configinvalid.md

@@ -1,39 +0,0 @@
----
-id: packages/github-action-builder/api/class/configinvalid
-title: "ConfigInvalid — github-action-builder class"
-summary: "Error when configuration file exists but contains invalid content."
-tier: packages
-source: generated
-tags: [github-action-builder, api]
-priority: 0.3
-related: []
----
-
-# ConfigInvalid
-
-Error when configuration file exists but contains invalid content.
-
-```ts
-class ConfigInvalid extends ConfigInvalidBase<{
-  readonly path: string;
-  readonly errors: ReadonlyArray<string>;
-}>
-```
-
-## Members
-
-### errors
-
-```ts
-readonly errors: ReadonlyArray<string>;
-```
-
-List of validation errors.
-
-### path
-
-```ts
-readonly path: string;
-```
-
-The path to the invalid config file.

package/content/packages/github-action-builder/api/class/configloadfailed.md

@@ -1,39 +0,0 @@
----
-id: packages/github-action-builder/api/class/configloadfailed
-title: "ConfigLoadFailed — github-action-builder class"
-summary: "Error when configuration file fails to load (import error, syntax error, etc.)."
-tier: packages
-source: generated
-tags: [github-action-builder, api]
-priority: 0.3
-related: []
----
-
-# ConfigLoadFailed
-
-Error when configuration file fails to load (import error, syntax error, etc.).
-
-```ts
-class ConfigLoadFailed extends ConfigLoadFailedBase<{
-  readonly path: string;
-  readonly cause: unknown;
-}>
-```
-
-## Members
-
-### cause
-
-```ts
-readonly cause: unknown;
-```
-
-The underlying error or error message.
-
-### path
-
-```ts
-readonly path: string;
-```
-
-The path to the config file that failed to load.

package/content/packages/github-action-builder/api/class/confignotfound.md

@@ -1,39 +0,0 @@
----
-id: packages/github-action-builder/api/class/confignotfound
-title: "ConfigNotFound — github-action-builder class"
-summary: "Error when configuration file is not found."
-tier: packages
-source: generated
-tags: [github-action-builder, api]
-priority: 0.3
-related: []
----
-
-# ConfigNotFound
-
-Error when configuration file is not found.
-
-```ts
-class ConfigNotFound extends ConfigNotFoundBase<{
-  readonly path: string;
-  readonly message?: string;
-}>
-```
-
-## Members
-
-### message
-
-```ts
-readonly message?: string;
-```
-
-Additional context about the search.
-
-### path
-
-```ts
-readonly path: string;
-```
-
-The path that was searched for the config file.