@sunstack/cli 0.5.0 → 0.7.0

package/CHANGELOG.md

@@ -1,5 +1,65 @@
 # Changelog
 
+## 0.7.0
+
+Release date: 2026-11-05.
+
+### Added
+
+- Declare `filters` to group checked files by folder and ask one native Choice
+  question about a configured text field per folder per run. Context files use
+  the checked source and limits; changes to them select affected members,
+  including evidence that needs selection.
+- Rule entries accept `only_when` to run only for named filter answers. Excluded
+  rules report a judged `not_applicable` reason before any decision step runs.
+  Unsure, incomplete and folderless checks are listed as skips; unsure runs exit
+  5, while failed filter requests and folderless checks exit 3.
+- Evidence kinds accept either a named `rule` or an `inline_rule` YAML string.
+  Inline matchers use the kind name as their rule ID, retain native matching and
+  field behavior, and locate refusals at the owning configuration key.
+- JSON reports expose `filter_answers`, `filter_skips` and result reasons.
+  Answers retain their probabilities, requested and resolved model names and
+  input-cut provenance. Default output lists answers and skips; SARIF continues
+  to represent findings rather than skips.
+
+### Breaking
+
+- The report schema requires the filter answer and skip collections. Older
+  reports do not validate against the 0.7.0 schema.
+- Native evidence kind definitions now carry `KindMatcher`; project loading
+  takes inline rules and their configuration source. Native rule admission,
+  assembly and shared-dispatch execution receive their filter context.
+
+## 0.6.0
+
+Release date: 2026-10-31.
+
+### Added
+
+- Findings carry related places, beginning with the rule's standard, and a
+  mechanical or judged basis. JSON, SARIF, default and GitHub output retain the
+  files and lines of the evidence the run read.
+- Finding routes can declare a `locate` Choice question. A selection meeting its
+  probability threshold resolves the line inside its field and piece; `span`
+  stays intact. `max_locate_lines` defaults to 80, and locators fit within the
+  existing request budgets while preserving every authored question.
+- Every result retains its walked `path` and the model `answers` it read,
+  including passes, gate exclusions and incomplete walks. Completed results
+  carry `basis`; cut model fields appear in row `cut` and state `cut-fields`.
+- Target fields accept rule-only `exclude` ranges. Enclosing and same-file
+  fields accept `text: "full"`, and path targets can collect `as_kind` fields.
+  Shortened target openings carry `opening_cut`.
+- Evidence projects admit JSON rules and utils alongside Markdown. JSON uses
+  the existing field sources except `yaml`; field references stay within their
+  language, while `as_kind` can select either grammar. A malformed JSON file is
+  incomplete without preventing valid files from being checked.
+
+### Breaking
+
+- The report schema requires `related`, `anchor` and `basis` on findings and
+  `path` on result rows. Readers that ignore new fields retain the meaning of
+  existing fields; older reports do not validate against the 0.6.0 schema.
+
 ## 0.5.0
 
 Release date: 2026-10-31.

package/npm-shrinkwrap.json

@@ -19,7 +19,7 @@
       "hasInstallScript": true,
       "license": "MIT",
       "name": "@sunstack/cli",
-      "version": "0.5.0"
+      "version": "0.7.0"
     },
     "node_modules/detect-libc": {
       "engines": {
@@ -48,5 +48,5 @@
     }
   },
   "requires": true,
-  "version": "0.5.0"
+  "version": "0.7.0"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "artifactDownloadUrls": [
-    "https://github.com/ShravanSunder/sunstack-tools/releases/download/v0.5.0"
+    "https://github.com/ShravanSunder/sunstack-tools/releases/download/v0.7.0"
   ],
   "bin": {
     "sunstack": "run-sunstack.js"
@@ -88,7 +88,7 @@
       "zipExt": ".tar.gz"
     }
   },
-  "version": "0.5.0",
+  "version": "0.7.0",
   "volta": {
     "node": "18.14.1",
     "npm": "9.5.0"