@sunstack/cli 0.4.0 → 0.6.0

package/CHANGELOG.md

@@ -1,5 +1,57 @@
 # Changelog
 
+## 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.
+
+### Added
+
+- Add rule-only `next` and `previous` evidence fields with a default `count` of 1
+  and a range of 1 through 5. Neighbours share the match's parent and retain
+  source order and spans; continuation nodes do not count or stop the walk.
+- Let ask and combine steps route uncertain answers to another decision step
+  using the same request's answers. Reports name the step that ended the walk.
+
+### Breaking
+
+- Incomplete provider-failure reasons require `failure_class` and carry
+  `http_status` when received. Requests refused by the engine use
+  `invalid_request`; answers that fail admission use `invalid_response`.
+  The default line includes the provider class and any HTTP status.
+- Rename selection's `malformed_answer` reason to `invalid_response` and carry
+  provider class/status in incomplete selection candidates. Update report
+  consumers for this hard cutover.
+
 ## 0.4.0
 
 Release date: 2026-10-30.

package/README.md

@@ -35,6 +35,27 @@ finding. Questions reach the model as authored, with one piece's bounded field
 view. The binary embeds six generic Markdown utilities; rulebooks, questions and
 domain-specific evidence rules belong to the caller.
 
+Evidence fields can use `next` or `previous` to collect full matching sibling
+texts and source spans. They name an ast-grep `rule`; `count` defaults to 1 and
+accepts 1 through 5. For example, a kind's `fields` can include:
+
+```json
+{
+	"following": { "from": "next", "rule": "list", "count": 1 },
+	"preceding": { "from": "previous", "rule": "list_item", "count": 2 }
+}
+```
+
+The walk stays within the match's direct parent and stops at the first
+nonmatching sibling. Blank-line and indentation continuation nodes do not stop
+or count toward the walk. Values stay in source order, including `previous`
+values. These sources accept only rule references and leave `remainder` intact.
+
+An ask or combine step can add `"uncertain": "verdict"` to route an in-band
+answer, or a choice below `min_probability`, to another step. The walk uses
+answers from the same request. Omitting the route ends uncertain at that step.
+Both the `uncertain` and `results` views report the step that ended the walk.
+
 Rulebook and ast-grep project paths resolve relative to the configuration file.
 Checked-file globs resolve from its Git repository root, or from the config
 directory outside Git. Without `--config`, lint searches the current directory
@@ -79,6 +100,19 @@ and answers for the caller to inspect. Cancellation takes precedence over
 incomplete work, then findings, then uncertainty. A warning alone does not fail
 unless it exceeds `--max-warnings`.
 
+A failed provider request carries its class and, when received, its HTTP status
+in the incomplete reason:
+
+```json
+{ "kind": "provider_failure", "failure_class": "rate_limit", "http_status": 429 }
+```
+
+When no HTTP response arrived, `http_status` is omitted. The default output
+prints `provider failure (rate_limit, HTTP 429)` or
+`provider failure (connection)`. A request refused by the engine is
+`invalid_request`; an answer that fails admission is `invalid_response`.
+Incomplete selection candidates use these reason shapes too.
+
 See the checked-in [worked configuration](tests/fixtures/rulebook-lint/skill-rules.config.json)
 and its [rulebook entries](tests/fixtures/rulebook-lint/rulebook/steering.rules.json)
 for a complete test example. Copy the fixture directory to an isolated root to

package/npm-shrinkwrap.json

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

package/package.json

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