sourcecode 5.9.1__tar.gz → 5.9.2__tar.gz

{sourcecode-5.9.1 → sourcecode-5.9.2}/CHANGELOG.md

@@ -1,5 +1,27 @@
 # Changelog
 
+## [5.9.2] — 2026-08-27
+
+*Commercial positioning increment: bounded agent context, reproducible cost
+measurement, source-level SARIF delivery and workspace entitlement pilot.*
+
+**Added**
+
+- `repo-ir --budget-tokens N` composes with `--since` and declares graph
+  non-coverage instead of truncating an answer.
+- `scripts/context_cost_harness.py` compares two declared task commands without
+  a shell and publishes no delta unless both sides resolve comparably.
+- `migrate-check --format sarif` emits ASK-owned migration findings with source
+  locations, provenance and non-coverage.
+- `auth workspace --enforce` provides an opt-in named-buyer pilot using the
+  existing Pro gate; advisory mode remains the default.
+
+**Documentation and validation**
+
+- README, user guide, roadmap and CLI help describe the new commercial surfaces.
+- The changes were verified against the four repositories in
+  `Documents/workspace/testing` and the focused regression batteries.
+
 ## [5.9.1] — 2026-08-26
 
 *Audit correction and stress-validation patch release. The `AUD-608` fixes

{sourcecode-5.9.1 → sourcecode-5.9.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sourcecode
-Version: 5.9.1
+Version: 5.9.2
 Summary: Persistent structural context and ultra-fast repeated analysis for AI coding agents
 Project-URL: Homepage, https://github.com/HarounDominique/sourcecode
 Project-URL: Repository, https://github.com/HarounDominique/sourcecode
@@ -59,7 +59,7 @@ Description-Content-Type: text/markdown
 > question. All analysis is local and deterministic; see [Privacy](#configuration--privacy)
 > before inspecting a repository whose telemetry policy you need to control.
 
-![Version](https://img.shields.io/badge/version-5.9.1-blue)
+![Version](https://img.shields.io/badge/version-5.9.2-blue)
 ![Python](https://img.shields.io/badge/python-3.9%2B-green)
 
 Copyright (c) 2026 Dominique Haroun. All rights reserved. ASK Engine 5.7.0 and
@@ -122,6 +122,14 @@ the CI signal; `--allow-unverified` can change only that exit code, never the
 reported verdict. Every pack carries a manifest with component invocations,
 source evidence and content fingerprints.
 
+For agent integrations, `ask repo-ir --since <ref> --budget-tokens N` bounds the
+serialized inline answer. If the full graph does not fit, ASK returns its summary
+view and declares `token_budget.coverage: non_coverage`; it never silently truncates
+JSON. For a rerunnable cost comparison, use `scripts/context_cost_harness.py` with
+explicit `--with-ask` and `--without-ask` command templates. It executes without a
+shell and publishes a token delta only when both commands resolve and `--comparable`
+is declared.
+
 The [Product Route](docs/PRODUCT-ROUTE.md) is normative: ASK focuses on
 deterministic evidence for Java/Spring modernization and safe change. Packs
 compose existing commands; they do not hide or replace them.
@@ -188,7 +196,7 @@ set `ASK_MAX_RSS_MB=<megabytes>`; if the process exceeds it, ASK refuses the
 answer with `MEMORY_TOO_LARGE`, including the observed peak and limit. Leave it
 unset, or set it to `0`, to disable the ceiling explicitly.
 
-**Current performance status.** Release 5.9.1 retains the shared Canonical IR
+**Current performance status.** Release 5.9.2 retains the shared Canonical IR
 path used by `validation` and now passes that same CIR into labelled `data-exposure`
 runs; the no-label path remains parse-free. These are implementation properties,
 not duration promises. A controlled external warm-path audit has opened performance
@@ -197,6 +205,13 @@ and bounded-output regressions for this release; use `ask cache model <repo>` an
 [latest external audit intake](docs/AUDIT-2026-08-26-EXTERNAL-5.9.0.md) before
 treating a historical timing or bounded flag as a current guarantee.
 
+**CI delivery and workspace licensing.** `migrate-check --format sarif` emits
+ASK-owned migration findings with source locations and provenance; it does not
+re-emit imported scanner findings. `ask auth workspace <repo>...` previews the
+aggregate Java entitlement. `--enforce` is an opt-in named-buyer pilot that reuses
+the existing Pro gate; advisory mode remains the default and no billing is
+performed by the CLI.
+
 **What a warm actually covers.** `ask cache warm` rebuilds the declared root views and their
 shared structural layers (L1/L2 + the Repository Intelligence Snapshot + the shared Canonical
 IR). Pass `--views compact` or `--views compact,agent` to warm only selected views; without
@@ -222,7 +237,7 @@ brew tap haroundominique/sourcecode && brew install sourcecode
 # pip / pipx
 pipx install sourcecode        # or: pip install sourcecode
 
-ask version                    # ask 5.9.1 — and, on a build that has aged,
+ask version                    # ask 5.9.2 — and, on a build that has aged,
                                # how many releases have probably shipped since
 ```
 
@@ -506,27 +521,28 @@ from it.
 | `posture` | supported | which beans a profile set wires, and how effective endpoint access differs between two sets | the most differentiated capability here. `--resolve-environments` says which set the repository decides; `--profile-from <file>` reads the artefact that actually decides it (Kubernetes manifest, compose file, deployment plan, `Dockerfile`, dotenv) and answers under that set, with the `file:line` — deciding nothing leaves the verdict untouched |
 | `risk` | supported | what each defect actually costs, once reach, access, write effect and the shape of the input path are in it | `defect_severity × reachability × auth_verdict × write_effect × query_construction × input_constraints`; every factor names its authority; the `query_construction` factor covers MyBatis `${}` splicing with a three-state verdict (`reaches` / `does_not_reach` / `undecidable`) and publishes the census; `--table --rule SEC-008 --band high --top-n 20` gives audit triage without `jq` |
 | `enrich` | experimental | another scanner's SARIF findings, ranked by what this repository does with them | `--sarif <log>`; same composition as `risk`, with `--table --rule <id> --band high --top-n 20` for triage |
-| `audit-report` | supported | human audit bundle over existing `risk` + `posture` evidence, optionally signed | includes `evidence_manifest` claim provenance; `--format markdown`; `--sign-key <file>` signs canonical JSON with HMAC-SHA256 |
+| `audit-report` | supported | human audit bundle over existing `risk` + `posture` evidence, optionally signed | includes `evidence_manifest` claim provenance; `--format markdown`; `--sign-key <file>` signs canonical JSON with HMAC-SHA256; `--pack ens` adds a technical ENS control matrix |
+| `audit-verify` | supported | offline verification of a signed `audit-report` bundle | recomputes the canonical payload and HMAC-SHA256; returns `valid: true/false` and a CI-friendly exit code without re-running the audit |
 | `migrate-recipe` | supported | the migration report as the OpenRewrite recipe that applies it | only recipes a finding named; the manual remainder published beside them; writes nothing without `--write`, and never a runnable command for an empty recipe list |
 | `migrate-apply` | supported | apply a measured recipe without touching the main tree | Maven and Gradle executors; plan by default; `--write` requires clean Git, pinned version and isolated worktree; no automatic commit or merge |
 | `data-exposure` | supported | which routes can carry the data you labelled, and who reaches them | labels declared in `sourcecode.config.json` — never inferred from a name; `signature` and `call_reach` evidence published apart, field-level flow out of scope (NC-008). With nothing declared, `ask data-exposure /path/to/repo` answers `answered: false` and hands back the file, the key and an example to declare — it never reports zero exposed routes |
 | `data-exposure --init` | supported | generate review-only label candidates | writes only `.ask/data-label-candidates-v1.json` with `status: proposed_only`; it never activates labels |
 | `endpoints` | core | every REST endpoint, effective path, security policy, confidence | Spring MVC + JAX-RS (~65 % recall on JAX-RS sub-resource locators). `--compact` answers the exposure census without the rows; `--servlets` lists the servlet-mounted surface as its own population; `--client-usage` says which routes the TS/JS client in this repository actually calls; `--consumer <repo>` (repeatable) joins the routes against consumers in **other** repositories — TypeScript/JS and Java — and turns the census into a surface-reduction plan: open and called (fix now), open and called by nobody (delete rather than guard), and calls this server serves no route for |
 | `spring-audit` | core | transactional anomalies + security configuration/exposure + validation gaps | `--ci`, `-f github-comment`, or `-f github-actions` for native CI annotations; `--table --rule SEC-008 --top-n 20` for human-scale review. Every run inventories its own rules — `rules_run`, `rules_not_run`, `rules_partially_run`, `rules_run_count`/`rules_total` — so "all of them" is a fact, not an assumption |
-| `migrate-check` | core | Boot 2→3 readiness + Java LTS/licensing inventory: located blockers, per-dimension score, effort, detected Java 8/11/17/21/25 evidence and explicit licensing-review signals | `--target-jdk 25` sets the target LTS route; `--blast-radius` orders the re-test plan; `--format github-actions` emits a stable CI annotation; `--table --rule MIG-001 --band critical --top-n 20` for blocker triage |
+| `migrate-check` | core | Boot 2→3 readiness + Java LTS/licensing inventory: located blockers, per-dimension score, effort, detected Java 8/11/17/21/25 evidence and explicit licensing-review signals | `--target-jdk 25` sets the target LTS route; `--blast-radius` orders the re-test plan; `--format github-actions` emits a stable CI annotation; `--format sarif` emits located ASK-owned findings; `--table --rule MIG-001 --band critical --top-n 20` for blocker triage |
 | `impact` / `impact-chain` | core | blast radius of a change, to the endpoints it reaches | target the **interface**, not the `Impl` |
 | `pr-impact` | core | the same, scoped to a PR diff | local `git diff HEAD`, `--since REF`, explicit `--files`, or opt-in `--pr NUMBER`; `--format github-actions` emits CI annotations; `--fail-on` gates |
 | `verify` | core | does the repo satisfy its declared contracts, **relative to a baseline** | `.ask/contracts.yml`; `--format github-actions` emits a native CI annotation while preserving exit 0/1/2. `.ask/waivers.yml` adjudicates a finding as *not a defect here* (stable id + required reason, optional expiry) so a reviewed row stops holding the gate red — a baseline records accepted debt, a waiver says it was never a defect |
 | `verify-edit` | supported | did the working-tree edits change runtime behaviour | semantic diff gate for the edit loop |
 | `--compact` / `--agent` | — | bounded structural context for an agent | flags of the root command, not commands: not tiered |
 | `onboard` / `explain` / `cold-start` | supported | orientation in an unfamiliar repo; per-class summary; bootstrap snapshot | `onboard` publishes `population`, `population_unit` and `population_total` for its source-file universe |
-| `export` / `repo-ir` / `schema` | supported | tool-agnostic views (C4, module graph, integrations); symbol-level IR; published JSON Schemas | `export --c4 --render mermaid\|svg` **draws** the model instead of only emitting it — presentation over the same payload, with the node cap written on the canvas |
+| `export` / `repo-ir` / `schema` | supported | tool-agnostic views (C4, module graph, integrations); symbol-level IR; published JSON Schemas | `export --c4 --render mermaid\|svg` **draws** the model instead of only emitting it; `repo-ir --since REF --budget-tokens N` provides bounded, deterministic agent context |
 | `modernize` | supported | coupling hubs, cycles, dead zones, refactor candidates | |
 | `review-pr` / `fix-bug` / `prepare-context` | supported | diff review, symptom triage, task-shaped context | |
 | `plan` / `compare` / `delta` / `contract-diff` | supported | what to review for a change; candidates by measured cost; outcome of a change; public-contract break | no verdicts, measured cost only |
 | `validation` | supported | request-body validation coverage and gaps | |
-| `baseline capture\|diff` · `trend` | supported | versioned architectural metrics over time — and, with `--kind findings`, the **defect population** as a series, so "open since 5.8.28" is answerable without anybody keeping the tally (`first_seen` is the earliest STORED capture, and the payload says so); `ask trend .` reads the series (a repository path or a baselines directory), `ask baseline diff .` compares the tree against its newest point | trend reporting, not gating. Baselines land in `.ask/baselines` **inside the repository** — the history travels with the code, not with a vendor; an audit that must not write passes `--dir`. `capture --auto` is the unattended form (one baseline per commit, never rewrites one, never fails the build) — automate it: [baseline-ci.yml](docs/baseline-ci.yml) |
-| `cve` | supported | which dependency advisories a route can actually **reach** — not which are on the classpath | reads a **local** OSV feed (`--feed`); takes no network at analysis time, so a CI gate can never pass because a fetch timed out. Four verdicts: `reachable` (with the routes), `imported_not_exposed`, `not_observed` and `unknown`. Nothing answers *"not reachable"* — reflection, SPI loading and container wiring reach code no source edge names — and an unresolved Maven version is `unknown`, never `not_affected`. Feed staleness is read off the feed's own dates |
+| `baseline capture\|diff\|trend\|attest` | supported | versioned architectural metrics over time, findings history and a bounded read-only evidence attestation (`baseline-attestation-v1`) with explicit comparability and non-coverage | trend reporting and evidence continuity, not gating or legal compliance. Baselines land in `.ask/baselines` **inside the repository** or an external `--dir`; automate capture with [baseline-ci.yml](docs/baseline-ci.yml) |
+| `cve` | supported | which dependency advisories a route can actually **reach** — not which are on the classpath | reads a **local** OSV feed (`--feed`) and optional local VEX statements (`--vex`); VEX is matched exactly and annotates `accepted_by_vex` without changing reachability; takes no network at analysis time |
 | `intent` | supported | a plain-language question, resolved to the typed `retrieve` query that answers it | `ask intent "what breaks if I change OrderService?"`. A scored lexical match against a declared vocabulary — **no model, no generation** — so it resolves identically on every machine. It selects a query and prints it; `--run` executes it. A question fitting two intents too closely is refused with both named, because a well-formed answer to a question you did not ask is invisible once printed |
 | `remediate` | supported | the loop from a finding to a **verified** change | audit → recipe → apply in a dedicated worktree → `verify-edit`. Dry by default. Most findings are not mechanical and the plan says which and why; an apply that could not be verified reports `unverified`, never `applied` |
 | `pr-risk` | supported | one verdict for **this diff** — does the change make things worse? | `pack gate` answers about the repository; this answers about the change. Joins `pr-impact` reach, endpoint access, the shared risk model and CODEOWNERS. `--since` differences route inventories so `new_endpoints` is a fact rather than a guess. A changed file that maps to no class caps the verdict at `UNKNOWN`, which fails every gate — a partial blast radius is not a small one |

{sourcecode-5.9.1 → sourcecode-5.9.2}/README.md

@@ -10,7 +10,7 @@
 > question. All analysis is local and deterministic; see [Privacy](#configuration--privacy)
 > before inspecting a repository whose telemetry policy you need to control.
 
-![Version](https://img.shields.io/badge/version-5.9.1-blue)
+![Version](https://img.shields.io/badge/version-5.9.2-blue)
 ![Python](https://img.shields.io/badge/python-3.9%2B-green)
 
 Copyright (c) 2026 Dominique Haroun. All rights reserved. ASK Engine 5.7.0 and
@@ -73,6 +73,14 @@ the CI signal; `--allow-unverified` can change only that exit code, never the
 reported verdict. Every pack carries a manifest with component invocations,
 source evidence and content fingerprints.
 
+For agent integrations, `ask repo-ir --since <ref> --budget-tokens N` bounds the
+serialized inline answer. If the full graph does not fit, ASK returns its summary
+view and declares `token_budget.coverage: non_coverage`; it never silently truncates
+JSON. For a rerunnable cost comparison, use `scripts/context_cost_harness.py` with
+explicit `--with-ask` and `--without-ask` command templates. It executes without a
+shell and publishes a token delta only when both commands resolve and `--comparable`
+is declared.
+
 The [Product Route](docs/PRODUCT-ROUTE.md) is normative: ASK focuses on
 deterministic evidence for Java/Spring modernization and safe change. Packs
 compose existing commands; they do not hide or replace them.
@@ -139,7 +147,7 @@ set `ASK_MAX_RSS_MB=<megabytes>`; if the process exceeds it, ASK refuses the
 answer with `MEMORY_TOO_LARGE`, including the observed peak and limit. Leave it
 unset, or set it to `0`, to disable the ceiling explicitly.
 
-**Current performance status.** Release 5.9.1 retains the shared Canonical IR
+**Current performance status.** Release 5.9.2 retains the shared Canonical IR
 path used by `validation` and now passes that same CIR into labelled `data-exposure`
 runs; the no-label path remains parse-free. These are implementation properties,
 not duration promises. A controlled external warm-path audit has opened performance
@@ -148,6 +156,13 @@ and bounded-output regressions for this release; use `ask cache model <repo>` an
 [latest external audit intake](docs/AUDIT-2026-08-26-EXTERNAL-5.9.0.md) before
 treating a historical timing or bounded flag as a current guarantee.
 
+**CI delivery and workspace licensing.** `migrate-check --format sarif` emits
+ASK-owned migration findings with source locations and provenance; it does not
+re-emit imported scanner findings. `ask auth workspace <repo>...` previews the
+aggregate Java entitlement. `--enforce` is an opt-in named-buyer pilot that reuses
+the existing Pro gate; advisory mode remains the default and no billing is
+performed by the CLI.
+
 **What a warm actually covers.** `ask cache warm` rebuilds the declared root views and their
 shared structural layers (L1/L2 + the Repository Intelligence Snapshot + the shared Canonical
 IR). Pass `--views compact` or `--views compact,agent` to warm only selected views; without
@@ -173,7 +188,7 @@ brew tap haroundominique/sourcecode && brew install sourcecode
 # pip / pipx
 pipx install sourcecode        # or: pip install sourcecode
 
-ask version                    # ask 5.9.1 — and, on a build that has aged,
+ask version                    # ask 5.9.2 — and, on a build that has aged,
                                # how many releases have probably shipped since
 ```
 
@@ -457,27 +472,28 @@ from it.
 | `posture` | supported | which beans a profile set wires, and how effective endpoint access differs between two sets | the most differentiated capability here. `--resolve-environments` says which set the repository decides; `--profile-from <file>` reads the artefact that actually decides it (Kubernetes manifest, compose file, deployment plan, `Dockerfile`, dotenv) and answers under that set, with the `file:line` — deciding nothing leaves the verdict untouched |
 | `risk` | supported | what each defect actually costs, once reach, access, write effect and the shape of the input path are in it | `defect_severity × reachability × auth_verdict × write_effect × query_construction × input_constraints`; every factor names its authority; the `query_construction` factor covers MyBatis `${}` splicing with a three-state verdict (`reaches` / `does_not_reach` / `undecidable`) and publishes the census; `--table --rule SEC-008 --band high --top-n 20` gives audit triage without `jq` |
 | `enrich` | experimental | another scanner's SARIF findings, ranked by what this repository does with them | `--sarif <log>`; same composition as `risk`, with `--table --rule <id> --band high --top-n 20` for triage |
-| `audit-report` | supported | human audit bundle over existing `risk` + `posture` evidence, optionally signed | includes `evidence_manifest` claim provenance; `--format markdown`; `--sign-key <file>` signs canonical JSON with HMAC-SHA256 |
+| `audit-report` | supported | human audit bundle over existing `risk` + `posture` evidence, optionally signed | includes `evidence_manifest` claim provenance; `--format markdown`; `--sign-key <file>` signs canonical JSON with HMAC-SHA256; `--pack ens` adds a technical ENS control matrix |
+| `audit-verify` | supported | offline verification of a signed `audit-report` bundle | recomputes the canonical payload and HMAC-SHA256; returns `valid: true/false` and a CI-friendly exit code without re-running the audit |
 | `migrate-recipe` | supported | the migration report as the OpenRewrite recipe that applies it | only recipes a finding named; the manual remainder published beside them; writes nothing without `--write`, and never a runnable command for an empty recipe list |
 | `migrate-apply` | supported | apply a measured recipe without touching the main tree | Maven and Gradle executors; plan by default; `--write` requires clean Git, pinned version and isolated worktree; no automatic commit or merge |
 | `data-exposure` | supported | which routes can carry the data you labelled, and who reaches them | labels declared in `sourcecode.config.json` — never inferred from a name; `signature` and `call_reach` evidence published apart, field-level flow out of scope (NC-008). With nothing declared, `ask data-exposure /path/to/repo` answers `answered: false` and hands back the file, the key and an example to declare — it never reports zero exposed routes |
 | `data-exposure --init` | supported | generate review-only label candidates | writes only `.ask/data-label-candidates-v1.json` with `status: proposed_only`; it never activates labels |
 | `endpoints` | core | every REST endpoint, effective path, security policy, confidence | Spring MVC + JAX-RS (~65 % recall on JAX-RS sub-resource locators). `--compact` answers the exposure census without the rows; `--servlets` lists the servlet-mounted surface as its own population; `--client-usage` says which routes the TS/JS client in this repository actually calls; `--consumer <repo>` (repeatable) joins the routes against consumers in **other** repositories — TypeScript/JS and Java — and turns the census into a surface-reduction plan: open and called (fix now), open and called by nobody (delete rather than guard), and calls this server serves no route for |
 | `spring-audit` | core | transactional anomalies + security configuration/exposure + validation gaps | `--ci`, `-f github-comment`, or `-f github-actions` for native CI annotations; `--table --rule SEC-008 --top-n 20` for human-scale review. Every run inventories its own rules — `rules_run`, `rules_not_run`, `rules_partially_run`, `rules_run_count`/`rules_total` — so "all of them" is a fact, not an assumption |
-| `migrate-check` | core | Boot 2→3 readiness + Java LTS/licensing inventory: located blockers, per-dimension score, effort, detected Java 8/11/17/21/25 evidence and explicit licensing-review signals | `--target-jdk 25` sets the target LTS route; `--blast-radius` orders the re-test plan; `--format github-actions` emits a stable CI annotation; `--table --rule MIG-001 --band critical --top-n 20` for blocker triage |
+| `migrate-check` | core | Boot 2→3 readiness + Java LTS/licensing inventory: located blockers, per-dimension score, effort, detected Java 8/11/17/21/25 evidence and explicit licensing-review signals | `--target-jdk 25` sets the target LTS route; `--blast-radius` orders the re-test plan; `--format github-actions` emits a stable CI annotation; `--format sarif` emits located ASK-owned findings; `--table --rule MIG-001 --band critical --top-n 20` for blocker triage |
 | `impact` / `impact-chain` | core | blast radius of a change, to the endpoints it reaches | target the **interface**, not the `Impl` |
 | `pr-impact` | core | the same, scoped to a PR diff | local `git diff HEAD`, `--since REF`, explicit `--files`, or opt-in `--pr NUMBER`; `--format github-actions` emits CI annotations; `--fail-on` gates |
 | `verify` | core | does the repo satisfy its declared contracts, **relative to a baseline** | `.ask/contracts.yml`; `--format github-actions` emits a native CI annotation while preserving exit 0/1/2. `.ask/waivers.yml` adjudicates a finding as *not a defect here* (stable id + required reason, optional expiry) so a reviewed row stops holding the gate red — a baseline records accepted debt, a waiver says it was never a defect |
 | `verify-edit` | supported | did the working-tree edits change runtime behaviour | semantic diff gate for the edit loop |
 | `--compact` / `--agent` | — | bounded structural context for an agent | flags of the root command, not commands: not tiered |
 | `onboard` / `explain` / `cold-start` | supported | orientation in an unfamiliar repo; per-class summary; bootstrap snapshot | `onboard` publishes `population`, `population_unit` and `population_total` for its source-file universe |
-| `export` / `repo-ir` / `schema` | supported | tool-agnostic views (C4, module graph, integrations); symbol-level IR; published JSON Schemas | `export --c4 --render mermaid\|svg` **draws** the model instead of only emitting it — presentation over the same payload, with the node cap written on the canvas |
+| `export` / `repo-ir` / `schema` | supported | tool-agnostic views (C4, module graph, integrations); symbol-level IR; published JSON Schemas | `export --c4 --render mermaid\|svg` **draws** the model instead of only emitting it; `repo-ir --since REF --budget-tokens N` provides bounded, deterministic agent context |
 | `modernize` | supported | coupling hubs, cycles, dead zones, refactor candidates | |
 | `review-pr` / `fix-bug` / `prepare-context` | supported | diff review, symptom triage, task-shaped context | |
 | `plan` / `compare` / `delta` / `contract-diff` | supported | what to review for a change; candidates by measured cost; outcome of a change; public-contract break | no verdicts, measured cost only |
 | `validation` | supported | request-body validation coverage and gaps | |
-| `baseline capture\|diff` · `trend` | supported | versioned architectural metrics over time — and, with `--kind findings`, the **defect population** as a series, so "open since 5.8.28" is answerable without anybody keeping the tally (`first_seen` is the earliest STORED capture, and the payload says so); `ask trend .` reads the series (a repository path or a baselines directory), `ask baseline diff .` compares the tree against its newest point | trend reporting, not gating. Baselines land in `.ask/baselines` **inside the repository** — the history travels with the code, not with a vendor; an audit that must not write passes `--dir`. `capture --auto` is the unattended form (one baseline per commit, never rewrites one, never fails the build) — automate it: [baseline-ci.yml](docs/baseline-ci.yml) |
-| `cve` | supported | which dependency advisories a route can actually **reach** — not which are on the classpath | reads a **local** OSV feed (`--feed`); takes no network at analysis time, so a CI gate can never pass because a fetch timed out. Four verdicts: `reachable` (with the routes), `imported_not_exposed`, `not_observed` and `unknown`. Nothing answers *"not reachable"* — reflection, SPI loading and container wiring reach code no source edge names — and an unresolved Maven version is `unknown`, never `not_affected`. Feed staleness is read off the feed's own dates |
+| `baseline capture\|diff\|trend\|attest` | supported | versioned architectural metrics over time, findings history and a bounded read-only evidence attestation (`baseline-attestation-v1`) with explicit comparability and non-coverage | trend reporting and evidence continuity, not gating or legal compliance. Baselines land in `.ask/baselines` **inside the repository** or an external `--dir`; automate capture with [baseline-ci.yml](docs/baseline-ci.yml) |
+| `cve` | supported | which dependency advisories a route can actually **reach** — not which are on the classpath | reads a **local** OSV feed (`--feed`) and optional local VEX statements (`--vex`); VEX is matched exactly and annotates `accepted_by_vex` without changing reachability; takes no network at analysis time |
 | `intent` | supported | a plain-language question, resolved to the typed `retrieve` query that answers it | `ask intent "what breaks if I change OrderService?"`. A scored lexical match against a declared vocabulary — **no model, no generation** — so it resolves identically on every machine. It selects a query and prints it; `--run` executes it. A question fitting two intents too closely is refused with both named, because a well-formed answer to a question you did not ask is invisible once printed |
 | `remediate` | supported | the loop from a finding to a **verified** change | audit → recipe → apply in a dedicated worktree → `verify-edit`. Dry by default. Most findings are not mechanical and the plan says which and why; an apply that could not be verified reports `unverified`, never `applied` |
 | `pr-risk` | supported | one verdict for **this diff** — does the change make things worse? | `pack gate` answers about the repository; this answers about the change. Joins `pr-impact` reach, endpoint access, the shared risk model and CODEOWNERS. `--since` differences route inventories so `new_endpoints` is a fact rather than a guess. A changed file that maps to no class caps the verdict at `UNKNOWN`, which fails every gate — a partial blast radius is not a small one |

{sourcecode-5.9.1 → sourcecode-5.9.2}/docs/CACHE.md

@@ -137,6 +137,7 @@ The second anchor is the field one, and it carries its own build for the same re
 | `chunk-file` | nothing | not timed | no | — | Reads one file; nothing to cache. |
 | `intent` | nothing | not timed | no | — | Resolving a question is a string operation over a declared vocabulary; only --run reaches the retrieval engine. |
 | `self-audit` | nothing | not timed | no | — | Reads this build's own registries and manifest; it never analyses a repository, so there is nothing to cache. |
+| `remediation-report` | nothing | not timed | no | — | Reads the bundled remediation ledger and build provenance; it analyses no repository and uses no cache layer. |
 | `drift` | the shared work | not timed | no | `parse`, `cir` | Resolves the posture through the shared CIR; --against resolves a second profile set over the same parse. |
 | `watch` | the shared work | not timed | yes | `parse`, `cir` | Warms once, then answers each save against the warm IR — the reason a per-save question is affordable at all. |
 | `pr-risk` | the shared work | not timed | no | `parse`, `cir` | Reuses the shared CIR for the blast radius; --since builds a second IR over the base tree, which is not cached. |
@@ -147,6 +148,7 @@ The second anchor is the field one, and it carries its own build for the same re
 | `explain-endpoint` | the shared work | not measured on the battery yet — bounded by `endpoints` on the same repository | yes | `cir`, `parse` | Builds the repository IR to answer about ONE route, so the warm it shares with `endpoints` and `posture` is the whole difference between a question you ask once and a question you ask twenty times. |
 | `selftest` | the shared work | not timed | no | `cir`, `parse` | Runs the ledger's acceptance criteria by invoking other commands against this repository, so it inherits their layers — a warm makes those runs warm. It holds no cache of its own and stores nothing. |
 | `regress` | nothing | not timed | no | — | Diffs two payload files this CLI already wrote; analyses no source, so no cache layer applies. What it reads about caching is the `cache_layers` field inside those payloads — to refuse a comparison taken under different cache states, not to use one. |
+| `audit-verify` | nothing | not timed | no | — | Verifies one local report and key; it does not inspect a repository or use ASK analysis caches. |
 | `trend` | nothing | not timed | no | — | Reads stored baseline artifacts from disk; analyses no source, so no cache layer applies. Same command as `baseline trend`. |
 | `baseline` | the shared work | capture 8.7 s → 3.6 s | no | `parse` | `capture`/`diff`/`trend` over architectural metrics. The field figure is `capture`, the subcommand that analyses; `trend` reads stored artifacts and has its own row. |
 | `retrieve` | the shared work | not timed | no | `cir`, `parse` | Every query builds or reuses the shared CIR a warm builds. |

{sourcecode-5.9.1 → sourcecode-5.9.2}/docs/DEVELOPMENT-ROADMAP.md

@@ -3,7 +3,7 @@
 *Chief-engineer development record. This is the internal, dev-facing counterpart to the
 customer-facing `docs/EXECUTIVE-ROADMAP.md`.*
 
-> **CURRENT QUEUE — release `5.9.1`; external reconciliation `AUD-608` is implemented.**
+> **CURRENT QUEUE — release `5.9.2`; external reconciliation `AUD-608` is implemented.**
 > `AUD-608-C01` is closed in `fe1f624`: `cve` declares static
 > dependency-inventory coverage and non-coverage. `AUD-608-P01` is closed in
 > `b479465`: `pr-risk --since` constructs its base context and surfaces failures
@@ -98,6 +98,7 @@ aspirations: each is asserted by that row's tests.
 | `AUD-607-X07` | P3 | Stored finding baselines across releases. | `ask baseline capture/diff/trend --kind findings` (`findings-baseline-v1`) | **Implemented (`55b93c2`).** The same store as the architectural series, prefixed so neither reads the other's documents. `first_seen` is the earliest STORED capture and the payload says so. A rename is published as one resolved and one new. |
 | `AUD-607-X08` | P3 | Environment drift alerting. | `ask drift` (`access-drift-v1`) | **Implemented (`6463fdf`).** One arithmetic for both axes (time and environment), so the two answers cannot disagree. `newly_unmatched` and `newly_matched` are separate buckets; a `removed` route is never reported as having become safe. |
 | `AUD-607-X09` | P3 | `self-audit` — run ASK against its own build. | `ask self-audit` (`self-audit-v1`) | **Implemented (`f1fa913`), with its "not recommended" reason shipped inside the payload.** The semantic engine does not apply to Python source, so those figures are absent and declared rather than reported as zeros. What it does check — cache model, format contract, schema registry and output affordances over the INSTALLED build — found a real drift on its first run. |
+| `ASK-COM-01` | P1 | Continuous evidence attestation over persisted baseline history. | `ask baseline attest` (`baseline-attestation-v1`) | **Implemented.** Read-only projection of architecture or findings trend; publishes capture boundaries, latest commit, comparability and explicit non-coverage. It never claims legal compliance, improvement, or a clean zero without history. |
 
 ### Explicitly Rejected
 
@@ -677,12 +678,17 @@ Java file, ~500 MB per 24 000-file repository), which is a sizing document and a
 **What blocks `S-18` is `S-27`, and no memo saw it.** The row below is the reason `fleet`
 moves ahead of everything except `S-23`.
 
+**S-27 measurement increment shipped:** `ask auth workspace <repo>...` now publishes
+`workspace-entitlement-v1` with unique repository count, aggregate Java population and
+an explicit `advisory_only` policy status. It does not alter the existing per-repository
+gate; entitlement enforcement remains pending named-buyer validation.
+
 | # | Row | Mechanism | Done when |
 |---|---|---|---|
-| `S-27` | **The licence axis cannot charge the buyer the product is being built for** ⭐ — `P-13` | `is_large_repo()` counts Java files **per repository path** against `_FREE_REPO_JAVA_FILE_LIMIT = 500` (`license.py:121`, `:521`), and the only other axis is the `delta` automation quota (`:267`). An organisation of 40 microservices at 300 Java files each crosses no threshold on any repository and **pays nothing**. That is precisely the buyer the third memo identifies correctly — flota, defendibilidad, *"how many unauthenticated routes does my organisation have"* — so the product's own price model excludes it. This is not a pricing preference: it is a measured contradiction between the gate in `license.py` and the route in `PRODUCT-ROUTE.md` | An axis that can charge an organisation — repository count, or a fleet manifest, or seats over a workspace — declared in `license.entitlement()` with `when_it_changes` saying what it costs, exactly as `P-2` established for the existing axis. **Not** by lowering the per-repo threshold, which would start charging the users the current rule deliberately leaves free. Acceptance: a fixture workspace of N small repositories reaches the same entitlement decision as one large repository of the same total size, or the difference is published as a stated product decision rather than an accident of the counter |
-| `S-28` ◑ | **SARIF out — the findings reach the tab the developer already reads** — **first safe increment in `17fe1ca`**: `ask pack gate --format sarif` emits SARIF 2.1.0 decision diagnostics from the gate manifest only. A BLOCK/UNVERIFIED component becomes a locationless result with its component, status and exit code; a PASS emits nothing. This is deliberately narrower than an audit-finding export: no source location is invented and no component payload is re-emitted. | The schema was already in the house: `sarif.py` parses SARIF 2.1.0 for `enrich`, with severity mapping, location resolution and an `unresolved` list that names why a result could not be placed. The implemented gate channel reaches CI without presenting imported findings as ASK discoveries. **Remaining:** source-level exports for commands that own a finding population, with a round-trip assertion over their locations and non-coverage. A result that arrived through `enrich` stays attributed to the tool that found it and is never re-emitted as ASK's own: the enrichment is the reachability, not the detection (`NC-001`, `NC-002`). |
-| `S-29` | **The remediation record becomes a public, generated page** | Twenty rows closed and field-verified in twenty-four hours, a mechanism in source per row, two rejected with their measurement and their price. It lives in `docs/DEFECT-LEDGER.md`, which is shipped inside the wheel and nowhere else. The commercial argument is exact and is the memo's best: the first objection to a single-maintainer proprietary product is *"what if it disappears"*, and the hardest answer is not an SLA promise but the product's own numbers | A **generated projection**, never the raw file — `P-14`: rows open and closed per version, median days to closure, declined rows with their reason, derived from the ledger plus `build_commit` so it cannot drift from what shipped. Redaction is part of the acceptance criterion, not a follow-up: no absolute maintainer paths, no third-party evaluation subjects named as audited. Assertion over the generator, not over the output |
-| `S-30` | **The token bill becomes a measured number, and `--since` carries the budget** | Two halves of one thesis the memo states correctly: the customer's real cost is the agent's context bill, not the licence. The stateful half it proposes (a session that remembers what the agent was given) is **refused** — it makes the answer depend on what the agent claims it saw, which breaks the determinism this product sells. The stateless half is already almost built: `--since`, `delta`, `regress`, content-addressed answers and the declared `--compact` / `--agent` ceilings | (a) `--since <ref>` composed with a token budget on the existing bounded views, so an agent supplies the sha it holds and gets only what changed inside a stated ceiling, with `non_coverage` for what the budget cut. (b) A reproducible harness in the repository that runs one real agent task with and without ASK and publishes tokens per resolved task — under the honest-benchmark rule: what did **not** work is reported first, and no figure is published that a reader cannot re-run |
+| `S-27` ◑ | **The licence axis cannot charge the buyer the product is being built for** ⭐ — `P-13` | `is_large_repo()` counts Java files **per repository path** against `_FREE_REPO_JAVA_FILE_LIMIT = 500`, while `auth workspace` aggregates the fleet. The opt-in `--enforce` pilot now applies the existing Pro gate to that aggregate without changing per-repository behavior or billing code. | Measurement and pilot gate shipped. Full activation remains conditional on named-buyer validation; no default user is charged or blocked. |
+| `S-28` ✅ | **SARIF out — the findings reach the tab the developer already reads** — **closed with source-level migration export:** `pack gate`, `spring-audit`, `verify` and `migrate-check` emit SARIF 2.1.0 through dedicated ASK-owned renderers. Source findings carry their own locations; contract and gate decisions remain locationless where no source span exists. | The output channel is now available for the ASK-owned finding populations, with provenance and non-coverage preserved. Imported SARIF remains input to `enrich` and is never re-emitted as ASK discovery. |
+| `S-29` ✅ | **The remediation record becomes a public, generated page** — **closed:** `remediation-report` publishes the redacted projection of the shipped ledger with counts, distributions, provenance and closure coverage. Private narrative and paths stay excluded; the output is explicitly a trust artifact, not an SLA or security verdict. | `ask remediation-report` is the generated public projection; its tests assert redaction, provenance and consistency with the ledger. |
+| `S-30` ✅ | **The token bill becomes a measured number, and `--since` carries the budget** | **Shipped:** `repo-ir --budget-tokens N` composes with `--since`, and `scripts/context_cost_harness.py` measures a declared task with and without ASK. It publishes bytes/tokens, build and tree state, output hashes and a delta only when both commands resolve and the operator declares `--comparable`; otherwise it records `not_comparable` without a commercial figure. The stateful session proposal remains refused because it would make answers depend on what the agent claims to have seen, breaking determinism. | Closed for the stateless scope: budgeted bounded view plus reproducible two-command harness. No agent quality claim is published by default; comparable task definitions and their rerunnable artifacts remain the operator's evidence. |
 
 **One anti-goal recorded here so it is refused once.** No rule DSL and no third-party rule
 plugins for the architecture contracts of `S-23`'s neighbourhood. The memo cites *"grep grew

{sourcecode-5.9.1 → sourcecode-5.9.2}/docs/EXECUTIVE-ROADMAP.md

@@ -5,7 +5,10 @@
 > `pack assessment` and `pack gate`, and make evidence and safe change the
 > product surface. This roadmap must not introduce a competing product thesis.
 
-> **CURRENT UPDATE — release `5.9.1`, following the external `5.9.0` reconciliation (`AUD-608`).**
+> **CURRENT UPDATE — release `5.9.2`, following the external `5.9.0` reconciliation (`AUD-608`).**
+> The commercial increment adds stateless context budgets, a reproducible context-cost harness,
+> source-level migration SARIF and an opt-in workspace entitlement pilot. Advisory behaviour remains
+> the default; named-buyer validation is still required before broad enforcement.
 > Three defects confirmed in the shipped release are closed: `cve` now
 > discloses its static inventory (`fe1f624`), `pr-risk --since` returns a
 > structured error for unreadable base context (`b479465`), and

{sourcecode-5.9.1 → sourcecode-5.9.2}/docs/PRODUCT-ROUTE.md

@@ -180,6 +180,11 @@ vulnerability is exploitable; and `not_observed` is explicitly not a statement
 of safety, because reflection, SPI loading and container wiring reach code no
 source edge names.
 
+An operator may also pass `--vex` with local, exact advisory/package decisions.
+ASK publishes those decisions as `accepted_by_vex` while preserving its own
+reachability verdict; an expired or absent VEX statement is not treated as a
+negative.
+
 ## Implementation order
 
 The implementation route is shipped through five bounded steps. The status is

{sourcecode-5.9.1 → sourcecode-5.9.2}/docs/USER_GUIDE.md

@@ -46,13 +46,13 @@ CLI commands        — impact, endpoints, spring-audit, explain, … each a pro
 The key idea: the extraction is **content-addressed**. Commands reuse the parse cache and,
 where their analysed scope matches, the shared Canonical IR; `ask cache model` names what a
 warm buys for each command rather than implying that every projection costs the same. In
-5.9.1, `validation` enters through that shared CIR and `data-exposure` reuses one semantic
+5.9.2, `validation` enters through that shared CIR and `data-exposure` reuses one semantic
 model across all declared label seeds. (The extraction and consumption contract is fixed in
 the architecture ADRs 0001–0004 under `docs/architecture/`.)
 
 The current external pack audit intake is tracked in
 [`AUDIT-2026-08-26-EXTERNAL-5.8.28-PACK.md`](AUDIT-2026-08-26-EXTERNAL-5.8.28-PACK.md);
-the two pack fixes are included in release 5.9.1, with release-artifact verification
+the two pack fixes are included in release 5.9.2, with release-artifact verification
 remaining for detached execution and pack evidence.
 
 ---
@@ -171,6 +171,7 @@ human. They project the same semantic model into agent-ready context:
 |---------|---------|
 | `ask prepare-context <task>` | Task-shaped context bundle (`onboard`, `review-pr`, `fix-bug`, `refactor`, `generate-tests`) sized for an LLM prompt. |
 | `ask repo-ir` | The low-level symbol IR itself — the raw semantic representation, for tools that want the graph, not a report. |
+| `ask repo-ir --budget-tokens N` | Stateless context budget for the inline IR. Composes with `--since`; returns the full view when it fits, otherwise the summary and explicit `non_coverage` for omitted graph fields. |
 | `ask --agent` | Agent-optimized output envelope for any command. |
 | `ask --compact` | A bounded subset (status, stacks, entry points, key dependencies) for cheap orientation. See `ask --help` for the current output budget. |
 | `ask mcp` | Runs ASK as an MCP server so an agent (Claude Desktop / Cursor) calls it as a tool. |
@@ -179,6 +180,20 @@ Rule of thumb: **developer-facing** commands (`impact`, `spring-audit`, `endpoin
 `validation`) answer a question you read; **agent-facing** commands (`prepare-context`,
 `repo-ir`, `--agent`, `--compact`) assemble context another model will consume.
 
+`repo-ir --budget-tokens N` is intentionally stateless: `--since <ref>` narrows the
+semantic change set and `--budget-tokens N` bounds the serialized inline answer. If
+the graph does not fit, ASK returns the existing summary view and publishes
+`token_budget.coverage: non_coverage` with the omitted fields. A budget that cannot
+fit even that summary is refused rather than silently truncating JSON. The budget
+applies to stdout; use `--output FILE` for an unbounded artifact.
+
+For a rerunnable context-cost comparison, use
+`python3 scripts/context_cost_harness.py` with `--with-ask` and `--without-ask`
+command templates. Templates are executed without a shell and may use `{repo}`
+and `{since}`. The report records both outputs, but only computes a token delta
+when both commands exit successfully and `--comparable` is explicit; otherwise
+the result is `not_comparable` and the process exits non-zero.
+
 **Honest state of `prepare-context` (measured in the field, 3 300-file repo):**
 
 | Task | State |
@@ -206,7 +221,7 @@ pipx install sourcecode   # isolated install, no venv needed
 
 # Verify
 ask version
-# ask 5.9.1
+# ask 5.9.2
 ```
 
 Requires Python 3.9+.
@@ -251,7 +266,7 @@ estimate scaled by file count would be wrong in the direction that costs you a s
 and an anchor printed without its release goes on recommending a nightly job for a command
 that has come to finish in seconds (C3-97).
 
-48 commands and seven command groups exist. Four of them carry most of the measured
+50 commands and seven command groups exist. Four of them carry most of the measured
 value in field use, and they are the ones to learn first:
 
 | Start with | Because |
@@ -605,6 +620,25 @@ ask audit-report . --profile prod --format markdown
 ask audit-report . --sign-key audit.key -o audit-report.json
 ```
 
+Add a technical ENS evidence mapping to the signed bundle. The mapping is not
+a certification: controls that ASK cannot observe are explicitly marked
+`missing_evidence`. Owners, expiry dates and exceptions can be supplied in a
+JSON metadata file.
+
+```bash
+ask audit-report . --pack ens --sign-key audit.key --pack-metadata controls.json -o ens-report.json
+```
+
+### `ask audit-verify` *(supported)*
+
+Verify a signed `audit-report` locally without re-running the analysis. The
+command recomputes the canonical JSON payload and HMAC-SHA256, returning
+`valid: true` with exit code 0 or `valid: false` with exit code 1.
+
+```bash
+ask audit-verify audit-report.json --sign-key audit.key
+```
+
 `--sign-key` signs the canonical JSON payload with HMAC-SHA256 using a local key file and
 publishes `payload_sha256`, `key_id` and `signature`. This is integrity evidence for the
 bundle, not a public PKI or compliance certification.
@@ -1114,6 +1148,7 @@ ask baseline capture . --ref v1.4.0     # freeze the measured fingerprint
 ask baseline capture . --auto           # the same, safe to run on every push
 ask trend .                             # read the series (same as `baseline trend`)
 ask baseline diff .                     # the tree against the newest captured point
+ask baseline attest .                   # emit a bounded evidence attestation
 ```
 
 Both readers take **either** a repository path or a directory of baselines: `ask trend .`
@@ -1140,6 +1175,19 @@ passes `--dir` and writes them elsewhere.
 `trend` reports movement — totals over time and per-hotspot fan-in tracks. It labels nothing
 "improving" or "degrading"; that reading is yours.
 
+`baseline attest` is the read-only packaging seam for an auditor or CI artifact. It reads
+the stored architecture or findings series (`--kind findings`) and publishes its capture
+boundaries, latest commit, comparability and explicit limits as `baseline-attestation-v1`.
+It is evidence continuity, not a legal or regulatory compliance verdict, and it returns
+`status: no_history` instead of manufacturing a clean zero when no capture exists.
+
+For a multi-repository buyer, `ask auth workspace <repo>...` previews the aggregate Java
+population that a workspace-sized entitlement would see. The preview is advisory only: it
+does not change the current per-repository gate or charge the workspace.
+For a named-buyer pilot, add `--enforce`: crossing the aggregate threshold then requires
+the existing Pro entitlement and exits with the standard license-required contract; below
+the threshold it passes. This flag is opt-in and does not change per-repository gates.
+
 ---
 
 ## The gate commands
@@ -1297,15 +1345,15 @@ explaining. The rest do one thing; `ask <command> --help` is the whole story.
 
 | Command | Tier | What it does |
 |---|---|---|
-| `ask migrate-check` | core | Spring Boot 2→3 readiness plus Java LTS/licensing inventory: blockers, effort range, target JDK evidence and explicit licensing-review signals. Full reference: [migrate-check.md](migrate-check.md) |
+| `ask migrate-check` | core | Spring Boot 2→3 readiness plus Java LTS/licensing inventory: blockers, effort range, target JDK evidence and explicit licensing-review signals. Supports `--format sarif` for located ASK-owned findings. Full reference: [migrate-check.md](migrate-check.md) |
 | `ask drift` | supported | What changed in the effective access — since the last capture (`--capture` records; the default compares) or between two profile sets (`--against`). One arithmetic for both axes. Separates `newly_unmatched` from `newly_matched`, and a `removed` route is NOT reported as having become safe. |
 | `ask watch` | supported | Warm the index once, then answer what each save affected — one JSON line per tick. `--once` is the pre-commit shape; `--ticks`/`--for` bound the loop. A file added since the warm is reported `unresolved`, never `unreachable`, and a failed analysis is an `error` tick rather than an empty change list. |
 | `ask pr-risk` | supported | One verdict for one diff — does this change make things worse? Joins `pr-impact` reach, endpoint access, the shared risk model and CODEOWNERS. `--since` differences route inventories so `new_endpoints` is a fact rather than a guess. An unresolved changed file caps the verdict at `UNKNOWN`, which fails every gate. |
 | `ask remediate` | supported | One loop from finding to verified change: audit → recipe → apply in a dedicated worktree → `verify-edit`. Dry by default; `--write` applies. Publishes `mechanisable` against `manual_remainder` with the reason each family cannot be rewritten, and reports `unverified` — never `applied` — when the result could not be checked. |
-| `ask cve` | supported | Cross the dependency inventory against a **local** OSV advisory feed (`--feed`; no network is taken), then report whether a route can reach the vulnerable package: `reachable`, `imported_not_exposed`, `not_observed` or `unknown`. `not_observed` is not a statement of safety, and nothing here answers "not reachable". |
+| `ask cve` | supported | Cross the dependency inventory against a **local** OSV advisory feed (`--feed`; no network is taken), then report whether a route can reach the vulnerable package: `reachable`, `imported_not_exposed`, `not_observed` or `unknown`. `--vex` imports exact local decisions as `accepted_by_vex` without changing reachability. `not_observed` is not a statement of safety, and nothing here answers "not reachable". |
 | `ask explain <Class>` | supported | Human-readable architectural summary for one class (text by design, not JSON) |
 | `ask export` | supported | Tool-agnostic views for downstream tooling: `--c4`, `--module-graph`, `--by-directory`, `--integrations`. `--c4 --render mermaid\|svg` draws the same model instead of emitting it — presentation over the existing payload, with the node cap written on the diagram. |
-| `ask repo-ir` | supported | Deterministic symbol-level IR for the whole repository |
+| `ask repo-ir` | supported | Deterministic symbol-level IR for the whole repository; `--since REF --budget-tokens N` bounds the inline agent context without silently truncating JSON |
 | `ask cold-start` | supported | Repository Intelligence Snapshot bootstrap context, returned from the persisted RIS |
 | `ask baseline … --kind findings` | supported | The defect population as a persisted series, in the same store as the architectural baseline: `capture` records it, `diff` reports new/resolved/persisting against the last capture, and `trend` says how long each still-open defect has been open. `first_seen` is the earliest STORED capture — not the day it was introduced. |
 | `ask prepare-context <task>` | supported | Task-shaped context: `onboard`, `delta`, `fix-bug`, `generate-tests`. See [Typical workflows](#typical-workflows) |
@@ -1314,9 +1362,11 @@ explaining. The rest do one thing; `ask <command> --help` is the whole story.
 | `ask rename-class` | supported | Word-boundary Java rename across the repository |
 | `ask schema <name>` | supported | Print a published JSON Schema for this tool's output |
 | `ask self-audit` | supported | Check the SHIPPED build's own coherence — cache model, format contract, schema registry and output affordances. Declares explicitly that the semantic engine does not apply to this product's own source (ASK analyses Java; this build is Python), rather than reporting zeros. `ask selftest` is the different question: the defect ledger run against a real repository. |
+| `ask auth workspace <repo>...` | supported | Aggregate workspace entitlement preview. `--enforce` opts into the named-buyer pilot that reuses the existing Pro gate when the organization-sized threshold is crossed; advisory mode remains the default and the CLI does not bill. |
+| `ask remediation-report` | supported | Redacted public projection of the shipped remediation ledger: unique row counts, status/severity distribution, build provenance and closure coverage; omits private narrative and paths. It is a trust artifact, not an SLA or security verdict. |
 | `ask archetype` | experimental | Evidence-based architectural archetype across four dimensions |
 | `ask retrieve` | parked | Typed knowledge queries over the model — kept working, no longer developed. Symbol-oriented queries accept `--target/-t`; `--module/-m`, `--subsystem/-s` and `--endpoint/-e` remain compatible domain aliases. |
-| `ask baseline capture\|diff\|trend` | supported | Versioned architectural metrics over time; see [`ask trend`](#ask-trend-dir--how-the-architecture-moved) |
+| `ask baseline capture\|diff\|trend\|attest` | supported | Versioned architectural metrics over time plus a bounded read-only evidence attestation; see [`ask trend`](#ask-trend-dir--how-the-architecture-moved) |
 | `ask cache status\|warm\|model\|clear\|freshness` | supported | Cache inspection; `ask cache model` states what a warm buys each command |
 | `ask config` · `ask version` · `ask activate` · `ask auth` · `ask telemetry` · `ask mcp` | supported | Configuration, version, licence, authentication, telemetry (on by default), MCP integration |
 
@@ -1770,7 +1820,7 @@ Allowed formats per command (the first is the default):
 | `impact-chain` | `json`, `yaml` | `json` |
 | `spring-audit` | `json`, `yaml`, `github-comment`, `github-actions` | `json` |
 | `prepare-context` | `json`, `github-comment` | `json` |
-| `migrate-check` | `json`, `text`, `github-actions` | `json` |
+| `migrate-check` | `json`, `text`, `github-actions`, `sarif` | `json` |
 | `explain` | `text`, `json` | `text` |
 | `pr-impact` | `json`, `text`, `github-actions` | `json` |
 | `verify` | `json`, `yaml`, `github-actions` | `json` |

{sourcecode-5.9.1 → sourcecode-5.9.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "sourcecode"
-version = "5.9.1"
+version = "5.9.2"
 description = "Persistent structural context and ultra-fast repeated analysis for AI coding agents"
 readme = "README.md"
 requires-python = ">=3.9"