@agentxm/registry-protocol 0.28.11 → 0.28.13

package/dist/src/unstable/lint/compose-path.js

@@ -1,64 +0,0 @@
-/**
- * `composePath` — render a display path from a rule context's `displayRoot`
- * and a finding's accessor-relative `location.file`.
- *
- * Rules emit accessor-relative `location.file` values only; messages carry no
- * paths or coordinates. The format-time composition here lets the same rule
- * render different paths for publish (`displayRoot: ""`), registry-installed
- * skills, external skills, and workspace-scope findings.
- *
- * Relative rendered paths are posix and prefixed with `./` so logs are
- * unambiguous about relative-ness. Absolute finding paths are preserved for
- * files outside the workspace root. `location.line` / `location.column`
- * append as `:line:column` when present.
- *
- * @experimental This API is unstable and may change without notice.
- * @packageDocumentation
- */
-// -----------------------------------------------------------------------------
-// composePath
-// -----------------------------------------------------------------------------
-/**
- * Compose the rendered path for a finding.
- *
- * @param displayRoot - Context-supplied posix-relative root (or `""`).
- * @param location    - Accessor-relative or absolute file + optional coordinates.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export const composePath = (displayRoot, location) => {
-    const locationFile = location?.file ?? "";
-    const base = isAbsolutePath(locationFile) ? locationFile : joinPosix(displayRoot, locationFile);
-    const withPrefix = base === "" ? "." : isAbsolutePath(base) || base.startsWith("./") ? base : `./${base}`;
-    if (location === undefined) {
-        return withPrefix;
-    }
-    return appendCoordinates(withPrefix, location);
-};
-const isAbsolutePath = (value) => value.startsWith("/") || value.startsWith("\\\\") || /^[A-Za-z]:[\\/]/.test(value);
-const joinPosix = (left, right) => {
-    const l = stripTrailingSlash(left);
-    const r = stripLeadingSlash(right);
-    if (l === "" && r === "") {
-        return "";
-    }
-    if (l === "") {
-        return r;
-    }
-    if (r === "") {
-        return l;
-    }
-    return `${l}/${r}`;
-};
-const stripTrailingSlash = (s) => (s.endsWith("/") ? s.slice(0, -1) : s);
-const stripLeadingSlash = (s) => (s.startsWith("/") ? s.slice(1) : s);
-const appendCoordinates = (path, location) => {
-    if (location.line === undefined) {
-        return path;
-    }
-    if (location.column === undefined) {
-        return `${path}:${location.line}`;
-    }
-    return `${path}:${location.line}:${location.column}`;
-};
-//# sourceMappingURL=compose-path.js.map

package/dist/src/unstable/lint/config.d.ts

@@ -1,77 +0,0 @@
-/**
- * `LintConfig` — workspace-settings-level lint configuration.
- *
- * Workspace settings carry a `lint` section whose `rules` map binds rule ids
- * to `"off" | "info" | "warn" | "error"`. The registry publish
- * gate ignores workspace overrides; this config affects `axm lint` only.
- *
- * Keys are **exact** rule ids (`<namespace>/<name>`). No glob, wildcard, or
- * regex syntax is accepted. The accepted-key set comes from the static lint
- * catalog metadata, so validation never depends on which executable catalog
- * modules happened to be imported first.
- *
- * @experimental This API is unstable and may change without notice.
- * @packageDocumentation
- */
-import * as Schema from "effect/Schema";
-/**
- * Accepted values for a `lint.rules` entry.
- *
- * Note: `"warn"` is the config surface for `Severity` `"warning"`; mirror's
- * ESLint convention. The evaluator treats `"warn"` as equivalent to `warning`
- * severity; `"off"` suppresses emission.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export declare const LintRuleSeveritySchema: Schema.Literals<readonly ["off", "info", "warn", "error"]>;
-/**
- * Effective severity of a `lint.rules` entry.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export type LintRuleSeverity = Schema.Schema.Type<typeof LintRuleSeveritySchema>;
-/**
- * Record of `<namespace>/<name>` ids to severity overrides.
- *
- * Unknown / wildcard / regex keys are rejected at decode by the filter — the
- * filter walks the decoded record's keys and checks every key against the
- * registered rule-id set. Wildcard patterns like `"skill/*"` fail the filter
- * because they are not registered ids.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export declare const LintRulesMapSchema: Schema.$Record<Schema.String, Schema.Literals<readonly ["off", "info", "warn", "error"]>>;
-/**
- * Inferred type for `LintRulesMap`.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export type LintRulesMap = Schema.Schema.Type<typeof LintRulesMapSchema>;
-/**
- * `lint` section of `axm.json`.
- *
- * Today only `rules` is defined; future fields (per-rule options, reporter
- * selection) extend this struct. The schema rejects excess top-level keys so
- * typos surface at decode.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export declare const LintConfigSchema: Schema.Struct<{
-    readonly rules: Schema.optionalKey<Schema.$Record<Schema.String, Schema.Literals<readonly ["off", "info", "warn", "error"]>>>;
-}>;
-/**
- * Inferred type for `LintConfig`.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export type LintConfig = Schema.Schema.Type<typeof LintConfigSchema>;
-/**
- * The platform-canonical `LintConfig` — empty rules, no overrides.
- *
- * Registry publish uses this config; it carries no overrides so every rule
- * fires at its catalog severity.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export declare const platformCanonicalLintConfig: LintConfig;
-//# sourceMappingURL=config.d.ts.map

package/dist/src/unstable/lint/config.js

@@ -1,99 +0,0 @@
-/**
- * `LintConfig` — workspace-settings-level lint configuration.
- *
- * Workspace settings carry a `lint` section whose `rules` map binds rule ids
- * to `"off" | "info" | "warn" | "error"`. The registry publish
- * gate ignores workspace overrides; this config affects `axm lint` only.
- *
- * Keys are **exact** rule ids (`<namespace>/<name>`). No glob, wildcard, or
- * regex syntax is accepted. The accepted-key set comes from the static lint
- * catalog metadata, so validation never depends on which executable catalog
- * modules happened to be imported first.
- *
- * @experimental This API is unstable and may change without notice.
- * @packageDocumentation
- */
-import * as Schema from "effect/Schema";
-import { allLintCatalogRuleIds } from "./catalog-metadata.js";
-// -----------------------------------------------------------------------------
-// Config value schema
-// -----------------------------------------------------------------------------
-/**
- * Accepted values for a `lint.rules` entry.
- *
- * Note: `"warn"` is the config surface for `Severity` `"warning"`; mirror's
- * ESLint convention. The evaluator treats `"warn"` as equivalent to `warning`
- * severity; `"off"` suppresses emission.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export const LintRuleSeveritySchema = Schema.Literals(["off", "info", "warn", "error"]).annotate({
-    identifier: "LintRuleSeverity",
-    title: "Lint Rule Severity",
-    description: "Severity override for a lint rule: 'off' silences it, 'info'/'warn'/'error' raise or lower severity.",
-});
-const acceptedRuleIds = new Set(allLintCatalogRuleIds);
-// -----------------------------------------------------------------------------
-// Rules map schema
-// -----------------------------------------------------------------------------
-const ruleIdKeyFilter = Schema.makeFilter((input) => {
-    const invalid = [];
-    for (const key of Object.keys(input)) {
-        if (!acceptedRuleIds.has(key)) {
-            invalid.push(key);
-        }
-    }
-    if (invalid.length === 0) {
-        return undefined;
-    }
-    return `Unknown lint rule IDs in lint.rules: ${invalid.join(", ")}. Keys must be exact <namespace>/<name> IDs; wildcards and globs are not supported.`;
-});
-/**
- * Record of `<namespace>/<name>` ids to severity overrides.
- *
- * Unknown / wildcard / regex keys are rejected at decode by the filter — the
- * filter walks the decoded record's keys and checks every key against the
- * registered rule-id set. Wildcard patterns like `"skill/*"` fail the filter
- * because they are not registered ids.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export const LintRulesMapSchema = Schema.Record(Schema.String, LintRuleSeveritySchema)
-    .annotate({
-    identifier: "LintRulesMap",
-    title: "Lint Rules Map",
-    description: "Map of exact <namespace>/<name> rule ids to severity overrides for `axm lint`.",
-})
-    .check(ruleIdKeyFilter);
-// -----------------------------------------------------------------------------
-// LintConfig schema
-// -----------------------------------------------------------------------------
-/**
- * `lint` section of `axm.json`.
- *
- * Today only `rules` is defined; future fields (per-rule options, reporter
- * selection) extend this struct. The schema rejects excess top-level keys so
- * typos surface at decode.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export const LintConfigSchema = Schema.Struct({
-    rules: Schema.optionalKey(LintRulesMapSchema.annotate({
-        description: "Exact lint rule ids mapped to severity overrides.",
-        examples: [{ "workspace/settings-schema-valid": "error" }],
-    })),
-}).annotate({
-    identifier: "LintConfig",
-    title: "Lint Config",
-    description: "Lint configuration under `lint` in workspace settings.",
-});
-/**
- * The platform-canonical `LintConfig` — empty rules, no overrides.
- *
- * Registry publish uses this config; it carries no overrides so every rule
- * fires at its catalog severity.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export const platformCanonicalLintConfig = { rules: {} };
-//# sourceMappingURL=config.js.map

package/dist/src/unstable/lint/context.d.ts

@@ -1,239 +0,0 @@
-/**
- * Rule-context types and narrow accessors.
- *
- * Each rule-context type bundles a caller-decoded `subject` with a narrow
- * caller-bound accessor and a `displayRoot` used for path rendering. Rules
- * consume accessors as ordinary property access (no Layer wiring); tests pass
- * literal fakes.
- *
- * Accessor surfaces are intentionally minimal — rules SHALL see only the
- * methods the current catalog requires. Extend a surface only for a documented
- * rule consumer.
- *
- * @experimental This API is unstable and may change without notice.
- * @packageDocumentation
- */
-import type * as Effect from "effect/Effect";
-import type { KnowledgeInspection } from "../knowledge/okf.js";
-/**
- * Tagged error surfaced by `SkillFileAccessor` / `PackFileAccessor` when a
- * read fails for reasons other than "file not found" (which is represented
- * by `exists -> false`).
- *
- * This interface fixes the error shape rules can rely on.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export interface FileAccessError {
-    readonly _tag: "FileAccessError";
-    /** Accessor-relative posix path that failed. */
-    readonly path: string;
-    /** Machine-readable reason. */
-    readonly reason: "path-escape" | "read-error" | "io-error";
-    /** Human-readable detail; no rendered display path. */
-    readonly message: string;
-}
-/**
- * Narrow skill-rooted file accessor.
- *
- * Root is the directory containing `SKILL.md`. Paths are posix and relative
- * to the root; implementations MUST reject path-traversal attempts (`..`,
- * absolute paths, symlink escapes) by returning `false` from `exists` or
- * failing `readBytes` with `FileAccessError { reason: "path-escape" }`.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export interface SkillFileAccessor {
-    readonly exists: (path: string) => Effect.Effect<boolean>;
-    readonly readBytes: (path: string) => Effect.Effect<Uint8Array, FileAccessError>;
-}
-/**
- * Narrow pack-rooted file accessor.
- *
- * Root is the directory containing `pack.json`. Same traversal
- * constraints as `SkillFileAccessor`.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export interface PackFileAccessor {
-    readonly exists: (path: string) => Effect.Effect<boolean>;
-    readonly readBytes: (path: string) => Effect.Effect<Uint8Array, FileAccessError>;
-}
-export interface SubagentFileAccessor {
-    readonly exists: (path: string) => Effect.Effect<boolean>;
-    readonly readBytes: (path: string) => Effect.Effect<Uint8Array, FileAccessError>;
-}
-export interface McpServerFileAccessor {
-    readonly exists: (path: string) => Effect.Effect<boolean>;
-    readonly readBytes: (path: string) => Effect.Effect<Uint8Array, FileAccessError>;
-}
-export interface HookFileAccessor {
-    readonly exists: (path: string) => Effect.Effect<boolean>;
-    readonly readBytes: (path: string) => Effect.Effect<Uint8Array, FileAccessError>;
-}
-export interface RuleFileAccessor {
-    readonly exists: (path: string) => Effect.Effect<boolean>;
-    readonly readBytes: (path: string) => Effect.Effect<Uint8Array, FileAccessError>;
-}
-export interface KnowledgeFileAccessor {
-    readonly exists: (path: string) => Effect.Effect<boolean>;
-    readonly readBytes: (path: string) => Effect.Effect<Uint8Array, FileAccessError>;
-}
-/**
- * Context passed to `skill/*` rules.
- *
- * `subject` is the caller-decoded skill content (SKILL.md frontmatter +
- * optional skill.json).
- *
- * `displayRoot` is posix and relative; `""` means the accessor root is the
- * rendering base. See `./compose-path.ts` for the four documented cases.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export interface SkillRuleContext<S = SkillContent> {
-    readonly subject: S;
-    /**
-     * Content-root accessor. Rooted at the directory containing `SKILL.md`.
-     * For native (registry-installed) skills this is the `src/` sub-directory
-     * of the package; for non-native skills it is the skill's own
-     * directory. Rules validating skill content (`skill-md-present`,
-     * `frontmatter-parseable`, and any future rule evaluating files that
-     * render into agent directories) read through this accessor.
-     */
-    readonly files: SkillFileAccessor;
-    /**
-     * Package-root accessor. Rooted at the skill's package root —
-     * the directory containing `skill.json` for native skills. For non-native
-     * skills that have no package/content split, this MAY alias `files`.
-     * Rules validating package-shape concerns (`manifest-present` and any
-     * future rule inspecting files at or above the content root) read through
-     * this accessor.
-     */
-    readonly packageFiles: SkillFileAccessor;
-    readonly displayRoot: string;
-}
-/**
- * Concrete subject shape passed to `skill/*` rules.
- *
- * Rules read `SKILL.md` bytes through `context.files` (the authoritative
- * source shared across publish and `axm lint`). The `subject` carries only
- * what rules can't efficiently re-derive from bytes:
- *
- * - `isNative` — whether the caller expects this skill to carry a
- *   `skill.json` manifest. Native (registry-installed) skills set this to
- *   `true`; non-native (managed external) skills set it to `false`. Rules
- *   that depend on `skill.json` (`skill/manifest-present`,
- *   `skill/manifest-schema-valid`, `skill/manifest-keys-recognized`)
- *   early-return `[]` when `isNative === false`, so the same catalog covers
- *   both.
- * - `skillJson` — the already-decoded `skill.json` contents when present
- *   (caller decodes once, rules don't re-read + re-parse). `undefined` when
- *   the file is absent. Schema-valid rules pipe this into
- *   `Schema.decodeUnknownResult(SkillManifestSchema)`; keys-recognized
- *   enumerates top-level keys after narrowing to `Record<string, unknown>`.
- *
- * Workspace consumers build `SkillContent` via `buildSkillRuleContexts`
- * against the lint workspace view; publish builds one `SkillContent` per
- * incoming archive.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export interface SkillContent {
-    readonly isNative: boolean;
-    readonly skillJson: unknown;
-    /** Agent-facing skill directory name used for the standard name-match check. */
-    readonly expectedName?: string;
-}
-/**
- * Context passed to `pack/*` rules.
- *
- * `subject` is the caller-decoded pack content — concrete `PackContent` shape
- * defined below. Packs are registry-only at v1 (no non-native arm), so the
- * subject carries only the already-decoded manifest and rules read
- * `pack.json` bytes through `context.files` as needed.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export interface PackRuleContext<S = PackContent> {
-    readonly subject: S;
-    readonly files: PackFileAccessor;
-    readonly displayRoot: string;
-}
-/**
- * Concrete subject shape passed to `pack/*` rules.
- *
- * Rules read `pack.json` bytes through `context.files` (the
- * authoritative source shared across publish and `axm lint`). The `subject`
- * carries only what rules can't efficiently re-derive from bytes:
- *
- * - `packJson` — the already-decoded `pack.json` contents when
- *   present (caller decodes once, rules don't re-read + re-parse).
- *   `undefined` when the file is absent. Schema-valid rules pipe this into
- *   `Schema.decodeUnknownResult(PackManifestSchema)`;
- *   keys-recognized enumerates top-level keys after narrowing to
- *   `Record<string, unknown>`.
- *
- * Unlike `SkillContent`, there is no `isNative` discriminator — packs are
- * registry-only and every pack context is expected to expose a manifest.
- * The presence rule (`pack/manifest-present`) owns the absence arm.
- *
- * Workspace consumers build `PackContent` via `buildPackRuleContexts`
- * against the lint workspace view; publish builds one `PackContent` per
- * incoming archive.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export interface PackContent {
-    readonly packJson: unknown;
-}
-export interface SubagentRuleContext<S = SubagentContent> {
-    readonly subject: S;
-    readonly files: SubagentFileAccessor;
-    readonly displayRoot: string;
-}
-export interface SubagentContent {
-    readonly subagentJson: unknown;
-}
-export interface McpServerRuleContext<S = McpServerContent> {
-    readonly subject: S;
-    readonly files: McpServerFileAccessor;
-    readonly displayRoot: string;
-}
-export interface McpServerContent {
-    readonly mcpServerJson: unknown;
-}
-export interface HookRuleContext<S = HookContent> {
-    readonly subject: S;
-    readonly files: HookFileAccessor;
-    readonly displayRoot: string;
-}
-export interface HookContent {
-    readonly hookJson: unknown;
-}
-/**
- * Context passed to `rule/*` rules.
- *
- * The doubled word is unavoidable: `rule` is an extension type and `rule` is
- * also the lint primitive, so the context for the `rule` extension type is a
- * `RuleRuleContext`. Every other name here follows `<Type>RuleContext`.
- */
-export interface RuleRuleContext<S = RuleContent> {
-    readonly subject: S;
-    readonly files: RuleFileAccessor;
-    readonly displayRoot: string;
-}
-export interface RuleContent {
-    readonly ruleJson: unknown;
-}
-export interface KnowledgeRuleContext<S = KnowledgeContent> {
-    readonly subject: S;
-    readonly files: KnowledgeFileAccessor;
-    readonly displayRoot: string;
-    /** Absolute package root used once while constructing the cached inspection. */
-    readonly packageRoot?: string;
-}
-export interface KnowledgeContent {
-    readonly knowledgeJson: unknown;
-    readonly inspection?: KnowledgeInspection;
-}
-//# sourceMappingURL=context.d.ts.map

package/dist/src/unstable/lint/context.js

@@ -1,17 +0,0 @@
-/**
- * Rule-context types and narrow accessors.
- *
- * Each rule-context type bundles a caller-decoded `subject` with a narrow
- * caller-bound accessor and a `displayRoot` used for path rendering. Rules
- * consume accessors as ordinary property access (no Layer wiring); tests pass
- * literal fakes.
- *
- * Accessor surfaces are intentionally minimal — rules SHALL see only the
- * methods the current catalog requires. Extend a surface only for a documented
- * rule consumer.
- *
- * @experimental This API is unstable and may change without notice.
- * @packageDocumentation
- */
-export {};
-//# sourceMappingURL=context.js.map

package/dist/src/unstable/lint/describe-document.d.ts

@@ -1,31 +0,0 @@
-/**
- * The one place lint turns a document filename into the human label that opens
- * a finding message ("Skill manifest has unrecognized top-level field ...").
- *
- * Three copies of this switch used to exist — one in `issues-to-findings.ts`,
- * one in `catalog/shared/schema-rule.ts`, one in
- * `catalog/shared/manifest-json.ts` — and they had drifted: only one knew
- * `hook.json`, none knew `rule.json` or `knowledge.json`, and the parse-failure
- * copy defaulted to "Manifest" where the others defaulted to "Document".
- *
- * The manifest labels are derived from `MANIFEST_FILENAME_BY_TYPE` and
- * `extensionTypeSentenceLabels`, both of which are total over `ExtensionType`,
- * so a new extension type gets a label the moment its row lands in
- * `EXTENSION_TYPE_TABLE`.
- *
- * @experimental This API is unstable and may change without notice.
- * @packageDocumentation
- */
-/** Label used when a filename matches no known document. */
-export declare const UNKNOWN_DOCUMENT_LABEL = "Document";
-/**
- * Describe the document at `file` for use as the subject of a finding message.
- *
- * Keyed by basename, so both bare accessor-relative filenames (`hook.json`,
- * as the per-extension rules pass) and workspace-relative paths
- * (`axm.json`, as `issues-to-findings` passes) resolve.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export declare const describeSchemaDocument: (file: string) => string;
-//# sourceMappingURL=describe-document.d.ts.map

package/dist/src/unstable/lint/describe-document.js

@@ -1,50 +0,0 @@
-/**
- * The one place lint turns a document filename into the human label that opens
- * a finding message ("Skill manifest has unrecognized top-level field ...").
- *
- * Three copies of this switch used to exist — one in `issues-to-findings.ts`,
- * one in `catalog/shared/schema-rule.ts`, one in
- * `catalog/shared/manifest-json.ts` — and they had drifted: only one knew
- * `hook.json`, none knew `rule.json` or `knowledge.json`, and the parse-failure
- * copy defaulted to "Manifest" where the others defaulted to "Document".
- *
- * The manifest labels are derived from `MANIFEST_FILENAME_BY_TYPE` and
- * `extensionTypeSentenceLabels`, both of which are total over `ExtensionType`,
- * so a new extension type gets a label the moment its row lands in
- * `EXTENSION_TYPE_TABLE`.
- *
- * @experimental This API is unstable and may change without notice.
- * @packageDocumentation
- */
-import { extensionTypeSentenceLabels, extensionTypes, } from "@agentxm/extension-model/unstable/extensions/common";
-import { LOCKFILE_NAME } from "@agentxm/extension-model/unstable/workspace-files";
-import { MANIFEST_FILENAME_BY_TYPE } from "../publish/manifest-policy.js";
-import { SETTINGS_FILENAME } from "@agentxm/extension-model/unstable/workspace-files";
-/** Label used when a filename matches no known document. */
-export const UNKNOWN_DOCUMENT_LABEL = "Document";
-const capitalizeFirst = (value) => value.length === 0 ? value : `${value.charAt(0).toUpperCase()}${value.slice(1)}`;
-// eslint-disable-next-line no-restricted-syntax -- Immutable lookup over the closed manifest filename vocabulary.
-const documentLabels = new Map([
-    ...extensionTypes.map((type) => [
-        MANIFEST_FILENAME_BY_TYPE[type],
-        `${capitalizeFirst(extensionTypeSentenceLabels[type])} manifest`,
-    ]),
-    [SETTINGS_FILENAME, "Workspace settings"],
-    [LOCKFILE_NAME, "Lockfile"],
-]);
-const basename = (file) => {
-    const normalized = file.replace(/\\/g, "/");
-    const parts = normalized.split("/");
-    return parts[parts.length - 1] ?? normalized;
-};
-/**
- * Describe the document at `file` for use as the subject of a finding message.
- *
- * Keyed by basename, so both bare accessor-relative filenames (`hook.json`,
- * as the per-extension rules pass) and workspace-relative paths
- * (`axm.json`, as `issues-to-findings` passes) resolve.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export const describeSchemaDocument = (file) => documentLabels.get(basename(file)) ?? UNKNOWN_DOCUMENT_LABEL;
-//# sourceMappingURL=describe-document.js.map

package/dist/src/unstable/lint/evaluate.d.ts

@@ -1,47 +0,0 @@
-/**
- * Pure evaluator for the lint engine.
- *
- * `evaluateContexts(rules, contexts, config)` pairs each rule with each context,
- * invokes `rule.check`, applies severity overrides from `config.rules`, and
- * drops findings from rules configured `"off"`.
- *
- * Both functions are plain `Effect` values; neither requires a Layer or an
- * ambient service. See the `lint-engine` design doc §3 for the rationale
- * behind library primitives over a central engine service.
- *
- * @experimental This API is unstable and may change without notice.
- * @packageDocumentation
- */
-import * as Effect from "effect/Effect";
-import type { LintConfig } from "./config.js";
-import type { LintFinding, LintRule } from "./rule.js";
-/**
- * One `(rule, context, findings)` evaluation result.
- *
- * `findings` is emitted after severity overrides from `config.rules` have been
- * applied; rule-level severity is the platform default, finding-level severity
- * is the effective post-override severity.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export interface Evaluated<C> {
-    readonly rule: LintRule<C>;
-    readonly context: C;
-    readonly findings: ReadonlyArray<LintFinding>;
-}
-/**
- * Pair each rule with each context, run `rule.check`, apply severity overrides
- * from `config.rules`, and return one `Evaluated<C>` per pair.
- *
- * Findings whose configured severity is `"off"` are suppressed entirely; the
- * `Evaluated` entry still ships (with an empty `findings` array) so consumers
- * that group by rule still see the rule ran.
- *
- * Rules are evaluated in catalog order; contexts are evaluated in caller
- * order. Rule-context invocation is sequential within a single
- * `evaluateContexts` call so tests can observe deterministic ordering.
- *
- * @experimental This API is unstable and may change without notice.
- */
-export declare const evaluateContexts: <C>(rules: ReadonlyArray<LintRule<C>>, contexts: ReadonlyArray<C>, config: LintConfig) => Effect.Effect<ReadonlyArray<Evaluated<C>>>;
-//# sourceMappingURL=evaluate.d.ts.map