pasika 0.3.3 → 0.3.4

package/README.md

@@ -2,13 +2,14 @@
 
 Documentation, the lint rules derived from it, and the CLI that applies and diagnoses both.
 
-`pasika` owns the framework's documentation and turns it into checks. Every requirement in `docs/` is recorded in an enforcement registry that says which ESLint rule, which `pasika` check, or which human judgment covers it — and CI fails when a requirement has no answer.
+`pasika` owns the framework's documentation and turns it into checks. Every requirement in `docs/` is recorded in an enforcement registry that says which ESLint rule or `pasika` check governs it — or, when none does, how a reviewer or agent applies it by hand. CI fails when a requirement has no recorded answer.
 
 ## Layout
 
 ```text
 docs/
-  agent-policy.md                 # repo-wide requirements (Policy)
+  agent-policy.md                 # agent-conduct requirements (Policy)
+  repository-policy.md            # repo-wide code and documentation requirements (Policy)
   code-organization-guide/        # placement, extraction, module conventions
   documentation-guide/            # how documents themselves are written
   framework-adoption-guide/       # adopting and updating the framework
@@ -36,23 +37,16 @@ Requirements are identified by a hash of their canonical text, not by a hand-wri
   "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"
 }
 ```
 
-The `text` field is the bullet as written in the document (markdown links and code spans intact), so it is greppable in the doc it came from; the `hash` is computed from the same text with links collapsed to their text and code spans unwrapped, so editing a URL or adding backticks does not read as a change. The `note` field is where a check's known gap is recorded, so a partial check never reads as a complete one.
+The `text` field is the bullet as written in the document (markdown links and code spans intact), so it is greppable in the doc it came from; the `hash` is computed from the same text with links collapsed to their text and code spans unwrapped, so editing a URL or adding backticks does not read as a change.
 
-| Kind | Meaning |
-| --- | --- |
-| `eslint` | An ESLint rule reports it, and a fixture test titled with the requirement pins it |
-| `doctor` | A `pasika doctor` check reports it |
-| `planned` | Mechanically checkable, not written yet; `note` names the intended check |
-| `judgment` | No mechanical check can decide it; `note` says why |
-| `permission` | The requirement grants permission, so there is nothing to check |
+Every requirement carries a `note` explaining how it is met: what the ref'd rule or doctor check does and where it falls short, or — with no `ref` — how a reviewer or agent applies it by hand. When a rule governs the requirement's subject without fully deciding it (e.g. its placement), the `ref` still names that rule and the `note` says what stays judgment, so a partial check never reads as a complete one.
 
-`pasika coverage` fails when a requirement is unclassified, when its text changed, when it disappeared, when its `ref` names a check that does not exist, or when a lint-enforced requirement has no test. Confirm a reworded requirement with `pasika coverage --accept`.
+`pasika coverage` fails when a requirement has no recorded answer, when its text changed, when it disappeared, when its `ref` names a rule or doctor check that does not exist, or when a requirement a rule governs has no test titled with its text. Confirm a reworded requirement with `pasika coverage --accept`.
 
 ## Commands
 
@@ -68,11 +62,11 @@ Both accept `--json` for agent use.
 A requirement `coverage` reports as `new` is classified with the hash it prints:
 
 ```bash
-npx pasika coverage --classify d311a1457a --kind eslint --ref pasika/import-boundaries
-npx pasika coverage --classify 041b665bd7 --kind judgment --note "no check can compare against the previous state"
+npx pasika coverage --classify d311a1457a --ref pasika/import-boundaries --note "reports imports that cross a feature boundary"
+npx pasika coverage --classify 041b665bd7 --note "no check can compare against the previous state"
 ```
 
-The command refuses a hash no requirement has, a `ref` naming a rule or check that does not exist, a `ref` on a kind that nothing reports, and `judgment` or `planned` without a note — so a mismatch cannot reach the registry by hand. Re-running it on an already-classified requirement reclassifies it and reports what it was.
+The command refuses a hash no requirement has, a `ref` naming a rule or doctor check that does not exist, and an entry without a note — so a mismatch cannot reach the registry by hand. Re-running it on an already-recorded requirement replaces the earlier entry.
 
 ## ESLint ruleset
 
@@ -144,6 +138,8 @@ export default [pasikaConfig];
 | `pasika/locale-placement` † | Shared locales at the top level, single-feature locales namespaced |
 | `pasika/shared-style-dedup` † | A className combo used by two or more components becomes a named utility |
 | `pasika/no-eslint-disable` | No `eslint-disable` directives |
+| `pasika/zod-schema-validation` | Runtime validation through Zod schemas, not hand-written type guards |
+| `pasika/source-under-src` | Application source lives under `src/`, not in root-level folders |
 
 ### CSS rules
 
@@ -173,7 +169,7 @@ Applied to `package.json` through `@eslint/json`.
 
 ### Documentation rules
 
-The `pasika/*` markdown rules enforce the documentation guide over `docs/**/*.md` (24 rules): file-name suffixes and titles, overview presence and length, guide step structure, Incorrect/Correct pairing, policy document shape, reference block headings, RFC 2119 placement, template hygiene, link anchoring, and glossary-term linking. They run through `@eslint/markdown`; `pasika coverage` verifies each has a test and a registry entry. Pasika's own `docs/` are linted by them in CI (`npm run docs`).
+The `pasika/*` markdown rules enforce the documentation guide over `docs/**/*.md` (24 rules): file-name suffixes and titles, overview presence and length, guide step structure, Incorrect/Correct pairing, policy document shape, reference block headings, RFC 2119 placement, template hygiene, link anchoring, and glossary-term linking. They run through `@eslint/markdown`; `pasika coverage` verifies each has a test and a registry entry. Pasika's own `docs/` are linted by them in CI (`npm run lint`).
 
 Run `pasika coverage --json` for the exact requirement each rule covers.
 
@@ -181,7 +177,7 @@ Run `pasika coverage --json` for the exact requirement each rule covers.
 
 Where a component, hook, value, type, or style belongs depends on which files use it, so the rules marked † index the whole `src/` tree instead of looking at one file. Two consequences:
 
-- **Do not pass `--cache`.** Move a file and the finding belongs to a *different* file, whose cache entry is unchanged — so ESLint would replay a stale verdict. `agent-policy.md` requires lint commands to run without it.
+- **Do not pass `--cache`.** Move a file and the finding belongs to a *different* file, whose cache entry is unchanged — so ESLint would replay a stale verdict. `repository-policy.md` requires lint commands to run without it.
 - The index is read from disk rather than from ESLint's file list, so a partial run such as `lint-staged` still judges against the true graph.
 
 All are inert in a repository with no `src/` tree.

package/dist/cli/index.d.ts

@@ -1,2 +1 @@
 #!/usr/bin/env node
-export {};