@sunstack/cli 0.7.0 → 0.8.0

package/CHANGELOG.md

@@ -1,5 +1,41 @@
 # Changelog
 
+## 0.8.0
+
+Release date: 2026-11-06.
+
+- Filters now use named questions and the shared decision-tree walker, with
+  declared label endings or unsure. The old single-question filter shape is refused.
+- Rule and filter reference material reaches request state unchanged. Questions
+  name their input fields; location is sent only when a rule question reads it.
+  Reserved state names and missing reference paths are refused at load.
+- The mechanical `complete` check guards cut or unresolved text. Skill-name loads
+  include their opening and cut metadata, as path loads do; unavailable inputs
+  remain explicit and a question requiring them ends incomplete.
+- Human lint output uses short numbered warnings, unsure/gap lines and a filter
+  summary. `--report FILE` retains exact requests, all answers, model receipts,
+  source contents and hashes; `lint show FILE ID` explains one saved result.
+- `lint cases FILE [--set SET]` checks revision-bound rule and filter cases through
+  ordinary lint on whole-repository copies with today's rulebook overlaid. It
+  reports per-owner counts, stale/unmatched/excluded cases and unassessed bars,
+  without changing files used by ordinary lint. Selected historical symlink paths
+  are listed as not judged, without following them into a different lint scope.
+
+## 0.7.1
+
+Release date: 2026-11-06.
+
+- Refuse `limits.max_locate_lines` above the provider's 255-option Choice cap
+  during config checking. Filter declarations above that cap are refused at
+  `filters.<name>.question.criteria`, with their option count and limit.
+  Native rule, filter, direct decision and exec requests refuse oversized
+  Choice questions locally before any HTTP call; filter results retain the
+  count and limit. Unreached locators preserve mechanical outcomes.
+- Findings and result rows carry optional `locator_omitted` evidence when a
+  reached locator exceeds the configured line limit: locator name, field,
+  reason, candidate-line count and limit. The established default line and
+  anchor remain intact; default output explains that fallback.
+
 ## 0.7.0
 
 Release date: 2026-11-05.

package/README.md

@@ -51,11 +51,29 @@ 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.
+Every ask or combine step must declare its `uncertain` route: use `"uncertain"`
+as the ending, or name another step such as `"verdict"`. The walk follows it for
+an in-band answer or a choice below `min_probability`, using answers from the
+same request. A missing route is refused when the rulebook loads.
 Both the `uncertain` and `results` views report the step that ended the walk.
 
+Filters declare `per`, `reads: {file, kind, fields: [names]}`, `labels`,
+`questions` and `decision`, with optional `reference`. They use the same steps
+as rules and end in `{ "label": "declared-name" }` or `"unsure"`. Question
+option names are not filter endings. All of a folder's questions go in one
+request; a gate uses the resulting label. The old `question`, `reads.field` and
+filter-level `min_probability` shape is refused.
+
+Each question names the fields or reference paths it reads with `check`,
+`against` or `context` in its instructions. Fixed `reference` material reaches
+`state.reference` unchanged and counts toward the request-size limit. The names
+`standard`, `where`, `cut-fields`, `unavailable-fields` and `reference` are
+reserved. Rules send `where` only when a question names it; filters send no
+folder location. A question requiring an unavailable field ends incomplete
+before any model call. `mechanical_check: {tool: "complete", field: "targets"}`
+returns yes only for an uncut available field whose loaded targets resolved and
+have uncut openings. A resolved skill-name load now has an opening too.
+
 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
@@ -85,6 +103,44 @@ logical report order. Each entry has the rule's `name` and marker, the piece's
 file and first and last line, its outcome (`pass`, `finding`, `not_applicable`,
 `uncertain` or `incomplete`) and its ending `step` (null before any step ran).
 
+Default output prints short numbered lines and a filter summary. To inspect a
+result later, save the full report and request one id:
+
+```sh
+sunstack lint --all --report run.json
+sunstack lint show run.json 3
+sunstack lint cases cases.json --set development
+```
+
+A saved report contains each request's exact state and questions, every returned
+answer, requested and resolved models, and the contents and hashes of its config
+and rule files. It retains raw piece evidence for mechanical steps. `lint show`
+needs only that saved file; an excluded rule is marked as never asked and cannot
+be re-walked. Unknown ids return an error with the valid range.
+
+A case file contains `cases` and `bars`, plus an optional local `repository`
+path (relative to the case file). Each case has a unique `id`, `revision`, `set`
+and `label_from` (`owner-fix` or `blind-agents`). Rule cases add `kind: "rule"`,
+`rule`, `file`, `lines: [first, last]`, `text_sha256`, and `expected: "warn" |
+"pass"`. Filter cases add `kind: "filter"`, `filter`, `folder`, `reads_sha256`
+and `expected_label`. Line hashes retain line endings. Filter hashes cover
+compact JSON of the declared unprojected field values in lexical key order,
+without reference, cut metadata or folder location; normal filter results expose
+the hash. Each recorded bar names `{for, step, bound, value, set_from: [case ids]}`,
+where `bound` is `yes_at_or_above`, `no_at_or_below` or `min_probability`.
+
+Case runs archive the whole repository at each revision, initialize Git metadata
+inside each disposable copy so nested configs retain the repository root, overlay
+today's config and rule inputs, and invoke ordinary lint on selected case paths.
+A selected file or folder that is or traverses a historical symlink is listed as
+`not_judged` with reason `selected path is a symlink`, no result link and no crossed
+bars. It never selects the link's target. Context loads retain their usual behavior.
+Rule cases match exactly one piece that overlaps their lines after checking the
+case's own archived line hash.
+Every selected case is counted or listed, with per-rule and per-filter counts,
+result links and crossed bars. A changed or unrecorded bar is unassessed. The
+command writes no adoption state and changes no ordinary lint inputs.
+
 The decision model is always configured and enabled for asking rules; there is
 no model-off switch. Ordinary runs with asking rules require an OpenRouter
 credential before checked-file acquisition, even if a later mechanical branch

package/npm-shrinkwrap.json

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

package/package.json

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