okstra 0.231.0 → 0.232.0

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.
Files changed (143) hide show
  1. package/README.md +15 -3
  2. package/dist/cli-registry.mjs +6 -0
  3. package/dist/cli-registry.mjs.map +1 -1
  4. package/dist/commands/memory/memory.mjs +9 -55
  5. package/dist/commands/memory/memory.mjs.map +1 -1
  6. package/dist/lib/memory-auto-register.d.mts +1 -0
  7. package/dist/lib/memory-auto-register.mjs +113 -0
  8. package/dist/lib/memory-auto-register.mjs.map +1 -0
  9. package/dist/lib/memory-entry-contract.d.mts +12 -0
  10. package/dist/lib/memory-entry-contract.mjs +46 -0
  11. package/dist/lib/memory-entry-contract.mjs.map +1 -0
  12. package/dist/lib/python-helper.d.mts +1 -1
  13. package/dist/lib/python-helper.mjs +3 -2
  14. package/dist/lib/python-helper.mjs.map +1 -1
  15. package/dist/lib/record-secrets.d.mts +1 -0
  16. package/dist/lib/record-secrets.mjs +28 -0
  17. package/dist/lib/record-secrets.mjs.map +1 -0
  18. package/dist/lib/types.d.mts +2 -1
  19. package/docs/architecture/storage-model.md +129 -2
  20. package/docs/architecture.md +11 -2
  21. package/docs/cli.md +234 -0
  22. package/docs/project-structure-overview.md +2 -1
  23. package/package.json +1 -1
  24. package/runtime/BUILD.json +2 -2
  25. package/runtime/agents/common.json +8 -8
  26. package/runtime/agents/roles/verifier.json +2 -4
  27. package/runtime/bin/okstra-provider-exec.py +10 -4
  28. package/runtime/prompts/coding-preflight/architectures/hexagonal.md +23 -30
  29. package/runtime/prompts/coding-preflight/authoring-checks.md +17 -0
  30. package/runtime/prompts/coding-preflight/clean-code.md +85 -281
  31. package/runtime/prompts/coding-preflight/frameworks/node-server.md +2 -3
  32. package/runtime/prompts/coding-preflight/languages/java.md +3 -5
  33. package/runtime/prompts/coding-preflight/languages/javascript-typescript.md +5 -12
  34. package/runtime/prompts/coding-preflight/languages/kotlin.md +2 -4
  35. package/runtime/prompts/coding-preflight/languages/python.md +2 -7
  36. package/runtime/prompts/coding-preflight/languages/rust.md +2 -8
  37. package/runtime/prompts/coding-preflight/languages/sql.md +2 -4
  38. package/runtime/prompts/coding-preflight/overview.md +25 -38
  39. package/runtime/prompts/coding-preflight/review-rules.json +30 -0
  40. package/runtime/prompts/duties/code-reviewer.json +15 -18
  41. package/runtime/prompts/duties/implementation-verifier.json +1 -0
  42. package/runtime/prompts/lead/convergence.md +3 -3
  43. package/runtime/prompts/lead/okstra-lead-contract.md +2 -2
  44. package/runtime/prompts/lead/report-writer.md +1 -1
  45. package/runtime/prompts/lead/team-contract.md +1 -1
  46. package/runtime/prompts/profiles/_clarification-recommendation.md +3 -2
  47. package/runtime/prompts/profiles/_coding-conventions-preflight.md +41 -6
  48. package/runtime/python/okstra_ctl/agent/invocation.py +121 -36
  49. package/runtime/python/okstra_ctl/agent/prompt_cli/cli.py +6 -0
  50. package/runtime/python/okstra_ctl/agent/prompt_cli/materialize.py +30 -4
  51. package/runtime/python/okstra_ctl/agent/standalone.py +3 -0
  52. package/runtime/python/okstra_ctl/analysis_packet.py +2 -19
  53. package/runtime/python/okstra_ctl/approval_decisions.py +16 -0
  54. package/runtime/python/okstra_ctl/attempt_evidence.py +10 -0
  55. package/runtime/python/okstra_ctl/business_flow/invocation.py +35 -3
  56. package/runtime/python/okstra_ctl/code_review_census.py +71 -7
  57. package/runtime/python/okstra_ctl/code_review_coverage.py +4 -274
  58. package/runtime/python/okstra_ctl/code_review_integrity.py +154 -0
  59. package/runtime/python/okstra_ctl/code_review_invocation.py +212 -0
  60. package/runtime/python/okstra_ctl/code_review_scope.py +36 -9
  61. package/runtime/python/okstra_ctl/code_review_target.py +85 -11
  62. package/runtime/python/okstra_ctl/consumers.py +12 -9
  63. package/runtime/python/okstra_ctl/convergence.py +112 -20
  64. package/runtime/python/okstra_ctl/convergence_engine.py +1 -0
  65. package/runtime/python/okstra_ctl/convergence_provenance.py +27 -11
  66. package/runtime/python/okstra_ctl/correction_round.py +6 -1
  67. package/runtime/python/okstra_ctl/design_review.py +207 -0
  68. package/runtime/python/okstra_ctl/design_review_evidence.py +297 -0
  69. package/runtime/python/okstra_ctl/dispatch_checkpoints.py +28 -5
  70. package/runtime/python/okstra_ctl/dispatch_core.py +3 -11
  71. package/runtime/python/okstra_ctl/doctor.py +8 -25
  72. package/runtime/python/okstra_ctl/doyouknow/__init__.py +9 -0
  73. package/runtime/python/okstra_ctl/doyouknow/cli.py +91 -0
  74. package/runtime/python/okstra_ctl/doyouknow/config.py +58 -0
  75. package/runtime/python/okstra_ctl/doyouknow/contracts.py +184 -0
  76. package/runtime/python/okstra_ctl/doyouknow/identity.py +22 -0
  77. package/runtime/python/okstra_ctl/doyouknow/paths.py +22 -0
  78. package/runtime/python/okstra_ctl/doyouknow/pending.py +72 -0
  79. package/runtime/python/okstra_ctl/doyouknow/registration.py +260 -0
  80. package/runtime/python/okstra_ctl/doyouknow/source_contracts.py +128 -0
  81. package/runtime/python/okstra_ctl/doyouknow/source_store.py +172 -0
  82. package/runtime/python/okstra_ctl/doyouknow/sources/io.py +36 -0
  83. package/runtime/python/okstra_ctl/doyouknow/sources/manager.py +261 -0
  84. package/runtime/python/okstra_ctl/doyouknow/sources/memory.py +179 -0
  85. package/runtime/python/okstra_ctl/doyouknow/sources/task.py +95 -0
  86. package/runtime/python/okstra_ctl/doyouknow/store.py +260 -0
  87. package/runtime/python/okstra_ctl/doyouknow/sync.py +58 -0
  88. package/runtime/python/okstra_ctl/execution_mutation_audit.py +18 -2
  89. package/runtime/python/okstra_ctl/file_size_cap.py +3 -4
  90. package/runtime/python/okstra_ctl/json_boundary.py +21 -2
  91. package/runtime/python/okstra_ctl/jsonl.py +21 -0
  92. package/runtime/python/okstra_ctl/manager_cli.py +26 -0
  93. package/runtime/python/okstra_ctl/manager_registration.py +29 -0
  94. package/runtime/python/okstra_ctl/manager_sync.py +3 -22
  95. package/runtime/python/okstra_ctl/model_io/renderers.py +13 -2
  96. package/runtime/python/okstra_ctl/model_io_cli.py +7 -1
  97. package/runtime/python/okstra_ctl/phases/final_verification/validation.py +20 -0
  98. package/runtime/python/okstra_ctl/phases/implementation/instructions/_implementation-deliverable.md +12 -2
  99. package/runtime/python/okstra_ctl/phases/implementation/instructions/_implementation-diff-review.md +19 -6
  100. package/runtime/python/okstra_ctl/phases/implementation/instructions/_implementation-self-check.md +5 -3
  101. package/runtime/python/okstra_ctl/phases/implementation/instructions/_implementation-verifier.md +39 -11
  102. package/runtime/python/okstra_ctl/phases/implementation/report_assets/implementation.template.html +13 -0
  103. package/runtime/python/okstra_ctl/phases/implementation/spec.md +26 -1
  104. package/runtime/python/okstra_ctl/phases/implementation/validation.py +86 -2
  105. package/runtime/python/okstra_ctl/phases/implementation_planning/authoring.py +4 -0
  106. package/runtime/python/okstra_ctl/phases/implementation_planning/profile.md +1 -1
  107. package/runtime/python/okstra_ctl/report_assembly.py +15 -0
  108. package/runtime/python/okstra_ctl/report_narrative.py +3 -0
  109. package/runtime/python/okstra_ctl/report_prose_keys.py +7 -0
  110. package/runtime/python/okstra_ctl/report_synthesis_packet.py +19 -2
  111. package/runtime/python/okstra_ctl/review_policy.py +359 -0
  112. package/runtime/python/okstra_ctl/review_verdicts.py +291 -0
  113. package/runtime/python/okstra_ctl/run.py +24 -1
  114. package/runtime/python/okstra_ctl/stage_done.py +11 -0
  115. package/runtime/python/okstra_ctl/standalone_review_audit.py +28 -0
  116. package/runtime/python/okstra_ctl/team.py +3 -1
  117. package/runtime/python/okstra_ctl/verification_generation.py +23 -1
  118. package/runtime/python/okstra_ctl/verification_input_types.py +15 -1
  119. package/runtime/python/okstra_ctl/verification_inputs.py +28 -6
  120. package/runtime/python/okstra_ctl/verification_invocation.py +7 -1
  121. package/runtime/python/okstra_ctl/verification_target.py +2 -0
  122. package/runtime/python/okstra_ctl/worker_dispatch.py +3 -1
  123. package/runtime/python/okstra_ctl/worker_prompt_headers.py +24 -9
  124. package/runtime/python/okstra_ctl/worker_runner.py +66 -10
  125. package/runtime/python/okstra_ctl/wrapper_status.py +16 -0
  126. package/runtime/python/okstra_ctl/write_policy.py +34 -1
  127. package/runtime/python/okstra_project/__init__.py +2 -0
  128. package/runtime/python/okstra_project/dirs.py +18 -0
  129. package/runtime/python/okstra_project/state.py +25 -20
  130. package/runtime/schemas/doyouknow-config-v1.schema.json +20 -0
  131. package/runtime/schemas/doyouknow-v1.schema.json +65 -0
  132. package/runtime/schemas/final-report-v2.0.schema.json +157 -0
  133. package/runtime/schemas/final-report-v3.0.schema.json +157 -0
  134. package/runtime/schemas/memory-entry-contract-v1.json +11 -0
  135. package/runtime/schemas/record-secret-patterns.json +41 -0
  136. package/runtime/skills/okstra-code-review/SKILL.md +71 -123
  137. package/runtime/skills/okstra-code-review/references/census-rules.md +29 -105
  138. package/runtime/skills/okstra-code-review/references/review-calibration.md +34 -54
  139. package/runtime/skills/okstra-manager/SKILL.md +7 -0
  140. package/runtime/skills/okstra-memory/SKILL.md +7 -0
  141. package/runtime/templates/implementation-worker-preamble.md +4 -9
  142. package/runtime/templates/worker-prompt-preamble.md +4 -12
  143. package/runtime/validators/validate-run.py +17 -8
@@ -11,13 +11,15 @@ If unsure, ask the user once: *"Does this project use ports-and-adapters? What f
11
11
 
12
12
  These rules are language-agnostic. The examples use TypeScript/Java-ish syntax; translate to Rust traits, Kotlin interfaces, etc., as needed.
13
13
 
14
+ Apply the policy precedence in `../overview.md`: explicit repository instructions and declared architecture, this common resource pack, then surrounding code conventions. Once this overlay is selected, apply each rule's stated criteria and severity whether selection came from a declaration or layout signals. H5 alone keeps its undeclared-style advisory exception. Existing concrete dependencies or misplaced rules do not create an exception to an applicable architecture rule.
15
+
14
16
  ---
15
17
 
16
18
  ## Rule H1 — Ports stay thin
17
19
 
18
- A port is the interface (or abstract class) at the domain/application boundary. The port declares **shape**, not behavior.
20
+ A port is the interface (or abstract class) at the domain/application boundary. It declares an operation's inputs, outputs, errors and domain-owned query specifications without implementing business decisions. Describing those behavioral contracts is part of the port's interface.
19
21
 
20
- A port file's method body — or the interface contract itself — must **not** contain:
22
+ A port file's executable method body does not implement:
21
23
 
22
24
  - `if` statements that branch on domain state.
23
25
  - Validation that throws or returns errors based on input shape.
@@ -53,36 +55,29 @@ Not a violation:
53
55
 
54
56
  ---
55
57
 
56
- ## Rule H2 — Adapters do I/O, not business logic
57
-
58
- Same principle as H1, on the adapter side. The adapter's job is to implement **just** the I/O — a SQL query, an HTTP call, a filesystem read. It is **not** the place to filter by domain state, branch on domain values, or compute business answers.
58
+ ## Rule H2 — Adapters execute I/O; the domain owns business policy
59
59
 
60
- Smells in adapter methods:
60
+ An adapter translates a port operation into a SQL query, HTTP call, filesystem operation or other I/O. The domain owns the policy that determines eligibility, validity or a business outcome; the adapter may execute that policy's query specification efficiently without redefining its meaning.
61
61
 
62
- - A `.filter(x => x.status === 'active')` predicate over domain state, *after fetching rows*.
63
- - An `if` that rejects results based on a domain rule (*"skip if expired"*, *"exclude shared items"*).
64
- - A method whose name encodes a business rule — `findValid*` / `findActive* `/ `findEligible*`. The adapter should fetch *things*; the caller (or the query itself) should apply the rule.
65
- - Multiple joins and conditions assembled specifically to satisfy a compound domain rule — the adapter is answering a business question rather than offering a primitive fetch.
62
+ Inspect policy ownership and preservation of the port contract:
66
63
 
67
- Judgment: an adapter **can** push filtering into SQL (`WHERE status = 'active'`) — that's still I/O-shaped. The smell is when:
64
+ - A predicate or business calculation invented inside an adapter, with no domain-owned policy or defined port contract, hides the decision in infrastructure.
65
+ - An adapter that changes, omits or duplicates the policy's conditions can return a different business answer. Cite the governing policy and the differing condition.
66
+ - Post-fetch filtering merits inspection of its owner and cost. Technical row mapping or execution of a domain-owned specification is not inherently a policy violation.
68
67
 
69
- - The filtering is *application code after the fetch*, or
70
- - The method name itself encodes a domain rule that a reader cannot tell from the name alone.
68
+ SQL predicates, joins, aggregation, ordering and pagination may implement a domain-owned query specification at the storage boundary. Complexity or the number of conditions alone does not establish a misplaced rule. Check where the policy is defined and whether the query preserves its semantics.
71
69
 
72
- A domain-flavored method name (`findValid*` / `findActive*` / `findEligible*`) is not automatically a violation. Accept it when **either** holds:
70
+ A name such as `findValid*`, `findActive*` or `findEligible*` is valid when the port contract defines that term and identifies its governing policy or specification. An undefined or misleading term is a contract or naming problem, not proof that every business-oriented query belongs outside the adapter.
73
71
 
74
- - The query body is still simple — a single `WHERE` clause on an obvious column, no compound predicate.
75
- - Moving the predicate out would force an N+1 (the caller would have to fetch all rows and round-trip per row to decide which are valid).
72
+ Keep efficient execution near the data. Do not replace a policy-driven query with `findAll` plus in-memory filtering merely to move the predicate's syntax. Express the policy at the domain/application boundary and let the adapter translate it while preserving bounded work and avoiding N+1 calls.
76
73
 
77
- Reject it when the query is complex enough that a reader can't tell what "valid"/"active"/"eligible" means without reverse-engineering the SQL. At that point the rule really is hiding in infrastructure — move the predicate to the domain and rename the adapter to `findAll` / `findByX`.
78
-
79
- Not a smell:
74
+ Examples of adapter responsibilities:
80
75
 
81
76
  - Simple `WHERE` clauses for *data-shape* reasons (`WHERE user_id = ?`) — that's scoping the fetch, not a business rule.
82
77
  - Pagination, ordering, basic projection.
83
78
  - Mapping raw rows to domain objects — that's the adapter's translation job.
84
79
 
85
- Why it matters: when adapters hold business rules, the rules become invisible from the domain. A reviewer reading the domain sees a clean method; the rule is hidden two layers down in a repository. Changes to the rule require editing infrastructure code. Tests of the rule are forced through I/O. The whole point of ports-and-adapters collapses.
80
+ The review distinguishes changing business policy from translating it for a storage or transport system. A finding names the policy hidden or changed by the adapter and the concrete consequence; a complex query or a domain-oriented name alone is not evidence.
86
81
 
87
82
  ---
88
83
 
@@ -109,7 +104,7 @@ The test: **is this type/class a thing the business talks about, or is it plumbi
109
104
 
110
105
  ## Rule H4 — Dependency direction: the domain imports nothing outward
111
106
 
112
- The cardinal rule of ports and adapters: dependencies point inward. A file under the domain folder imports only from the domain itself and from pure utility code. Unlike H1–H3 this verdict is **mechanical** — read the import list of every changed domain file; no judgment about what the code means is required.
107
+ Dependencies point inward. A file under the domain folder imports only from the domain itself and from pure utility code. Read each changed domain file's imports and resolve their targets against the declared boundaries; apply the explicit repository instructions before judging an outward dependency.
113
108
 
114
109
  Violations — any import of:
115
110
 
@@ -131,9 +126,9 @@ When the domain needs something the outside owns, invert it: declare the shape a
131
126
 
132
127
  When a change adds or modifies a service's dependency on a concrete adapter — constructor injection of a repository class, or direct model / DB access from a service — that boundary should be a port the adapter implements, so the caller depends on shape rather than on infrastructure.
133
128
 
134
- The verdict is mechanical: this change adds or modifies such a dependency → finding; the injection sits entirely on lines this change did not touch → clean.
129
+ Inspect dependencies this change adds or modifies against the declared boundary and explicit repository instructions. An injection entirely outside the changed scope is not a new finding merely because it already uses a concrete class.
135
130
 
136
- **An existing convention does not clear this one.** A codebase that injects concrete `*Repository` classes everywhere is precisely the debt this rule pays down, one touched injection at a time — matching the surrounding style is the condition being flagged, not a defence against it. Record it, say so in the note (*"matches existing convention — advisory"*), and propose the port: its name and the two or three method signatures it would declare — unless the project declares `architecture.style = hexagonal` in `.okstra/project.json`, where this item is blocking and that same port sketch is what you write rather than what you record: fix the injection before the write, never record-and-pass.
131
+ Existing concrete `*Repository` injections do not waive a declared hexagonal boundary. Apply the precedence in `../overview.md` and cite any explicit repository exception. Under a declared hexagonal style, fix a current violating dependency through a port before completion. Without that declaration, record the advisory and a proposed port with the method signatures it needs; do not require unrelated legacy cleanup.
137
132
 
138
133
  ---
139
134
 
@@ -145,7 +140,7 @@ Violations:
145
140
 
146
141
  - An `if` / `else` chain over domain fields that decides an outcome — eligibility, validity, which branch of a business process runs.
147
142
  - Arithmetic expressing a business formula: money, ranking, quota, date-based entitlement.
148
- - A private service method whose name is a domain concept (`isEligible…`, `computeDowngrade…`, `resolve…Status`). The name is telling you where it belongs.
143
+ - A private service method that implements a business decision such as eligibility, a downgrade formula or status transition. Inspect its body and governing rule; a domain-oriented name alone is not a violation.
149
144
 
150
145
  Not a violation:
151
146
 
@@ -155,21 +150,19 @@ Not a violation:
155
150
 
156
151
  The test: **if this decision changed, would the change be described as a business rule change or as a plumbing change?** A business rule change that lands in a service is the violation — the rule is now invisible to the domain's own tests, and the next caller that needs it writes its own copy.
157
152
 
158
- Severity: `should-fix`, and blocking when the embedded rule is substantial — money, permissions, or a state machine. Under a declared `architecture.style = hexagonal` the substantial case is fixed before the write, never record-and-pass.
153
+ Grade an established H6 violation by `clean-code.md` "Finding evidence and grading". A substantial embedded rule, such as money, permissions or a state machine, is a current blocking finding even when layout signals selected this overlay. Current blocking findings are fixed before completion, subject to the explicit repository instructions.
159
154
 
160
155
  ---
161
156
 
162
- **How far a project convention reaches.** H5 above is the one rule in this overlay a project-local convention cannot clear. Elsewhere here, a documented convention does resolve the conflict in the project's favour — but that latitude stops at okstra's own gates. It never clears a check the implementation verifier's blocking list declares **mechanical**: a changed file under the domain folder importing an ORM / DB layer, a framework or its DI decorators, or anything under adapters / infrastructure / services is decided by reading the import list, and no convention argument reaches that verdict (`prompts/profiles/_implementation-verifier.md` §"Static design & test-quality review" → Hexagonal). Resolving a declared-mechanical finding as "project convention" is the failure this paragraph exists to prevent — a real run did exactly that, returned `clean`, and the team's own PR review then flagged the same import.
163
-
164
- Severity: advisory in a project that has not declared `architecture.style = hexagonal` — a direction-of-travel rule there, not a correctness gate, so it never blocks on its own. Under that declaration it is blocking: the injection is fixed before the write.
157
+ **Conflict resolution.** The precedence in `../overview.md` applies to every rule in this overlay, including H4 and H5. A surrounding code pattern alone cannot clear an explicit architecture violation. Cite an explicit repository instruction when it overrides a common-pack rule; record an unresolved conflict instead of treating it as a clean result. Boundary interpretation and grading are self-check and review judgments, not a guarantee from import scanning alone.
165
158
 
166
159
  ---
167
160
 
168
161
  ## Quick checklist before declaring a port/adapter change complete
169
162
 
170
163
  - [ ] No `if` / `.filter` / validation / business math inside any port body.
171
- - [ ] Adapter methods are I/O only — any post-fetch JS filtering moved into the query or back to the caller.
172
- - [ ] Adapter method names are neutral (`findAll`, `findByUserId`) unless the domain-flavored name passes the H2 judgment test.
164
+ - [ ] The domain owns business policy; adapter queries and any post-fetch processing preserve that policy and the port contract without redefining it.
165
+ - [ ] Domain-oriented adapter names identify a policy defined by the port contract; query complexity or the name alone is not a violation.
173
166
  - [ ] Every entity, value object, domain enum, and domain error is declared under `domain/`.
174
167
  - [ ] Port files only declare shape and `import` domain types — they don't *define* them.
175
168
  - [ ] No changed domain file imports an ORM, a framework, or anything under adapters / infrastructure / services.
@@ -0,0 +1,17 @@
1
+ # Authoring checks
2
+
3
+ These execution procedures apply only to the worker authorized to change project source. Read-only reviewers evaluate the shared criteria and report findings; this resource grants no write authority. Enforcement is author self-check and code review unless a referenced rule names an automated gate.
4
+
5
+ ## Mandatory pre-write checks (every language)
6
+
7
+ - [ ] Read project instructions, configured conventions and every selected resource for this turn. Apply the shared [quality outcomes](clean-code.md#five-simultaneous-quality-outcomes) before editing.
8
+ - [ ] Before adding a unit, search identifiers, behavior, callers, domain literals, error strings and returned-data shapes; read the candidates. Record search terms, nearest implementation and `extend <path:line>` or `new (nothing covers <behavior>)`. Name-only uniqueness does not establish absence; missing survey evidence leaves the addition unfinished.
9
+ - [ ] **Tests planned:** identify retained or extended tests and uncovered outcomes under [Testing discipline](clean-code.md#testing-discipline) and [test reuse](clean-code.md#reuse-tests-before-adding-coverage). Record any permitted waiver and its unverified scope there.
10
+ - [ ] Apply the detailed checks in `clean-code.md`, including mutation/state, security, testing, third-party wrappers and failure paths where applicable.
11
+ - [ ] If the hexagonal overlay is selected, apply its H1–H6 criteria and stated exceptions under the policy precedence in `overview.md`.
12
+
13
+ ## Completion sweep (before declaring a multi-file change done)
14
+
15
+ - [ ] Review the combined change for shared decisions and exported-name distinctions using `clean-code.md`'s DRY and naming checks, not only per-file checks.
16
+ - [ ] Manually inspect changed tests using the selected language's self-mock signals and `clean-code.md`'s testing criteria. Distinguish the tested unit from injected collaborators. In implementation runs, `validators/detect_self_mock.py` execution and its result files belong to the verifier designated by "Self-mock detection"; authors perform this manual sweep only. `validate-run.py` checks the result.
17
+ - [ ] Run the authorized repository commands selected under [Verification commands](overview.md#verification-commands). Report results, unresolved findings, waivers and unavailable checks without claiming unverified coverage.