npm - @savvy-web/silk - Versions diffs - 3.7.3 → 3.7.5 - Mend

@savvy-web/silk 3.7.3 → 3.7.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (10) hide show

package/changesets-changelog.cjs +302 -100
package/changesets-changelog.d.cts +105 -12
package/changesets-changelog.d.ts +105 -12
package/changesets-changelog.js +303 -100
package/changesets-markdownlint.cjs +302 -100
package/changesets-markdownlint.d.cts +105 -12
package/changesets-markdownlint.d.ts +105 -12
package/changesets-markdownlint.js +303 -100
package/package.json +4 -4
package/tsconfig/node/dist/tsconfig.tsbuildinfo +0 -1

package/changesets-markdownlint.d.cts CHANGED Viewed

@@ -3298,7 +3298,7 @@ type Label = Label$1;
 type Severity = Severity$1;
 type Plugin<Tree extends Node$3 = Node$3, Option extends unknown = unknown> = (config?: [level: Label | Severity | boolean, option?: Option] | Label | Option | Severity) => ((tree: Tree, file: VFile, next: TransformCallback<Tree>) => undefined) | undefined;
 //#endregion
-//#region ../../node_modules/.pnpm/@effected+git@0.7.0_effect@4.0.0-beta.107/node_modules/@effected/git/index.d.ts
+//#region ../../node_modules/.pnpm/@effected+git@0.8.0_effect@4.0.0-beta.107/node_modules/@effected/git/index.d.ts
 //#region src/Git.d.ts
 declare const GitCommandError_base: Schema.Class<GitCommandError, Schema.TaggedStruct<"GitCommandError", {
   /**
@@ -3751,8 +3751,28 @@ interface GitShape {
   }) => Effect.Effect<ReadonlyArray<LsTreeEntry>, GitCommandError | NotARepositoryError | UnknownRefError>;
   /** `git cat-file -e <ref>` — whether `ref` resolves to an existing object. */
   readonly refExists: (cwd: string, ref: string) => Effect.Effect<boolean, GitCommandError | NotARepositoryError>;
-  /** `git merge-base <a> <b>` — the best common ancestor commit, trimmed. */
+  /**
+   * `git merge-base <a> <b>` — the best common ancestor commit, trimmed.
+   * For when absence is EXCEPTIONAL: two refs with no common ancestor fail
+   * loudly as `GitCommandError` (git's silent exit 1 rides the generic
+   * failure arm). When "no common ancestor" is a legitimate answer at your
+   * call site — a reachability probe — use `mergeBaseOption` instead.
+   */
   readonly mergeBase: (cwd: string, a: string, b: string) => Effect.Effect<string, GitCommandError | NotARepositoryError | UnknownRefError>;
+  /**
+   * `git merge-base <a> <b>` — the best common ancestor commit, trimmed, as
+   * a PROBE: two refs with no common ancestor (disjoint histories — a
+   * grafted CI clone, an orphan branch) answer `Option.none`, never an
+   * error, because git signals that case as a silent exit 1. An unknown ref
+   * is still a real failure (`UnknownRefError`), and a noisy exit 1 stays a
+   * loud `GitCommandError`. The sibling of `mergeBase`, which fails loudly
+   * when the ancestor is absent.
+   *
+   * The value is a plain sha string — no decode or brand step. A caller
+   * that only wants reachability ("do these histories connect?") reads the
+   * boolean directly: `Option.isSome(yield* git.mergeBaseOption(cwd, a, b))`.
+   */
+  readonly mergeBaseOption: (cwd: string, a: string, b: string) => Effect.Effect<Option.Option<string>, GitCommandError | NotARepositoryError | UnknownRefError>;
   /**
    * `git diff --name-only -z [--relative] <base>...<head>` — the paths that
    * differ. Pass `relative: true` to report paths relative to `cwd` and
@@ -3789,18 +3809,33 @@ interface GitShape {
     readonly detach?: boolean;
   }) => Effect.Effect<void, GitCommandError | NotARepositoryError | UnknownRefError>;
   /**
-   * Mutating: `git fetch [--depth <n>] <remote> [tag] <ref>` — fetches
-   * `options.ref` from `options.remote` (default `origin`) into the local
-   * object database, optionally shallow (`options.depth`) and/or as a tag
-   * (`options.tag`). A ref the remote does not have surfaces as
-   * `UnknownRefError` — the typed signal a tag-then-branch fetch fallback
-   * can branch on.
+   * Mutating: `git fetch [--depth <n>] [--unshallow] <remote> [tag] <ref>` —
+   * fetches `options.ref` from `options.remote` (default `origin`) into the
+   * local object database, optionally shallow (`options.depth`), unshallowing
+   * (`options.unshallow`), and/or as a tag (`options.tag`). A ref the remote
+   * does not have surfaces as `UnknownRefError` — the typed signal a
+   * tag-then-branch fetch fallback can branch on.
+   *
+   * `options.ref` also accepts a full refspec (`src:dst`, optionally
+   * `+`-prefixed), passed through verbatim — never guessed at or
+   * transformed. Under a single-branch clone (`actions/checkout`'s default
+   * `fetch-depth: 1` shape) a bare-ref fetch updates only `FETCH_HEAD` and
+   * never creates the remote-tracking ref, so
+   * `+refs/heads/<b>:refs/remotes/origin/<b>` is the spelling that
+   * materializes `origin/<b>`.
+   *
+   * `options.unshallow` follows `fetchUnshallow`'s caller-guards rule: git
+   * rejects `--unshallow` in a non-shallow repository (a loud
+   * `GitCommandError`, deliberately untolerated) — probe with `isShallow`
+   * first. Combining it with `options.depth` is refused typed, pre-spawn,
+   * exactly as git itself would reject the pair.
    */
   readonly fetch: (cwd: string, options: {
     readonly ref: string;
     readonly remote?: string;
     readonly depth?: number;
     readonly tag?: boolean;
+    readonly unshallow?: boolean;
   }) => Effect.Effect<void, GitCommandError | NotARepositoryError | UnknownRefError>;
   /**
    * Mutating: fetches `options.ref` from `options.remote` (default
@@ -3856,6 +3891,11 @@ interface GitShape {
    * a reset that silently did nothing would hand a retry of a
    * non-idempotent operation the same dirty tree. `mode` defaults to
    * `"mixed"` (git's own default), emitted explicitly in the argv.
+   *
+   * `mode: "hard"` is destructive and legitimately reached for: after
+   * committing through an out-of-band channel (e.g. the GitHub Data API,
+   * which writes the commit server-side), `reset --hard origin/<branch>`
+   * is how the local tree is synchronized to the commit it never made.
    */
   readonly reset: (cwd: string, options?: {
     readonly mode?: "soft" | "mixed" | "hard";
@@ -3929,15 +3969,30 @@ interface GitShape {
     readonly force?: boolean;
   }) => Effect.Effect<void, GitCommandError | NotARepositoryError | UnknownRefError>;
   /**
-   * Mutating: `git submodule update [--init] [--depth <n>] [-- <paths>...]`
+   * Mutating:
+   * `git submodule update [--init] [--checkout] [--remote] [--no-fetch] [--recursive] [--force] [--depth <n>] [-- <paths>...]`
    * — updates registered submodules in the working tree, optionally
    * initializing them (`options.init`), with an optional depth limit and
    * scoped to `options.paths`.
+   *
+   * `options.checkout` is the documented override for a
+   * `submodule.<name>.update = none` configuration — without it, updating
+   * such a submodule silently no-ops (git reports success and checks out
+   * nothing). `options.fetch` accepts only the literal `false` (emitting
+   * `--no-fetch`): the default already fetches and git has no positive
+   * spelling. `options.remote` tracks the remote branch's tip instead of
+   * the recorded sha; `options.recursive` descends into nested submodules;
+   * `options.force` discards local changes in the submodule working tree.
    */
   readonly submoduleUpdate: (cwd: string, options?: {
     readonly init?: boolean;
     readonly depth?: number;
     readonly paths?: ReadonlyArray<string>;
+    readonly checkout?: boolean;
+    readonly remote?: boolean;
+    readonly fetch?: false;
+    readonly recursive?: boolean;
+    readonly force?: boolean;
   }) => Effect.Effect<void, GitCommandError | NotARepositoryError | UnknownRefError>;
   /**
    * Mutating: `git submodule add [--depth <n>] -- <url> <path>` —
@@ -4310,6 +4365,28 @@ interface GitShape {
     readonly file?: string;
     readonly all?: boolean;
   }) => Effect.Effect<void, GitCommandError | NotARepositoryError | UnknownRefError>;
+  /**
+   * Mutating: `git config [-f <file>] --remove-section <section>` — removes
+   * a whole configuration section (every key under it, and the header) from
+   * the live config, or from `options.file`. The section-level sibling of
+   * `configUnset` — clearing a stale `submodule.<name>` registration is one
+   * invocation instead of a key-by-key probe-and-unset. Removing a section
+   * that does not exist fails LOUDLY (git exits 128,
+   * `fatal: no such section`) — the `configUnset` posture; probe with
+   * `configList` first when idempotency is wanted.
+   */
+  readonly configRemoveSection: (cwd: string, section: string, options?: {
+    readonly file?: string;
+  }) => Effect.Effect<void, GitCommandError | NotARepositoryError | UnknownRefError>;
+  /**
+   * Mutating: `git config [-f <file>] --rename-section <old> <new>` —
+   * renames a configuration section, carrying every key under it across.
+   * Renaming a section that does not exist fails LOUDLY (git exits 128,
+   * `fatal: no such section`) — the same posture as `configRemoveSection`.
+   */
+  readonly configRenameSection: (cwd: string, oldName: string, newName: string, options?: {
+    readonly file?: string;
+  }) => Effect.Effect<void, GitCommandError | NotARepositoryError | UnknownRefError>;
   /**
    * Mutating: `git rm [--cached] [-r] [--force] -- <paths...>` — removes
    * `paths` from the index and (without `options.cached`) the working tree.
@@ -6162,7 +6239,7 @@ declare class LockfileIntegrity extends LockfileIntegrity_base {
   static compare(lockfile: Lockfile, manifests: ReadonlyArray<WorkspaceManifest>): LockfileIntegrity;
 }
 //#endregion
-//#region ../../node_modules/.pnpm/@effected+package-json@0.8.0_effect@4.0.0-beta.107/node_modules/@effected/package-json/index.d.ts
+//#region ../../node_modules/.pnpm/@effected+package-json@0.9.0_effect@4.0.0-beta.107/node_modules/@effected/package-json/index.d.ts
 //#region src/Dependency.d.ts
 declare const Dependency_base: Schema.Class<Dependency, Schema.Struct<{
   /** The package name. */
@@ -6744,7 +6821,7 @@ declare class Package extends Package_base {
   toJsonString(options?: PackageFormatOptions): string;
 }
 //#endregion
-//#region ../../node_modules/.pnpm/@effected+workspaces@0.12.0_@effected+jsonc@0.6.0_effect@4.0.0-beta.107__effect@4.0.0-beta.107/node_modules/@effected/workspaces/index.d.ts
+//#region ../../node_modules/.pnpm/@effected+workspaces@0.13.0_@effected+jsonc@0.6.0_effect@4.0.0-beta.107__effect@4.0.0-beta.107/node_modules/@effected/workspaces/index.d.ts
 //#region src/WorkspacePackage.d.ts
 declare const PublishConfig_base: Schema.Class<PublishConfig, Schema.Struct<{
   /** Scoped-package visibility. Its presence overrides `private`. */
@@ -7571,6 +7648,8 @@ declare const DetectedPackageManager_base: Schema.Class<DetectedPackageManager,
   readonly version: Schema.Option<Schema.String>;
   /** The JavaScript runtime the manager implies. */
   readonly runtime: Schema.Literals<readonly ["node", "bun"]>;
+  /** The rung of the priority order that decided the name. */
+  readonly evidence: Schema.Literals<readonly ["pnpm-workspace.yaml", "bun.lock", "bun.lockb", "yarn.lock", "package.json#workspaces", "pnpm-lock.yaml", "package-lock.json", "package.json#devEngines.packageManager", "package.json#packageManager"]>;
 }>, {}>;
 /**
  * The outcome of package-manager detection at a workspace root.
@@ -7583,6 +7662,15 @@ declare const DetectedPackageManager_base: Schema.Class<DetectedPackageManager,
  * `devEngines.packageManager`; see {@link PackageManagerDetector} for the
  * precedence between them.
  *
+ * `evidence` is the rung of the priority order that decided the **name** — the
+ * verdict's provenance, in the same vocabulary the failure path reports as
+ * `PackageManagerDetectionError.checked`. For the bun and yarn rungs the
+ * lockfile is the recorded signal even though the rung is a conjunction (the
+ * lockfile *plus* a manifest field naming the manager): the manifest field alone
+ * would have resolved in the declaration tier, so the lockfile is what this rung
+ * added. The version's provenance is deliberately not carried — it follows the
+ * two-field precedence above, which is a rule, not a probe.
+ *
  * @public
  */
 declare class DetectedPackageManager extends DetectedPackageManager_base {}
@@ -7704,7 +7792,12 @@ declare class PackageManagerDetector extends PackageManagerDetector_base {
    * const TestDetector = PackageManagerDetector.layerTest({
    *   detect: () =>
    *     Effect.succeed(
-   *       DetectedPackageManager.make({ name: "pnpm", version: Option.none(), runtime: "node" }),
+   *       DetectedPackageManager.make({
+   *         name: "pnpm",
+   *         version: Option.none(),
+   *         runtime: "node",
+   *         evidence: "pnpm-workspace.yaml",
+   *       }),
    *     ),
    * });
    * ```

package/changesets-markdownlint.d.ts CHANGED Viewed

@@ -3298,7 +3298,7 @@ type Label = Label$1;
 type Severity = Severity$1;
 type Plugin<Tree extends Node$3 = Node$3, Option extends unknown = unknown> = (config?: [level: Label | Severity | boolean, option?: Option] | Label | Option | Severity) => ((tree: Tree, file: VFile, next: TransformCallback<Tree>) => undefined) | undefined;
 //#endregion
-//#region ../../node_modules/.pnpm/@effected+git@0.7.0_effect@4.0.0-beta.107/node_modules/@effected/git/index.d.ts
+//#region ../../node_modules/.pnpm/@effected+git@0.8.0_effect@4.0.0-beta.107/node_modules/@effected/git/index.d.ts
 //#region src/Git.d.ts
 declare const GitCommandError_base: Schema.Class<GitCommandError, Schema.TaggedStruct<"GitCommandError", {
   /**
@@ -3751,8 +3751,28 @@ interface GitShape {
   }) => Effect.Effect<ReadonlyArray<LsTreeEntry>, GitCommandError | NotARepositoryError | UnknownRefError>;
   /** `git cat-file -e <ref>` — whether `ref` resolves to an existing object. */
   readonly refExists: (cwd: string, ref: string) => Effect.Effect<boolean, GitCommandError | NotARepositoryError>;
-  /** `git merge-base <a> <b>` — the best common ancestor commit, trimmed. */
+  /**
+   * `git merge-base <a> <b>` — the best common ancestor commit, trimmed.
+   * For when absence is EXCEPTIONAL: two refs with no common ancestor fail
+   * loudly as `GitCommandError` (git's silent exit 1 rides the generic
+   * failure arm). When "no common ancestor" is a legitimate answer at your
+   * call site — a reachability probe — use `mergeBaseOption` instead.
+   */
   readonly mergeBase: (cwd: string, a: string, b: string) => Effect.Effect<string, GitCommandError | NotARepositoryError | UnknownRefError>;
+  /**
+   * `git merge-base <a> <b>` — the best common ancestor commit, trimmed, as
+   * a PROBE: two refs with no common ancestor (disjoint histories — a
+   * grafted CI clone, an orphan branch) answer `Option.none`, never an
+   * error, because git signals that case as a silent exit 1. An unknown ref
+   * is still a real failure (`UnknownRefError`), and a noisy exit 1 stays a
+   * loud `GitCommandError`. The sibling of `mergeBase`, which fails loudly
+   * when the ancestor is absent.
+   *
+   * The value is a plain sha string — no decode or brand step. A caller
+   * that only wants reachability ("do these histories connect?") reads the
+   * boolean directly: `Option.isSome(yield* git.mergeBaseOption(cwd, a, b))`.
+   */
+  readonly mergeBaseOption: (cwd: string, a: string, b: string) => Effect.Effect<Option.Option<string>, GitCommandError | NotARepositoryError | UnknownRefError>;
   /**
    * `git diff --name-only -z [--relative] <base>...<head>` — the paths that
    * differ. Pass `relative: true` to report paths relative to `cwd` and
@@ -3789,18 +3809,33 @@ interface GitShape {
     readonly detach?: boolean;
   }) => Effect.Effect<void, GitCommandError | NotARepositoryError | UnknownRefError>;
   /**
-   * Mutating: `git fetch [--depth <n>] <remote> [tag] <ref>` — fetches
-   * `options.ref` from `options.remote` (default `origin`) into the local
-   * object database, optionally shallow (`options.depth`) and/or as a tag
-   * (`options.tag`). A ref the remote does not have surfaces as
-   * `UnknownRefError` — the typed signal a tag-then-branch fetch fallback
-   * can branch on.
+   * Mutating: `git fetch [--depth <n>] [--unshallow] <remote> [tag] <ref>` —
+   * fetches `options.ref` from `options.remote` (default `origin`) into the
+   * local object database, optionally shallow (`options.depth`), unshallowing
+   * (`options.unshallow`), and/or as a tag (`options.tag`). A ref the remote
+   * does not have surfaces as `UnknownRefError` — the typed signal a
+   * tag-then-branch fetch fallback can branch on.
+   *
+   * `options.ref` also accepts a full refspec (`src:dst`, optionally
+   * `+`-prefixed), passed through verbatim — never guessed at or
+   * transformed. Under a single-branch clone (`actions/checkout`'s default
+   * `fetch-depth: 1` shape) a bare-ref fetch updates only `FETCH_HEAD` and
+   * never creates the remote-tracking ref, so
+   * `+refs/heads/<b>:refs/remotes/origin/<b>` is the spelling that
+   * materializes `origin/<b>`.
+   *
+   * `options.unshallow` follows `fetchUnshallow`'s caller-guards rule: git
+   * rejects `--unshallow` in a non-shallow repository (a loud
+   * `GitCommandError`, deliberately untolerated) — probe with `isShallow`
+   * first. Combining it with `options.depth` is refused typed, pre-spawn,
+   * exactly as git itself would reject the pair.
    */
   readonly fetch: (cwd: string, options: {
     readonly ref: string;
     readonly remote?: string;
     readonly depth?: number;
     readonly tag?: boolean;
+    readonly unshallow?: boolean;
   }) => Effect.Effect<void, GitCommandError | NotARepositoryError | UnknownRefError>;
   /**
    * Mutating: fetches `options.ref` from `options.remote` (default
@@ -3856,6 +3891,11 @@ interface GitShape {
    * a reset that silently did nothing would hand a retry of a
    * non-idempotent operation the same dirty tree. `mode` defaults to
    * `"mixed"` (git's own default), emitted explicitly in the argv.
+   *
+   * `mode: "hard"` is destructive and legitimately reached for: after
+   * committing through an out-of-band channel (e.g. the GitHub Data API,
+   * which writes the commit server-side), `reset --hard origin/<branch>`
+   * is how the local tree is synchronized to the commit it never made.
    */
   readonly reset: (cwd: string, options?: {
     readonly mode?: "soft" | "mixed" | "hard";
@@ -3929,15 +3969,30 @@ interface GitShape {
     readonly force?: boolean;
   }) => Effect.Effect<void, GitCommandError | NotARepositoryError | UnknownRefError>;
   /**
-   * Mutating: `git submodule update [--init] [--depth <n>] [-- <paths>...]`
+   * Mutating:
+   * `git submodule update [--init] [--checkout] [--remote] [--no-fetch] [--recursive] [--force] [--depth <n>] [-- <paths>...]`
    * — updates registered submodules in the working tree, optionally
    * initializing them (`options.init`), with an optional depth limit and
    * scoped to `options.paths`.
+   *
+   * `options.checkout` is the documented override for a
+   * `submodule.<name>.update = none` configuration — without it, updating
+   * such a submodule silently no-ops (git reports success and checks out
+   * nothing). `options.fetch` accepts only the literal `false` (emitting
+   * `--no-fetch`): the default already fetches and git has no positive
+   * spelling. `options.remote` tracks the remote branch's tip instead of
+   * the recorded sha; `options.recursive` descends into nested submodules;
+   * `options.force` discards local changes in the submodule working tree.
    */
   readonly submoduleUpdate: (cwd: string, options?: {
     readonly init?: boolean;
     readonly depth?: number;
     readonly paths?: ReadonlyArray<string>;
+    readonly checkout?: boolean;
+    readonly remote?: boolean;
+    readonly fetch?: false;
+    readonly recursive?: boolean;
+    readonly force?: boolean;
   }) => Effect.Effect<void, GitCommandError | NotARepositoryError | UnknownRefError>;
   /**
    * Mutating: `git submodule add [--depth <n>] -- <url> <path>` —
@@ -4310,6 +4365,28 @@ interface GitShape {
     readonly file?: string;
     readonly all?: boolean;
   }) => Effect.Effect<void, GitCommandError | NotARepositoryError | UnknownRefError>;
+  /**
+   * Mutating: `git config [-f <file>] --remove-section <section>` — removes
+   * a whole configuration section (every key under it, and the header) from
+   * the live config, or from `options.file`. The section-level sibling of
+   * `configUnset` — clearing a stale `submodule.<name>` registration is one
+   * invocation instead of a key-by-key probe-and-unset. Removing a section
+   * that does not exist fails LOUDLY (git exits 128,
+   * `fatal: no such section`) — the `configUnset` posture; probe with
+   * `configList` first when idempotency is wanted.
+   */
+  readonly configRemoveSection: (cwd: string, section: string, options?: {
+    readonly file?: string;
+  }) => Effect.Effect<void, GitCommandError | NotARepositoryError | UnknownRefError>;
+  /**
+   * Mutating: `git config [-f <file>] --rename-section <old> <new>` —
+   * renames a configuration section, carrying every key under it across.
+   * Renaming a section that does not exist fails LOUDLY (git exits 128,
+   * `fatal: no such section`) — the same posture as `configRemoveSection`.
+   */
+  readonly configRenameSection: (cwd: string, oldName: string, newName: string, options?: {
+    readonly file?: string;
+  }) => Effect.Effect<void, GitCommandError | NotARepositoryError | UnknownRefError>;
   /**
    * Mutating: `git rm [--cached] [-r] [--force] -- <paths...>` — removes
    * `paths` from the index and (without `options.cached`) the working tree.
@@ -6162,7 +6239,7 @@ declare class LockfileIntegrity extends LockfileIntegrity_base {
   static compare(lockfile: Lockfile, manifests: ReadonlyArray<WorkspaceManifest>): LockfileIntegrity;
 }
 //#endregion
-//#region ../../node_modules/.pnpm/@effected+package-json@0.8.0_effect@4.0.0-beta.107/node_modules/@effected/package-json/index.d.ts
+//#region ../../node_modules/.pnpm/@effected+package-json@0.9.0_effect@4.0.0-beta.107/node_modules/@effected/package-json/index.d.ts
 //#region src/Dependency.d.ts
 declare const Dependency_base: Schema.Class<Dependency, Schema.Struct<{
   /** The package name. */
@@ -6744,7 +6821,7 @@ declare class Package extends Package_base {
   toJsonString(options?: PackageFormatOptions): string;
 }
 //#endregion
-//#region ../../node_modules/.pnpm/@effected+workspaces@0.12.0_@effected+jsonc@0.6.0_effect@4.0.0-beta.107__effect@4.0.0-beta.107/node_modules/@effected/workspaces/index.d.ts
+//#region ../../node_modules/.pnpm/@effected+workspaces@0.13.0_@effected+jsonc@0.6.0_effect@4.0.0-beta.107__effect@4.0.0-beta.107/node_modules/@effected/workspaces/index.d.ts
 //#region src/WorkspacePackage.d.ts
 declare const PublishConfig_base: Schema.Class<PublishConfig, Schema.Struct<{
   /** Scoped-package visibility. Its presence overrides `private`. */
@@ -7571,6 +7648,8 @@ declare const DetectedPackageManager_base: Schema.Class<DetectedPackageManager,
   readonly version: Schema.Option<Schema.String>;
   /** The JavaScript runtime the manager implies. */
   readonly runtime: Schema.Literals<readonly ["node", "bun"]>;
+  /** The rung of the priority order that decided the name. */
+  readonly evidence: Schema.Literals<readonly ["pnpm-workspace.yaml", "bun.lock", "bun.lockb", "yarn.lock", "package.json#workspaces", "pnpm-lock.yaml", "package-lock.json", "package.json#devEngines.packageManager", "package.json#packageManager"]>;
 }>, {}>;
 /**
  * The outcome of package-manager detection at a workspace root.
@@ -7583,6 +7662,15 @@ declare const DetectedPackageManager_base: Schema.Class<DetectedPackageManager,
  * `devEngines.packageManager`; see {@link PackageManagerDetector} for the
  * precedence between them.
  *
+ * `evidence` is the rung of the priority order that decided the **name** — the
+ * verdict's provenance, in the same vocabulary the failure path reports as
+ * `PackageManagerDetectionError.checked`. For the bun and yarn rungs the
+ * lockfile is the recorded signal even though the rung is a conjunction (the
+ * lockfile *plus* a manifest field naming the manager): the manifest field alone
+ * would have resolved in the declaration tier, so the lockfile is what this rung
+ * added. The version's provenance is deliberately not carried — it follows the
+ * two-field precedence above, which is a rule, not a probe.
+ *
  * @public
  */
 declare class DetectedPackageManager extends DetectedPackageManager_base {}
@@ -7704,7 +7792,12 @@ declare class PackageManagerDetector extends PackageManagerDetector_base {
    * const TestDetector = PackageManagerDetector.layerTest({
    *   detect: () =>
    *     Effect.succeed(
-   *       DetectedPackageManager.make({ name: "pnpm", version: Option.none(), runtime: "node" }),
+   *       DetectedPackageManager.make({
+   *         name: "pnpm",
+   *         version: Option.none(),
+   *         runtime: "node",
+   *         evidence: "pnpm-workspace.yaml",
+   *       }),
    *     ),
    * });
    * ```