pasika 0.3.0 → 0.3.2

package/enforcement/registry.json

@@ -2,8 +2,8 @@
   "requirements": [
     {
       "doc": "agent-policy.md",
-      "text": "A change MUST NOT introduce a finding that npx pasika doctor or the repository's lint command did not already report.",
-      "hash": "041b665bd7",
+      "text": "A change MUST NOT introduce a finding that the repository's lint command (mechanical rules) or npx pasika doctor (environment checks) did not already report.",
+      "hash": "f8d1db6aaf",
       "kind": "judgment",
       "note": "deciding a finding is new requires the previous state, which neither command carries"
     },
@@ -18,8 +18,8 @@
       "doc": "agent-policy.md",
       "text": "A change to the Vulyk registry MUST use Vulyk commands rather than edits to generated files.",
       "hash": "27247db8eb",
-      "kind": "planned",
-      "note": "doctor: compare managed files against their pinned sources"
+      "kind": "doctor",
+      "ref": "pasika/managed-file-edit"
     },
     {
       "doc": "agent-policy.md",
@@ -39,22 +39,22 @@
       "doc": "agent-policy.md",
       "text": "A file listed in a .vulyk manifest MUST NOT be edited by hand.",
       "hash": "2390e57f4f",
-      "kind": "planned",
-      "note": "doctor: compare managed files against their pinned sources"
+      "kind": "doctor",
+      "ref": "pasika/managed-file-edit"
     },
     {
       "doc": "agent-policy.md",
       "text": "A lint command MUST NOT pass ESLint's --cache flag, because rules that compare a file against the rest of the tree need every file in the run.",
       "hash": "2b3f806581",
-      "kind": "planned",
-      "note": "doctor: read the lint scripts from package.json"
+      "kind": "eslint",
+      "ref": "pasika/no-cache-flag"
     },
     {
       "doc": "agent-policy.md",
       "text": "A repository MUST take its lint, format, and TypeScript configuration from pasika and zirka rather than restating it locally.",
       "hash": "12553abd17",
-      "kind": "planned",
-      "note": "doctor: compare the repository's configuration against the baseline"
+      "kind": "doctor",
+      "ref": "pasika/config-baseline"
     },
     {
       "doc": "agent-policy.md",
@@ -73,8 +73,8 @@
       "doc": "agent-policy.md",
       "text": "Code MUST NOT use eslint-disable directives, and a reported violation MUST be fixed instead.",
       "hash": "628ab4f6a6",
-      "kind": "planned",
-      "note": "zirka: enable @eslint-community/eslint-comments/no-use; whether a fix is correct stays judgment"
+      "kind": "eslint",
+      "ref": "pasika/no-eslint-disable"
     },
     {
       "doc": "agent-policy.md",
@@ -94,15 +94,15 @@
       "doc": "agent-policy.md",
       "text": "Vulyk MUST NOT be added to package.json in order to run its CLI.",
       "hash": "1061447825",
-      "kind": "planned",
-      "note": "doctor: report a vulyk entry in package.json"
+      "kind": "eslint",
+      "ref": "pasika/no-vulyk-dependency"
     },
     {
       "doc": "agent-policy.md",
       "text": "Vulyk MUST run as an ephemeral command such as npx vulyk@latest.",
       "hash": "c8aaf8ce02",
-      "kind": "planned",
-      "note": "doctor: report a vulyk entry in package.json"
+      "kind": "eslint",
+      "ref": "pasika/no-vulyk-dependency"
     },
     {
       "doc": "agent-policy.md",
@@ -130,43 +130,43 @@
       "doc": "code-organization-guide/rules/application-structure-rule.md",
       "text": "A folder holding support files MUST be named hooks/, types/, schemas/, constants/, or utils/, matching the kind of file it holds.",
       "hash": "1ea6de0cbf",
-      "kind": "planned",
-      "note": "eslint: application-structure"
+      "kind": "eslint",
+      "ref": "pasika/application-structure"
     },
     {
       "doc": "code-organization-guide/rules/application-structure-rule.md",
       "text": "A support folder MUST NOT contain a component.",
       "hash": "25be7e89ec",
-      "kind": "planned",
-      "note": "eslint: application-structure"
+      "kind": "eslint",
+      "ref": "pasika/application-structure"
     },
     {
       "doc": "code-organization-guide/rules/application-structure-rule.md",
       "text": "Application source MUST live under src/.",
       "hash": "0a5c03a95d",
-      "kind": "planned",
-      "note": "doctor: report source folders outside src/"
+      "kind": "doctor",
+      "ref": "pasika/source-under-src"
     },
     {
       "doc": "code-organization-guide/rules/application-structure-rule.md",
       "text": "src/ MUST contain only the app/, compositions/, features/, and shared/ folders, the root support folders, config/, locales/, and the files a framework requires at the src root.",
       "hash": "dd84e5498f",
-      "kind": "planned",
-      "note": "eslint: application-structure"
+      "kind": "eslint",
+      "ref": "pasika/application-structure"
     },
     {
       "doc": "code-organization-guide/rules/application-structure-rule.md",
       "text": "src/features/ MUST contain only feature folders.",
       "hash": "8e68eeb8c4",
-      "kind": "planned",
-      "note": "eslint: application-structure"
+      "kind": "eslint",
+      "ref": "pasika/application-structure"
     },
     {
       "doc": "code-organization-guide/rules/component-placement-rule.md",
       "text": "A component that imports from two or more feature folders MUST live in src/compositions/.",
       "hash": "a00c621fbe",
-      "kind": "planned",
-      "note": "eslint: report a non-composition file importing two feature folders"
+      "kind": "eslint",
+      "ref": "pasika/cross-feature-import"
     },
     {
       "doc": "code-organization-guide/rules/component-placement-rule.md",
@@ -201,29 +201,29 @@
       "doc": "code-organization-guide/rules/component-placement-rule.md",
       "text": "src/app/ MUST contain Next.js App Router framework-convention files and assets, plus styles required by routing files, but MUST NOT contain ordinary components or support folders.",
       "hash": "6a1d1f370e",
-      "kind": "planned",
-      "note": "eslint: application-structure"
+      "kind": "eslint",
+      "ref": "pasika/application-structure"
     },
     {
       "doc": "code-organization-guide/rules/configuration-rule.md",
       "text": "A configuration module MUST be one src/config/<config-name>/ folder with index.ts as its entry point.",
       "hash": "2f17655f6f",
-      "kind": "planned",
-      "note": "eslint: application-structure"
+      "kind": "eslint",
+      "ref": "pasika/application-structure"
     },
     {
       "doc": "code-organization-guide/rules/configuration-rule.md",
       "text": "A type, schema, or utility used only to implement one configuration module MUST be extracted even with one consumer.",
       "hash": "9e5da88f2e",
-      "kind": "planned",
-      "note": "doctor: resolve consumers with the import graph"
+      "kind": "eslint",
+      "ref": "pasika/config-extraction"
     },
     {
       "doc": "code-organization-guide/rules/configuration-rule.md",
       "text": "All configuration modules MUST live in src/config/.",
       "hash": "068f9a0a91",
-      "kind": "planned",
-      "note": "eslint: application-structure"
+      "kind": "eslint",
+      "ref": "pasika/application-structure"
     },
     {
       "doc": "code-organization-guide/rules/configuration-rule.md",
@@ -236,8 +236,8 @@
       "doc": "code-organization-guide/rules/configuration-rule.md",
       "text": "An extracted configuration type, schema, or utility MUST live in its matching dedicated folder under src/config/<config-name>/.",
       "hash": "d931ef91df",
-      "kind": "planned",
-      "note": "eslint: application-structure"
+      "kind": "eslint",
+      "ref": "pasika/application-structure"
     },
     {
       "doc": "code-organization-guide/rules/constants-rule.md",
@@ -250,22 +250,22 @@
       "doc": "code-organization-guide/rules/constants-rule.md",
       "text": "A constants/ folder MUST either define its constants directly in index.ts or group related constants in files that index.ts named-re-exports.",
       "hash": "2d1591194c",
-      "kind": "planned",
-      "note": "eslint: support-folder-shape"
+      "kind": "eslint",
+      "ref": "pasika/support-folder-shape"
     },
     {
       "doc": "code-organization-guide/rules/constants-rule.md",
       "text": "A value MUST remain in its declaring component or file until another file imports it independently; it MUST then be extracted as a constant.",
       "hash": "e779f5ec6f",
-      "kind": "planned",
-      "note": "doctor: resolve consumers with the import graph"
+      "kind": "eslint",
+      "ref": "pasika/value-extraction"
     },
     {
       "doc": "code-organization-guide/rules/constants-rule.md",
       "text": "Consumers MUST import an extracted constant through the index.ts in that constant's constants/ folder.",
       "hash": "0a7bdc1dfe",
-      "kind": "planned",
-      "note": "eslint: import-through-index"
+      "kind": "eslint",
+      "ref": "pasika/import-through-index"
     },
     {
       "doc": "code-organization-guide/rules/constants-rule.md",
@@ -306,8 +306,8 @@
       "doc": "code-organization-guide/rules/exports-and-imports-rule.md",
       "text": "A file that exports values MUST use named exports unless a framework or third-party package requires a different export style for that file.",
       "hash": "b330b4c859",
-      "kind": "planned",
-      "note": "eslint: named-exports"
+      "kind": "eslint",
+      "ref": "pasika/named-exports"
     },
     {
       "doc": "code-organization-guide/rules/exports-and-imports-rule.md",
@@ -341,15 +341,15 @@
       "doc": "code-organization-guide/rules/folder-nesting-rule.md",
       "text": "A component MUST NOT be nested only because it has support files.",
       "hash": "bd8c041512",
-      "kind": "planned",
-      "note": "doctor: resolve consumers with the import graph"
+      "kind": "eslint",
+      "ref": "pasika/component-nesting"
     },
     {
       "doc": "code-organization-guide/rules/folder-nesting-rule.md",
       "text": "A component MUST stay flat until it has one or more exclusive child components, then MUST be nested in a folder with the same name.",
       "hash": "6adf7c4309",
-      "kind": "planned",
-      "note": "doctor: resolve consumers with the import graph"
+      "kind": "eslint",
+      "ref": "pasika/stay-flat"
     },
     {
       "doc": "code-organization-guide/rules/folder-nesting-rule.md",
@@ -369,22 +369,22 @@
       "doc": "code-organization-guide/rules/hook-extraction-rule.md",
       "text": "A custom hook MUST be extracted to its own file when two or more consumers use it.",
       "hash": "f7a5d6663d",
-      "kind": "planned",
-      "note": "doctor: report the same hook name defined in two files"
+      "kind": "eslint",
+      "ref": "pasika/hook-extraction"
     },
     {
       "doc": "code-organization-guide/rules/hook-extraction-rule.md",
       "text": "A custom hook with exactly one consumer MUST be extracted when it contains two or more imperative categories and can be described as one coherent behavior.",
       "hash": "b057015bf3",
-      "kind": "planned",
-      "note": "eslint: count imperative categories; one coherent behavior stays judgment"
+      "kind": "eslint",
+      "ref": "pasika/hook-complexity"
     },
     {
       "doc": "code-organization-guide/rules/hook-extraction-rule.md",
       "text": "A custom hook with one consumer that contains fewer than two imperative categories MUST stay inline in its consumer file.",
       "hash": "fb12bb6002",
-      "kind": "planned",
-      "note": "eslint: count imperative categories"
+      "kind": "eslint",
+      "ref": "pasika/hook-complexity"
     },
     {
       "doc": "code-organization-guide/rules/hook-extraction-rule.md",
@@ -404,8 +404,8 @@
       "doc": "code-organization-guide/rules/interactive-component-rule.md",
       "text": "An interactive HTML element MUST be extracted to a component with a descriptive name.",
       "hash": "56a186c55b",
-      "kind": "planned",
-      "note": "eslint: report an interactive element beside other content"
+      "kind": "eslint",
+      "ref": "pasika/interactive-component"
     },
     {
       "doc": "code-organization-guide/rules/jsx-hygiene-rule.md",
@@ -418,8 +418,8 @@
       "doc": "code-organization-guide/rules/jsx-hygiene-rule.md",
       "text": "Arithmetic, chained built-in method calls, calls to functions declared outside the component, nested ternaries, and conditions containing two or more logical operators MUST be extracted before return, including in JSX attributes.",
       "hash": "979a3e96c3",
-      "kind": "planned",
-      "note": "eslint: jsx-hygiene"
+      "kind": "eslint",
+      "ref": "pasika/jsx-hygiene"
     },
     {
       "doc": "code-organization-guide/rules/locales-rule.md",
@@ -432,29 +432,29 @@
       "doc": "code-organization-guide/rules/locales-rule.md",
       "text": "A namespaced locale MUST be read through its full dotted path (locales.stream.watchLiveStream).",
       "hash": "3c10684240",
-      "kind": "planned",
-      "note": "eslint: report a destructured locales namespace"
+      "kind": "eslint",
+      "ref": "pasika/locale-dotted-path"
     },
     {
       "doc": "code-organization-guide/rules/locales-rule.md",
       "text": "All locales MUST live in the named locales object exported from src/locales/index.ts.",
       "hash": "2469d743da",
-      "kind": "planned",
-      "note": "eslint: report user-facing text outside the locales object"
+      "kind": "eslint",
+      "ref": "pasika/locales-location"
     },
     {
       "doc": "code-organization-guide/rules/locales-rule.md",
       "text": "Locales read by files in more than one feature folder or by src/shared/, src/compositions/, src/app/, or root support folders MUST live at the top level of locales.",
       "hash": "4f947bf362",
-      "kind": "planned",
-      "note": "doctor: resolve consumers with the import graph"
+      "kind": "eslint",
+      "ref": "pasika/locale-placement"
     },
     {
       "doc": "code-organization-guide/rules/locales-rule.md",
       "text": "Locales read only by files in one feature folder MUST live in an object with the camelCase form of its feature folder name (for example, user-settings becomes userSettings).",
       "hash": "66addb15b3",
-      "kind": "planned",
-      "note": "doctor: resolve consumers with the import graph"
+      "kind": "eslint",
+      "ref": "pasika/locale-placement"
     },
     {
       "doc": "code-organization-guide/rules/nameable-visual-concept-rule.md",
@@ -482,29 +482,29 @@
       "doc": "code-organization-guide/rules/smart-vs-dumb-component-rule.md",
       "text": "A dumb component MAY set data-testid on its root element, and the value MUST be kebab-case.",
       "hash": "4c78863697",
-      "kind": "planned",
-      "note": "eslint: data-testid-case"
+      "kind": "eslint",
+      "ref": "pasika/data-testid-case"
     },
     {
       "doc": "code-organization-guide/rules/smart-vs-dumb-component-rule.md",
       "text": "A dumb component file name MUST be kebab-case.tsx.",
       "hash": "7639f7df0b",
-      "kind": "planned",
-      "note": "eslint: classify smart vs dumb, then require kebab-case"
+      "kind": "eslint",
+      "ref": "pasika/filename-case"
     },
     {
       "doc": "code-organization-guide/rules/smart-vs-dumb-component-rule.md",
       "text": "A smart component file name MUST be PascalCase.tsx.",
       "hash": "1ece393f32",
-      "kind": "planned",
-      "note": "eslint: classify smart vs dumb, then require PascalCase; filename-case accepts either case today"
+      "kind": "eslint",
+      "ref": "pasika/filename-case"
     },
     {
       "doc": "code-organization-guide/rules/smart-vs-dumb-component-rule.md",
       "text": "A smart component with one outer DOM element in every rendered result MUST set data-testid on that element, and its value MUST match the component name in PascalCase.",
       "hash": "31dc8b3188",
-      "kind": "planned",
-      "note": "eslint: data-testid-case"
+      "kind": "eslint",
+      "ref": "pasika/data-testid-case"
     },
     {
       "doc": "code-organization-guide/rules/smart-vs-dumb-component-rule.md",
@@ -517,8 +517,8 @@
       "doc": "code-organization-guide/rules/smart-vs-dumb-component-rule.md",
       "text": "Next.js App Router routing files MUST use their required kebab-case names and are exempt from smart/dumb file-name and data-testid requirements.",
       "hash": "fb2c9ab370",
-      "kind": "planned",
-      "note": "eslint: report a src/app file whose name differs only in case from a routing-file name; filename-case only avoids conflicting with the exemption"
+      "kind": "eslint",
+      "ref": "pasika/data-testid-case"
     },
     {
       "doc": "code-organization-guide/rules/sole-state-owner-rule.md",
@@ -538,15 +538,15 @@
       "doc": "code-organization-guide/rules/types-and-schemas-rule.md",
       "text": "A type or schema declared in a component MUST stay in that component file until another file imports it without the component where it is defined.",
       "hash": "165d0c0cad",
-      "kind": "planned",
-      "note": "doctor: resolve consumers with the import graph"
+      "kind": "eslint",
+      "ref": "pasika/type-extraction"
     },
     {
       "doc": "code-organization-guide/rules/types-and-schemas-rule.md",
       "text": "A type or schema declared outside a component MUST stay in its file until another file needs it without using the code in that file.",
       "hash": "e63d1fbcb8",
-      "kind": "planned",
-      "note": "doctor: resolve consumers with the import graph"
+      "kind": "eslint",
+      "ref": "pasika/type-extraction"
     },
     {
       "doc": "code-organization-guide/rules/types-and-schemas-rule.md",
@@ -559,15 +559,15 @@
       "doc": "code-organization-guide/rules/types-and-schemas-rule.md",
       "text": "A types/ or schemas/ folder MUST either define its exports directly in index.ts or group related types and schemas in files that index.ts named-re-exports.",
       "hash": "b13a973306",
-      "kind": "planned",
-      "note": "eslint: support-folder-shape"
+      "kind": "eslint",
+      "ref": "pasika/support-folder-shape"
     },
     {
       "doc": "code-organization-guide/rules/types-and-schemas-rule.md",
       "text": "Consumers MUST import an extracted type or schema through the index.ts in that type or schema's types/ or schemas/ folder.",
       "hash": "24fb9c0774",
-      "kind": "planned",
-      "note": "eslint: import-through-index"
+      "kind": "eslint",
+      "ref": "pasika/import-through-index"
     },
     {
       "doc": "code-organization-guide/rules/types-and-schemas-rule.md",
@@ -594,22 +594,22 @@
       "doc": "code-organization-guide/rules/utilities-rule.md",
       "text": "A pure function MUST be extracted to utils/, even when it has one consumer.",
       "hash": "d49b4ce49a",
-      "kind": "planned",
-      "note": "eslint: report a pure function declared in a component file"
+      "kind": "eslint",
+      "ref": "pasika/pure-function-extract"
     },
     {
       "doc": "code-organization-guide/rules/utilities-rule.md",
       "text": "A utility MUST be imported directly without a barrel.",
       "hash": "a3bd205f5c",
-      "kind": "planned",
-      "note": "eslint: no-util-barrel"
+      "kind": "eslint",
+      "ref": "pasika/no-util-barrel"
     },
     {
       "doc": "code-organization-guide/rules/utilities-rule.md",
       "text": "A utility file that exports one function MUST have a name in that function's kebab-case form.",
       "hash": "9b82ca27ee",
-      "kind": "planned",
-      "note": "eslint: util-file-name"
+      "kind": "eslint",
+      "ref": "pasika/util-file-name"
     },
     {
       "doc": "code-organization-guide/rules/utilities-rule.md",
@@ -649,71 +649,74 @@
       "doc": "documentation-guide/rules/guide-creation-rule.md",
       "text": "A Guide overview MUST contain one or two short descriptive sentences about the guide's scope and purpose, and MUST NOT contain instructions or links to other documentation.",
       "hash": "694bfba1ab",
-      "kind": "docs-check",
-      "ref": "overview-length, guide-overview-no-links"
+      "kind": "eslint",
+      "ref": "pasika/overview-length, pasika/guide-overview-no-links"
     },
     {
       "doc": "documentation-guide/rules/guide-creation-rule.md",
       "text": "A Guide whose steps use terms that a glossary Reference defines MUST link that Reference from its first step.",
       "hash": "caef1018c4",
-      "kind": "planned",
+      "kind": "eslint",
+      "ref": "pasika/glossary-term-linking",
       "note": "docs-check: compare glossary terms against the guide's steps"
     },
     {
       "doc": "documentation-guide/rules/guide-creation-rule.md",
       "text": "A Guide with support files MUST become a folder named the same as its entry-point file, without the .md extension.",
       "hash": "26a4eb93d4",
-      "kind": "docs-check",
-      "ref": "guide-folder-entry-point"
+      "kind": "eslint",
+      "ref": "pasika/guide-folder-entry-point"
     },
     {
       "doc": "documentation-guide/rules/guide-creation-rule.md",
       "text": "A Reference file that a Guide owns MUST live in a references/ subfolder inside the Guide's folder.",
       "hash": "4efb50f75f",
-      "kind": "docs-check",
-      "ref": "support-document-placement"
+      "kind": "eslint",
+      "ref": "pasika/support-document-placement"
     },
     {
       "doc": "documentation-guide/rules/guide-creation-rule.md",
       "text": "A Rule file that a Guide owns MUST live in a rules/ subfolder inside the Guide's folder.",
       "hash": "73d2f1cc23",
-      "kind": "docs-check",
-      "ref": "support-document-placement"
+      "kind": "eslint",
+      "ref": "pasika/support-document-placement"
     },
     {
       "doc": "documentation-guide/rules/guide-creation-rule.md",
       "text": "A step that links another Guide MUST link directly to the relevant How To section.",
       "hash": "eade3a0166",
-      "kind": "planned",
+      "kind": "eslint",
+      "ref": "pasika/guide-link-anchors",
       "note": "docs-check: a guide link carries a How To anchor"
     },
     {
       "doc": "documentation-guide/rules/guide-creation-rule.md",
       "text": "Each How To step MUST be concise and use one sentence.",
       "hash": "5992821880",
-      "kind": "docs-check",
-      "ref": "guide-step-single-sentence",
+      "kind": "eslint",
+      "ref": "pasika/guide-step-single-sentence",
       "note": "one sentence is checked; whether it is concise is judgment"
     },
     {
       "doc": "documentation-guide/rules/guide-creation-rule.md",
       "text": "Each How To step MUST link at most one documentation file total, whatever kind that file is.",
       "hash": "12585da0c8",
-      "kind": "docs-check",
-      "ref": "guide-step-single-link"
+      "kind": "eslint",
+      "ref": "pasika/guide-step-single-link"
     },
     {
       "doc": "documentation-guide/rules/guide-creation-rule.md",
       "text": "Guide file names MUST match the document title in kebab-case and use the -guide suffix (e.g., foo-guide.md).",
       "hash": "e820de2429",
-      "kind": "docs-check",
-      "ref": "title-matches-file-name, doc-kind-suffix"
+      "kind": "eslint",
+      "ref": "pasika/title-matches-file-name, pasika/doc-kind-suffix"
     },
     {
       "doc": "documentation-guide/rules/guide-creation-rule.md",
       "text": "How To sections MUST NOT nest inside other How To sections.",
       "hash": "23415cb949",
-      "kind": "planned",
+      "kind": "eslint",
+      "ref": "pasika/no-nested-how-to",
       "note": "docs-check: no heading nests inside a How To section"
     },
     {
@@ -727,29 +730,30 @@
       "doc": "documentation-guide/rules/policy-creation-rule.md",
       "text": "A Policy document MUST NOT contain Incorrect/Correct examples, and a requirement that a reader cannot apply without one MUST live in a Rule instead.",
       "hash": "c1e046ec18",
-      "kind": "docs-check",
-      "ref": "policy-no-examples"
+      "kind": "eslint",
+      "ref": "pasika/policy-no-examples"
     },
     {
       "doc": "documentation-guide/rules/policy-creation-rule.md",
       "text": "A Policy document MUST NOT link to Rules, References, Guides, or other Policy documents.",
       "hash": "483c98a275",
-      "kind": "docs-check",
-      "ref": "no-cross-document-link"
+      "kind": "eslint",
+      "ref": "pasika/no-cross-document-link"
     },
     {
       "doc": "documentation-guide/rules/policy-creation-rule.md",
       "text": "A Policy document MUST group its bullets under a heading per subject.",
       "hash": "fa77621dda",
-      "kind": "planned",
+      "kind": "eslint",
+      "ref": "pasika/policy-subject-headings",
       "note": "docs-check: every bullet sits under a subject heading"
     },
     {
       "doc": "documentation-guide/rules/policy-creation-rule.md",
       "text": "A Policy document MUST state every requirement as a bullet that uses RFC 2119 vocabulary.",
       "hash": "eff345fe21",
-      "kind": "docs-check",
-      "ref": "requirement-present"
+      "kind": "eslint",
+      "ref": "pasika/requirement-present"
     },
     {
       "doc": "documentation-guide/rules/policy-creation-rule.md",
@@ -762,22 +766,22 @@
       "doc": "documentation-guide/rules/policy-creation-rule.md",
       "text": "A Policy overview MUST contain one or two short sentences naming the scope the requirements apply to.",
       "hash": "cd5ad978b1",
-      "kind": "docs-check",
-      "ref": "overview-length"
+      "kind": "eslint",
+      "ref": "pasika/overview-length"
     },
     {
       "doc": "documentation-guide/rules/policy-creation-rule.md",
       "text": "A repository MUST NOT have more than one Policy document per audience.",
       "hash": "74dd5ffc9e",
-      "kind": "docs-check",
-      "ref": "policy-single-document"
+      "kind": "eslint",
+      "ref": "pasika/policy-single-document"
     },
     {
       "doc": "documentation-guide/rules/policy-creation-rule.md",
       "text": "Policy file names MUST match the document title in kebab-case and use the -policy suffix (e.g., foo-policy.md).",
       "hash": "e83fddcd78",
-      "kind": "docs-check",
-      "ref": "title-matches-file-name, doc-kind-suffix"
+      "kind": "eslint",
+      "ref": "pasika/title-matches-file-name, pasika/doc-kind-suffix"
     },
     {
       "doc": "documentation-guide/rules/reference-creation-rule.md",
@@ -796,8 +800,8 @@
       "doc": "documentation-guide/rules/reference-creation-rule.md",
       "text": "A Reference MUST NOT link to Rules, Guides, Policy documents, or other References.",
       "hash": "50070e301c",
-      "kind": "docs-check",
-      "ref": "no-cross-document-link"
+      "kind": "eslint",
+      "ref": "pasika/no-cross-document-link"
     },
     {
       "doc": "documentation-guide/rules/reference-creation-rule.md",
@@ -810,36 +814,36 @@
       "doc": "documentation-guide/rules/reference-creation-rule.md",
       "text": "A Reference MUST NOT use RFC 2119 vocabulary (MUST, MUST NOT, SHOULD, SHOULD NOT, MAY), because lookup material describes what exists rather than imposing requirements.",
       "hash": "b06563ebdb",
-      "kind": "docs-check",
-      "ref": "reference-no-rfc-vocabulary"
+      "kind": "eslint",
+      "ref": "pasika/reference-no-rfc-vocabulary"
     },
     {
       "doc": "documentation-guide/rules/reference-creation-rule.md",
       "text": "A Reference overview and the overview of each headed lookup block MUST contain one or two short sentences.",
       "hash": "829df330c7",
-      "kind": "docs-check",
-      "ref": "overview-length"
+      "kind": "eslint",
+      "ref": "pasika/overview-length"
     },
     {
       "doc": "documentation-guide/rules/reference-creation-rule.md",
       "text": "A Reference with a single lookup block MUST NOT add a section heading for it.",
       "hash": "a599ad8306",
-      "kind": "docs-check",
-      "ref": "reference-block-headings"
+      "kind": "eslint",
+      "ref": "pasika/reference-block-headings"
     },
     {
       "doc": "documentation-guide/rules/reference-creation-rule.md",
       "text": "A Reference with two or more lookup blocks MUST add a section heading for every block, including the first.",
       "hash": "8c8152f907",
-      "kind": "docs-check",
-      "ref": "reference-block-headings"
+      "kind": "eslint",
+      "ref": "pasika/reference-block-headings"
     },
     {
       "doc": "documentation-guide/rules/reference-creation-rule.md",
       "text": "Reference file names MUST match the document title in kebab-case and use the -reference suffix (e.g., foo-reference.md).",
       "hash": "8aae1d6156",
-      "kind": "docs-check",
-      "ref": "title-matches-file-name, doc-kind-suffix"
+      "kind": "eslint",
+      "ref": "pasika/title-matches-file-name, pasika/doc-kind-suffix"
     },
     {
       "doc": "documentation-guide/rules/rule-creation-rule.md",
@@ -851,22 +855,22 @@
       "doc": "documentation-guide/rules/rule-creation-rule.md",
       "text": "A Rule MUST NOT link to References, Guides, or other Rules.",
       "hash": "bda91d953c",
-      "kind": "docs-check",
-      "ref": "no-cross-document-link"
+      "kind": "eslint",
+      "ref": "pasika/no-cross-document-link"
     },
     {
       "doc": "documentation-guide/rules/rule-creation-rule.md",
       "text": "A Rule MUST contain at least one Incorrect/Correct pair.",
       "hash": "099da63c35",
-      "kind": "docs-check",
-      "ref": "rule-paired-examples"
+      "kind": "eslint",
+      "ref": "pasika/rule-paired-examples"
     },
     {
       "doc": "documentation-guide/rules/rule-creation-rule.md",
       "text": "A Rule MUST contain at least one bullet point that uses RFC 2119 vocabulary (MUST, MUST NOT, SHOULD, SHOULD NOT, MAY).",
       "hash": "2cfcc88337",
-      "kind": "docs-check",
-      "ref": "requirement-present"
+      "kind": "eslint",
+      "ref": "pasika/requirement-present"
     },
     {
       "doc": "documentation-guide/rules/rule-creation-rule.md",
@@ -879,8 +883,8 @@
       "doc": "documentation-guide/rules/rule-creation-rule.md",
       "text": "A Rule overview MUST contain one or two short sentences naming the problem the rule solves.",
       "hash": "ab67bac18e",
-      "kind": "docs-check",
-      "ref": "overview-length"
+      "kind": "eslint",
+      "ref": "pasika/overview-length"
     },
     {
       "doc": "documentation-guide/rules/rule-creation-rule.md",
@@ -900,29 +904,31 @@
       "doc": "documentation-guide/rules/rule-creation-rule.md",
       "text": "An Incorrect/Correct pair MUST add a concise description after an em dash in both headings, so readers can scan the examples by decision.",
       "hash": "001ce1c18c",
-      "kind": "docs-check",
-      "ref": "example-heading-description"
+      "kind": "eslint",
+      "ref": "pasika/example-heading-description"
     },
     {
       "doc": "documentation-guide/rules/rule-creation-rule.md",
       "text": "Prose outside bullet points — intros, Why: explanations, table cells, and code comments — MUST restate a requirement in plain language instead of repeating RFC 2119 vocabulary.",
       "hash": "961d7db3b9",
-      "kind": "planned",
+      "kind": "eslint",
+      "ref": "pasika/rfc-only-in-bullets",
       "note": "docs-check: RFC 2119 vocabulary appears only in bullets"
     },
     {
       "doc": "documentation-guide/rules/rule-creation-rule.md",
       "text": "RFC 2119 vocabulary MUST appear only in bullet points, so the bullet list is the single place a requirement is stated.",
       "hash": "e68233ce8b",
-      "kind": "planned",
+      "kind": "eslint",
+      "ref": "pasika/rfc-only-in-bullets",
       "note": "docs-check: RFC 2119 vocabulary appears only in bullets"
     },
     {
       "doc": "documentation-guide/rules/rule-creation-rule.md",
       "text": "Rule file names MUST match the document title in kebab-case and use the -rule suffix (e.g., foo-rule.md).",
       "hash": "58b18e4f61",
-      "kind": "docs-check",
-      "ref": "title-matches-file-name, doc-kind-suffix"
+      "kind": "eslint",
+      "ref": "pasika/title-matches-file-name, pasika/doc-kind-suffix"
     },
     {
       "doc": "documentation-guide/rules/template-usage-rule.md",
@@ -935,8 +941,8 @@
       "doc": "documentation-guide/rules/template-usage-rule.md",
       "text": "Authors MUST replace each bracketed prompt with the final title, explanation, step, or lookup content it asks for.",
       "hash": "7e7db98db0",
-      "kind": "docs-check",
-      "ref": "no-template-prompt"
+      "kind": "eslint",
+      "ref": "pasika/no-template-prompt"
     },
     {
       "doc": "documentation-guide/rules/template-usage-rule.md",
@@ -963,15 +969,15 @@
       "doc": "styling-guide/rules/class-composition-rule.md",
       "text": "A className passed to a component MUST contain only outer-layout utilities: margins, sizing, flex or grid item placement, and z-index.",
       "hash": "a84eca1927",
-      "kind": "planned",
-      "note": "eslint: a passed className carries only outer-layout utilities"
+      "kind": "eslint",
+      "ref": "pasika/enforce-cn-merge"
     },
     {
       "doc": "styling-guide/rules/class-composition-rule.md",
       "text": "A component MUST expose its supported appearance and size variants through typed props, not through a passed className or separate class-name props for internal elements.",
       "hash": "294fb0dbae",
-      "kind": "planned",
-      "note": "eslint: report class-name props for internal elements"
+      "kind": "eslint",
+      "ref": "pasika/enforce-cn-merge"
     },
     {
       "doc": "styling-guide/rules/class-composition-rule.md",
@@ -999,8 +1005,8 @@
       "doc": "styling-guide/rules/component-ui-state-rule.md",
       "text": "A component MUST express a UI state through the native element, attribute, or ARIA state for it and MUST NOT use a custom equivalent.",
       "hash": "bb3c5b82cd",
-      "kind": "planned",
-      "note": "eslint: report a custom state prop without its native attribute"
+      "kind": "eslint",
+      "ref": "pasika/ui-state"
     },
     {
       "doc": "styling-guide/rules/component-ui-state-rule.md",
@@ -1013,29 +1019,29 @@
       "doc": "styling-guide/rules/component-ui-state-rule.md",
       "text": "A component MUST use Tailwind \"state variants\" when they can express a supported UI state.",
       "hash": "0f6c3bb7ed",
-      "kind": "planned",
-      "note": "eslint: report a conditional class a state variant could express"
+      "kind": "eslint",
+      "ref": "pasika/ui-state"
     },
     {
       "doc": "styling-guide/rules/component-variant-rule.md",
       "text": "A boolean prop that changes appearance MUST use a CVA variant when both boolean values have explicit treatments or when the boolean participates in a compound variant.",
       "hash": "3393d959ca",
-      "kind": "planned",
-      "note": "eslint: cva-boolean-variants"
+      "kind": "eslint",
+      "ref": "pasika/cva-boolean-variants"
     },
     {
       "doc": "styling-guide/rules/component-variant-rule.md",
       "text": "A boolean prop that changes appearance MUST use conditional cn() when it only adds or removes one standalone class treatment.",
       "hash": "c1fc4dacbd",
-      "kind": "planned",
-      "note": "eslint: cva-boolean-variants"
+      "kind": "eslint",
+      "ref": "pasika/cva-boolean-variants"
     },
     {
       "doc": "styling-guide/rules/component-variant-rule.md",
       "text": "A component that lets callers choose visual options MUST define them with cva.",
       "hash": "8162f16933",
-      "kind": "planned",
-      "note": "eslint: report appearance props not defined with cva"
+      "kind": "eslint",
+      "ref": "pasika/cva-appearance-props"
     },
     {
       "doc": "styling-guide/rules/component-variant-rule.md",
@@ -1048,92 +1054,92 @@
       "doc": "styling-guide/rules/global-stylesheet-rule.md",
       "text": "A repository MUST have one global stylesheet entry point that registers Tailwind.",
       "hash": "4f548b26c4",
-      "kind": "planned",
-      "note": "doctor: parse the global stylesheet"
+      "kind": "doctor",
+      "ref": "pasika/global-stylesheet"
     },
     {
       "doc": "styling-guide/rules/global-stylesheet-rule.md",
       "text": "Every value used for the project's styling MUST be defined as a CSS variable in :root, even when no theme selector overrides it. A Tailwind theme variable MUST reference that CSS variable through @theme inline.",
       "hash": "d89d54996c",
-      "kind": "planned",
-      "note": "doctor: parse the global stylesheet"
+      "kind": "eslint",
+      "ref": "pasika/root-variables"
     },
     {
       "doc": "styling-guide/rules/global-stylesheet-rule.md",
       "text": "Style declarations added by the project inside global selectors MUST use @apply.",
       "hash": "9799ce3761",
-      "kind": "planned",
-      "note": "doctor: parse the global stylesheet"
+      "kind": "eslint",
+      "ref": "pasika/apply-usage"
     },
     {
       "doc": "styling-guide/rules/global-stylesheet-rule.md",
       "text": "The global base layer MUST apply base-canvas and base-ink to the document body as the default page pair.",
       "hash": "a3b7faf6da",
-      "kind": "planned",
-      "note": "doctor: parse the global stylesheet"
+      "kind": "eslint",
+      "ref": "pasika/base-layer-pair"
     },
     {
       "doc": "styling-guide/rules/global-stylesheet-rule.md",
       "text": "The global stylesheet MUST order imports, @custom-variant definitions, :root variables and the selectors that override them, @theme definitions, custom utilities, base styles, and keyframes in that order.",
       "hash": "d483eb365b",
-      "kind": "planned",
-      "note": "doctor: parse the global stylesheet"
+      "kind": "eslint",
+      "ref": "pasika/stylesheet-ordering"
     },
     {
       "doc": "styling-guide/rules/global-stylesheet-rule.md",
       "text": "The global stylesheet MUST reset Tailwind's default theme with --*: initial.",
       "hash": "d28608a7a3",
-      "kind": "planned",
-      "note": "doctor: parse the global stylesheet"
+      "kind": "eslint",
+      "ref": "pasika/theme-reset"
     },
     {
       "doc": "styling-guide/rules/global-stylesheet-rule.md",
       "text": "The project's global CSS MUST live in the global stylesheet entry point and MUST NOT be imported from another file.",
       "hash": "dce78502d3",
-      "kind": "planned",
-      "note": "doctor: parse the global stylesheet"
+      "kind": "eslint",
+      "ref": "pasika/global-css-location"
     },
     {
       "doc": "styling-guide/rules/theme-and-utility-definition-rule.md",
       "text": "A CSS variable intended only for a background MUST be named --<role>-canvas, and one intended only for readable text MUST be named --<role>-ink. When a named custom utility exposes one of those values by itself, it MUST use bg-<role>-canvas or text-<role>-ink.",
       "hash": "0fb98de16d",
-      "kind": "planned",
-      "note": "doctor: parse the global stylesheet"
+      "kind": "eslint",
+      "ref": "pasika/css-variable-naming"
     },
     {
       "doc": "styling-guide/rules/theme-and-utility-definition-rule.md",
       "text": "A custom utility MUST use @apply for every styling declaration added by the project. When no named built-in utility represents a property value, it MUST apply the Tailwind custom-property or arbitrary-property utility instead.",
       "hash": "a61de0650b",
-      "kind": "planned",
-      "note": "doctor: parse the global stylesheet"
+      "kind": "eslint",
+      "ref": "pasika/custom-utility-apply"
     },
     {
       "doc": "styling-guide/rules/theme-and-utility-definition-rule.md",
       "text": "A repeated combination of canvas, ink, and related styles MUST become a *-surface custom Tailwind utility that owns the combination.",
       "hash": "0d965db624",
-      "kind": "planned",
-      "note": "doctor: parse the global stylesheet"
+      "kind": "eslint",
+      "ref": "pasika/surface-utility"
     },
     {
       "doc": "styling-guide/rules/theme-and-utility-definition-rule.md",
       "text": "A style or group of styles that two or more components use together and should change together MUST become one named custom utility. The group MAY include utilities generated by theme variables, built-in utilities, other custom utilities, and interaction styles.",
       "hash": "9cf4c454fb",
-      "kind": "planned",
-      "note": "doctor: compare per-component styling against shared utilities"
+      "kind": "eslint",
+      "ref": "pasika/shared-style-dedup"
     },
     {
       "doc": "styling-guide/rules/theme-and-utility-definition-rule.md",
       "text": "A value that needs at least two utility classes from the same Tailwind theme-variable namespace MUST use that namespace and have the same name in :root.",
       "hash": "d9b8eeb83d",
-      "kind": "planned",
-      "note": "doctor: parse the global stylesheet"
+      "kind": "eslint",
+      "ref": "pasika/theme-variable-namespace"
     },
     {
       "doc": "styling-guide/rules/theme-and-utility-definition-rule.md",
       "text": "Styling used by only one component MUST stay in that component file as static Tailwind utility classes and MUST NOT be moved to the global stylesheet.",
       "hash": "50f1692be2",
-      "kind": "planned",
-      "note": "doctor: compare per-component styling against shared utilities"
+      "kind": "eslint",
+      "ref": "pasika/shared-style-dedup"
     }
   ]
 }