@kirill.konshin/lint 0.6.6 → 0.6.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -23,12 +23,12 @@ Do not report what these report:
23
23
 
24
24
  - `openspec validate` and `spec-tools gates`: the corpus gates (structure, citations, binding, markers, size, the scenario ratchet).
25
25
  - `spec-tools scope`: the scope, the partition and the evidence of each part.
26
- - `spec-tools report`: the merge. It re-proves each ERROR's quotes at their `file:line`, applies the tiers and the judge's verdicts, and computes the verdict.
26
+ - `spec-tools report`: the merge. It caps each severity by the kind rules and re-proves the quotes of an ERROR-band finding at their `file:line`, combines the judge's reading with the reader's, gives each finding its tier, and computes the verdict.
27
27
  - `spec-tools steward coverage`: which requirements and scenarios a test binds.
28
28
 
29
29
  ## Focused mode — `/spec-verify changed`
30
30
 
31
- `spec-tools changed` has already written `.spec-audit/parts/changed.yaml`: the requirements the working tree changed, each with its bound tests, where its terms occur, and its related requirements in full. You are the one reader. Read that file. Run checks 2, 3 and 4 over those requirements. Print the findings in the conversation. Do not start workers or write a file.
31
+ `spec-tools changed` has already written `.spec-audit/parts/changed.yaml`: the affected set of the working tree, as the `AUDIT_AFFECTED_*` variables tune it, each requirement with its bound tests, where its terms occur, and its related requirements in full. You are the one reader. Read that file. Run checks 2, 3 and 4 over those requirements. Print the findings in the conversation, each with its severity and confidence. Do not start workers or write a file.
32
32
 
33
33
  ## The material
34
34
 
@@ -41,9 +41,9 @@ Address a requirement as `<capability>#<slug>`.
41
41
 
42
42
  ## The reader
43
43
 
44
- The tool starts one reader per part, then a completion reader for each part that is short, then one judge per ERROR. The judge's rules are [`spec-verify-judge.md`](../spec-tools/references/rules/spec-verify-judge.md); the judge loads no skill.
44
+ The tool starts one reader per part, then a completion reader for each part that is short, then one judge for each finding that is severe and sure enough (`AUDIT_JUDGE_FROM`, `AUDIT_JUDGE_MIN_CONFIDENCE`). The tool combines the judge's reading with the reader's. The judge's rules are [`spec-verify-judge.md`](../spec-tools/references/rules/spec-verify-judge.md); the judge loads no skill.
45
45
 
46
- A reader judges checks 1–5 over every requirement of its part, writes its findings file, and returns one line: the path and its counts per tier. When the reader stops, the tool checks the file. If the file has errors, the tool sends them back, and the reader corrects the file.
46
+ A reader judges checks 1–5 over every requirement of its part, writes its findings file, and returns one line: the path and its counts per band (ERROR, WARN, INFO). When the reader stops, the tool checks the file. If the file has errors, the tool sends them back, and the reader corrects the file.
47
47
 
48
48
  ## The findings file
49
49
 
@@ -56,7 +56,7 @@ capabilities:
56
56
  - 'billing/refunds'
57
57
  findings:
58
58
  - kind: 'code-mismatch'
59
- tier: 'ERROR'
59
+ readerSeverity: 85
60
60
  where: 'billing/refunds#requirement-a-refund-is-applied-once / src/refunds.ts:6'
61
61
  readerConfidence: 80
62
62
  quotes:
@@ -84,10 +84,10 @@ notes:
84
84
 
85
85
  How to write each key:
86
86
 
87
- - `kind`, `tier`, `where`, `file`: double-quoted strings. `tier` is `ERROR`, `WARN` or `INFO`.
88
- - `readerConfidence`, `line`, `part`, `reader`: plain integers. Each finding has a `readerConfidence`.
87
+ - `kind`, `where`, `file`: double-quoted strings.
88
+ - `readerSeverity`, `readerConfidence`, `line`, `part`, `reader`: plain integers. Each finding has a `readerSeverity` and a `readerConfidence`, on the scales of the common rules.
89
89
  - `detail`: a literal block (`|`), one or two sentences. The report shows its first sentence.
90
- - `quotes[].text`: a stripped literal block (`|-`), copied from the source line without its line-number prefix. An ERROR has at least two quotes: one from the specification and one from the code. A quote from `.spec-audit/` or from installed dependency code (`node_modules/`) does not count: the audit judges the repository's own code. WARN and INFO findings have no quotes.
90
+ - `quotes[].text`: a stripped literal block (`|-`), copied from the source line without its line-number prefix. A finding with a severity in the ERROR band has at least two quotes: one from the specification and one from the code. Without them, the tool keeps it below the ERROR band. A quote from `.spec-audit/` or from installed dependency code (`node_modules/`) does not count: the audit judges the repository's own code. Findings below the ERROR band need no quotes.
91
91
  - `coverage`: one string per check, `"1"` to `"5"`: `"full"`. Write `"sampled: <the source>"` only when a source was not available after you tried to read it. The tool keeps it as a note; it does not change the verdict.
92
92
  - `judged`: every requirement id of the part that you judged. A missing id leaves the run short until the completion pass judges it.
93
93
  - Every path you name exists. Do not write a bare file name.
@@ -96,8 +96,8 @@ How to write each key:
96
96
 
97
97
  Run `spec-tools audit` (`--here` judges the uncommitted edits). Then summarize `.spec-audit/spec-verify.md` in ASD-STE100, one line for each finding, most severe first:
98
98
 
99
- `⟨ERROR|WARN|INFO⟩ <capability>#requirement-<slug> <file>:<line> — <kind> — <one sentence>`
99
+ `⟨ERROR|WARN|INFO⟩ <capability>#requirement-<slug> <file>:<line> — <kind> — severity <n> at <n>% — <one sentence>`
100
100
 
101
- End with the counts per tier. Without an operator (no AskUserQuestion tool), stop there. With an operator, ask once what to do next (rerun, fix the errors, fix errors and warnings, go one by one, stop), and do nothing until the operator answers. For each fix, propose the side to change (code or specification), and edit nothing until the operator confirms. After the fixes, run `spec-tools changed`, judge as in _Focused mode_, and run the checks the repository's `AGENTS.md` lists.
101
+ End with the counts per band. Without an operator (no AskUserQuestion tool), stop there. With an operator, ask once what to do next (rerun, fix the errors, fix errors and warnings, go one by one, stop), and do nothing until the operator answers. For each fix, propose the side to change (code or specification), and edit nothing until the operator confirms. After the fixes, run `spec-tools changed`, judge as in _Focused mode_, and run the checks the repository's `AGENTS.md` lists.
102
102
 
103
103
  `spec-tools report` writes `.spec-audit/spec-verify.md`. Its first line is the verdict CI reads. You never write it.