pasika 0.3.2 → 0.3.3

package/enforcement/registry.json

@@ -1,1145 +0,0 @@
-{
-  "requirements": [
-    {
-      "doc": "agent-policy.md",
-      "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"
-    },
-    {
-      "doc": "agent-policy.md",
-      "text": "A change MUST update every in-repo call site rather than preserve backward compatibility, unless the user asks for compatibility.",
-      "hash": "e765276ded",
-      "kind": "judgment",
-      "note": "recognizing a compatibility shim requires knowing the change's intent"
-    },
-    {
-      "doc": "agent-policy.md",
-      "text": "A change to the Vulyk registry MUST use Vulyk commands rather than edits to generated files.",
-      "hash": "27247db8eb",
-      "kind": "doctor",
-      "ref": "pasika/managed-file-edit"
-    },
-    {
-      "doc": "agent-policy.md",
-      "text": "A commit MUST NOT use the --no-verify flag.",
-      "hash": "e1c615452f",
-      "kind": "judgment",
-      "note": "how git was invoked is not observable from the repository"
-    },
-    {
-      "doc": "agent-policy.md",
-      "text": "A data contract's fields MUST be required unless runtime evidence shows they are optional or nullable.",
-      "hash": "b404251c21",
-      "kind": "judgment",
-      "note": "deciding a field is genuinely optional requires evidence about runtime data"
-    },
-    {
-      "doc": "agent-policy.md",
-      "text": "A file listed in a .vulyk manifest MUST NOT be edited by hand.",
-      "hash": "2390e57f4f",
-      "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": "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": "doctor",
-      "ref": "pasika/config-baseline"
-    },
-    {
-      "doc": "agent-policy.md",
-      "text": "An agent MAY discover available commands with agent-browser --help and command-specific usage with agent-browser <command> --help.",
-      "hash": "8370ec5f41",
-      "kind": "permission"
-    },
-    {
-      "doc": "agent-policy.md",
-      "text": "Browser behavior a task depends on MUST be verified with agent-browser.",
-      "hash": "034197e9d7",
-      "kind": "judgment",
-      "note": "whether a task depends on browser behavior is not observable"
-    },
-    {
-      "doc": "agent-policy.md",
-      "text": "Code MUST NOT use eslint-disable directives, and a reported violation MUST be fixed instead.",
-      "hash": "628ab4f6a6",
-      "kind": "eslint",
-      "ref": "pasika/no-eslint-disable"
-    },
-    {
-      "doc": "agent-policy.md",
-      "text": "Documentation written outside this repository MUST be consumed through Vulyk rather than copied in.",
-      "hash": "8177201b42",
-      "kind": "judgment",
-      "note": "recognizing a document as copied from elsewhere is not decidable from the repository"
-    },
-    {
-      "doc": "agent-policy.md",
-      "text": "Runtime validation MUST use Zod schemas rather than ad hoc type guards.",
-      "hash": "b5facfa0c0",
-      "kind": "judgment",
-      "note": "whether a value crosses a runtime boundary and needs validation is not decidable from source"
-    },
-    {
-      "doc": "agent-policy.md",
-      "text": "Vulyk MUST NOT be added to package.json in order to run its CLI.",
-      "hash": "1061447825",
-      "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": "eslint",
-      "ref": "pasika/no-vulyk-dependency"
-    },
-    {
-      "doc": "agent-policy.md",
-      "text": "agent-browser upgrade MUST run before agent-browser is used in a task.",
-      "hash": "aea9247939",
-      "kind": "judgment",
-      "note": "tool invocation order within a task is not observable"
-    },
-    {
-      "doc": "code-organization-guide/rules/application-structure-rule.md",
-      "text": "A feature folder, src/compositions/, src/shared/, and a nested component folder MAY each contain support folders.",
-      "hash": "5cc68d9d44",
-      "kind": "permission",
-      "note": "the application-structure check must allow support folders in these scopes"
-    },
-    {
-      "doc": "code-organization-guide/rules/application-structure-rule.md",
-      "text": "A file that does not define a component MUST have a kebab-case name.",
-      "hash": "19eb3df87a",
-      "kind": "eslint",
-      "ref": "pasika/filename-case",
-      "note": "a .tsx file that defines no component is treated as a component file"
-    },
-    {
-      "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": "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": "eslint",
-      "ref": "pasika/application-structure"
-    },
-    {
-      "doc": "code-organization-guide/rules/application-structure-rule.md",
-      "text": "Application source MUST live under src/.",
-      "hash": "0a5c03a95d",
-      "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": "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": "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": "eslint",
-      "ref": "pasika/cross-feature-import"
-    },
-    {
-      "doc": "code-organization-guide/rules/component-placement-rule.md",
-      "text": "A component whose CCF is src/features/ MUST live in src/shared/.",
-      "hash": "b1a3a85205",
-      "kind": "eslint",
-      "ref": "pasika/component-placement"
-    },
-    {
-      "doc": "code-organization-guide/rules/component-placement-rule.md",
-      "text": "A component with at least one consumer outside src/app/ and configuration modules MUST live in its CCF, calculated without imports from src/app/ or configuration modules.",
-      "hash": "ace1e1e4e0",
-      "kind": "eslint",
-      "ref": "pasika/component-placement"
-    },
-    {
-      "doc": "code-organization-guide/rules/component-placement-rule.md",
-      "text": "A component with no consumers outside src/app/ or configuration modules, and that does not import from two or more feature folders, MUST live in the feature folder it represents or supports. If no existing feature applies, it MUST introduce a new feature folder.",
-      "hash": "b3d12b8551",
-      "kind": "eslint",
-      "ref": "pasika/component-placement",
-      "note": "checks the component sits under a feature folder; which feature represents it stays judgment"
-    },
-    {
-      "doc": "code-organization-guide/rules/component-placement-rule.md",
-      "text": "When calculating a component's CCF, consumers under src/compositions/ MUST count only when no consumer is outside src/compositions/.",
-      "hash": "861dd64bfa",
-      "kind": "eslint",
-      "ref": "pasika/component-placement"
-    },
-    {
-      "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": "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": "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": "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": "eslint",
-      "ref": "pasika/application-structure"
-    },
-    {
-      "doc": "code-organization-guide/rules/configuration-rule.md",
-      "text": "An extracted configuration schema or utility MUST move to its matching root support folder when a consumer outside its configuration module imports it.",
-      "hash": "c9a8b972f2",
-      "kind": "eslint",
-      "ref": "pasika/support-file-placement"
-    },
-    {
-      "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": "eslint",
-      "ref": "pasika/application-structure"
-    },
-    {
-      "doc": "code-organization-guide/rules/constants-rule.md",
-      "text": "A constant MAY live in src/config/<module>/ instead of a constants/ folder when a developer determines that it configures application behavior and is best understood alongside the configuration that parameterizes it, even when consumers exist outside the config module.",
-      "hash": "57f90aa714",
-      "kind": "permission",
-      "note": "pasika/support-file-placement skips the constants/ folder of a configuration module"
-    },
-    {
-      "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": "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": "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": "eslint",
-      "ref": "pasika/import-through-index"
-    },
-    {
-      "doc": "code-organization-guide/rules/constants-rule.md",
-      "text": "Extracted constants MUST live in a constants/ folder at the CCF of their consumers.",
-      "hash": "34022a9e2b",
-      "kind": "eslint",
-      "ref": "pasika/support-file-placement"
-    },
-    {
-      "doc": "code-organization-guide/rules/constants-rule.md",
-      "text": "When a constant's CCF is src/features/, it MUST move to src/constants/.",
-      "hash": "2b137b9350",
-      "kind": "eslint",
-      "ref": "pasika/support-file-placement"
-    },
-    {
-      "doc": "code-organization-guide/rules/exports-and-imports-rule.md",
-      "text": "A configuration module MUST import only from root support folders and its own files.",
-      "hash": "1ef619154c",
-      "kind": "eslint",
-      "ref": "pasika/import-boundaries"
-    },
-    {
-      "doc": "code-organization-guide/rules/exports-and-imports-rule.md",
-      "text": "A file in a feature folder MUST NOT import from another feature folder, src/compositions/, or src/app/.",
-      "hash": "e91ffc37d1",
-      "kind": "eslint",
-      "ref": "pasika/import-boundaries"
-    },
-    {
-      "doc": "code-organization-guide/rules/exports-and-imports-rule.md",
-      "text": "A file in the root layer MUST NOT import from src/app/, src/compositions/, a feature folder, or src/shared/.",
-      "hash": "a73db9af2e",
-      "kind": "eslint",
-      "ref": "pasika/import-boundaries"
-    },
-    {
-      "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": "eslint",
-      "ref": "pasika/named-exports"
-    },
-    {
-      "doc": "code-organization-guide/rules/exports-and-imports-rule.md",
-      "text": "A file under src/compositions/ MUST NOT import from src/app/.",
-      "hash": "591ad01f1d",
-      "kind": "eslint",
-      "ref": "pasika/import-boundaries"
-    },
-    {
-      "doc": "code-organization-guide/rules/exports-and-imports-rule.md",
-      "text": "A file under src/shared/ MUST NOT import from src/app/, src/compositions/, or a feature folder.",
-      "hash": "901b928be3",
-      "kind": "eslint",
-      "ref": "pasika/import-boundaries"
-    },
-    {
-      "doc": "code-organization-guide/rules/exports-and-imports-rule.md",
-      "text": "Imports MUST use the relative path when the relative path and the @/* alias have the same number of segments.",
-      "hash": "2e467d4659",
-      "kind": "eslint",
-      "ref": "pasika/import-boundaries"
-    },
-    {
-      "doc": "code-organization-guide/rules/exports-and-imports-rule.md",
-      "text": "Imports MUST use whichever of the relative path and the @/* alias has fewer segments, counting each ../ step and each name in the path as one segment.",
-      "hash": "47c4ccc7fd",
-      "kind": "eslint",
-      "ref": "pasika/import-boundaries"
-    },
-    {
-      "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": "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": "eslint",
-      "ref": "pasika/stay-flat"
-    },
-    {
-      "doc": "code-organization-guide/rules/folder-nesting-rule.md",
-      "text": "A nested component's support files MUST live in its folder.",
-      "hash": "73ae41cdfe",
-      "kind": "eslint",
-      "ref": "pasika/support-file-placement"
-    },
-    {
-      "doc": "code-organization-guide/rules/folder-nesting-rule.md",
-      "text": "The nested folder's index.ts MUST named-re-export the nested component and MUST NOT re-export its exclusive children.",
-      "hash": "d3fba850df",
-      "kind": "eslint",
-      "ref": "pasika/enforce-barrel-exports"
-    },
-    {
-      "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": "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": "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": "eslint",
-      "ref": "pasika/hook-complexity"
-    },
-    {
-      "doc": "code-organization-guide/rules/hook-extraction-rule.md",
-      "text": "An extracted custom hook MUST live in a hooks/ folder at the CCF of its consumers.",
-      "hash": "9b975cbb62",
-      "kind": "eslint",
-      "ref": "pasika/support-file-placement"
-    },
-    {
-      "doc": "code-organization-guide/rules/hook-extraction-rule.md",
-      "text": "When a custom hook's CCF is src/features/, it MUST move to src/hooks/.",
-      "hash": "afef325493",
-      "kind": "eslint",
-      "ref": "pasika/support-file-placement"
-    },
-    {
-      "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": "eslint",
-      "ref": "pasika/interactive-component"
-    },
-    {
-      "doc": "code-organization-guide/rules/jsx-hygiene-rule.md",
-      "text": "An inline expression MAY contain one condition with up to one logical operator, one ternary, or one built-in method call. cn() MAY be called inline. An event handler MAY make one call inline.",
-      "hash": "d8f4ceb822",
-      "kind": "permission",
-      "note": "the jsx-hygiene check must treat exactly these as the permitted inline set"
-    },
-    {
-      "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": "eslint",
-      "ref": "pasika/jsx-hygiene"
-    },
-    {
-      "doc": "code-organization-guide/rules/locales-rule.md",
-      "text": "A locale key MUST be camelCase English based on the text, unless a direct translation would be unclear or unwieldy. In that case, it MAY describe the message's purpose instead.",
-      "hash": "94ea814921",
-      "kind": "judgment",
-      "note": "whether a key reads as its text or its purpose depends on the language"
-    },
-    {
-      "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": "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": "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": "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": "eslint",
-      "ref": "pasika/locale-placement"
-    },
-    {
-      "doc": "code-organization-guide/rules/nameable-visual-concept-rule.md",
-      "text": "A block of elements SHOULD be extracted to a component when one clear name describes the whole block.",
-      "hash": "ca77bfffc0",
-      "kind": "judgment",
-      "note": "deciding one clear name describes a block is a naming judgment"
-    },
-    {
-      "doc": "code-organization-guide/rules/no-mixed-concerns-rule.md",
-      "text": "A .tsx file that defines a component MUST contain exactly one component.",
-      "hash": "b19fe3bd34",
-      "kind": "eslint",
-      "ref": "pasika/no-mixed-concerns",
-      "note": "counts exported components; a second component that is not exported is not detected"
-    },
-    {
-      "doc": "code-organization-guide/rules/repeated-structure-rule.md",
-      "text": "A block of elements MUST be extracted as a named component when two or more places use the same arrangement of elements for the same purpose. Different data or labels do not prevent extraction.",
-      "hash": "3c1b9c7807",
-      "kind": "judgment",
-      "note": "recognizing the same arrangement used for the same purpose needs structural comparison"
-    },
-    {
-      "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": "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": "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": "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": "eslint",
-      "ref": "pasika/data-testid-case"
-    },
-    {
-      "doc": "code-organization-guide/rules/smart-vs-dumb-component-rule.md",
-      "text": "A smart component without one outer DOM element in every rendered result MAY omit data-testid.",
-      "hash": "b0dc309f05",
-      "kind": "permission",
-      "note": "the data-testid check must exempt a component with no single outer element"
-    },
-    {
-      "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": "eslint",
-      "ref": "pasika/data-testid-case"
-    },
-    {
-      "doc": "code-organization-guide/rules/sole-state-owner-rule.md",
-      "text": "A component MUST extract a named component when one part of its JSX contains every JSX expression, callback, and effect that reads one state hook's value or calls its updater.",
-      "hash": "22a896ea5f",
-      "kind": "judgment",
-      "note": "deciding one JSX part owns every read of a state hook needs subtree analysis a rule cannot ground"
-    },
-    {
-      "doc": "code-organization-guide/rules/types-and-schemas-rule.md",
-      "text": "A type MAY stay in src/config/<module>/ when its meaning is derived from the configuration that it parameterizes, even when consumers exist outside the config module.",
-      "hash": "091724ed27",
-      "kind": "permission",
-      "note": "pasika/support-file-placement skips the types/ folder of a configuration module"
-    },
-    {
-      "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": "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": "eslint",
-      "ref": "pasika/type-extraction"
-    },
-    {
-      "doc": "code-organization-guide/rules/types-and-schemas-rule.md",
-      "text": "A type or schema used only to implement one configuration module MUST live in that module's types/ or schemas/ folder.",
-      "hash": "7a5f58f278",
-      "kind": "eslint",
-      "ref": "pasika/support-file-placement"
-    },
-    {
-      "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": "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": "eslint",
-      "ref": "pasika/import-through-index"
-    },
-    {
-      "doc": "code-organization-guide/rules/types-and-schemas-rule.md",
-      "text": "Extracted types and schemas MUST live in their matching types/ or schemas/ folder at the CCF of their consumers.",
-      "hash": "d8f89cd54a",
-      "kind": "eslint",
-      "ref": "pasika/support-file-placement"
-    },
-    {
-      "doc": "code-organization-guide/rules/types-and-schemas-rule.md",
-      "text": "Importing a type or schema alongside the component that defines it MUST NOT require extraction.",
-      "hash": "061a5c0936",
-      "kind": "permission",
-      "note": "the extraction check must not fire when the consumer also imports the component from that file"
-    },
-    {
-      "doc": "code-organization-guide/rules/types-and-schemas-rule.md",
-      "text": "When a type or schema's CCF is src/features/, it MUST move to src/types/ or src/schemas/.",
-      "hash": "c8fc7e7374",
-      "kind": "eslint",
-      "ref": "pasika/support-file-placement"
-    },
-    {
-      "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": "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": "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": "eslint",
-      "ref": "pasika/util-file-name"
-    },
-    {
-      "doc": "code-organization-guide/rules/utilities-rule.md",
-      "text": "A utility used only to implement one configuration module MUST live in that module's utils/ folder.",
-      "hash": "c9d890d2d7",
-      "kind": "eslint",
-      "ref": "pasika/support-file-placement"
-    },
-    {
-      "doc": "code-organization-guide/rules/utilities-rule.md",
-      "text": "An extracted utility MUST live in the utils/ folder at the CCF of its consumers.",
-      "hash": "bb1130ed9d",
-      "kind": "eslint",
-      "ref": "pasika/support-file-placement"
-    },
-    {
-      "doc": "code-organization-guide/rules/utilities-rule.md",
-      "text": "Utilities that are used together MAY be grouped in one file.",
-      "hash": "23f36f077b",
-      "kind": "permission"
-    },
-    {
-      "doc": "code-organization-guide/rules/utilities-rule.md",
-      "text": "When a utility's CCF is src/features/, it MUST move to src/utils/.",
-      "hash": "ff2b2398f3",
-      "kind": "eslint",
-      "ref": "pasika/support-file-placement"
-    },
-    {
-      "doc": "documentation-guide/rules/guide-creation-rule.md",
-      "text": "A Guide MAY link Rules, References, Policy documents, and other Guides.",
-      "hash": "254850923a",
-      "kind": "permission",
-      "note": "docs-check no-cross-document-link exempts guides"
-    },
-    {
-      "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": "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": "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": "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": "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": "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": "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": "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": "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": "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": "eslint",
-      "ref": "pasika/no-nested-how-to",
-      "note": "docs-check: no heading nests inside a How To section"
-    },
-    {
-      "doc": "documentation-guide/rules/guide-creation-rule.md",
-      "text": "When a step links another document, the step MUST name the concrete decision or result the reader will have after reading it.",
-      "hash": "b38e3ef9c9",
-      "kind": "judgment",
-      "note": "whether a step names a concrete result is a reading judgment"
-    },
-    {
-      "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": "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": "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": "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": "eslint",
-      "ref": "pasika/requirement-present"
-    },
-    {
-      "doc": "documentation-guide/rules/policy-creation-rule.md",
-      "text": "A Policy document MUST state requirements that apply to the whole repository and span two or more unrelated subjects.",
-      "hash": "689de34a0a",
-      "kind": "judgment",
-      "note": "deciding subjects are unrelated enough to share one document is an editorial call"
-    },
-    {
-      "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": "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": "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": "eslint",
-      "ref": "pasika/title-matches-file-name, pasika/doc-kind-suffix"
-    },
-    {
-      "doc": "documentation-guide/rules/reference-creation-rule.md",
-      "text": "A Reference MAY define terms that Rules, Guides, and Policy documents use.",
-      "hash": "0286f4b092",
-      "kind": "permission"
-    },
-    {
-      "doc": "documentation-guide/rules/reference-creation-rule.md",
-      "text": "A Reference MAY name an RFC 2119 keyword as lookup content, because naming a keyword does not impose a requirement.",
-      "hash": "5e3305d40a",
-      "kind": "permission",
-      "note": "docs-check reference-no-rfc-vocabulary ignores code spans"
-    },
-    {
-      "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": "eslint",
-      "ref": "pasika/no-cross-document-link"
-    },
-    {
-      "doc": "documentation-guide/rules/reference-creation-rule.md",
-      "text": "A Reference MUST NOT state a constraint the reader has to satisfy, even in plain declarative wording, and a constraint the reader has to satisfy MUST live in a Rule.",
-      "hash": "36dfefa25c",
-      "kind": "judgment",
-      "note": "recognizing a constraint stated as description requires reading it as a reader would"
-    },
-    {
-      "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": "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": "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": "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": "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": "eslint",
-      "ref": "pasika/title-matches-file-name, pasika/doc-kind-suffix"
-    },
-    {
-      "doc": "documentation-guide/rules/rule-creation-rule.md",
-      "text": "A Rule MAY contain multiple Incorrect/Correct pairs.",
-      "hash": "f6d4ce8fa7",
-      "kind": "permission"
-    },
-    {
-      "doc": "documentation-guide/rules/rule-creation-rule.md",
-      "text": "A Rule MUST NOT link to References, Guides, or other Rules.",
-      "hash": "bda91d953c",
-      "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": "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": "eslint",
-      "ref": "pasika/requirement-present"
-    },
-    {
-      "doc": "documentation-guide/rules/rule-creation-rule.md",
-      "text": "A Rule MUST state requirements about one subject.",
-      "hash": "5385606287",
-      "kind": "judgment",
-      "note": "deciding requirements share one subject is an editorial call"
-    },
-    {
-      "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": "eslint",
-      "ref": "pasika/overview-length"
-    },
-    {
-      "doc": "documentation-guide/rules/rule-creation-rule.md",
-      "text": "A bullet MUST NOT define a term, and a term a reader needs in order to apply the Rule MUST be defined in a Reference instead.",
-      "hash": "26f85889e2",
-      "kind": "judgment",
-      "note": "recognizing a bullet as a definition rather than a demand is a reading judgment"
-    },
-    {
-      "doc": "documentation-guide/rules/rule-creation-rule.md",
-      "text": "A bullet MUST use MUST or MUST NOT only when the requirement admits no exception, and SHOULD or SHOULD NOT only when exceptions are possible.",
-      "hash": "67e994bec5",
-      "kind": "judgment",
-      "note": "matching a keyword's strength to the requirement's intent is a reading judgment"
-    },
-    {
-      "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": "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": "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": "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": "eslint",
-      "ref": "pasika/title-matches-file-name, pasika/doc-kind-suffix"
-    },
-    {
-      "doc": "documentation-guide/rules/template-usage-rule.md",
-      "text": "Authors MUST delete template branches that do not apply to the document being written.",
-      "hash": "dbe2070bf9",
-      "kind": "judgment",
-      "note": "an unused branch is only recognizable by comparing against the template"
-    },
-    {
-      "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": "eslint",
-      "ref": "pasika/no-template-prompt"
-    },
-    {
-      "doc": "documentation-guide/rules/template-usage-rule.md",
-      "text": "Authors MUST start from the template that matches the chosen document kind and structure.",
-      "hash": "08faa3cb70",
-      "kind": "judgment",
-      "note": "which template an author started from is not recorded in the result"
-    },
-    {
-      "doc": "documentation-guide/rules/template-usage-rule.md",
-      "text": "Documentation support assets MAY live in folders whose names start with an underscore.",
-      "hash": "faeb62c465",
-      "kind": "permission",
-      "note": "the documentation parser skips folders whose names start with an underscore"
-    },
-    {
-      "doc": "styling-guide/rules/arbitrary-value-rule.md",
-      "text": "Components MUST NOT use arbitrary-value classes for project styling. They MUST use an existing Tailwind or project utility, or define a project token or custom utility first.",
-      "hash": "426116116d",
-      "kind": "eslint",
-      "ref": "pasika/no-arbitrary-tailwind"
-    },
-    {
-      "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": "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": "eslint",
-      "ref": "pasika/enforce-cn-merge"
-    },
-    {
-      "doc": "styling-guide/rules/class-composition-rule.md",
-      "text": "A static class list with more than five class names MUST use cn with multiple string literals, each grouped by styling concern and containing no more than five class names.",
-      "hash": "2c58fa578d",
-      "kind": "eslint",
-      "ref": "pasika/enforce-cn-merge"
-    },
-    {
-      "doc": "styling-guide/rules/class-composition-rule.md",
-      "text": "Components MUST NOT concatenate class strings with template literals or + when any part is conditional.",
-      "hash": "3afbe2697b",
-      "kind": "eslint",
-      "ref": "pasika/enforce-cn-merge"
-    },
-    {
-      "doc": "styling-guide/rules/class-composition-rule.md",
-      "text": "Components MUST use cn or the project's equivalent class-merging helper for conditional classes and a className passed to the component.",
-      "hash": "ecc15933e6",
-      "kind": "eslint",
-      "ref": "pasika/enforce-cn-merge",
-      "note": "detects + and template literals; a conditional expression without cn is not detected"
-    },
-    {
-      "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": "eslint",
-      "ref": "pasika/ui-state"
-    },
-    {
-      "doc": "styling-guide/rules/component-ui-state-rule.md",
-      "text": "A component MUST own a distinguishable appearance for every UI state it supports.",
-      "hash": "fae776da92",
-      "kind": "judgment",
-      "note": "whether every supported state looks distinguishable is a visual judgment"
-    },
-    {
-      "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": "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": "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": "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": "eslint",
-      "ref": "pasika/cva-appearance-props"
-    },
-    {
-      "doc": "styling-guide/rules/component-variant-rule.md",
-      "text": "A component's variant prop types MUST be derived from its cva definition with VariantProps rather than manually duplicated unions.",
-      "hash": "c9d1cf136c",
-      "kind": "eslint",
-      "ref": "pasika/enforce-cva-variant-props"
-    },
-    {
-      "doc": "styling-guide/rules/global-stylesheet-rule.md",
-      "text": "A repository MUST have one global stylesheet entry point that registers Tailwind.",
-      "hash": "4f548b26c4",
-      "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": "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": "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": "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": "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": "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": "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": "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": "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": "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": "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": "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": "eslint",
-      "ref": "pasika/shared-style-dedup"
-    }
-  ]
-}