@savvy-web/silk-core 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Savvy Web Systems
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,47 @@
+# @savvy-web/silk-core
+
+[![npm](https://img.shields.io/npm/v/@savvy-web%2Fsilk-core?label=npm&color=cb3837)](https://www.npmjs.com/package/@savvy-web/silk-core)
+[![License: MIT](https://img.shields.io/badge/License-MIT-4caf50.svg)](https://opensource.org/licenses/MIT)
+
+The platform-free domain core of the Silk Suite: the [Effect](https://effect.website/) schemas, tagged errors and the PR-body contract that every other Silk package builds on. Nothing in this package touches a filesystem, a subprocess, a clock or `process` — it is pure data modelling, safe to import from any runtime.
+
+## Features
+
+- Workspace-analysis schemas — `AnalyzedWorkspace`, `WorkspaceAnalysis` and the Silk-extended `SilkPublishConfig` with its multi-registry `targets`
+- Changeset config file schemas (`ChangesetConfigFile`, `SilkChangesetConfigFile`) and the config-discovery result types
+- The managed `savvy-*` shell sections (`SavvyBaseSection`, `SavvyHooksSection`, `SavvyInstallSection`, `SavvyToolchainSection`) and their block builders
+- The frozen `PrBody` contract — `silk-release` markers, managed regions, closing-reference spellings and diagnostics — shared by every PR-body writer
+- Typed errors (`BiomeSyncError`, `ChangesetConfigError`, `ConfigNotFoundError`, `PublishTargetBindingError`, `WorkspaceAnalysisError`)
+
+## Install
+
+```bash
+pnpm add @savvy-web/silk-core effect @effected/workspaces
+```
+
+`effect` and `@effected/workspaces` are peer dependencies.
+
+## Usage
+
+```ts
+import { PrBody, SilkPublishConfig } from "@savvy-web/silk-core";
+import { Schema } from "effect";
+
+const config = Schema.decodeUnknownSync(SilkPublishConfig)({
+ access: "public",
+ targets: ["npm", "github"],
+});
+
+const body = PrBody.ManagedPrBody.build({
+ subject: "feat(silk-core): extract domain core",
+ linkedIssues: [PrBody.LinkedIssueRef.make({ number: 419, title: "Share the PR-body contract", state: "open" })],
+ signoff: "Signed-off-by: C. Spencer Beggs <spencer@savvyweb.systems>",
+ summary: "Extract the domain core.",
+});
+```
+
+Most consumers reach these symbols through `@savvy-web/silk-effects`, which re-exports the whole surface under the same names alongside the platform-backed services. Depend on `@savvy-web/silk-core` directly when you only need the data model.
+
+## License
+
+MIT

package/_virtual/_rolldown/runtime.js

@@ -0,0 +1,18 @@
+//#region \0rolldown/runtime.js
+var __defProp = Object.defineProperty;
+var __exportAll = (all, no_symbols) => {
+	let target = {};
+	for (var name in all) {
+		__defProp(target, name, {
+			get: all[name],
+			enumerable: true
+		});
+	}
+	if (!no_symbols) {
+		__defProp(target, Symbol.toStringTag, { value: "Module" });
+	}
+	return target;
+};
+
+//#endregion
+export { __exportAll };

package/errors/BiomeSyncError.js

@@ -0,0 +1,22 @@
+import { Data } from "effect";
+
+//#region src/errors/BiomeSyncError.ts
+/**
+* Raised when a Biome config file cannot be read or its `$schema` URL cannot be updated.
+*
+* @remarks
+* Returned by `BiomeSchemaSync.sync` and `BiomeSchemaSync.check` when
+* a `biome.json` or `biome.jsonc` file exists but cannot be read, contains invalid JSON,
+* or cannot be written back to disk.
+*
+* @since 0.1.0
+* @public
+*/
+var BiomeSyncError = class extends Data.TaggedError("BiomeSyncError") {
+	get message() {
+		return `Failed to sync biome schema in ${this.path}: ${this.reason}`;
+	}
+};
+
+//#endregion
+export { BiomeSyncError };

package/errors/ChangesetConfigError.js

@@ -0,0 +1,21 @@
+import { Data } from "effect";
+
+//#region src/errors/ChangesetConfigError.ts
+/**
+* Raised when the `.changeset/config.json` file cannot be read or decoded.
+*
+* @remarks
+* Returned by `ChangesetConfigReader.read` when the file is missing,
+* contains invalid JSON, or fails Effect Schema validation.
+*
+* @since 0.1.0
+* @public
+*/
+var ChangesetConfigError = class extends Data.TaggedError("ChangesetConfigError") {
+	get message() {
+		return `Failed to read changeset config at ${this.path}: ${this.reason}`;
+	}
+};
+
+//#endregion
+export { ChangesetConfigError };

package/errors/ConfigNotFoundError.js

@@ -0,0 +1,22 @@
+import { Data } from "effect";
+
+//#region src/errors/ConfigNotFoundError.ts
+/**
+* Raised when a config file cannot be located in any of the expected locations.
+*
+* @remarks
+* Returned by consumers that require a config file to exist. `ConfigDiscovery.find`
+* itself returns `null` instead of failing — callers that need a hard failure should
+* map `null` to this error.
+*
+* @since 0.1.0
+* @public
+*/
+var ConfigNotFoundError = class extends Data.TaggedError("ConfigNotFoundError") {
+	get message() {
+		return `Config '${this.name}' not found. Searched: ${this.searchedPaths.join(", ")}`;
+	}
+};
+
+//#endregion
+export { ConfigNotFoundError };

package/errors/PublishTargetBindingError.js

@@ -0,0 +1,30 @@
+import { Data } from "effect";
+
+//#region src/errors/PublishTargetBindingError.ts
+/**
+* Raised when publishability detection selects a directory that the package's
+* `dist/prod/targets.json` binding does not describe.
+*
+* @remarks
+* The bundler's prod build writes `targets.json` naming every byte-group
+* directory it produced. Once that binding exists it is authoritative: the only
+* directories whose bytes may be published are the ones it lists. A detector
+* that returns anything else — most often `publishConfig.directory` pointing at
+* a **dev** build, because silk mode was misdetected — is about to pack an
+* unresolved workspace manifest and ship it to a registry.
+*
+* That is the `yaml-effect@0.7.1` failure: detection picked `dist/dev/pkg`, the
+* dev manifest still carried `catalog:` specifiers, and the published package
+* was uninstallable (`EUNSUPPORTEDPROTOCOL`).
+*
+* @since 3.1.0
+* @public
+*/
+var PublishTargetBindingError = class extends Data.TaggedError("PublishTargetBindingError") {
+	get message() {
+		return `Package ${this.pkg} resolved publish directory "${this.directory}", which is not one of the directories bound by dist/prod/targets.json (${this.boundDirectories.join(", ")}). This means publishability detection did not select the prod build output — refusing to publish before packing an unresolved manifest.`;
+	}
+};
+
+//#endregion
+export { PublishTargetBindingError };

package/errors/WorkspaceAnalysisError.js

@@ -0,0 +1,22 @@
+import { Data } from "effect";
+
+//#region src/errors/WorkspaceAnalysisError.ts
+/**
+* Raised when workspace analysis fails for a given root directory.
+*
+* @remarks
+* Returned by `SilkWorkspaceAnalyzer.analyze` when the analysis pipeline
+* encounters an unrecoverable error — e.g. workspace discovery failure,
+* package manager detection failure, or publishability detection errors.
+*
+* @since 0.2.0
+* @public
+*/
+var WorkspaceAnalysisError = class extends Data.TaggedError("WorkspaceAnalysisError") {
+	get message() {
+		return `Workspace analysis failed at ${this.root}: ${this.reason}`;
+	}
+};
+
+//#endregion
+export { WorkspaceAnalysisError };