sourcecode 5.9.16__tar.gz → 5.9.17__tar.gz

{sourcecode-5.9.16 → sourcecode-5.9.17}/.github/workflows/windows-battery.yml

@@ -44,3 +44,24 @@ jobs:
         env:
           SOURCECODE_CACHE_DIR: ${{ runner.temp }}/ask-cache
           SOURCECODE_CONTEXT_CACHE_DIR: ${{ runner.temp }}/ask-context-cache
+
+      - name: Record critical command reliability matrix
+        shell: pwsh
+        run: |
+          $root = Join-Path $env:RUNNER_TEMP "ask-reliability-repo"
+          $evidence = Join-Path $env:RUNNER_TEMP "ask-windows-reliability.json"
+          New-Item -ItemType Directory -Force (Join-Path $root "src/main/java/com/acme") | Out-Null
+          Set-Content -Path (Join-Path $root "pom.xml") -Value '<project><modelVersion>4.0.0</modelVersion><groupId>com.acme</groupId><artifactId>app</artifactId><version>1</version></project>'
+          Set-Content -Path (Join-Path $root "src/main/java/com/acme/App.java") -Value 'package com.acme; public class App {}'
+          git -C $root init --quiet
+          git -C $root config user.email ci@example.invalid
+          git -C $root config user.name ASK-CI
+          git -C $root add .
+          git -C $root commit --quiet -m baseline
+          python scripts/windows_reliability_matrix.py $root --output $evidence
+
+      - name: Upload Windows reliability evidence
+        uses: actions/upload-artifact@v4
+        with:
+          name: ask-windows-reliability-matrix
+          path: ${{ runner.temp }}/ask-windows-reliability.json

{sourcecode-5.9.16 → sourcecode-5.9.17}/CHANGELOG.md

@@ -1,5 +1,25 @@
 # Changelog
 
+## [5.9.17] — 2026-08-31
+
+*Reliability and monorepo performance follow-up after the 5.9.16 external audit.*
+
+### Fixed
+
+- `risk`, `verify`, `audit-report` and `migrate-check` now emit structured
+  `EXECUTION_FAILED` evidence with a non-zero exit when unexpected analysis
+  failures occur; they cannot report an empty successful result through that path.
+- Semantic workspace analysis reuses the already scanned workspace tree, and
+  root graph, documentation and metrics analysis share one pruned monorepo tree.
+
+### Verification
+
+- Added a Windows reliability-matrix tool and manual workflow artifact covering
+  `risk`, `verify`, Markdown `audit-report`, `spring-audit`, `migrate-check` and
+  `migrate-apply`. It records each exit code and output size across 30 repetitions.
+- Native Windows process cleanup and the remaining contradictory reliability
+  observations remain open until that evidence is collected.
+
 ## [5.9.16] — 2026-08-31
 
 *Audit candidate following the 5.9.15 release recovery.*

{sourcecode-5.9.16 → sourcecode-5.9.17}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sourcecode
-Version: 5.9.16
+Version: 5.9.17
 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.16-blue)
+![Version](https://img.shields.io/badge/version-5.9.17-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,13 +196,14 @@ 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.16 retains the shared Canonical IR
+**Current performance status.** Release 5.9.17 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. It also removes two repeated walks of the same file tree in
 the detection phase, measured at **1.69× on a 24,073-file monorepo** — 54.9 s to
 32.5 s cold, with a byte-identical answer. A measurement on one repository and one
-machine is not a duration promise either.
+machine is not a duration promise either. It also avoids repeated monorepo tree
+walks when optional context and semantic analysis share the same scan.
 
 The root analysis now stops at `ASK_MAX_ANALYSIS_SECONDS` instead of running past
 it: a spent budget returns a structured partial result naming the phases that
@@ -233,7 +234,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.16 also carries the boundary-contract hardening: missing consumer repositories,
+Release 5.9.17 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
@@ -266,7 +267,7 @@ brew tap haroundominique/sourcecode && brew install sourcecode
 # pip / pipx
 pipx install sourcecode        # or: pip install sourcecode
 
-ask version                    # ask 5.9.16 — and, on a build that has aged,
+ask version                    # ask 5.9.17 — and, on a build that has aged,
                                # how many releases have probably shipped since
 ```
 

{sourcecode-5.9.16 → sourcecode-5.9.17}/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.16-blue)
+![Version](https://img.shields.io/badge/version-5.9.17-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,13 +147,14 @@ 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.16 retains the shared Canonical IR
+**Current performance status.** Release 5.9.17 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. It also removes two repeated walks of the same file tree in
 the detection phase, measured at **1.69× on a 24,073-file monorepo** — 54.9 s to
 32.5 s cold, with a byte-identical answer. A measurement on one repository and one
-machine is not a duration promise either.
+machine is not a duration promise either. It also avoids repeated monorepo tree
+walks when optional context and semantic analysis share the same scan.
 
 The root analysis now stops at `ASK_MAX_ANALYSIS_SECONDS` instead of running past
 it: a spent budget returns a structured partial result naming the phases that
@@ -184,7 +185,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.16 also carries the boundary-contract hardening: missing consumer repositories,
+Release 5.9.17 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
@@ -217,7 +218,7 @@ brew tap haroundominique/sourcecode && brew install sourcecode
 # pip / pipx
 pipx install sourcecode        # or: pip install sourcecode
 
-ask version                    # ask 5.9.16 — and, on a build that has aged,
+ask version                    # ask 5.9.17 — and, on a build that has aged,
                                # how many releases have probably shipped since
 ```
 

sourcecode-5.9.17/docs/AUDIT-2026-08-31-EXTERNAL-5.9.16.md

@@ -0,0 +1,54 @@
+# External Audit — 5.9.16 Re-audit
+
+**Received:** 2026-08-31  
+**Scope:** repositories under `testing/`  
+**Evidence status:** external observations; contradictory fork results are kept
+open rather than converted into closure claims.
+
+## Summary
+
+Release `5.9.16` substantially recovers from the defective `5.9.15` artefact.
+The nine missing commands are restored: `ask --help` lists 57 top-level commands,
+`self-audit` reports 104 registered CLI commands, and independent forks invoked
+the recovered commands rather than only checking help text.
+
+The audit also re-confirms recovery of `/dev/null` error handling, the space form
+of `--max-output-tokens`, endpoint/posture validation, `risk --limit 0`, missing
+`explain` error output, and baseline attest/diff/trend behavior.
+
+This is not a full reliability clearance. Independent forks still observed silent
+failures for `risk` with a non-zero limit, `verify`, and Markdown `audit-report`.
+The measurements for `spring-audit`, `migrate-check`, and `migrate-apply` conflict
+between forks and therefore cannot close the historical shared-worker defect.
+
+## Measured Improvements
+
+| Area | External result | Status |
+|---|---|---|
+| Command surface | Nine commands restored and exercised; `self-audit` passes with 104 CLI commands. | Closed for this incident. |
+| Error handling | `/dev/null` and `--max-output-tokens 10` regressions no longer reproduced. | Closed, retain release tests. |
+| `tutorials` manifest parsing | More than four minutes became 21.5 seconds. | Confirmed improvement. |
+| `tutorials` total root analysis | Completed in 4m52.6s with JSON output. | Improved, not yet bounded at a seconds-scale target. |
+| `review-pr` | No reproduction in 38 accumulated repetitions. | Closed/no-repro, retain regression test. |
+
+## Open Risks
+
+| ID | Finding | Required closure |
+|---|---|---|
+| `AUD-620-R` | `risk` with `--limit != 0`, `verify`, and Markdown `audit-report` still silently fail in independent forks. `spring-audit`, `migrate-check`, and `migrate-apply` have conflicting results. | A controlled native Windows/pipx matrix with at least 30 repetitions per command and complete result evidence. |
+| `AUD-620-TUTORIALS` | The improved manifest stage exposed `analyzing repository context` as the new dominant delay, up to roughly 2.3 minutes without progress change. | Profile and optimize that phase; repeat whole-command timing on the same Windows corpus. |
+| `AUD-620-I` | `cold-start --compact` size is state-dependent; observed values across rounds differ. `cache warm` may return agent-view exit 143. | Publish a reproducible priming sequence and investigate agent-view warm failure separately. |
+| `AUD-620-WIN-PROC` | Two to four `ask.exe` descendants were observed after runs. | Native Windows/Git Bash process-tree tests for successful, timed-out and interrupted commands. |
+
+## Audit Procedure Requirement
+
+Before every measured command, capture the target repository's `pwd`, `git status
+--short`, and `git rev-parse HEAD`, plus the installed `ask version`. Record command,
+timeout, exit code and bytes written to stdout, stderr and any output file. This avoids
+counting an empty scratch directory as a successful run against the intended corpus.
+
+## Release Position
+
+`5.9.16` is a verified recovery of the lost command surface and several concrete
+regressions. It remains suitable for bounded use, but not for production CI-gating
+or enterprise-scale reliability claims until the open native-Windows evidence closes.

{sourcecode-5.9.16 → sourcecode-5.9.17}/docs/DEFECT-LEDGER.md

@@ -14,6 +14,36 @@ Status values: `open` · `in-progress` · `closed <version>` · `by-design` (wit
 The facts these rows are keyed to are published: `ask schema facts-v1` prints the registry
 (authority, definition, consumers, parity test) that the release battery enforces.
 
+## Current Synchronization — External Audit `AUD-620`
+
+**Re-audit of release `5.9.16`, received 2026-08-31.** This audit confirms that
+the defective `5.9.15` command surface was restored: all nine missing commands
+are again registered and independently invoked. It also confirms the `/dev/null`,
+space-form `--max-output-tokens`, input-validation, baseline and `risk --limit 0`
+repairs. On the same Windows corpus, `tutorials` manifest parsing fell from more
+than four minutes to 21.5 seconds; total root analysis was 4m52.6s.
+
+The recovery does **not** close the shared reliability defect. Independent forks
+agree that `risk` with a non-zero limit, `verify`, and Markdown `audit-report`
+can still fail silently. Results for `spring-audit`, `migrate-check`, and
+`migrate-apply` conflict between forks, so they remain open pending a single
+controlled Windows matrix of at least 30 repetitions per command. The authoritative
+record is [`AUDIT-2026-08-31-EXTERNAL-5.9.16.md`](AUDIT-2026-08-31-EXTERNAL-5.9.16.md).
+
+| ID | Severity | Status | Evidence and required closure |
+|---|---:|---|---|
+| `AUD-620-COMMAND-SURFACE` | Critical | **closed 5.9.16** | The nine commands absent from `5.9.15` are present in `ask --help`, `self-audit` reports 104 registered CLI commands, and three forks invoked them. Keep the installed-wheel command-surface gate. |
+| `AUD-620-R` | Critical maximum | **open, P0** | `risk` with `--limit != 0`, `verify`, and Markdown `audit-report` still have independently observed silent failures. `spring-audit`, `migrate-check`, and `migrate-apply` gave conflicting results. Capture target identity and run >=30 native-Windows/pipx repetitions per command, recording exit code, stdout/stderr bytes, output file and timeout. |
+| `AUD-620-TUTORIALS` | High | **partially fixed, P1** | Manifest parsing improved to 21.5s, but `analyzing repository context` now dominates and total time remains 4m52.6s. Profile that phase on the auditor platform and publish a sustained size/time envelope. |
+| `AUD-620-I` | High | **open, P1** | `cold-start --compact` remains state-dependent (3,496, 31,260, 19,781 and 15,034 bytes across rounds); `cache warm` can fail its agent view with exit 143. Define the priming sequence and investigate the agent-view failure separately. |
+| `AUD-620-WIN-PROC` | Medium | **open, platform-blocked** | Two to four `ask.exe` descendants were still observed. Establish native Windows/Git Bash process-tree evidence before shipping platform-specific teardown. |
+| `AUD-620-REVIEW-PR` | Medium | **closed/no-repro** | The historical lowercase `no_git_repo` path did not reproduce in 38 accumulated repetitions. Retain its regression test. |
+
+The release remains suitable for bounded use, but production CI-gating and
+enterprise-scale reliability claims stay blocked until `AUD-620-R`, the Windows
+process lifecycle and the remaining `tutorials` scale work close with repeatable
+native evidence.
+
 ## Current Synchronization — External Audit `AUD-619`
 
 **Re-audit of release `5.9.13`, received 2026-08-28.** The previous apparent

{sourcecode-5.9.16 → sourcecode-5.9.17}/docs/DEVELOPMENT-ROADMAP.md

@@ -1,5 +1,34 @@
 # ASK — Development Roadmap
 
+### External Audit Intake — `AUD-620` re-audit, release 5.9.16
+
+The external re-audit received 2026-08-31 confirms a major recovery from the
+defective `5.9.15` artefact. The nine missing commands are restored and invoked
+in three independent forks; Bug F, Bug Q, validation and baseline regressions are
+also independently healthy. On the Windows `tutorials` corpus, manifest parsing
+improved from more than four minutes to 21.5 seconds and total root analysis
+completed in 4m52.6s.
+
+**Engineering decision: retain the recovery, but keep the reliability gate active.**
+Two independent forks still observed silent failures in `risk` with a non-zero
+limit, `verify`, and Markdown `audit-report`. Results for `spring-audit`,
+`migrate-check`, and `migrate-apply` disagree between forks, so no success sample
+closes them. The next work is a controlled native Windows matrix, not another
+uncontrolled retry: record `pwd`, target Git revision/status, installed wheel
+commit, command, timeout, exit status and output sizes for at least 30 repetitions
+per affected command.
+
+| ID | Priority | Next action and closure boundary |
+|---|---:|---|
+| `AUD-620-R` | P0 | Instrument and reproduce the silent paths for `risk`, `verify` and Markdown `audit-report`; run the controlled 30-run native Windows matrix for all six historically affected commands. A command closes only with non-empty success evidence or structured, non-zero failure evidence in every recorded run. |
+| `AUD-620-TUTORIALS` | P1 | Apply phase profiling to `analyzing repository context`, now the dominant Windows delay. Preserve the measured manifest improvement, but do not claim seconds-scale root analysis until the whole command is repeatedly bounded. |
+| `AUD-620-I` | P1 | Specify a cold-start/cache-warm priming procedure and diagnose agent-view exit 143; output size is state-dependent until then. |
+| `AUD-620-WIN-PROC` | P1 | Add native Windows/Git Bash process-tree measurements for success, timeout and interruption. Do not ship untested Job Object changes from Darwin. |
+
+The commercial position is bounded pilots only. Do not claim production CI gating
+or enterprise-scale reliability above roughly 3,000 files while these rows remain
+open. Full evidence is in [`AUDIT-2026-08-31-EXTERNAL-5.9.16.md`](AUDIT-2026-08-31-EXTERNAL-5.9.16.md).
+
 ### External Audit Intake — `AUD-619` re-audit, release 5.9.13
 
 The follow-up received 2026-08-28 materially revises the apparent closure of

{sourcecode-5.9.16 → sourcecode-5.9.17}/docs/EXECUTIVE-ROADMAP.md

@@ -5,6 +5,19 @@
 > `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.16`, external re-audit.** The defective
+> `5.9.15` command surface has been recovered: all nine missing commands are
+> restored and independently invoked, and the prior `/dev/null`, option-parser,
+> validation and baseline regressions are again healthy. Windows `tutorials`
+> manifest parsing fell from more than four minutes to 21.5 seconds, although
+> root analysis still took 4m52.6s because the bottleneck moved to repository
+> context analysis. The reliability gate remains active: independent forks still
+> see silent failures in `risk` with a non-zero limit, `verify`, and Markdown
+> `audit-report`; results for `spring-audit`, `migrate-check`, and `migrate-apply`
+> conflict and are not closed. Keep bounded pilots only until a controlled native
+> Windows 30-run matrix closes the affected commands and process cleanup. The
+> authoritative evidence is in [`AUDIT-2026-08-31-EXTERNAL-5.9.16.md`](AUDIT-2026-08-31-EXTERNAL-5.9.16.md).
+
 > **CURRENT UPDATE — release `5.9.14`, 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

{sourcecode-5.9.16 → sourcecode-5.9.17}/docs/RELEASE-VERIFICATION.md

@@ -36,6 +36,20 @@ Run every command from a clean checkout at the intended release commit.
    The worktree must be clean. Record the commit and branch in the release
    issue; do not infer either from the version string.
 
+   For every external-audit command, also record the **target** identity before
+   running it:
+
+   ```sh
+   pwd
+   git status --short
+   git rev-parse HEAD
+   ```
+
+   Save the canonical target path, Git state, installed `ask version`, command,
+   timeout, exit code and stdout/stderr/output-file byte counts with the result.
+   A run from an empty scratch directory is not evidence for the intended
+   repository and must be discarded rather than counted as a pass.
+
 2. Build a fresh, isolated artefact.
 
    ```sh

{sourcecode-5.9.16 → sourcecode-5.9.17}/docs/USER_GUIDE.md

@@ -46,16 +46,23 @@ 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.16, `validation` enters through that shared CIR and `data-exposure` reuses one semantic
+5.9.17, `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.16, with release-artifact verification
+the two pack fixes are included in release 5.9.17, with release-artifact verification
 remaining for detached execution and pack evidence.
 
-### Reliability contracts in 5.9.16
+### Reliability contracts in 5.9.17
+
+**Failures must be visible.** `risk`, `verify`, `audit-report` and
+`migrate-check` turn unexpected analysis failures into structured
+`EXECUTION_FAILED` output and a non-zero exit, rather than an empty success.
+The release battery includes a repeatable six-command Windows matrix; it records
+exit codes and output sizes, but native Windows evidence remains required before
+closing platform-specific findings.
 
 **A deadline the root analysis honours.** `ASK_MAX_ANALYSIS_SECONDS=<seconds>` now
 stops `ask <repo>` at a measured phase boundary. A run that spends its budget
@@ -260,7 +267,7 @@ pipx install sourcecode   # isolated install, no venv needed
 
 # Verify
 ask version
-# ask 5.9.16
+# ask 5.9.17
 ```
 
 Requires Python 3.9+.

{sourcecode-5.9.16 → sourcecode-5.9.17}/pyproject.toml

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

sourcecode-5.9.17/scripts/windows_reliability_matrix.py

@@ -0,0 +1,97 @@
+"""Record a repeatable Windows answer-delivery matrix for critical commands."""
+from __future__ import annotations
+
+import argparse
+import json
+import os
+import subprocess
+import sys
+import time
+from pathlib import Path
+
+
+COMMANDS: tuple[tuple[str, tuple[str, ...], frozenset[int]], ...] = (
+    ("risk", ("risk", "--limit", "20"), frozenset({0})),
+    # A repository with no declared contracts is deliberately unverified.
+    ("verify", ("verify",), frozenset({2})),
+    ("audit-report-markdown", ("audit-report", "--format", "markdown"), frozenset({0})),
+    ("spring-audit", ("spring-audit", "--compact"), frozenset({0})),
+    ("migrate-check", ("migrate-check", "--compact"), frozenset({0})),
+    ("migrate-apply", ("migrate-apply",), frozenset({0})),
+)
+
+
+def _run(target: Path, repetitions: int, timeout: float) -> list[dict[str, object]]:
+    records: list[dict[str, object]] = []
+    for name, args, expected_codes in COMMANDS:
+        for attempt in range(1, repetitions + 1):
+            started = time.monotonic()
+            try:
+                completed = subprocess.run(
+                    [sys.executable, "-m", "sourcecode", *args, str(target)],
+                    capture_output=True,
+                    text=False,
+                    timeout=timeout,
+                    check=False,
+                )
+                record: dict[str, object] = {
+                    "command": name,
+                    "attempt": attempt,
+                    "exit_code": completed.returncode,
+                    "stdout_bytes": len(completed.stdout),
+                    "stderr_bytes": len(completed.stderr),
+                    "elapsed_seconds": round(time.monotonic() - started, 3),
+                    "timed_out": False,
+                }
+                if completed.returncode not in expected_codes:
+                    record["failure"] = f"expected exit code {sorted(expected_codes)}"
+                elif not completed.stdout:
+                    record["failure"] = "command completed without stdout evidence"
+            except subprocess.TimeoutExpired as exc:
+                record = {
+                    "command": name,
+                    "attempt": attempt,
+                    "exit_code": None,
+                    "stdout_bytes": len(exc.stdout or b""),
+                    "stderr_bytes": len(exc.stderr or b""),
+                    "elapsed_seconds": round(time.monotonic() - started, 3),
+                    "timed_out": True,
+                    "failure": f"timed out after {timeout:g}s",
+                }
+            records.append(record)
+    return records
+
+
+def main() -> int:
+    parser = argparse.ArgumentParser()
+    parser.add_argument("target", type=Path)
+    parser.add_argument("--repetitions", type=int, default=30)
+    parser.add_argument("--timeout", type=float, default=120.0)
+    parser.add_argument("--output", type=Path, required=True)
+    args = parser.parse_args()
+    if args.repetitions < 1 or args.timeout <= 0:
+        parser.error("--repetitions and --timeout must be positive")
+
+    target = args.target.resolve()
+    payload: dict[str, object] = {
+        "schema_version": "ask-windows-reliability-matrix-v1",
+        "target": str(target),
+        "cwd": os.getcwd(),
+        "python": sys.version.split()[0],
+        "repetitions": args.repetitions,
+        "timeout_seconds": args.timeout,
+        "records": _run(target, args.repetitions, args.timeout),
+    }
+    failures = [record for record in payload["records"] if "failure" in record]
+    payload["passed"] = not failures
+    args.output.parent.mkdir(parents=True, exist_ok=True)
+    args.output.write_text(json.dumps(payload, indent=2, sort_keys=True), encoding="utf-8")
+    if failures:
+        print(f"{len(failures)} reliability-matrix run(s) failed; see {args.output}", file=sys.stderr)
+        return 1
+    print(f"{len(payload['records'])} reliability-matrix runs passed; evidence: {args.output}")
+    return 0
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())

{sourcecode-5.9.16 → sourcecode-5.9.17}/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.16"
+__version__ = "5.9.17"

{sourcecode-5.9.16 → sourcecode-5.9.17}/src/sourcecode/cli.py

@@ -3015,6 +3015,26 @@ def _require_answer_delivery(command: str) -> None:
     _ANSWER_REQUIRED_BY = command
 
 
+def _analysis_failed(command: str, phase: str, exc: Exception) -> NoReturn:
+    """Fail a costly command with evidence instead of an empty successful exit.
+
+    The Windows worker failure reported in AUD-620 can surface below the
+    command-specific exception types.  These commands are consumed by CI, so an
+    unexpected analysis exception must retain a machine-readable cause and a
+    non-zero process status rather than relying on a framework traceback.
+    """
+    _emit_error_json(
+        EXECUTION_FAILED_CODE,
+        f"{command} failed while {phase}.",
+        command=command,
+        phase=phase,
+        exception_type=type(exc).__name__,
+        hint="Retry once; if it persists, retain this error envelope and the run record.",
+        expected="a completed analysis with a parseable answer",
+    )
+    raise typer.Exit(code=1) from exc
+
+
 def _fail_on_missing_required_answer(exit_code: object) -> None:
     """Turn a silent successful composed run into a typed failure (C3-122)."""
     if exit_code not in (0, None) or _OUTPUT_DELIVERED or not _ANSWER_REQUIRED_BY:
@@ -6430,20 +6450,22 @@ def main(
     # name the broader work that follows instead of leaving a completed stage on
     # screen.
     _progress.update("analyzing repository context")
+    # Graph, documentation and metrics all analyse the root-only portion of the
+    # same tree.  Pruning a large monorepo is itself a full traversal, so derive
+    # that view once instead of repeating it for every optional analyzer.
+    root_context_tree = (
+        prune_workspace_paths(
+            file_tree,
+            [workspace.path for workspace in workspace_analysis.workspaces],
+        )
+        if workspace_analysis.workspaces
+        else file_tree
+    )
     module_graphs = []
     if graph_analyzer is not None:
-        root_graph_tree = (
-            prune_workspace_paths(
-                file_tree,
-                [workspace.path for workspace in workspace_analysis.workspaces],
-            )
-            if workspace_analysis.workspaces
-            else file_tree
-        )
         module_graphs.append(
             graph_analyzer.analyze(
-                target,
-                root_graph_tree,
+                target, root_context_tree,
                 detail="full",
                 entry_points=entry_points,
             )
@@ -6451,17 +6473,8 @@ def main(
     doc_records: list[DocRecord] = []
     doc_summaries: list[DocSummary] = []
     if doc_analyzer is not None:
-        root_doc_tree = (
-            prune_workspace_paths(
-                file_tree,
-                [workspace.path for workspace in workspace_analysis.workspaces],
-            )
-            if workspace_analysis.workspaces
-            else file_tree
-        )
         root_doc_records, root_doc_summary = doc_analyzer.analyze(
-            target,
-            root_doc_tree,
+            target, root_context_tree,
             depth=docs_depth_typed,
             entry_points=[ep.path for ep in entry_points],   # LQN-03
         )
@@ -6471,21 +6484,16 @@ def main(
     file_metrics_records: list[Any] = []
     metrics_summaries = []
     if metrics_analyzer is not None:
-        root_metrics_tree = (
-            prune_workspace_paths(
-                file_tree,
-                [workspace.path for workspace in workspace_analysis.workspaces],
-            )
-            if workspace_analysis.workspaces
-            else file_tree
-        )
         root_file_metrics, root_metrics_summary = metrics_analyzer.analyze(
-            target,
-            root_metrics_tree,
+            target, root_context_tree,
         )
         file_metrics_records.extend(root_file_metrics)
         metrics_summaries.append(root_metrics_summary)
 
+    # Semantic analysis follows this loop. Keep each already filtered workspace
+    # tree so it does not walk the same files a second time when --semantics is
+    # enabled; on large monorepos that duplicated the context phase's I/O.
+    workspace_trees: dict[str, Any] = {}
     for workspace in workspace_analysis.workspaces:
         workspace_root = target / workspace.path
         if not workspace_root.exists() or not workspace_root.is_dir():
@@ -6502,6 +6510,7 @@ def main(
         _ws_topology = RepoClassifier().classify(workspace_root)
         workspace_scanner = AdaptiveScanner(workspace_root, topology=_ws_topology, base_depth=depth)
         workspace_tree = filter_sensitive_files(workspace_scanner.scan_tree(), redactor)
+        workspace_trees[workspace.path] = workspace_tree
         workspace_manifests = workspace_scanner.find_manifests()
         workspace_stacks, workspace_entry_points, _ = detector.detect(
             workspace_root,
@@ -6672,14 +6681,15 @@ def main(
             all_sem_links: list[Any] = []
             all_sem_summaries: list[Any] = []
             for ws in workspace_analysis.workspaces:
+                workspace_tree = workspace_trees.get(ws.path)
+                if workspace_tree is None:
+                    # The general pass deliberately skipped this workspace (for
+                    # example because --exclude named it), so semantics must not
+                    # reintroduce it through a fresh scan.
+                    continue
                 ws_calls, ws_syms, ws_links, ws_sum = semantic_analyzer.analyze(
                     target / ws.path,
-                    (
-                        filter_sensitive_files(
-                            AdaptiveScanner(target / ws.path, base_depth=depth).scan_tree(),
-                            redactor,
-                        )
-                    ),
+                    workspace_tree,
                     workspace=ws.path,
                 )
                 # Prefix paths to repo-root-relative (sm.file_paths uses root-relative)
@@ -13412,6 +13422,9 @@ def verify_cmd(
                 hint=f"--fail-on accepts: {' | '.join(_vr.FAIL_ON_CHOICES)}.",
             )
             raise typer.Exit(code=2 if ci else 0)
+        except Exception as exc:
+            _prog.stop()
+            _analysis_failed("verify", "verifying contracts", exc)
         _prog.stop()
 
     payload = report.to_dict()
@@ -13678,6 +13691,8 @@ def risk_cmd(
                 ci=ci,
                 allow_partial=allow_partial,
             )
+        except Exception as exc:
+            _analysis_failed("risk", phase, exc)
         finally:
             _prog.stop()
     if table:
@@ -14179,6 +14194,8 @@ def audit_report_cmd(
                 checkpoint=_run.checkpoint,
                 partial_status=lambda **cut: _run.status(_WHY_BUDGET, **cut),
             )
+        except Exception as exc:
+            _analysis_failed("audit-report", _phase, exc)
         finally:
             _prog.stop()
     output = render_markdown(data) if fmt == "markdown" else _serialize_dict(data, fmt)
@@ -15579,6 +15596,8 @@ def migrate_check_cmd(
                 timings=_mig_timings,
             )
             report.include_hygiene = include_hygiene
+        except Exception as exc:
+            _analysis_failed("migrate-check", phase, exc)
         finally:
             _prog.finish()
         if blast_radius: