@kirill.konshin/lint 0.6.4 → 0.6.6
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.
- package/README.md +6 -6
- package/dist/lintPrepare.d.ts +18 -23
- package/dist/lintPrepare.js +68 -82
- package/package.json +1 -3
- package/rules/agent.md +2 -7
- package/skills/lint-repo/SKILL.md +2 -2
- package/{commands/spec-author.md → skills/spec-author/SKILL.md} +4 -4
- package/skills/spec-steward/SKILL.md +14 -9
- package/skills/spec-steward/references/apply.md +14 -14
- package/skills/spec-steward/references/audit.md +15 -15
- package/skills/spec-steward/references/contract.md +6 -6
- package/skills/spec-steward/references/model.md +13 -1
- package/skills/spec-steward/references/review-format.md +70 -44
- package/skills/spec-steward/references/worker.md +51 -53
- package/skills/spec-tools/SKILL.md +14 -8
- package/skills/spec-tools/references/contract.md +19 -12
- package/skills/spec-tools/references/gitlab.md +22 -24
- package/skills/spec-tools/references/rules/common.md +46 -0
- package/skills/spec-tools/references/rules/spec-steward.md +71 -0
- package/skills/spec-tools/references/rules/spec-verify-judge.md +17 -0
- package/skills/spec-tools/references/rules/spec-verify.md +50 -0
- package/skills/spec-tools/scripts/cli.js +8255 -1811
- package/skills/spec-verify/SKILL.md +78 -128
- package/skills/spec-steward/references/criteria.md +0 -59
|
@@ -7,7 +7,7 @@ The jobs a GitLab repository runs around `spec-steward` and `spec-tools`. Names
|
|
|
7
7
|
- `openspec validate` and `spec-tools gates` are gates over repository state, not unit tests: each runs as a job of its own, never inside a unit suite. An error fails its job; a warning never does.
|
|
8
8
|
- The diff, the coverage report and the merge-request comment are reports: they never fail a pipeline.
|
|
9
9
|
- `workflow-evidence` runs on merge requests to the default branch, and on default-branch pushes, where a red holds the release.
|
|
10
|
-
- The audit jobs accept exit 3 (`INCOMPLETE`) and 77 (
|
|
10
|
+
- The audit jobs accept exit 3 (`INCOMPLETE`) and 77 (`ADVISORY`, ERRORs at 80% confidence or lower, or a `FAIL` on an advisory run) as allowed failures; a gating `FAIL` (exit 1, an ERROR above 80%) blocks.
|
|
11
11
|
- Report jobs depend on the audits with `dependencies:` and `when: always`, never `needs:` — a failed audit is exactly when its report matters.
|
|
12
12
|
- The default-branch pipeline publishes the reports on Pages, a failing one included; a report a run did not produce is omitted.
|
|
13
13
|
- The scheduled nightly sets `SPEC_AUDIT_NIGHTLY=true`, so `spec-tools tier` audits the corpus there.
|
|
@@ -40,6 +40,8 @@ Cache `.claude-code/` keyed on `CLAUDE_CODE_VERSION`, and gitignore it. The job
|
|
|
40
40
|
|
|
41
41
|
## Jobs
|
|
42
42
|
|
|
43
|
+
Every job writes under `.spec-audit/` and publishes that one folder; the repository ignores it with one `.gitignore` line, `.spec-audit/`. Jobs that hand files on through `dependencies:` or `needs:` merge their `.spec-audit/` folders.
|
|
44
|
+
|
|
43
45
|
```yaml
|
|
44
46
|
openspec:
|
|
45
47
|
stage: review
|
|
@@ -60,31 +62,25 @@ spec-diff:
|
|
|
60
62
|
stage: review
|
|
61
63
|
rules: [if: $CI_MERGE_REQUEST_TARGET_BRANCH_NAME == $CI_DEFAULT_BRANCH]
|
|
62
64
|
script: [yarn spec-tools diff]
|
|
63
|
-
artifacts: { when: always, paths: [spec-
|
|
65
|
+
artifacts: { when: always, paths: [.spec-audit/] }
|
|
64
66
|
|
|
65
67
|
# The run class, the coverage report and the audit's inputs, handed on as artifacts — with the package's skills/,
|
|
66
68
|
# which hold the CLI the AI jobs run.
|
|
67
69
|
spec-coverage:
|
|
68
70
|
stage: review
|
|
69
71
|
script:
|
|
70
|
-
-
|
|
71
|
-
-
|
|
72
|
-
-
|
|
72
|
+
- mkdir -p .spec-audit
|
|
73
|
+
- yarn spec-tools tier | tee .spec-audit/tier.env
|
|
74
|
+
- set -a && . ./.spec-audit/tier.env && set +a
|
|
75
|
+
- yarn spec-tools steward coverage
|
|
73
76
|
- yarn spec-tools scope
|
|
74
77
|
artifacts:
|
|
75
78
|
when: always
|
|
76
|
-
reports: { dotenv: audit
|
|
77
|
-
paths:
|
|
78
|
-
[
|
|
79
|
-
audit-tier.env,
|
|
80
|
-
spec-coverage.md,
|
|
81
|
-
audit-scope.json,
|
|
82
|
-
audit-parts/,
|
|
83
|
-
node_modules/@kirill.konshin/lint/skills/,
|
|
84
|
-
]
|
|
79
|
+
reports: { dotenv: .spec-audit/tier.env }
|
|
80
|
+
paths: [.spec-audit/, node_modules/@kirill.konshin/lint/skills/]
|
|
85
81
|
|
|
86
82
|
# The audit, in one job: read (a failed reading leaves its parts to the completion pass), merge, complete what the
|
|
87
|
-
# reading left short,
|
|
83
|
+
# reading left short, judge every ERROR, gate.
|
|
88
84
|
spec-verify:
|
|
89
85
|
stage: review
|
|
90
86
|
image: <an image with node>
|
|
@@ -99,10 +95,10 @@ spec-verify:
|
|
|
99
95
|
- node node_modules/@kirill.konshin/lint/skills/spec-tools/scripts/cli.js report
|
|
100
96
|
- node node_modules/@kirill.konshin/lint/skills/spec-tools/scripts/cli.js workers --verify
|
|
101
97
|
- node node_modules/@kirill.konshin/lint/skills/spec-tools/scripts/cli.js report
|
|
102
|
-
- node node_modules/@kirill.konshin/lint/skills/spec-tools/scripts/cli.js verdict spec-verify.
|
|
103
|
-
artifacts: { when: always, paths: [
|
|
98
|
+
- node node_modules/@kirill.konshin/lint/skills/spec-tools/scripts/cli.js verdict .spec-audit/spec-verify.yaml
|
|
99
|
+
artifacts: { when: always, paths: [.spec-audit/] }
|
|
104
100
|
|
|
105
|
-
# Any other skill-driven review: headless, then its verdict.
|
|
101
|
+
# Any other skill-driven review: headless, its YAML report checked, then its verdict computed and its Markdown rendered.
|
|
106
102
|
some-review:
|
|
107
103
|
stage: review
|
|
108
104
|
image: <an image with node>
|
|
@@ -110,8 +106,8 @@ some-review:
|
|
|
110
106
|
allow_failure: { exit_codes: [3, 77] }
|
|
111
107
|
script:
|
|
112
108
|
- *claude-code
|
|
113
|
-
- node node_modules/@kirill.konshin/lint/skills/spec-tools/scripts/cli.js run some-review --verdict some-review.
|
|
114
|
-
artifacts: { when: always, paths: [
|
|
109
|
+
- node node_modules/@kirill.konshin/lint/skills/spec-tools/scripts/cli.js run some-review --verdict .spec-audit/some-review.yaml --advisory
|
|
110
|
+
artifacts: { when: always, paths: [.spec-audit/] }
|
|
115
111
|
|
|
116
112
|
render-reviews:
|
|
117
113
|
stage: deploy
|
|
@@ -122,11 +118,13 @@ render-reviews:
|
|
|
122
118
|
- if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
|
|
123
119
|
when: always
|
|
124
120
|
script:
|
|
125
|
-
- yarn spec-tools html spec-verify.md some-review.md spec-coverage.md spec-diff.md
|
|
126
|
-
- yarn spec-tools comment spec-verify
|
|
121
|
+
- yarn spec-tools html .spec-audit/spec-verify.md .spec-audit/some-review.md .spec-audit/coverage.md .spec-audit/spec-diff.md
|
|
122
|
+
- yarn spec-tools comment spec-verify=.spec-audit/spec-verify.md some-review=.spec-audit/some-review.md
|
|
127
123
|
# Posting needs a token that may write notes; CI_JOB_TOKEN cannot.
|
|
128
|
-
- '[ -z "$CI_MERGE_REQUEST_IID" ] || glab api --method POST "projects/$CI_PROJECT_ID/merge_requests/$CI_MERGE_REQUEST_IID/notes" -f "body=$(cat mr-comment.md)"'
|
|
129
|
-
artifacts: { when: always, paths: [
|
|
124
|
+
- '[ -z "$CI_MERGE_REQUEST_IID" ] || glab api --method POST "projects/$CI_PROJECT_ID/merge_requests/$CI_MERGE_REQUEST_IID/notes" -f "body=$(cat .spec-audit/mr-comment.md)"'
|
|
125
|
+
artifacts: { when: always, paths: [.spec-audit/] }
|
|
130
126
|
```
|
|
131
127
|
|
|
132
128
|
A release job that must wait for the audit `needs:` the judge (`spec-verify`), so a gating `FAIL` on the default branch holds it.
|
|
129
|
+
|
|
130
|
+
A skill-driven review writes `.spec-audit/<review>.yaml` in the shape `spec-tools run` checks (`findings[tier, where, detail, readerConfidence, fields]`, `coverage{complete, notes}`). `verdict` computes its state from that file, never from the model's words, and writes `.spec-audit/<review>.md` beside it for the comment and the HTML.
|
|
@@ -0,0 +1,46 @@
|
|
|
1
|
+
# Judging rules: common
|
|
2
|
+
|
|
3
|
+
These rules tell what a finding is and which tier it gets. They apply to every audit that spec-tools runs: spec-verify, its judge, spec-steward and check-entity-hacks. The skill and the tool tell how a run works.
|
|
4
|
+
|
|
5
|
+
## Evidence
|
|
6
|
+
|
|
7
|
+
- Judge what the repository shows: the specification as written, the code, the tests and the configuration.
|
|
8
|
+
- A comment, a citation, a description, a marker (`SANCTIONED`, `FIXME`, `TODO`) or prompt text is not evidence. It is also not a defect.
|
|
9
|
+
- Behaviour that comes from a dependency (a command-line flag, a library default) is not demonstrated when the repository does not show it.
|
|
10
|
+
- Installed dependency code (`node_modules/`) is not the repository. Do not judge it, and do not use it as evidence. A defect in a dependency is for that dependency's own tests, not for this audit.
|
|
11
|
+
- A finding is demonstrated when you read both sides and quote each side at `file:line`. Other findings are suspected.
|
|
12
|
+
- A finding names the difference. The owner decides which side to change.
|
|
13
|
+
|
|
14
|
+
## Production effect
|
|
15
|
+
|
|
16
|
+
- A real defect has a production effect when it does one of these in production:
|
|
17
|
+
- It breaks a flow. An operation fails, stops, does not stop, or does a completely wrong thing (strong disconnect between requirement and effect: save deletes, update goes nowhere, etc).
|
|
18
|
+
- It violates a contract or an invariant: an interface, a data rule, an order, an identity, or a write to the wrong record.
|
|
19
|
+
- It leaks sensitive data: credentials, tokens or personal data go to logs, to users or to another system.
|
|
20
|
+
- It causes a performance problem: work without a limit, a loop that does not stop, or a resource that is not released.
|
|
21
|
+
- Code that does not run in production has no production effect. This includes tests, local-only and development-only modes, demo agents, and internal CI or developer scripts. The exception: such code lets a production defect through now, and you show an instance.
|
|
22
|
+
- A difference in words, names, structure or style has no production effect when the behaviour stays the same.
|
|
23
|
+
|
|
24
|
+
## Tiers
|
|
25
|
+
|
|
26
|
+
- ERROR: a demonstrated defect with a production effect. Write the production scenario in one sentence: what occurs, to whom, and what breaks, leaks or becomes slow.
|
|
27
|
+
- WARN: a suspected defect, or a demonstrated defect with no production effect.
|
|
28
|
+
- INFO: a state or a risk for a reviewer. It is never a failure.
|
|
29
|
+
- A finding against a requirement marked `**⚠️ Advisory:**` is WARN or lower.
|
|
30
|
+
- Use the effect to find the tier. The size of the difference does not decide the tier.
|
|
31
|
+
|
|
32
|
+
## Confidence
|
|
33
|
+
|
|
34
|
+
- Give each finding `readerConfidence`, an integer from 0 to 100. It tells how sure you are that the finding is an ERROR as ERROR rule in Tiers section tells. It includes the defect and its production effect.
|
|
35
|
+
- Use a value below 50 when you could not read a side, or when the effect needs a condition that you could not confirm.
|
|
36
|
+
- Assess if defect is on critical path or is an edge case. Issues not on critical path or low severity edge cases are a WARN. Edge cases that may lead to real production defect may be ERROR. Reflect this in `readerConfidence`.
|
|
37
|
+
|
|
38
|
+
## Scope
|
|
39
|
+
|
|
40
|
+
- Report each defect one time, at its final tier.
|
|
41
|
+
- Do not report a thing that a deterministic tool reports: coverage, citations, gates, lint.
|
|
42
|
+
- Do not report style preferences.
|
|
43
|
+
|
|
44
|
+
## Language
|
|
45
|
+
|
|
46
|
+
- Write finding details, verdict reasons, review items and messages to the reviewer in ASD-STE100: short sentences, active voice, one statement in each sentence, one word for one meaning. Technical names (files, functions, fields) stay as they are.
|
|
@@ -0,0 +1,71 @@
|
|
|
1
|
+
# Judging rules: spec-steward
|
|
2
|
+
|
|
3
|
+
Use the common rules first: [common.md](common.md). How to write a specification is in the spec-steward [model](../../../spec-steward/references/model.md).
|
|
4
|
+
|
|
5
|
+
This audit judges if the specification holds the correct rules with the correct evidence. It reports problems in the specification. Defects in the code are for spec-verify.
|
|
6
|
+
|
|
7
|
+
## Items to report
|
|
8
|
+
|
|
9
|
+
1. A REQUIRED rule that must be ⚠️ Advisory (see Severity).
|
|
10
|
+
2. A rule that belongs in `AGENTS.md`, a scoped rule, a skill, a command, the OpenSpec configuration or a README. The placement guide is `rules/agent.md`.
|
|
11
|
+
3. A rule that a deterministic tool can enforce better than an AI audit.
|
|
12
|
+
4. A rule that causes tests of low value or artificial tests.
|
|
13
|
+
5. A rule whose tests satisfy the wording while failing to protect the intent.
|
|
14
|
+
6. A rule that you cannot verify in a reasonable way.
|
|
15
|
+
7. A rule whose words permit different meanings. This includes a vague word in a REQUIRED statement (thin, safe, lean, at parity, needed).
|
|
16
|
+
8. A rule that describes implementation detail, not an invariant that is important outside the code.
|
|
17
|
+
9. A rule redundant with, or substantially overlapping, another.
|
|
18
|
+
10. Contradictory rules.
|
|
19
|
+
11. A rule that no longer matches the implementation or architecture.
|
|
20
|
+
12. An implementation that shows that the specification is wrong or old.
|
|
21
|
+
13. A missing invariant of high value that the architecture uses.
|
|
22
|
+
14. A rule with an unclear scope.
|
|
23
|
+
15. A rule that needs reasoning about the full repository when one subsystem is sufficient.
|
|
24
|
+
16. A rule that causes agents to change a specification only to make the code pass.
|
|
25
|
+
17. A rule whose verification uses comments or text matching.
|
|
26
|
+
18. A rule whose cost is too high for the failure that it prevents.
|
|
27
|
+
19. Requirements or scenarios that repeat each other.
|
|
28
|
+
20. A scenario structure that adds words but not precision.
|
|
29
|
+
21. One concern that two or more mechanisms hold. Name the owner and the copies to remove.
|
|
30
|
+
22. A rule that more than one repository shares, with different words.
|
|
31
|
+
23. A CI or audit configuration that costs more than the signal it gives.
|
|
32
|
+
24. Citation machinery that costs more to keep than it gives.
|
|
33
|
+
|
|
34
|
+
Items 5, 9, 10 and 11 have the same names as spec-verify's checks 5, 3, 2 and 4. spec-verify judges them against the code. This audit judges if the rule itself must change.
|
|
35
|
+
|
|
36
|
+
## How to judge
|
|
37
|
+
|
|
38
|
+
25. Find the failure that the verification of the rule catches. If that failure is trivial, artificial or only textual, do not propose that verification.
|
|
39
|
+
26. Do not propose a test only because a rule has no test.
|
|
40
|
+
27. An ordinary code defect is out of scope. The exception: it shows that the rule is not realistic, not clear, old, or contradicted.
|
|
41
|
+
28. When the intent is not clear, say it, give options, and set `needsHumanIntent`.
|
|
42
|
+
29. An internal contract that other code uses is specification. Do not move it out because it is not visible to users.
|
|
43
|
+
30. A proposal that reverses an owner decision names that decision.
|
|
44
|
+
|
|
45
|
+
## Severity: REQUIRED or ⚠️ Advisory
|
|
46
|
+
|
|
47
|
+
31. REQUIRED: a rule whose violation has a production effect (common rules, Production effect). This includes a contract, an invariant, security, data and performance.
|
|
48
|
+
32. ⚠️ Advisory: implementation detail that stays in the specification, development-only and local-only behaviour, demo agents, internal CI and developer tools, prompt wording, and design direction.
|
|
49
|
+
33. Split a rule that mixes a contract and guidance. The contract stays REQUIRED.
|
|
50
|
+
34. An existing requirement becomes Advisory only by the owner's decision. Propose it. Do not apply it.
|
|
51
|
+
|
|
52
|
+
## Proposals
|
|
53
|
+
|
|
54
|
+
35. Each proposal names its target:
|
|
55
|
+
- `Keep → OpenSpec REQUIRED invariant`, with a rewrite or a `**⚠️ Known gap (<tracker>):**` line when its behaviour or evidence is missing.
|
|
56
|
+
- `Reclassify → OpenSpec ⚠️ ADVISORY`.
|
|
57
|
+
- `Move → <target>`: the design narrative, `<dir>/AGENTS.md`, `scoped rule (<glob>)`, `skill <name>`, `command <name>`, `openspec/config.yaml#<key>`, `README.md`.
|
|
58
|
+
- `Replace → <tool>`: an ESLint rule, a dependency rule, a type assertion, a schema, a script.
|
|
59
|
+
- `Merge → <other rule>`, `Rewrite → "<new text>"`, `Delete → <reason>`.
|
|
60
|
+
|
|
61
|
+
## The steward judge
|
|
62
|
+
|
|
63
|
+
36. Keep a finding that is specific, has evidence, and has a correct proposal. Change or remove a finding when:
|
|
64
|
+
- it decides an unclear intent without the owner (change it: set `needsHumanIntent`);
|
|
65
|
+
- it is a style preference, an ordinary defect or a guess (remove it);
|
|
66
|
+
- its proposed verification catches no real failure (change or remove it);
|
|
67
|
+
- it moves an internal contract out only because users cannot see it (change it);
|
|
68
|
+
- it contradicts the placement guide (change it);
|
|
69
|
+
- it reverses an owner decision and does not say so (change it);
|
|
70
|
+
- it uses a false statement about code, tests, tools or CI (change or remove it).
|
|
71
|
+
37. Give `judgeConfidence`, an integer from 0 to 100. The review file puts items at 70 or lower under "Low confidence".
|
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
# Judging rules: spec-verify judge
|
|
2
|
+
|
|
3
|
+
Use the common rules first: [common.md](common.md).
|
|
4
|
+
|
|
5
|
+
Be aware of the reader rules: [spec-verify.md](spec-verify.md), but focus on the rules below in THIS file, you MUST follow them strictly.
|
|
6
|
+
|
|
7
|
+
You judge one finding. The reader gave it the tier ERROR and a `readerConfidence`. You can confirm it or make it WARN. You CANNOT make a finding more severe (WARN/INFO -> ERROR or INFO->ERROR etc).
|
|
8
|
+
|
|
9
|
+
- Read the requirement, the two quoted sources, and the code near them.
|
|
10
|
+
- Answer `confirmed` only when all three statements are true:
|
|
11
|
+
- The quotes exist, and they say what the finding tells.
|
|
12
|
+
- The code does not satisfy the intent of the requirement. The difference is not in words only. Other code does not resolve it. It does not come from a dependency that the repository does not show.
|
|
13
|
+
- The defect has a production effect. Write the production scenario. If you cannot write it, answer `warn`.
|
|
14
|
+
- In all other conditions, answer `warn`. Name the statement that is not true.
|
|
15
|
+
- Give `judgeConfidence`, an integer from 0 to 100. It tells how sure you are that the finding is an ERROR.
|
|
16
|
+
- Think about `readerConfidence`. When it is low, you need a very strong evidence to confirm. Do not copy it, make your own judgement.
|
|
17
|
+
- The tool keeps the finding as an ERROR only when you answer `confirmed` and `judgeConfidence` is more than 70.
|
|
@@ -0,0 +1,50 @@
|
|
|
1
|
+
# Judging rules: spec-verify reader
|
|
2
|
+
|
|
3
|
+
Use the common rules first: [common.md](common.md).
|
|
4
|
+
|
|
5
|
+
This audit compares the specification with the code. It does not decide if a rule is a good rule. The spec-steward audit does that.
|
|
6
|
+
|
|
7
|
+
| Check | Compares | Kind |
|
|
8
|
+
| ----------- | --------------------------------------------------- | ---------------- |
|
|
9
|
+
| 1 Gap | a requirement with the code that must implement it | `undeclared-gap` |
|
|
10
|
+
| 2 Conflict | a requirement with a related requirement | `conflict` |
|
|
11
|
+
| 3 Duplicate | a requirement with a related requirement | `spec-dup` |
|
|
12
|
+
| 4 Mismatch | the intent of a requirement with what the code does | `code-mismatch` |
|
|
13
|
+
| 5 Test | a scenario with the test that cites it | `untested` |
|
|
14
|
+
|
|
15
|
+
Do not compare code with code.
|
|
16
|
+
|
|
17
|
+
## Gap honesty
|
|
18
|
+
|
|
19
|
+
- For a requirement that no test binds, find if the behaviour exists. Start where its terms occur.
|
|
20
|
+
- When no code implements the behaviour and no `**⚠️ Known gap (<tracker>):**` line records it, report `undeclared-gap`.
|
|
21
|
+
- A process rule or a documentation rule has nothing to implement. It is not a gap.
|
|
22
|
+
- A missing citation is not a reason to suspect a gap.
|
|
23
|
+
|
|
24
|
+
## Contradictory rules
|
|
25
|
+
|
|
26
|
+
- Two requirements conflict when one system cannot obey both.
|
|
27
|
+
- A conflict is a defect in the specification. It is WARN or lower. The owner decides.
|
|
28
|
+
|
|
29
|
+
## A rule redundant with, or substantially overlapping, another
|
|
30
|
+
|
|
31
|
+
- Two requirements that state the same rule are `spec-dup`. This is always INFO.
|
|
32
|
+
|
|
33
|
+
## A rule that no longer matches the implementation or architecture
|
|
34
|
+
|
|
35
|
+
- Find the intent of the requirement: the behaviour it requires and the failure it prevents.
|
|
36
|
+
- Report `code-mismatch` when the code does not satisfy that intent: it does what the requirement prevents, or it does not do what the requirement requires.
|
|
37
|
+
- Do not compare words. A different word, a different order of words, or a narrower or wider phrase is not a finding when the code satisfies the intent.
|
|
38
|
+
- When the requirement names a specific class, pattern, value or field as its contract, the code must use it.
|
|
39
|
+
- Code that satisfies the requirement is not a defect. A citation is not necessary.
|
|
40
|
+
|
|
41
|
+
## A rule whose tests satisfy the wording while failing to protect the intent
|
|
42
|
+
|
|
43
|
+
- For each test that a scenario binds, make sure that the test asserts the outcome of the scenario. The name of the test is not evidence.
|
|
44
|
+
- A test that asserts less than its scenario is `untested`. This is always INFO.
|
|
45
|
+
|
|
46
|
+
## Coverage
|
|
47
|
+
|
|
48
|
+
- A check is full when you judged each item that the part lists for it, and each requirement id is in your judged list.
|
|
49
|
+
- A check is sampled only when an assigned source was not available after you tried to read it. Name that source.
|
|
50
|
+
- An uncertain conclusion is a finding with a low `readerConfidence`. It is not sampled coverage.
|