@savvy-web/silk 2.0.0 → 2.1.1

package/packages/silk-effects/dist/dev/pkg/changesets/schemas/options.cjs

@@ -1,183 +0,0 @@
-const require_errors = require('../errors.cjs');
-const require_version_files = require('./version-files.cjs');
-const require_package_scope = require('./package-scope.cjs');
-let effect = require("effect");
-
-//#region ../silk-effects/dist/dev/pkg/changesets/schemas/options.js
-/**
-* Changeset configuration option schemas and validation.
-*
-* @remarks
-* Defines the schema for the options object passed to the
-* \@savvy-web/changesets changelog formatter in `.changeset/config.json`.
-* The options are specified as the second element of the changelog array:
-*
-* ```json
-* {
-*   "changelog": ["@savvy-web/changesets/changelog", { "repo": "owner/repo" }]
-* }
-* ```
-*
-* @see {@link https://github.com/changesets/changesets/blob/main/docs/config-file-options.md | Changesets config docs}
-* @see {@link https://effect.website/docs/schema/introduction | Effect Schema documentation}
-*
-*/
-/** Regex for `owner/repo` format, shared between schema and validation. */
-const REPO_PATTERN = /^[a-zA-Z0-9._-]+\/[a-zA-Z0-9._-]+$/;
-/**
-* Schema for a GitHub repository in `owner/repo` format.
-*
-* @remarks
-* Validates that the string matches the `owner/repository` format used
-* by GitHub. Both the owner and repository segments accept alphanumeric
-* characters, dots, underscores, and hyphens.
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { RepoSchema } from "@savvy-web/changesets";
-*
-* // Succeeds
-* Schema.decodeUnknownSync(RepoSchema)("microsoft/vscode");
-*
-* // Throws ParseError — missing slash
-* Schema.decodeUnknownSync(RepoSchema)("vscode");
-* ```
-*
-* @see {@link ChangesetOptionsSchema} which uses this for the `repo` field
-*
-* @public
-*/
-const RepoSchema = effect.Schema.String.pipe(effect.Schema.pattern(REPO_PATTERN, { message: () => "Repository must be in format \"owner/repository\" (e.g., \"microsoft/vscode\")" }));
-/**
-* Schema for changeset configuration options.
-*
-* @remarks
-* The `repo` field is required; all other fields are optional with sensible
-* defaults applied by the changelog formatter at runtime.
-*
-* Two related fields describe release surfaces:
-*
-* - `packages` (new, recommended) — a record keyed by package name with
-*   per-package `additionalScopes` and `versionFiles`. This is the shape
-*   introduced in 0.9.0 and the only shape that will be accepted in 1.0.0.
-* - `versionFiles` (deprecated) — a flat array of entries each carrying
-*   their own `package` field. Still accepted in 0.9.0 with a deprecation
-*   warning emitted by `ConfigInspector` at config-load time; removed in
-*   1.0.0.
-*
-* A config that declares **both** `packages` and the deprecated
-* `versionFiles` field is rejected — the user must pick one.
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { ChangesetOptionsSchema } from "@savvy-web/changesets";
-* import type { ChangesetOptions } from "@savvy-web/changesets";
-*
-* // New per-package shape (recommended)
-* const opts: ChangesetOptions = Schema.decodeUnknownSync(ChangesetOptionsSchema)({
-*   repo: "savvy-web/changesets",
-*   packages: {
-*     "@savvy-web/changesets": {
-*       additionalScopes: ["plugin/**"],
-*       versionFiles: [{ glob: "plugin/.claude-plugin/plugin.json", paths: ["$.version"] }],
-*     },
-*   },
-* });
-* ```
-*
-* @see {@link ChangesetOptions} for the inferred TypeScript type
-* @see {@link validateChangesetOptions} for Effect-idiomatic validation with detailed error messages
-* @see {@link PackagesRecordSchema} for the new `packages` shape
-* @see {@link LegacyVersionFilesSchema} for the deprecated `versionFiles` shape
-*
-* @public
-*/
-const ChangesetOptionsSchema = effect.Schema.Struct({
-	/** GitHub repository in `owner/repo` format. */
-	repo: RepoSchema,
-	/** Whether to include commit hash links in output. */
-	commitLinks: effect.Schema.optional(effect.Schema.Boolean),
-	/** Whether to include pull request links in output. */
-	prLinks: effect.Schema.optional(effect.Schema.Boolean),
-	/** Whether to include issue reference links in output. */
-	issueLinks: effect.Schema.optional(effect.Schema.Boolean),
-	/** Custom issue reference prefixes (e.g., `["#", "GH-"]`). */
-	issuePrefixes: effect.Schema.optional(effect.Schema.Array(effect.Schema.String)),
-	/**
-	* Per-package release surfaces. Each entry declares `additionalScopes`
-	* (globs outside the workspace dir that belong to the package) and
-	* `versionFiles` (files bumped in lockstep with the package's version).
-	*/
-	packages: effect.Schema.optional(require_package_scope.PackagesRecordSchema),
-	/**
-	* DEPRECATED. Top-level flat array of version-file entries each with
-	* their own `package` field. Migrate to `packages[<name>].versionFiles`.
-	* Removed in 1.0.0.
-	*
-	* @deprecated 0.9.0 — migrate to `packages`. Removed in 1.0.0.
-	*/
-	versionFiles: effect.Schema.optional(require_version_files.LegacyVersionFilesSchema)
-}).pipe(effect.Schema.filter((opts) => opts.packages === void 0 || opts.versionFiles === void 0, { message: () => "Configuration cannot declare both `packages` and the deprecated top-level `versionFiles` array. Migrate the legacy `versionFiles` entries into `packages[<name>].versionFiles` and remove the top-level field." }));
-/**
-* Validate changeset options with Effect-idiomatic error handling.
-*
-* @remarks
-* Provides detailed, user-friendly error messages that match the prior art
-* from \@savvy-web/changelog. Performs manual pre-validation for `null`,
-* non-object, and missing `repo` before delegating to schema decoding.
-* This layered approach ensures that the most common misconfiguration
-* (missing `repo`) produces a clear, actionable message rather than a
-* generic schema parse error.
-*
-* @example
-* ```typescript
-* import { Effect } from "effect";
-* import { validateChangesetOptions, ConfigurationError } from "@savvy-web/changesets";
-*
-* const program = validateChangesetOptions({ repo: "savvy-web/changesets" }).pipe(
-* 	Effect.catchTag("ConfigurationError", (err) =>
-* 		Effect.logError(`Config invalid: ${err.message}`)
-* 	),
-* );
-*
-* Effect.runPromise(program);
-* ```
-*
-* @param input - Raw configuration input (typically from `.changeset/config.json`)
-* @returns An Effect that succeeds with decoded {@link ChangesetOptions} or fails with a {@link ConfigurationError}
-*
-* @see {@link ChangesetOptionsSchema} for the expected configuration shape
-* @see {@link ConfigurationError} for the error type produced on validation failure
-*
-* @public
-*/
-function validateChangesetOptions(input) {
-	if (input === null || input === void 0) return effect.Effect.fail(new require_errors.ConfigurationError({
-		field: "options",
-		reason: "Configuration is required. Add options to your changesets config:\n\"changelog\": [\"@savvy-web/changesets\", { \"repo\": \"owner/repository\" }]"
-	}));
-	if (typeof input !== "object") return effect.Effect.fail(new require_errors.ConfigurationError({
-		field: "options",
-		reason: "Configuration must be an object"
-	}));
-	const obj = input;
-	if (!("repo" in obj) || obj.repo === void 0) return effect.Effect.fail(new require_errors.ConfigurationError({
-		field: "repo",
-		reason: "Repository name is required. Add the \"repo\" option to your changesets config:\n\"changelog\": [\"@savvy-web/changesets\", { \"repo\": \"owner/repository\" }]"
-	}));
-	if (typeof obj.repo === "string" && !REPO_PATTERN.test(obj.repo)) return effect.Effect.fail(new require_errors.ConfigurationError({
-		field: "repo",
-		reason: `Invalid repository format: "${obj.repo}". Expected format is "owner/repository" (e.g., "microsoft/vscode")`
-	}));
-	return effect.Schema.decodeUnknown(ChangesetOptionsSchema)(input).pipe(effect.Effect.mapError((parseError) => new require_errors.ConfigurationError({
-		field: "options",
-		reason: String(parseError)
-	})));
-}
-
-//#endregion
-exports.ChangesetOptionsSchema = ChangesetOptionsSchema;
-exports.RepoSchema = RepoSchema;
-exports.validateChangesetOptions = validateChangesetOptions;

package/packages/silk-effects/dist/dev/pkg/changesets/schemas/options.js

@@ -1,181 +0,0 @@
-import { ConfigurationError } from "../errors.js";
-import { LegacyVersionFilesSchema } from "./version-files.js";
-import { PackagesRecordSchema } from "./package-scope.js";
-import { Effect, Schema } from "effect";
-
-//#region ../silk-effects/dist/dev/pkg/changesets/schemas/options.js
-/**
-* Changeset configuration option schemas and validation.
-*
-* @remarks
-* Defines the schema for the options object passed to the
-* \@savvy-web/changesets changelog formatter in `.changeset/config.json`.
-* The options are specified as the second element of the changelog array:
-*
-* ```json
-* {
-*   "changelog": ["@savvy-web/changesets/changelog", { "repo": "owner/repo" }]
-* }
-* ```
-*
-* @see {@link https://github.com/changesets/changesets/blob/main/docs/config-file-options.md | Changesets config docs}
-* @see {@link https://effect.website/docs/schema/introduction | Effect Schema documentation}
-*
-*/
-/** Regex for `owner/repo` format, shared between schema and validation. */
-const REPO_PATTERN = /^[a-zA-Z0-9._-]+\/[a-zA-Z0-9._-]+$/;
-/**
-* Schema for a GitHub repository in `owner/repo` format.
-*
-* @remarks
-* Validates that the string matches the `owner/repository` format used
-* by GitHub. Both the owner and repository segments accept alphanumeric
-* characters, dots, underscores, and hyphens.
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { RepoSchema } from "@savvy-web/changesets";
-*
-* // Succeeds
-* Schema.decodeUnknownSync(RepoSchema)("microsoft/vscode");
-*
-* // Throws ParseError — missing slash
-* Schema.decodeUnknownSync(RepoSchema)("vscode");
-* ```
-*
-* @see {@link ChangesetOptionsSchema} which uses this for the `repo` field
-*
-* @public
-*/
-const RepoSchema = Schema.String.pipe(Schema.pattern(REPO_PATTERN, { message: () => "Repository must be in format \"owner/repository\" (e.g., \"microsoft/vscode\")" }));
-/**
-* Schema for changeset configuration options.
-*
-* @remarks
-* The `repo` field is required; all other fields are optional with sensible
-* defaults applied by the changelog formatter at runtime.
-*
-* Two related fields describe release surfaces:
-*
-* - `packages` (new, recommended) — a record keyed by package name with
-*   per-package `additionalScopes` and `versionFiles`. This is the shape
-*   introduced in 0.9.0 and the only shape that will be accepted in 1.0.0.
-* - `versionFiles` (deprecated) — a flat array of entries each carrying
-*   their own `package` field. Still accepted in 0.9.0 with a deprecation
-*   warning emitted by `ConfigInspector` at config-load time; removed in
-*   1.0.0.
-*
-* A config that declares **both** `packages` and the deprecated
-* `versionFiles` field is rejected — the user must pick one.
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { ChangesetOptionsSchema } from "@savvy-web/changesets";
-* import type { ChangesetOptions } from "@savvy-web/changesets";
-*
-* // New per-package shape (recommended)
-* const opts: ChangesetOptions = Schema.decodeUnknownSync(ChangesetOptionsSchema)({
-*   repo: "savvy-web/changesets",
-*   packages: {
-*     "@savvy-web/changesets": {
-*       additionalScopes: ["plugin/**"],
-*       versionFiles: [{ glob: "plugin/.claude-plugin/plugin.json", paths: ["$.version"] }],
-*     },
-*   },
-* });
-* ```
-*
-* @see {@link ChangesetOptions} for the inferred TypeScript type
-* @see {@link validateChangesetOptions} for Effect-idiomatic validation with detailed error messages
-* @see {@link PackagesRecordSchema} for the new `packages` shape
-* @see {@link LegacyVersionFilesSchema} for the deprecated `versionFiles` shape
-*
-* @public
-*/
-const ChangesetOptionsSchema = Schema.Struct({
-	/** GitHub repository in `owner/repo` format. */
-	repo: RepoSchema,
-	/** Whether to include commit hash links in output. */
-	commitLinks: Schema.optional(Schema.Boolean),
-	/** Whether to include pull request links in output. */
-	prLinks: Schema.optional(Schema.Boolean),
-	/** Whether to include issue reference links in output. */
-	issueLinks: Schema.optional(Schema.Boolean),
-	/** Custom issue reference prefixes (e.g., `["#", "GH-"]`). */
-	issuePrefixes: Schema.optional(Schema.Array(Schema.String)),
-	/**
-	* Per-package release surfaces. Each entry declares `additionalScopes`
-	* (globs outside the workspace dir that belong to the package) and
-	* `versionFiles` (files bumped in lockstep with the package's version).
-	*/
-	packages: Schema.optional(PackagesRecordSchema),
-	/**
-	* DEPRECATED. Top-level flat array of version-file entries each with
-	* their own `package` field. Migrate to `packages[<name>].versionFiles`.
-	* Removed in 1.0.0.
-	*
-	* @deprecated 0.9.0 — migrate to `packages`. Removed in 1.0.0.
-	*/
-	versionFiles: Schema.optional(LegacyVersionFilesSchema)
-}).pipe(Schema.filter((opts) => opts.packages === void 0 || opts.versionFiles === void 0, { message: () => "Configuration cannot declare both `packages` and the deprecated top-level `versionFiles` array. Migrate the legacy `versionFiles` entries into `packages[<name>].versionFiles` and remove the top-level field." }));
-/**
-* Validate changeset options with Effect-idiomatic error handling.
-*
-* @remarks
-* Provides detailed, user-friendly error messages that match the prior art
-* from \@savvy-web/changelog. Performs manual pre-validation for `null`,
-* non-object, and missing `repo` before delegating to schema decoding.
-* This layered approach ensures that the most common misconfiguration
-* (missing `repo`) produces a clear, actionable message rather than a
-* generic schema parse error.
-*
-* @example
-* ```typescript
-* import { Effect } from "effect";
-* import { validateChangesetOptions, ConfigurationError } from "@savvy-web/changesets";
-*
-* const program = validateChangesetOptions({ repo: "savvy-web/changesets" }).pipe(
-* 	Effect.catchTag("ConfigurationError", (err) =>
-* 		Effect.logError(`Config invalid: ${err.message}`)
-* 	),
-* );
-*
-* Effect.runPromise(program);
-* ```
-*
-* @param input - Raw configuration input (typically from `.changeset/config.json`)
-* @returns An Effect that succeeds with decoded {@link ChangesetOptions} or fails with a {@link ConfigurationError}
-*
-* @see {@link ChangesetOptionsSchema} for the expected configuration shape
-* @see {@link ConfigurationError} for the error type produced on validation failure
-*
-* @public
-*/
-function validateChangesetOptions(input) {
-	if (input === null || input === void 0) return Effect.fail(new ConfigurationError({
-		field: "options",
-		reason: "Configuration is required. Add options to your changesets config:\n\"changelog\": [\"@savvy-web/changesets\", { \"repo\": \"owner/repository\" }]"
-	}));
-	if (typeof input !== "object") return Effect.fail(new ConfigurationError({
-		field: "options",
-		reason: "Configuration must be an object"
-	}));
-	const obj = input;
-	if (!("repo" in obj) || obj.repo === void 0) return Effect.fail(new ConfigurationError({
-		field: "repo",
-		reason: "Repository name is required. Add the \"repo\" option to your changesets config:\n\"changelog\": [\"@savvy-web/changesets\", { \"repo\": \"owner/repository\" }]"
-	}));
-	if (typeof obj.repo === "string" && !REPO_PATTERN.test(obj.repo)) return Effect.fail(new ConfigurationError({
-		field: "repo",
-		reason: `Invalid repository format: "${obj.repo}". Expected format is "owner/repository" (e.g., "microsoft/vscode")`
-	}));
-	return Schema.decodeUnknown(ChangesetOptionsSchema)(input).pipe(Effect.mapError((parseError) => new ConfigurationError({
-		field: "options",
-		reason: String(parseError)
-	})));
-}
-
-//#endregion
-export { ChangesetOptionsSchema, RepoSchema, validateChangesetOptions };

package/packages/silk-effects/dist/dev/pkg/changesets/schemas/package-scope.cjs

@@ -1,129 +0,0 @@
-const require_version_files = require('./version-files.cjs');
-let effect = require("effect");
-
-//#region ../silk-effects/dist/dev/pkg/changesets/schemas/package-scope.js
-/**
-* Schemas for the per-package release-surface configuration introduced in
-* \@savvy-web/changesets 0.9.0.
-*
-* @remarks
-* A `PackageScope` is the value side of the `packages` record on the
-* \@savvy-web/changesets changelog options. It tells the formatter which
-* non-workspace paths belong to a package's release surface (via
-* `additionalScopes`) and which files have their version fields bumped in
-* lockstep with the package (via `versionFiles`).
-*
-* ```jsonc
-* "changelog": [
-*   "@savvy-web/changesets/changelog",
-*   {
-*     "repo": "savvy-web/changesets",
-*     "packages": {
-*       "@savvy-web/changesets": {
-*         "additionalScopes": ["plugin/**"],
-*         "versionFiles": [
-*           { "glob": "plugin/.claude-plugin/plugin.json",
-*             "paths": ["$.version"] }
-*         ]
-*       }
-*     }
-*   }
-* ]
-* ```
-*
-* Validation contracts that span multiple packages (no-overlap rules for
-* `additionalScopes`, no glob+path conflicts in `versionFiles`, unknown
-* package keys) are enforced by `ConfigInspector` at load time, not at the
-* schema level — schemas only validate per-entry shape.
-*
-* @see {@link ChangesetOptionsSchema} for the consuming options shape
-* @see {@link VersionFileConfigSchema} for the version-file entry shape
-* @see {@link https://effect.website/docs/schema/introduction | Effect Schema documentation}
-*
-*/
-/**
-* Schema for a single repo-relative glob pattern.
-*
-* @remarks
-* Globs in `additionalScopes` must be repo-relative — absolute paths and
-* parent traversal (`../`) are rejected outright because they cannot be
-* meaningfully resolved against the project workspace. Negation patterns
-* (`!path/**`) are accepted; minimatch handles them at match time.
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { GlobSchema } from "@savvy-web/changesets";
-*
-* Schema.decodeUnknownSync(GlobSchema)("plugin/**");          // ok
-* Schema.decodeUnknownSync(GlobSchema)("!plugin/cache/**");   // ok (negation)
-* Schema.decodeUnknownSync(GlobSchema)("/absolute/path");     // throws
-* Schema.decodeUnknownSync(GlobSchema)("../sibling/**");      // throws
-* ```
-*
-* @public
-*/
-const GlobSchema = effect.Schema.String.pipe(effect.Schema.minLength(1), effect.Schema.filter((s) => !s.startsWith("/") && !s.startsWith("../") && !s.includes("/../"), { message: () => "Glob must be repo-relative — absolute paths and parent traversal (../) are not allowed" }));
-/**
-* Schema for a single entry in the `packages` record — the per-package
-* release-surface declaration.
-*
-* @remarks
-* Both fields are optional. An empty object (`{}`) is a valid PackageScope
-* and means "this package uses only its workspace directory as its release
-* surface."
-*
-* - `additionalScopes` — repo-relative globs naming files outside the
-*   package's workspace directory that belong to the package's release
-*   surface. The contract is "a path belongs to exactly one package" — if
-*   two packages declare overlapping additionalScopes, the config is
-*   rejected by `ConfigInspector`.
-* - `versionFiles` — files whose JSON fields are bumped in lockstep with
-*   this package's version. Each entry uses the new {@link VersionFileConfigSchema}
-*   shape (no `package` field; the parent record key names the owner).
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { PackageScopeSchema } from "@savvy-web/changesets";
-*
-* const scope = Schema.decodeUnknownSync(PackageScopeSchema)({
-*   additionalScopes: ["plugin/**", "!plugin/.cache/**"],
-*   versionFiles: [
-*     { glob: "plugin/.claude-plugin/plugin.json", paths: ["$.version"] },
-*   ],
-* });
-* ```
-*
-* @see {@link PackageScope} for the inferred TypeScript type
-* @see {@link GlobSchema} for individual glob validation rules
-* @see {@link VersionFileConfigSchema} for the version-file entry shape
-*
-* @public
-*/
-const PackageScopeSchema = effect.Schema.Struct({
-	/** Repo-relative globs naming files outside the package's workspace directory that belong to its release surface. */
-	additionalScopes: effect.Schema.optional(effect.Schema.Array(GlobSchema)),
-	/** Files whose JSON fields are bumped in lockstep with this package's version. */
-	versionFiles: effect.Schema.optional(effect.Schema.Array(require_version_files.VersionFileConfigSchema))
-});
-/**
-* Schema for the `packages` record on the changelog options.
-*
-* @remarks
-* Keys are package names. The schema itself does not validate that keys
-* resolve to known workspace packages — that check is performed by
-* `ConfigInspector` at config-load time, where `WorkspaceDiscovery` is
-* available to enumerate the workspace.
-*
-* @public
-*/
-const PackagesRecordSchema = effect.Schema.Record({
-	key: effect.Schema.String,
-	value: PackageScopeSchema
-});
-
-//#endregion
-exports.GlobSchema = GlobSchema;
-exports.PackageScopeSchema = PackageScopeSchema;
-exports.PackagesRecordSchema = PackagesRecordSchema;

package/packages/silk-effects/dist/dev/pkg/changesets/schemas/package-scope.js

@@ -1,127 +0,0 @@
-import { VersionFileConfigSchema } from "./version-files.js";
-import { Schema } from "effect";
-
-//#region ../silk-effects/dist/dev/pkg/changesets/schemas/package-scope.js
-/**
-* Schemas for the per-package release-surface configuration introduced in
-* \@savvy-web/changesets 0.9.0.
-*
-* @remarks
-* A `PackageScope` is the value side of the `packages` record on the
-* \@savvy-web/changesets changelog options. It tells the formatter which
-* non-workspace paths belong to a package's release surface (via
-* `additionalScopes`) and which files have their version fields bumped in
-* lockstep with the package (via `versionFiles`).
-*
-* ```jsonc
-* "changelog": [
-*   "@savvy-web/changesets/changelog",
-*   {
-*     "repo": "savvy-web/changesets",
-*     "packages": {
-*       "@savvy-web/changesets": {
-*         "additionalScopes": ["plugin/**"],
-*         "versionFiles": [
-*           { "glob": "plugin/.claude-plugin/plugin.json",
-*             "paths": ["$.version"] }
-*         ]
-*       }
-*     }
-*   }
-* ]
-* ```
-*
-* Validation contracts that span multiple packages (no-overlap rules for
-* `additionalScopes`, no glob+path conflicts in `versionFiles`, unknown
-* package keys) are enforced by `ConfigInspector` at load time, not at the
-* schema level — schemas only validate per-entry shape.
-*
-* @see {@link ChangesetOptionsSchema} for the consuming options shape
-* @see {@link VersionFileConfigSchema} for the version-file entry shape
-* @see {@link https://effect.website/docs/schema/introduction | Effect Schema documentation}
-*
-*/
-/**
-* Schema for a single repo-relative glob pattern.
-*
-* @remarks
-* Globs in `additionalScopes` must be repo-relative — absolute paths and
-* parent traversal (`../`) are rejected outright because they cannot be
-* meaningfully resolved against the project workspace. Negation patterns
-* (`!path/**`) are accepted; minimatch handles them at match time.
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { GlobSchema } from "@savvy-web/changesets";
-*
-* Schema.decodeUnknownSync(GlobSchema)("plugin/**");          // ok
-* Schema.decodeUnknownSync(GlobSchema)("!plugin/cache/**");   // ok (negation)
-* Schema.decodeUnknownSync(GlobSchema)("/absolute/path");     // throws
-* Schema.decodeUnknownSync(GlobSchema)("../sibling/**");      // throws
-* ```
-*
-* @public
-*/
-const GlobSchema = Schema.String.pipe(Schema.minLength(1), Schema.filter((s) => !s.startsWith("/") && !s.startsWith("../") && !s.includes("/../"), { message: () => "Glob must be repo-relative — absolute paths and parent traversal (../) are not allowed" }));
-/**
-* Schema for a single entry in the `packages` record — the per-package
-* release-surface declaration.
-*
-* @remarks
-* Both fields are optional. An empty object (`{}`) is a valid PackageScope
-* and means "this package uses only its workspace directory as its release
-* surface."
-*
-* - `additionalScopes` — repo-relative globs naming files outside the
-*   package's workspace directory that belong to the package's release
-*   surface. The contract is "a path belongs to exactly one package" — if
-*   two packages declare overlapping additionalScopes, the config is
-*   rejected by `ConfigInspector`.
-* - `versionFiles` — files whose JSON fields are bumped in lockstep with
-*   this package's version. Each entry uses the new {@link VersionFileConfigSchema}
-*   shape (no `package` field; the parent record key names the owner).
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { PackageScopeSchema } from "@savvy-web/changesets";
-*
-* const scope = Schema.decodeUnknownSync(PackageScopeSchema)({
-*   additionalScopes: ["plugin/**", "!plugin/.cache/**"],
-*   versionFiles: [
-*     { glob: "plugin/.claude-plugin/plugin.json", paths: ["$.version"] },
-*   ],
-* });
-* ```
-*
-* @see {@link PackageScope} for the inferred TypeScript type
-* @see {@link GlobSchema} for individual glob validation rules
-* @see {@link VersionFileConfigSchema} for the version-file entry shape
-*
-* @public
-*/
-const PackageScopeSchema = Schema.Struct({
-	/** Repo-relative globs naming files outside the package's workspace directory that belong to its release surface. */
-	additionalScopes: Schema.optional(Schema.Array(GlobSchema)),
-	/** Files whose JSON fields are bumped in lockstep with this package's version. */
-	versionFiles: Schema.optional(Schema.Array(VersionFileConfigSchema))
-});
-/**
-* Schema for the `packages` record on the changelog options.
-*
-* @remarks
-* Keys are package names. The schema itself does not validate that keys
-* resolve to known workspace packages — that check is performed by
-* `ConfigInspector` at config-load time, where `WorkspaceDiscovery` is
-* available to enumerate the workspace.
-*
-* @public
-*/
-const PackagesRecordSchema = Schema.Record({
-	key: Schema.String,
-	value: PackageScopeSchema
-});
-
-//#endregion
-export { GlobSchema, PackageScopeSchema, PackagesRecordSchema };