sourcecode 5.9.7__tar.gz → 5.9.9__tar.gz

{sourcecode-5.9.7 → sourcecode-5.9.9}/CHANGELOG.md

@@ -1,5 +1,33 @@
 # Changelog
 
+## [5.9.9] — 2026-08-27
+
+*Release-alignment patch release.*
+
+**Release**
+
+- Synchronizes the package, CLI, README and user-guide version surfaces at `5.9.9`.
+- Carries forward the `5.9.8` reliability fixes and their dedicated TeaVM validation.
+- Keeps the `AUD-614` availability and native Windows/MSYS verification items explicitly open.
+
+## [5.9.8] — 2026-08-27
+
+*Audit correction and contract-alignment patch release.*
+
+**Fixed**
+
+- Standardizes `review-pr` and `activate` failures on structured stderr envelopes.
+- Distinguishes command typos from implicit repository paths and suggests commands.
+- Rejects raw unified diffs passed to `--files -`; the option now accepts path lists only.
+- Streams child progress from `pack gate` without contaminating aggregate stdout.
+- Adds per-row timeout control to `selftest` and removes the fixed-size `cold-start` warning.
+
+**Documentation and validation**
+
+- Reconciles CLI/MCP population documentation and `rename-class` migration guidance.
+- Updates README, English and Spanish guides, roadmap, ledger and CLI version output.
+- Validated with dedicated regressions against `/Users/user/Documents/workspace/testing/teavm`.
+
 ## [5.9.6] — 2026-08-27
 
 *Roadmap correction and release-alignment patch release.*

{sourcecode-5.9.7 → sourcecode-5.9.9}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sourcecode
-Version: 5.9.7
+Version: 5.9.9
 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.7-blue)
+![Version](https://img.shields.io/badge/version-5.9.9-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
@@ -196,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.7 retains the shared Canonical IR
+**Current performance status.** Release 5.9.9 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
@@ -218,7 +218,7 @@ in `overlapping_paths`; a missing or non-directory path is rejected as structure
 invalid input rather than treated as an empty repository. This prevents silent
 entitlement errors in CI and does not change per-repository gates or billing.
 
-Release 5.9.7 also hardens the boundary contracts: missing consumer repositories,
+Release 5.9.9 also carries the boundary-contract hardening: missing consumer repositories,
 malformed CVE feeds and unresolved `pack gate --since` refs fail as structured
 input errors; duplicate same-commit baselines are never overwritten. `posture
 --diff` validates unknown profiles when the repository declares profiles. In
@@ -251,7 +251,7 @@ brew tap haroundominique/sourcecode && brew install sourcecode
 # pip / pipx
 pipx install sourcecode        # or: pip install sourcecode
 
-ask version                    # ask 5.9.7 — and, on a build that has aged,
+ask version                    # ask 5.9.9 — and, on a build that has aged,
                                # how many releases have probably shipped since
 ```
 
@@ -501,6 +501,10 @@ The everyday loop: diff-based PR review, symptom-driven bug triage, and delta co
 
 ### 7 · Utilities
 `ask rename-class` (word-boundary Java rename) · `ask chunk-file` (split large files for agents) · `ask cache` (status / warm / model / clear / freshness) · `ask self-audit` (does the installed build's own registry agree with itself?)
+
+`rename-class` migration note: current releases require the explicit form
+`ask rename-class <repo> --from OldName --to NewName`. Older positional forms are
+not accepted; use `--dry-run` first when migrating scripts.
 → [reference](docs/USER_GUIDE.md)
 
 ---

{sourcecode-5.9.7 → sourcecode-5.9.9}/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.7-blue)
+![Version](https://img.shields.io/badge/version-5.9.9-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
@@ -147,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.7 retains the shared Canonical IR
+**Current performance status.** Release 5.9.9 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
@@ -169,7 +169,7 @@ in `overlapping_paths`; a missing or non-directory path is rejected as structure
 invalid input rather than treated as an empty repository. This prevents silent
 entitlement errors in CI and does not change per-repository gates or billing.
 
-Release 5.9.7 also hardens the boundary contracts: missing consumer repositories,
+Release 5.9.9 also carries the boundary-contract hardening: missing consumer repositories,
 malformed CVE feeds and unresolved `pack gate --since` refs fail as structured
 input errors; duplicate same-commit baselines are never overwritten. `posture
 --diff` validates unknown profiles when the repository declares profiles. In
@@ -202,7 +202,7 @@ brew tap haroundominique/sourcecode && brew install sourcecode
 # pip / pipx
 pipx install sourcecode        # or: pip install sourcecode
 
-ask version                    # ask 5.9.7 — and, on a build that has aged,
+ask version                    # ask 5.9.9 — and, on a build that has aged,
                                # how many releases have probably shipped since
 ```
 
@@ -452,6 +452,10 @@ The everyday loop: diff-based PR review, symptom-driven bug triage, and delta co
 
 ### 7 · Utilities
 `ask rename-class` (word-boundary Java rename) · `ask chunk-file` (split large files for agents) · `ask cache` (status / warm / model / clear / freshness) · `ask self-audit` (does the installed build's own registry agree with itself?)
+
+`rename-class` migration note: current releases require the explicit form
+`ask rename-class <repo> --from OldName --to NewName`. Older positional forms are
+not accepted; use `--dry-run` first when migrating scripts.
 → [reference](docs/USER_GUIDE.md)
 
 ---

{sourcecode-5.9.7 → sourcecode-5.9.9}/docs/DEFECT-LEDGER.md

@@ -71,6 +71,68 @@ Commercially, the audit supports normal repositories up to several thousand
 files and keeps a provisional $35-50/developer/month range, but B01/B02 block
 annual-grade reliability and enterprise-scale positioning until resolved.
 
+**External audit intake `AUD-612`, re-audit of release 5.9.7 — 2026-08-27.**
+The external scope covered roughly 130 new invocations across three forks and direct
+retests of all AUD-611 items. It reports five clean forks, no target writes, commits
+or task-kills, and a score of **7.8/10**. It confirms B05, B06, B08, B09, B10 and B11,
+and reports B01 fixed in its own matrix; B01 remains release-artifact verification
+because the prior external round reproduced it. The new queue is:
+
+| ID | Severity | Status | Evidence / closure boundary |
+|---|---:|---|---|
+| AUD-612-B02 | Critical | open | `tutorials` root compact still timed out after 300-311s with zero stdout; warning proves activity, not completion. Define scale, deadline and partial-diagnostic contracts. |
+| AUD-612-B03 | High | closed | YAML cache-hit delivery now publishes `_cache.cache_source` and `timing_ms.served_from_cache` consistently; TeaVM YAML smoke plus the direct cache-hit seam regression pass. A real L2 benchmark remains follow-up because this environment rebuilt both runs. |
+| AUD-612-B04 | High | partial | Each `selftest` row now has configurable 120 s default timeout and structured timeout diagnostics/code 75; valid-row scale latency remains open for profiling. Dedicated TeaVM timeout contract regression passes. |
+| AUD-612-B07 | Medium | closed | `pr-impact --since` now resolves refs through the shared authority and publishes `GIT_REF_NOT_FOUND`; dedicated TeaVM and existing Git-ref regressions pass. |
+| AUD-612-B13 | Medium | closed/no-repro | Controlled TeaVM campaign: 30/30 `retrieve endpoint-security --endpoint /` executions completed with exit 0, valid JSON, no errors and stable content identity after cache warm-up. Reopen on a new correlated failure. |
+| AUD-612-L | High | open | `audit-report --format markdown` timed out at 420s/500s, 2/2, after ~228s in 5.9.6. Performance regression remains open; the one-shot heartbeat sub-issue is mitigated by repeated warnings. |
+| AUD-612-K | Medium | closed | Pack orchestration now streams child stderr, forwarding inherited `ASK_PROGRESS=1` progress while preserving aggregate stdout JSON. Dedicated TeaVM gate regression passes. |
+| AUD-612-M | Medium | closed | `explain` missing-class failures now use structured `INVALID_INPUT` stderr and `exit 1`; dedicated TeaVM regression passes. |
+| AUD-612-E | Medium | closed | The events branch now applies `_exit_on_unresolved_target`; missing event symbols return `not_found` with `exit 1`. TeaVM regression passes. |
+| AUD-612-G | Medium | closed | `review-pr` runtime failures and `activate` failures now publish the shared `error.code` envelope on stderr; stdout remains reserved for valid results. `no_diff` remains the intentional successful `no_changes` result. Dedicated TeaVM and contract tests pass. |
+| AUD-612-I | Medium | closed | Removed the residual `~10K` wording from the large-output warning; help, runtime warning and compact payload consistently describe a snapshot-dependent subset with explicit `full_available` metadata. Dedicated TeaVM regression passes. |
+| AUD-612-07 | Low | closed | Missing single tokens close to a registered command now use command admission with a nearest-command suggestion; existing paths retain implicit root-scan behavior. Dedicated TeaVM regression passes. |
+| AUD-612-09 | Medium | closed | `--files -` is documented and enforced as a newline-delimited changed-path list; raw unified diffs fail with an `--name-only` conversion hint. Dedicated TeaVM regressions pass. |
+| AUD-612-14 | Medium | closed | The current population is 104 CLI leaves versus 110 MCP tools, explicitly decomposed as 101 runtime-derived plus 9 native orchestration tools; `mcp list-tools --json` matches and the relationship is published. Existing TeaVM-backed population regression passes. |
+| AUD-612-R | Medium | closed | README, English guide and Spanish manual document that `rename-class` requires `--from/--to`, the old positional syntax is unsupported, and `--dry-run` is the migration safety step. TeaVM dry-run verification passes. |
+| AUD-613-ROOT | High | closed 5.9.8 | On a TTY, explicit `ask .` was misclassified as bare `ask` after path preprocessing and rendered only the welcome card. An explicit-path marker now distinguishes both flows; TeaVM pseudo-TTY and focused CLI regressions pass. |
+
+**External audit intake `AUD-614`, re-audit of release 5.9.8 — 2026-08-27.**
+Five clean forks exercised the `testing/` corpus without target-repository writes,
+commits or Java-file changes. The initial **8.0/10** score was superseded by the
+addendum confirming a second severe availability regression; the governing score is
+**7.5/10**. Previously closed semantic fixes remained stable, but the following rows
+are the current release blockers and contract gaps:
+
+| ID | Severity | Status | Evidence / closure boundary |
+|---|---:|---|---|
+| AUD-614-F | Critical | closed 5.9.8 (reverified) | The external `/dev/null` false-success is not reproducible in the current checkout: invalid TeaVM input returns `exit 1` and identical structured stderr whether stdout is captured or discarded. A dedicated redirection regression protects the boundary. Native Windows/MSYS release-artifact verification remains required because the external evidence conflicts. |
+| AUD-614-L | Critical / regression | open | `audit-report` is contention-sensitive on `thingsboard` (3,714 files): one clean run completed in 136 s, while concurrent/isolated runs exceeded 5 minutes; JSON, YAML and Markdown all exhibited the problem. `tutorials` reached 5m39.6s with zero stdout. Requires profiling, stage visibility, deadline and structured partial output. |
+| AUD-614-RISK-L0 | High / regression | closed 5.9.8 | `risk --limit 0` now returns a fast explicit zero-row view without constructing the repository-wide composer. It publishes `risks: []`, `shown: 0`, null totals and `analysis_skipped: true`; the TeaVM flow and dedicated regression pass. |
+| AUD-614-SELFTEST-TIMEOUT | High / contract regression | closed 5.9.8 | `selftest --timeout` is now an overall deadline; each child receives the remaining budget, interrupted/unstarted rows are structured as `error`, and the command returns code 75. The real TeaVM flow and dedicated regression pass. The separate fourth-run hang remains mixed evidence. |
+| AUD-614-WIN-PROC | Medium | open | Windows/MSYS timeout or SIGTERM can leave `ask.exe` descendants alive, with MSYS PIDs unusable by native `taskkill`. Validate signal handling and Windows Job Objects from native Windows and Git Bash. |
+| AUD-614-G | Medium | closed 5.9.8 | The shared error authority normalizes legacy producer spellings to canonical uppercase codes (`NO_DIFF_SOURCE`, `INVALID_LICENSE`). TeaVM `review-pr` and activation contract tests pass. |
+| AUD-614-E | Low | open | Impact commands now agree on unresolved exit status, but their `risk_level` values still diverge (`unknown`/`low`/`unknown`). Define one not-found payload semantics and enforce parity. |
+| AUD-614-I | Medium | closed 5.9.8 | The user manual and internal compacting comment no longer promise `~10K`; they state that `cold-start --compact` is snapshot-dependent, expose `estimated_tokens`, and require size validation before direct AI injection. The CLI help and payload already used this contract. A hard ceiling remains optional future scope. |
+| AUD-614-INTENT-TIE | Medium | open | Exact lexical ties at score `2.8284` still resolve differently for `endpoint security` and `security surface`. Define deterministic tie/margin semantics and add a real-repository regression. |
+| AUD-614-07 | Low | closed 5.9.8 (reverified) | The installed `ask spring-audi` entry point returns `Did you mean: spring-audit?`; the TeaVM path/typo regression battery passes. The external wording report is not reproducible in the current checkout. |
+| AUD-614-JUNIT4 | Medium | open | JUnit4 projects remain `project_type: unknown`; add evidence-backed classification without broad heuristic false positives. |
+
+The audit also confirms root cache reuse, stdin contracts, pack progress, explain and
+impact error routing, self-audit population disclosure, endpoint compact disclosure,
+Spring detection controls, baseline safety and the prior `/dev/null` fix matrix. The
+intermittent endpoint-security retrieval issue had 0/18 failures in this pass and stays
+under observation because its historical rate is about 2% over 51 runs.
+
+**Commercial boundary.** The corrected assessment is `$25-40/developer/month`, not the
+initial `$45-58` headline. Do not market enterprise-scale support or production CI
+gating for repositories above roughly 3,000 files until the four critical/high
+availability and error-transport rows are independently closed with bounded evidence.
+
+Commercially, normal repositories up to about 4,000 files remain viable at a provisional
+$40-55/developer/month. B02, B04 and L block annual CI-gating and extreme-monorepo claims;
+B03, K, M and G weaken machine-consumable evidence.
+
 **External audit intake `AUD-610`, release 5.9.3 — 2026-08-27.** The attached
 report scored the build **7.2/10** after five parallel batches and approximately
 120 invocations. It verified a clean target repository, no Java-file changes,

{sourcecode-5.9.7 → sourcecode-5.9.9}/docs/DEVELOPMENT-ROADMAP.md

@@ -3,7 +3,15 @@
 *Chief-engineer development record. This is the internal, dev-facing counterpart to the
 customer-facing `docs/EXECUTIVE-ROADMAP.md`.*
 
-> **CURRENT QUEUE — release `5.9.7`; external reconciliation `AUD-611` adds the next correction queue.**
+> **CURRENT QUEUE — release `5.9.9`; external re-audit `AUD-614` remains the reliability gate.**
+> The latest external pass confirms the cache, stdin, progress, error-channel and
+> population fixes, but reports a serious availability regression: `audit-report`
+> is contention-sensitive on a normal large repository. The `/dev/null` report is
+> reverified as fixed in the current checkout; native Windows/MSYS release-artifact
+> confirmation remains. `risk --limit 0` and the `selftest --timeout` contract are now
+> closed in this cycle; Windows process-tree cleanup remains separately open.
+> `AUD-612` remains the preceding audit record; `AUD-614` is the governing queue
+> for the current `5.9.9` state, carrying forward the `5.9.8` fixes.
 > The 2026-08-27 external review adds `AUD-610-B01` through `AUD-610-B10`, led by
 > silent `selftest` nondeterminism, silent root/audit-report failures, a legal-zero
 > `risk --limit 0` crash, an unvalidated consumer path and contradictory Spring
@@ -211,6 +219,81 @@ findings block an annual-grade reliability claim. Pricing and enterprise
 positioning remain hypotheses until AUD-611-B01 and AUD-611-B02 are closed and
 the latency contract is explicit.
 
+### External Audit Intake — `AUD-612` re-audit, release 5.9.7
+
+The external re-audit covered repositories under `Documents/workspace/testing/` and
+ran approximately 130 new invocations across three forks, plus direct retests of all
+13 `AUD-611` items. It reports five clean forks, no target-repository changes, no
+commits and no task-kill intervention. The score is **7.8/10**, up from the recorded
+`AUD-611` score of 7.4/10. It confirms complete closure of B05, B06, B08, B09, B10
+and B11, confirms the endpoint compact disclosure improvement, and reports B01 as
+fixed in its own 13-run matrix. Because the preceding external round reproduced B01,
+that result remains release-artifact verification rather than erased history.
+
+| ID | Severity | Finding | Required future closure |
+|---|---:|---|---|
+| AUD-612-B02 | Critical | Cold root `ask . --compact` on `tutorials` (24,073 Java files) still timed out after 300-311 seconds with zero stdout; the 60-second warning proves activity but does not deliver a result. | Define and enforce a scale contract, bound or accelerate the root scan, and preserve structured partial/deadline diagnostics. |
+| AUD-612-B03 | High | **Closed in this fix.** The YAML cache-hit delivery branch now injects `_cache.cache_source` and refreshes `timing_ms.served_from_cache` from the same authoritative hit state as JSON. | Keep the YAML cache seam regression and a real cold/warm multi-process benchmark green; the current TeaVM environment did not generate an L2 hit spontaneously. |
+| AUD-612-B04 | High | **Partially closed in this fix.** `selftest` now bounds every ledger child with configurable `--timeout` (120 s default) and preserves structured timeout diagnostics/code 75. Valid-row scale latency remains open for profiling. TeaVM timeout contract regression passes. | Add phase/correlation IDs and profile slow valid rows; do not raise the default without evidence. |
+| AUD-612-B07 | Medium | **Closed in this fix.** `pr-impact --since` now resolves refs through the shared Git authority and publishes `GIT_REF_NOT_FOUND`, matching posture and timeline. | Keep the complete ref-consumer matrix green. |
+| AUD-612-B13 | Medium / investigation | **Closed as not reproduced in this investigation.** A controlled 30-run TeaVM campaign with an isolated cache completed 30/30 with exit 0, valid JSON, 0 errors and one stable content identity after warm-up. Reopen on any new failure with per-run correlation data. | Keep repeated/concurrent retrieval coverage in release audits. |
+| AUD-612-L | High / regression | `audit-report . --format markdown` timed out at 420s with contention and 500s in isolation, 2/2, after completing in about 228s in 5.9.6. The heartbeat-only sub-issue is now mitigated: warnings repeat at the configured interval. | Reproduce with a 900s diagnostic window, identify the performance regression and add a bounded failure envelope. |
+| AUD-612-K | Medium | **Closed in this fix.** Pack orchestration now forwards child stderr while each component runs, so inherited `ASK_PROGRESS=1` heartbeats reach the operator without contaminating the aggregate stdout JSON. TeaVM gate regression passes. | Keep nested progress and stdout purity tests green. |
+| AUD-612-M | Medium | **Closed in this fix.** `explain <nonexistent-class>` now emits `INVALID_INPUT` as structured stderr with `exit 1`; the internal explanation API remains unchanged. | Keep class-not-found and no-diff contract tests green for the remaining public commands. |
+| AUD-612-E | Medium | **Closed in this fix.** `impact-chain --type events` now applies the shared not-found exit policy after emitting its result, returning `exit 1` for unresolved symbols. | Keep every impact type on the shared CLI exit-policy test. |
+| AUD-612-G | Medium | **Closed in this fix.** `review-pr` runtime failures and `activate` failures now publish the shared `error.code` envelope on stderr, with stdout reserved for valid results. The intentional `review-pr` `no_diff` result remains `exit 0` / `no_changes`. TeaVM and contract regressions pass. | Keep public failure paths on the shared envelope and preserve the no-diff success semantics. |
+| AUD-612-I | Medium | **Closed in this fix.** The remaining `~10K` promise in the large-output warning is removed; help, runtime warning and compact payload now consistently describe a snapshot-dependent orientation subset with explicit `full_available` metadata. TeaVM compact regression passes. | Keep compact-size wording derived from the actual snapshot contract. |
+| AUD-612-07 | Low / UX | **Closed in this fix.** A missing single token close to a registered command is now rejected as an unknown command with nearest-command suggestions; existing paths retain implicit root-scan behavior. TeaVM path and typo regressions pass. | Keep command admission and implicit-path differential tests green. |
+| AUD-612-09 | Medium / docs | **Closed in this fix.** Help now describes `--files -` as a newline-delimited changed-path list. Raw unified diffs are rejected early with an `--name-only` conversion hint instead of being interpreted as file paths. TeaVM list and rejection regressions pass. | Keep the stdin grammar and raw-diff rejection tests green. |
+| AUD-612-14 | Medium / governance | **Closed in this reconciliation.** Current `self-audit` publishes 104 registered CLI leaves and 110 served MCP tools, decomposed as 101 runtime-derived plus 9 native orchestration tools; `mcp list-tools --json` matches 110. The payload states that the populations are intentionally different and gives the formula. Existing TeaVM-backed population regression passes. | Keep the population formula and parity regression generated from the live registries. |
+| AUD-612-R | Medium / migration | **Closed in this fix.** The explicit `--from/--to` contract is now documented in README, English guide and Spanish manual; the old positional syntax is explicitly marked unsupported and `--dry-run` is recommended for script migration. TeaVM dry-run verification passes. | Keep migration guidance aligned with the live command signature. |
+| AUD-613-ROOT | High / regression | **Closed in this fix.** On a TTY, explicit `ask <repo>` paths were removed during argv preprocessing and misclassified as a bare invocation, so `ask .` rendered only the welcome card. The preprocessor now retains an explicit-path marker: bare `ask` still shows the welcome card, while `ask .` analyzes and emits JSON. A real TeaVM pseudo-TTY run and focused CLI regressions pass. | Keep the bare-invocation versus explicit-root differential test green. |
+
+### External Audit Intake — `AUD-614` re-audit, release 5.9.8
+
+The external re-audit covered the repositories under `Documents/workspace/testing/`
+using five clean forks. It reports no target-repository writes, commits or Java-file
+changes. The initial score of **8.0/10** was superseded by the addendum after the
+previously incomplete `risk --limit 0` run was confirmed; the governing assessment is
+**7.5/10**, the first decline in the series. No previously closed semantic fix was
+reported as broken, but availability and contract reliability regressed.
+
+| ID | Severity | Finding | Required future closure |
+|---|---:|---|---|
+| AUD-614-F | Critical | **Closed in this verification.** The reported `/dev/null` false-success is not reproducible in the current `5.9.8` checkout: invalid TeaVM input returns `exit 1` and the identical structured stderr envelope with normal stdout capture or stdout discarded. A dedicated redirection matrix now protects this boundary. Keep release-artifact verification on native Windows/MSYS because the external witness remains contradictory. | Keep the redirection matrix green across error classes, entry points and platforms. |
+| AUD-614-L | Critical / regression | `audit-report` is not reliably bounded. `thingsboard` (3,714 files) completed once in 136 s but timed out after more than 5 minutes under concurrent load; JSON, YAML and Markdown all showed the same sensitivity. `tutorials` remained at 5m39.6s with zero stdout. | Profile contention and shared-cache/worker behaviour, expose stages, enforce a deadline and structured partial/failure output, and define a supported repository-size/load envelope. |
+| AUD-614-RISK-L0 | High / regression | **Closed in this fix.** `risk --limit 0` now returns a fast explicit zero-row view without constructing the repository-wide composer. It publishes `risks: []`, `shown: 0`, null totals and `analysis_skipped: true`, so an empty requested view is not misread as a zero-risk census. The real TeaVM flow completes within 12 s and the dedicated regression passes. | Keep the zero-row contract and ensure filters that request actual composition continue through the normal analysis path. |
+| AUD-614-SELFTEST-TIMEOUT | High / contract regression | **Closed in this fix.** `selftest` now treats `--timeout` as an overall execution deadline, bounds each child by the remaining budget, emits structured errors for the interrupted and unstarted rows, and returns code 75. The real TeaVM flow and dedicated regression pass. The separate fourth-run hang remains mixed evidence. | Keep the parent/child deadline and code-75 contract green on the installed entry point and TeaVM. |
+| AUD-614-WIN-PROC | Medium | On Windows/MSYS, timeout or SIGTERM can leave `ask.exe` descendants alive; the MSYS PID cannot be cleaned with native `taskkill`. The audit observed low-memory orphan processes after a timed-out run. | Implement signal/CTRL_BREAK cleanup and Windows Job Objects or document a verified equivalent; test parent and descendant termination from native Windows and Git Bash. |
+| AUD-614-G | Medium | **Closed in this fix.** The shared error authority now normalizes legacy producer spellings to canonical uppercase codes: `NO_DIFF_SOURCE` and `INVALID_LICENSE`. The TeaVM `review-pr` flow and activation contract tests pass. | Keep all public error producers on the canonical code authority. |
+| AUD-614-E | Low / semantic parity | The impact family now returns consistent `exit 1` for unresolved symbols, but `risk_level` still differs cosmetically (`unknown`/`low`/`unknown`) across the three commands. | Decide one not-found semantic shape and generate all impact-family payloads from it. |
+| AUD-614-I | Medium / contract | **Closed in this fix.** The user manual no longer promises `~10K` for `cold-start --compact`; it now states that the orientation subset depends on the stored snapshot, exposes `estimated_tokens`, and recommends checking the measured size before direct AI injection. The CLI help and payload already carried the same non-fixed-size contract. | Keep the manual, help and payload wording derived from the snapshot-size contract; a hard ceiling remains a separate product decision. |
+| AUD-614-INTENT-TIE | Medium | Equal lexical scores (`2.8284`) still produce different verdicts: `endpoint security` is refused while `security surface` resolves. This has remained unchanged for two rounds and exposes unstable tie semantics. | Define deterministic tie handling, publish the competing intents and margin, and add a real-repository regression for exact-score collisions. |
+| AUD-614-07 | Low / UX regression | **Closed in this verification.** The installed `ask spring-audi` entry point returns the command-admission error with `Did you mean: spring-audit?`; the TeaVM path/typo regression battery passes. The external wording report is not reproducible in the current checkout. | Keep command admission, error wording and help aligned in the installed-CLI test. |
+| AUD-614-JUNIT4 | Medium / classification | JUnit4 repositories remain classified as `unknown`; no change from the previous audit. | Add evidence-backed JUnit4 detection without weakening confidence or introducing Kotlin/Java false positives. |
+
+**Confirmed stable in this round.** Root cache reuse (cold 267 s to warm 1-2 s),
+`pr-impact`/`pr-risk --files -`, progress propagation through `pack gate --since`,
+`explain` error routing, impact exit status, self-audit population explanation,
+endpoint compact disclosure, Spring detection across six controls, baseline safety and
+the earlier `/dev/null` fix matrix were revalidated without regression. The intermittent
+`retrieve endpoint-security` issue had no failures in the latest 18 runs (51-run
+history: about 2%); keep it as a monitored investigation rather than a closure claim.
+
+**Commercial interpretation.** The first headline estimate of `$45-58/developer/month`
+is superseded by the corrected assessment of `$25-40/developer/month`. ASK remains
+credible for normal repositories, but the product must not claim enterprise-scale
+support or production CI gating for repositories above roughly 3,000 files until
+`AUD-614-F` and `AUD-614-L` have a bounded, independently reproduced closure. The
+Windows process-tree item remains a platform-specific reliability risk. The absence
+of target mutation remains a positive safety signal, not evidence of availability.
+
+**Commercial interpretation.** Normal repositories up to roughly 4,000 files remain a
+credible adoption target, with the external estimate at **$40-55/developer/month**.
+The product is not yet suitable for annual CI-gating commitments or extreme monorepos:
+B02, B04 and regression L leave the system without a reliable completion contract,
+while K and the remaining performance rows weaken machine-consumable evidence and completion confidence.
+
 ### External Audit Intake — `AUD-610` detail, release 5.9.3
 
 The attached external report audited ASK `5.9.3` in five parallel batches

{sourcecode-5.9.7 → sourcecode-5.9.9}/docs/EXECUTIVE-ROADMAP.md

@@ -5,7 +5,7 @@
 > `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.7`, following the external `5.9.3` reconciliation.**
+> **CURRENT UPDATE — release `5.9.9`, following the external `5.9.3` reconciliation.**
 > 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.
@@ -19,6 +19,30 @@
 > non-reproduction did not cover the payload shape now identified. Details are
 > in [`AUDIT-2026-08-26-EXTERNAL-5.9.0.md`](AUDIT-2026-08-26-EXTERNAL-5.9.0.md).
 
+> **RE-AUDIT — 5.9.9, received 2026-08-27.** The external re-audit confirms the
+> cache, stdin, progress, error-channel and population corrections, but the corrected
+> score is **7.5/10** after confirming a serious availability regression. `audit-report`
+> is sensitive to contention and can exceed five minutes even on a 3,714-file repository;
+> `risk . --limit 0` and `selftest --timeout` were also investigated and are now
+> bounded by explicit contracts. The long-standing `/dev/null` false-success is
+> reverified as fixed in the current checkout, with native Windows/MSYS artifact
+> confirmation still pending; `audit-report` remains sensitive to contention. Do not position ASK
+> for enterprise-scale repositories or production CI gating above roughly 3,000 files
+> until these remaining bounded reliability contracts are independently closed. The corrected commercial estimate is
+> `$25-40/developer/month`, superseding the preliminary `$45-58` headline. Full detail
+> is recorded as `AUD-614` in the development roadmap and defect ledger.
+
+> **RE-AUDIT — 5.9.7, received 2026-08-27.** Three independent forks added roughly
+> 130 invocations and retested the AUD-611 queue. The score rose to **7.8/10** and
+> confirmed the help, stdin, Git-ref, intent, impact-score and progress corrections.
+> It also found a high-severity `audit-report --format markdown` performance regression
+> (420-500s without completion), a YAML cache-hit disclosure defect, missing progress
+> propagation in `pack gate`, and inconsistent error envelopes in `explain`, `review-pr`
+> and `activate`. B02/B04 and the new regression remain blockers for annual CI-gating
+> or extreme-monorepo positioning. Normal repositories around 4,000 files remain the
+> viable commercial segment at a provisional `$40-55/developer/month`. Full detail is
+> recorded as `AUD-612` in the development roadmap and defect ledger.
+
 > **RE-AUDIT — 5.9.6, received 2026-08-27.** Seven independent forks exercised
 > approximately 250 invocations across the testing corpus with no target-repository
 > mutation or regression in the three latest fixes. The final score is **7.4/10**.

{sourcecode-5.9.7 → sourcecode-5.9.9}/docs/MANUAL-USUARIO.md

@@ -1,6 +1,6 @@
 # Manual de usuario — ASK Engine
 
-> Versión de la herramienta: **5.9.7**  ·  El comando que se ejecuta es `ask`.
+> Versión de la herramienta: **5.9.9**  ·  El comando que se ejecuta es `ask`.
 > (`sourcecode` sigue funcionando como alias en desactivación y reenvía a `ask`.)
 > Público: personas que van a usar `ask` por primera vez, sin conocimiento previo.
 
@@ -8,7 +8,7 @@
 
 ## 1. ¿Qué es ASK Engine?
 
-### Contratos de fiabilidad de la versión 5.9.7
+### Contratos de fiabilidad de la versión 5.9.9
 
 Las entradas inválidas se rechazan antes del análisis costoso mediante el
 envelope estructurado `INVALID_INPUT`: un `--consumer` inexistente, un feed CVE
@@ -955,6 +955,11 @@ ask rename-class . --from OldName --to NewName --output rename-audit.json
 **Opciones:**
 - `--from` (**obligatorio**): nombre actual de la clase (PascalCase, p. ej. `ServiceA`).
 - `--to` / `-t` (**obligatorio**): nombre nuevo (PascalCase, p. ej. `ServiceB`).
+
+**Nota de migracion:** las versiones actuales exigen la forma explicita
+`ask rename-class <repo> --from NombreAntiguo --to NombreNuevo`. La sintaxis
+posicional antigua ya no se acepta. Al actualizar scripts, anade `--dry-run`
+para revisar primero el plan de cambios.
 - `--dry-run`: calcula los cambios pero **no escribe ni renombra** nada en disco.
 - `--no-tests`: excluye los ficheros de test del rename (solo `src/main`).
 - `--format`: `json` (por defecto) o `yaml`.
@@ -1005,7 +1010,7 @@ foto).
 `ask cache freshness .` si necesitas comprobar su relación con el HEAD actual.
 
 **Aviso de tamaño:** la salida completa es grande (~100K–200K tokens en repos medianos).
-- `--compact`: emite un subconjunto compacto (~10K tokens): status, `git_head`, stacks, puntos de entrada y dependencias clave. **Seguro para inyectar directamente en una IA.**
+- `--compact`: emite un subconjunto de orientación con `status`, `git_head`, stacks y puntos de entrada. Su tamaño depende del snapshot persistido y no tiene un techo fijo; para imponer un límite de salida usa la configuración de ceiling o guarda la respuesta con `--output`. **Comprueba `estimated_tokens` antes de inyectarlo directamente en una IA.**
 - `--output` / `-o`: guarda la foto completa en fichero para herramientas de búsqueda local.
 - `--copy` / `-c`: al portapapeles. Con la salida completa esto son cientos de KB; normalmente lo que quieres copiar es `--compact -c`.
 

{sourcecode-5.9.7 → sourcecode-5.9.9}/docs/USER_GUIDE.md

@@ -46,16 +46,16 @@ 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.7, `validation` enters through that shared CIR and `data-exposure` reuses one semantic
+5.9.9, `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.7, with release-artifact verification
+the two pack fixes are included in release 5.9.9, with release-artifact verification
 remaining for detached execution and pack evidence.
 
-### Reliability contracts in 5.9.7
+### Reliability contracts in 5.9.9
 
 Invalid analysis inputs fail before expensive work and use the structured
 `INVALID_INPUT` envelope: a missing `--consumer` repository, a malformed CVE
@@ -236,7 +236,7 @@ pipx install sourcecode   # isolated install, no venv needed
 
 # Verify
 ask version
-# ask 5.9.7
+# ask 5.9.9
 ```
 
 Requires Python 3.9+.
@@ -1381,6 +1381,10 @@ explaining. The rest do one thing; `ask <command> --help` is the whole story.
 | `ask chunk-file <file>` | supported | Split a large Java file into semantic chunks an agent can consume |
 | `ask intent "<question>"` | supported | Resolve a plain-language question to the typed `retrieve` query that answers it (scored lexical match against a declared vocabulary — no model, no generation). Prints the query; `--run` executes it. A question fitting two intents too closely is refused with both named. |
 | `ask rename-class` | supported | Word-boundary Java rename across the repository |
+
+**Migration note:** `rename-class` requires the explicit `--from OldName --to NewName`
+options. Older positional name syntax is no longer accepted. Add `--dry-run` when
+updating an existing script so the planned file changes can be reviewed first.
 | `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. |

{sourcecode-5.9.7 → sourcecode-5.9.9}/pyproject.toml

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

{sourcecode-5.9.7 → sourcecode-5.9.9}/src/sourcecode/__init__.py

@@ -4,4 +4,4 @@ ASK Engine is the product. ``ask`` is the canonical CLI command; ``sourcecode``
 the legacy compatibility alias and the Python/PyPI package name. See
 docs/PRODUCT_IDENTITY.md (normative)."""
 
-__version__ = "5.9.7"
+__version__ = "5.9.9"