sourcecode 5.9.14__tar.gz → 5.9.15__tar.gz

sourcecode-5.9.15/.github/workflows/build-windows.yml

@@ -0,0 +1,40 @@
+name: Build Windows EXE
+
+on:
+  workflow_dispatch:
+
+jobs:
+  build-windows:
+    runs-on: windows-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Setup Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install nuitka
+          pip install .
+
+      - name: Build EXE
+        run: |
+          python -m nuitka ^
+            --onefile ^
+            --standalone ^
+            --follow-imports ^
+            --assume-yes-for-downloads ^
+            --output-dir=build ^
+            run_cli.py
+        shell: cmd
+
+      - name: Upload artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: sourcecode-windows
+          path: build/**/*.exe

{sourcecode-5.9.14 → sourcecode-5.9.15}/.github/workflows/windows-regression.yml

@@ -35,7 +35,8 @@ jobs:
           python -m pytest -q -n 0 \
             tests/test_encoding_regression.py \
             tests/test_output_encoding.py \
-            tests/test_path_prefix_selection.py
+            tests/test_path_prefix_selection.py \
+            tests/test_parallel_jobs.py
 
       - name: Prove Git Bash cannot turn a route filter into a clean zero
         shell: bash

{sourcecode-5.9.14 → sourcecode-5.9.15}/CHANGELOG.md

@@ -1,444 +1,51 @@
 # Changelog
 
-## [5.9.14] — 2026-08-30
-
-*AUD-619 intake, Windows reliability follow-up and release alignment.*
-
-**Changed**
-
-- Integrated the latest `master` fixes for Windows Git Bash routing, response
-  metadata preservation and nonbinding analysis-budget disclosure.
-- Preserved the audit boundary: native Windows repetition, cache-write lifecycle,
-  review-pr normalization and process teardown remain verification work.
-
-## [5.9.13] — 2026-08-28
-
-*AUD-618 remediation and release-alignment patch.*
-
-**Fixed**
-
-- Windows now selects the existing sequential parse path instead of creating a
-  `ProcessPoolExecutor` whose spawned workers can fail to duplicate IPC handles.
-  The fallback preserves the same IR and prevents the observed silent/hanging
-  worker-start path.
-- A missing bare token now explains when ASK interpreted it as an implicit
-  repository path, while close command spellings retain nearest-command hints.
-- Spanish user documentation no longer states a false fixed token size for
-  compact context.
+## [5.9.15] — 2026-08-31
 
-**Verification boundary**
+*Release metadata aligned for the PyPI publication.*
 
-- TeaVM validations cover risk delivery, migration planning and non-mutation.
-  Native Windows/pipx re-audit remains required for the worker, scale and
-  process-lifetime findings; this release does not claim that external evidence.
+## [5.8.24] — 2026-08-31
 
-## [5.9.12] — 2026-08-28
+*The Windows external re-audit correction queue is closed: every actionable
+5.9.13 → 5.9.14 finding now has a bounded implementation, native Windows
+evidence and a regression authority, without duplicating existing defect
+classes.*
 
-*Release-alignment patch release after the `AUD-617` regression battery.*
-
-**Fixed and verified**
-
-- Core answer-producing commands now fail closed with structured evidence instead
-  of silently returning success when composition fails (`AUD-617-R`).
-- Root option preprocessing preserves the value of `--max-output-tokens` in both
-  space-separated and equals forms (`AUD-617-Q`).
-- `migrate-apply` plan-only output is covered as a non-silent, non-mutating path
-  (`AUD-617-MIGRATE-APPLY`).
-
-The native Windows scale and process-cleanup findings remain open because they
-require evidence from that platform. The commercial gate and conservative scale
-positioning are unchanged.
-
-## [5.9.11] — 2026-08-28
-
-*`AUD-616` remediation: seven of nine rows closed, two partially, one carried forward.*
-
-**Fixed**
-
-- A stack's confidence now answers to the source in the tree. A repository of 151
-  `.kt` files with zero `.java` files and one `pom.xml` in a subdirectory published
-  `stack: java`, `confidence: high`, `primary: true` and headlined itself a Java
-  library. `JvmExtDetector` admits on source population as well as manifest
-  filename, so a Kotlin repository built with the Groovy DSL is no longer
-  invisible; and `TypeClassifier._enrich_stack`, which is the real authority for
-  `confidence`, now caps a stack with no source files of its own at `low` and
-  floors the tree's largest source population at `medium` against a competing
-  manifest-backed claim. (`AUD-616-KOTLIN`)
-- A JVM repository with sources and no application-defining framework classifies as
-  `library` rather than `unknown`, whether or not it is multi-module. Module count
-  describes a build layout, not whether a repository is a library. Measured over
-  thirteen JVM repositories: three change and all three are libraries, ten are
-  unchanged. (`AUD-616-JUNIT4-SELF`)
-- The output-ceiling refusal offers `--output FILE` before any `--format`
-  substitution, and each substitution states that it re-runs the command and that
-  its cost on this repository is unmeasured. The first suggestion was previously
-  the one path held open as an availability defect. (`AUD-616-O`)
-- The cache GC no longer evicts the entry the calling run has just written. A core
-  larger than the whole store budget was written and deleted inside one process on
-  every run, so that repository could never be served from cache and nothing said
-  why. `cache status` publishes `size_budget_mb`, `largest_core_bytes` and an
-  `over_budget_reason`. (`AUD-616-P`)
-- The delayed liveness warning names the phase, the stage and its counts, how long
-  the run has been in that phase, and whether the phase changed since the previous
-  warning — the signal that separates a blocked run from a slow one. The in-phase
-  clock is the phase's own, not the run's. (`AUD-616-L`)
-
-**Added**
-
-- The root analysis is a phase runner: `ASK_MAX_ANALYSIS_SECONDS` stops it at a
-  measured seam and returns a structured `partial-answer-v1` result naming the
-  phases completed and pending, the elapsed time and the budget's provenance,
-  instead of nothing at all. It declares `--ci` and `--allow-partial` from the same
-  factories every other phase runner uses, and a cut gated run exits 75.
-  (`AUD-616-TUTORIALS`)
-
-**Performance**
-
-- Two repeated walks of the same file tree removed from the detection phase:
-  `manifest_cache._key()` ran fourteen recursive globs per call and was called by
-  both `load()` and `save()` for each module, and the classifier flattened the tree
-  seven times per `enrich`. Measured cold on a 24,073-file monorepo: detection
-  30.3 s → 9.2 s, total 54.9 s → 32.5 s (**×1.69**), payload byte-identical.
-
-**Known limits**
-
-- The two availability items stay open and are not closed on measurements taken
-  here. Neither reproduces on the engineering platform — root compact completes in
-  54.9 s with output, and `audit-report --format markdown` ran 2/2 clean — and both
-  were reported against a different build and platform. Independent re-measurement
-  there, plus a published repository-size envelope, is the remaining work.
-  (`AUD-616-TUTORIALS`, `AUD-616-L`)
-- Windows process-tree cleanup is carried forward untouched: it cannot be
-  reproduced or refuted from the engineering platform. (`AUD-616-WIN-PROC`)
-
-## [5.9.10] — 2026-08-27
-
-*Release-alignment patch release.*
-
-**Release**
-
-- Synchronizes package metadata, CLI runtime, README and user-guide version surfaces at `5.9.10`.
-- Carries forward the `5.9.9` documentation and availability guidance.
-- Keeps the `AUD-615` reliability limits explicit pending their independent closure.
-
-## [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.*
-
-**Fixed**
-
-- Makes explicit cache warming durable across processes.
-- Reconciles Spring presence detection for foreign member annotations.
-- Removes split Markdown badge fragments from README-derived summaries.
-- Makes empty baseline history an explicit `no_history` result.
-- Explains the intentional CLI/MCP population difference in `self-audit`.
-
-**Validation**
-
-- Added dedicated regression coverage using `/Users/user/Documents/workspace/testing/teavm`.
-- Updated README, English and Spanish guides, roadmap, ledger and CLI version output.
-
-## [5.9.4] — 2026-08-27
-
-*External-audit reliability and contract-alignment release.*
-
-**Fixed**
-
-- Rejects missing consumer repositories, malformed CVE feeds and unresolved
-  `pack gate --since` refs as structured input errors.
-- Rejects unknown profiles in `posture --diff` when the repository declares a
-  profile population, while preserving annotation-only profile fixtures.
-- Prevents architectural baseline captures from overwriting the snapshot for
-  the same commit.
-- Makes `endpoints --compact` disclose inline that its empty row list is an
-  intentional omission, and makes unresolved `impact`/`impact-chain` runs exit
-  non-zero even when no Java files are present.
-
-**Documentation and validation**
-
-- Updated README, English and Spanish user guides, roadmap status and CLI help.
-- Dedicated regression tests pass against repositories under
-  `Documents/workspace/testing`.
-
-## [5.9.3] — 2026-08-27
-
-*Workspace entitlement correctness patch release.*
-
-**Fixed**
-
-- `auth workspace` collapses overlapping parent/child repository paths and
-  publishes `overlapping_paths`, preventing physical Java files from being
-  counted twice.
-- `auth workspace` rejects nonexistent or non-directory paths through the
-  standard structured `INVALID_INPUT` / `missing` contract instead of treating
-  them as empty repositories.
-
-**Validation**
-
-- Added regression coverage for duplicate, overlapping, invalid and mixed
-  workspace inputs.
-- Rechecked the contract against representative repositories under
-  `Documents/workspace/testing`.
-
-## [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
-from the `5.9.0` audit are shipped and documented; command contracts now
-disclose their limits and failure boundaries.*
-
-**Fixed**
-
-- `cve` publishes that its dependency inventory comes from static manifests and
-  supported lockfiles, without implying Maven or Gradle graph resolution.
-- `pr-risk --since` reports unreadable base refs as structured execution errors
-  instead of misleading `non_coverage`.
-- `posture --diff --limit` bounds `permit_all` and effective-access evidence
-  maps while preserving unrelated `evidence` payloads.
-- Seven new command helps state their command-level analysis and memory budget
-  applicability.
-
-**Documentation and validation**
-
-- README, roadmaps and defect ledger identify `5.9.1` as the current release;
-  the `5.9.0` audit remains historical evidence.
-- Focused regression batteries pass for all four corrections. A representative
-  stress smoke test passed on seven repositories under
-  `Documents/workspace/testing` with isolated caches and clean stderr.
-
-## [5.9.0] — 2026-08-26
-
-*The `AUD-607` external round, closed: three defects fixed and the whole feature
-intake built, one commit per row. Seven new commands (`cve`, `intent`,
-`remediate`, `pr-risk`, `drift`, `watch`, `self-audit`) and two extended ones
-(`baseline --kind findings`, `export --c4 --render`) make this the largest
-addition to the command surface since 5.0, so the minor version moves.*
-
-**Fixed**
-
-- `chunk-file` emitted chunk content that did not match its own declared
-  `start_line`/`end_line`: the boundary path serialised the untruncated buffer
-  while declaring a truncated end line, so a chunk ran past its own range and
-  those lines repeated at the head of the next one. A second, separate defect
-  made the annotation buffer's clearing guard unreachable, so a field's
-  `@Autowired` was carried onto the following method while the field's own
-  declaration dropped out of that chunk. The reported "deliberate overlap" is
-  refuted; the declared range is now exact and asserted against file content.
-- `explain` answered *"No stereotype detected"* under **Purpose** while listing
-  that same class's routes under **REST Endpoints**. Fixed by reading the
-  endpoint evidence the answer already computed — not by adding JAX-RS to a
-  Spring annotation list, which is the branching this project does not do.
-- `--files -` claimed *"stdin is a terminal"* for a Git Bash/MSYS redirect it
-  cannot verify. The message now names the outcome and states both routes into
-  it (the C3-106 rule, already applied to `_confirm`).
-
-**Added**
-
-- `ask cve --feed <osv>` — dependency advisories gated on whether a route can
-  **reach** the vulnerable package. Takes no network at analysis time; an
-  unreadable feed is a refusal, never a clean scan; nothing answers *"not
-  reachable"*, and an unresolvable Maven version is `unknown`, never
-  `not_affected`. Schema `cve-reachability-v1`, published as a document.
-- `ask intent "<question>"` — a plain-language question resolved to one of
-  `retrieve`'s typed queries. A scored lexical match against a declared
-  vocabulary: no model, no generation. Ambiguous or unanchored questions are
-  refused with the closest intents named.
-- `ask remediate` — finding → recipe → apply in a dedicated worktree →
-  `verify-edit`. Dry by default; an apply that could not be verified reports
-  `unverified`, never `applied`. Schema `remediation-plan-v1`.
-- `ask pr-risk` — one verdict for one diff, distinct from `pack gate`'s verdict
-  about the repository. `UNKNOWN` outranks `PASS` and fails every gate. Schema
-  `pr-risk-v1`.
-- `ask drift` — what changed in the effective access, across time or across two
-  profile sets, with one arithmetic for both axes. Schema `access-drift-v1`.
-- `ask watch` — one answer per save against a warm index; `--once` is the
-  pre-commit shape. Schema `watch-event-v1`.
-- `ask self-audit` — whether the **installed** build's registries agree with each
-  other, and an explicit statement of what it cannot check. Schema
-  `self-audit-v1`.
-- `ask baseline capture|diff|trend --kind findings` — the defect population as a
-  persisted series, so "how long has this been open?" has an answer. Schema
-  `findings-baseline-v1`.
-- `ask export --c4 --render mermaid|svg` — draws the C4 model instead of only
-  emitting it, with the node cap written on the canvas.
-
-**Note.** Building the features surfaced three defects no audit round had
-reported: the C4 renderer's first version drew report metadata (`summary`,
-`coverage_note`) as system architecture; the watch loop stat-ed
-repository-relative paths against the process CWD and so reported "nothing
-changed" on every tick; and `self-audit` found its own schema identifier
-unregistered on its first run. Each is now held by an assertion.
-
-## [5.8.32] — 2026-08-26
-
-*MCP and documentation alignment release. MCP assessment packs now support
-validated selective component execution through `only`, with omitted coverage
-and a reproducible CLI command recorded in the projection. MCP pull-request
-gates, pack guidance and the public roadmap are synchronized with the current
-release state.*
-
-## [5.8.31] — 2026-08-26
-
-*Windows portability and release-evidence remediation. Cache and licensing test
-isolation now honours explicit `HOME` overrides, warm workers use the active
-interpreter, migration and identity paths remain portable, and the Windows CI
-battery no longer disables the rendered help contract. Unix-only permission probes
-are skipped on Windows. Local full-suite verification is green; native Windows
-release-artifact verification remains the CI acceptance step.*
-
-## [5.8.30] — 2026-08-26
-
-*Pack audit remediation release. Unresolved test-only Java files no longer broaden
-`pack gate` endpoint uncertainty, and foreground `pack assessment` now reports
-component progress through the stderr-only heartbeat contract. Documentation and
-release evidence are synchronized with the AUD-605 fixes.*
-
-## [5.8.29] — 2026-08-26
-
-*Release synchronization for the external `5.8.28` audit. The posture diff now
-honours `--limit` for nested endpoint-access rows, help output distinguishes the
-historical timing anchor from the provisional cold observation, and the controlled
-performance follow-up is recorded without an unsupported parser change. Roadmaps,
-the defect ledger and the audit intake are aligned with the release state.*
-
-## [5.8.28] — 2026-08-26
-
-*Audit remediation release. Detached workers now use an executable package entry
-point; DEAD-001 ignores explanatory annotation prose; posture diffs honour the
-compact size contract; and non-interactive selftest runs publish nested-scope
-warnings. Help and audit documentation are synchronized with the remaining
-performance investigation.*
-
-## [5.8.27] — 2026-08-26
-
-*Audit remediation release. Detached workers avoid the Windows console shim,
-security scanning excludes platform and deprecated encoder definitions, and
-non-applicable Boot 3 readiness is represented consistently. `selftest` warns
-when an implicit current-directory run contains nested Git repositories. The
-release also synchronizes the user-facing documentation with these guarantees.*
-
-## [5.8.26] — 2026-08-23
-
-*Patch release for the expanded-corpus audit. It preserves endpoint declarations
-whose FQN is reused by separate modules, pairs MyBatis XML against the analysed
-tree rather than a compact display subset, and reports the runtime source commit
-for editable installs. Route inheritance and JAX-RS locator composition were
-revalidated after the module-identity change.*
-
-## [5.8.25] — 2026-08-23
-
-*Version and documentation synchronization release. The audited `5.8.24` tree is
-unchanged; the current package identity and user-facing documentation now report
-`5.8.25`. Verification: `12,700 passed, 40 skipped` with writable cache locations.*
-
-## [5.8.24] — 2026-08-22
-
-*The thirteenth audit-pass queue is closed entire: all six rows as separate
-commits, the regression first, with the full suite green at 12 329 tests. Three
-of the reported mechanisms are wider than reported and are corrected against
-measurement; one defect was found by the battery rather than by either.*
-
-### Fixed — the regression the pass led with
-
-- **`cache warm` warms every root view (`AUD-600-R01`)** — the warm built the
-  compact view only, so the first `--agent` call after an explicit warm paid a
-  full analysis: measured on `mall` (524 Java files) `--agent` 7.59 s → 0.34 s
-  (×22) and the raw contract view 3.20 s → 0.33 s (×9.7), against `--compact`
-  flat at 0.34 s. The field measured ×49.2 at ~3 000 files. Each view turns a
-  different set of analysers on and therefore has its own L1 core;
-  `cache_model.ROOT_VIEWS` is now the one authority the warm iterates and
-  `cache model` publishes a row per view. `--views` warms a subset, and a view
-  left cold is named rather than discovered by its first call.
-
-### Fixed — the new pack surface
-
-- **The gate composes `verify-edit` (`AUD-600-B01`)** — a pack named *Change
-  Safety Gate* did not compose the change-safety command, so a working tree
-  that had just gained `GET /internal/dump-config` returning `System.getenv(key)`
-  answered `NO_CHANGES` / exit 0. It now answers `UNVERIFIED` / exit 2 with the
-  route and its `access_policy`. The general half is the rule: every pack
-  publishes a `non_coverage` block, in its payload and in `pack list`, and the
-  battery asserts it over the axis and rule catalogues.
-- **`--compact` bounds the assessment pack (`AUD-600-B02`)** — the flag was
-  forwarded to the children and nothing else. It now substitutes each
-  component's own decision summary for its body: `mall` 608 K → 42 K estimated
-  tokens, `thingsboard` 8.5 K, both under the ceiling. A refusal may not deny a
-  variant the command declares, so `--format markdown` is derived as the
-  bounded rendering it is.
-- **The report keeps the figures the pack carries (`AUD-600-B03`)** — three
-  cells read `unknown` while the figure sat in a component payload the same
-  pack had written. One catalogue, `MARKDOWN_FIGURES`, read with the same
-  reader the bounded projection uses; every remaining `unknown` names what it
-  looked for.
-- **A write refusal is decided from `argv` (`AUD-600-D01`)** — `--output-dir`
-  inside a read-only tree cost 47.9 s before refusing. The destination is now
-  decided before any component runs and the run is served without its artefacts,
-  the shape `verify --init --no-write` established. Nothing is created inside
-  the analysed tree and every refusal is still announced with its path and type.
-
-### Added
+### Fixed
 
-- **`ask schema packs-v1` (`AUD-600-D02`)** — what each pack composes, what it
-  does not, its verdict vocabulary, its exit codes and the aggregation rule that
-  produced the verdict, generated from the pack declarations. The rule was
-  inferable from one run and published nowhere.
-- **Per-component timing in the pack manifest** — `duration_ms` per component
-  and a `timing` rollup naming the slowest one, so a 47 s gate can be attributed
-  from outside. A clock is never an answer: `timing` is excluded from
-  `content_id`, or two runs of an unchanged tree would disagree.
-- **The fourth exit code for packs** — when every unverified component was cut
-  short by its budget the pack leaves with `75` and names them in
-  `components_cut_short`. A mixed run keeps the stronger `2` and the verdict
-  word never moves.
+- **Windows worker reliability (`AUD-619-R`, `AUD-619-WIN-PROC`)** — worker
+  startup, collection, failure fallback and teardown are bounded. A failed pool
+  cannot report an empty success or leave ASK children behind.
+- **Cache correctness and scale (`AUD-619-CACHE-WRITE`, `AUD-620-CACHE-RECENCY`,
+  `AUD-620-MANIFEST-IDENTITY`)** — large projections are bounded, eviction no
+  longer depends on tied NTFS timestamps, all consumed manifests and lockfiles
+  participate in cache identity, and concurrent writers use unique temporary
+  files.
+- **Compact reproducibility (`AUD-619-I`)** — cold bounded output is independent
+  of supported cache-priming order and carries its own cut and identity
+  disclosures.
+- **CLI and Windows path compatibility (`AUD-620-CLI-RUNTIME`,
+  `AUD-620-CACHE-WARM`, `AUD-620-JOBS-ARGV`, `AUD-620-SARIF-URI`)** — Typer 0.27
+  runtime shapes use one compatibility adapter, cache warm re-enters through
+  Python, `--jobs` preserves the repository argument, and Windows file URIs
+  resolve inside their repository.
+- **Result ownership (`AUD-620-PACK-CLEANUP`)** — a sharing violation during
+  temporary pack cleanup can no longer replace an already computed result.
+- **Independent command contracts (`AUD-619-AR-FROM-RISK`,
+  `AUD-619-MIGRATE-APPLY`)** — structured risk input and non-empty migration
+  plans remain explicitly covered after the worker changes.
+
+### Validation
+
+- Native Windows matrices exercised 20 selected repositories from the
+  24-repository JVM corpus; `audit-report --from-risk` and `migrate-apply`
+  completed 20/20, and twenty repeated agent runs left zero residual ASK child
+  processes.
+- The release battery collects 12,271 tests. The complete serial and configured
+  `-n auto` runs both completed with 0 failures; the final parallel run emitted
+  0 warnings. The nine pytest-10 compatibility warnings discovered by the
+  serial run were closed and their 120 affected cases pass with those warnings
+  treated as errors.
 
 ## [5.8.23] — 2026-08-22
 
@@ -835,7 +442,7 @@ the evidence for outstanding field reproduction and performance work.*
 
 *Performance-mitigation and release-hygiene update. The external cross-version
 performance regression remains open until it is reproduced under its controlled
-`reference-service` protocol; this release does not present local warm-cache results
+`saint-server` protocol; this release does not present local warm-cache results
 as that closure.*
 
 ### Changed
@@ -1591,7 +1198,7 @@ said to name no smaller variant when one exists.*
 - An analysed population does not move between releases without a field that
   explains the move (B17-sv / AS-16). 5.8.0's E-35 fix removed symbols that were
   never declarations — `return unknownHelper("x");` parsed as one — and
-  `metadata.symbols_analyzed` fell with them (`reference-service` 43 642 → 43 003,
+  `metadata.symbols_analyzed` fell with them (`saint-server` 43 642 → 43 003,
   −1,46 %, after five constant versions). The correction was right and the
   release said nothing, so the next field re-audit read it as lost coverage and
   filed it P0. Every command that publishes `symbols_analyzed` now publishes
@@ -1974,7 +1581,7 @@ closed here, two refuted with the measurement that contradicts them.*
 
 ## [5.5.5] — 2026-08-13
 
-**reference corpus performance-audit corrections and read-only hygiene verification.**
+**MSAS performance-audit corrections and read-only hygiene verification.**
 
 ### Fixed
 - `spring-audit` now preserves full default JSON when it fits the stdout
@@ -1993,7 +1600,7 @@ closed here, two refuted with the measurement that contradicts them.*
   explicitly where no semantic model is available.
 
 ### Documentation
-- Recorded the reference corpus findings, their reproductions, the resolved commits, and
+- Recorded the MSAS findings, their reproductions, the resolved commits, and
   the remaining bounded-output, schema, timeline, benchmark, and Git-basis
   work in the roadmap.
 
@@ -2743,7 +2350,7 @@ product does not model — Keycloak, 8 204 Java files, Quarkus + JAX-RS,
 `spring_detected: false` in all six audited modules, 47 invocations under
 `ASK_READONLY=1` — and it split the product cleanly in two: every structural axis
 worked alone, and the axes that guess produced 86 `high` findings with zero true
-positives. Eval #21 is the seventh measurement of `reference-service`, and its
+positives. Eval #21 is the seventh measurement of `saint-server`, and its
 contribution is a partition rather than a defect.
 
 **Fixed in this release:**
@@ -3873,7 +3480,7 @@ them.
 ### Documentation
 
 - README and user guide examples now report `4.8.0`.
-- The development roadmap records the reference-service field-evaluation fixes and
+- The development roadmap records the saint-server field-evaluation fixes and
   future feature queue.
 
 ## [4.7.0] — 2026-08-04
@@ -4619,7 +4226,7 @@ verification against 4.0.1.
 
 - **SEC-007 — a credential stored in a deployment descriptor** (CL-10). The audit
   found `monitor:{SHA-256}dc20b820…` in
-  `src/main/options/{DPA,sample,tenant-dev}/WEB-INF/web.xml`: unsalted, the same hash in all
+  `src/main/options/{DPA,M3,M3DEV}/WEB-INF/web.xml`: unsalted, the same hash in all
   three per-environment overlays, and found by hand because *"los overlays
   `src/main/options/**` son punto ciego"*. The gap was admission surface, not
   detection — those descriptors are files `environment_resolution`,
@@ -6043,13 +5650,13 @@ and `registries` in both `ask schema` and `ask version`) are additive.
 
 - **A class was reported as conditional on a profile *and* on its negation, contradicting
   `ask posture` in the same run.** Found in the third field evaluation (3.2.0): a
-  configuration class declaring `@Profile("!sample")` — active exactly when `sample` is **absent** —
-  appeared in `signals.spring_profiles.profile_conditional_beans` under `sample` as well. Read as
+  configuration class declaring `@Profile("!m3")` — active exactly when `m3` is **absent** —
+  appeared in `signals.spring_profiles.profile_conditional_beans` under `m3` as well. Read as
   a security fact, it inverts the answer.
   - Root cause, reproduced: the source scan attributed every `@Profile` to *the next type
     declaration ahead of it*, falling back to the file name when there was none. A
-  `@Profile("sample")` on a `@Bean` **method** inside that class was therefore attributed to the
-    class itself, next to the class-level `@Profile("!sample")`.
+  `@Profile("m3")` on a `@Bean` **method** inside that class was therefore attributed to the
+    class itself, next to the class-level `@Profile("!m3")`.
   - Attribution is now the declaration the annotation actually annotates: only annotations
     and modifiers may stand between it and a type declaration; a member-level annotation is
     reported as `Type#member`, and an annotation whose target cannot be read is **not
@@ -9006,7 +8613,7 @@ Dependency audit (`pip-audit`): no known vulnerabilities in runtime dependencies
 
 ### Added
 - **`export --c4` now emits `components.module_roots` — architectural module
-  enumeration + DDD/legacy classification.** Field test (reference-service C4 doc pass)
+  enumeration + DDD/legacy classification.** Field test (saint-server C4 doc pass)
   surfaced that the C4 export keyed modules by *leaf source directory*
   (`dirname(source_file)`), so a DDD module split across
   `domain/` / `application/` / `infrastructure/` subdirs fragmented into several
@@ -9366,13 +8973,3 @@ implementors.
 - 3 `--slim` tests verifying the option is absent from help and CLI surface.
 - 6 `angular_version` parsing tests covering `dependencies`, `devDependencies`,
   `peerDependencies`, `null` JSON values, and version prefix stripping.
-## [5.9.7] — 2026-08-27
-
-### Fixed
-- Exposed functional root options in `ask --help` and aligned help discoverability tests.
-- Unified empty `--files -` handling for `pr-impact` and `pr-risk`.
-- Normalized Git reference failures to `GIT_REF_NOT_FOUND`.
-- Corrected the `cold-start --compact` size contract and endpoint omission disclosure.
-- Added delayed liveness warnings for long non-interactive runs.
-- Improved natural-language routing for unsecured endpoint questions.
-- Kept unresolved impact symbols explicitly unscored.

{sourcecode-5.9.14 → sourcecode-5.9.15}/CLAUDE.md

@@ -75,16 +75,8 @@ the same command runs on a 3 300-file monolith.
   not 246 s. `-o addopts=""` is no longer the way to see the count; it now
   *removes* the parallelism. Override the worker count with `-n <k>`, not by
   clearing `addopts`.
-- **Run only the tests your change touches. The full suite runs once, at the end
-  of a session of modifications — not per change, not per commit.** Name the
-  files that cover what you edited: ~2 s each. A whole-suite run is 70 s plus the
-  wait, and repeating it after every step is the single most expensive habit
-  available here — a documentation-only edit never needs one at all (the doc
-  batteries `test_ledger_*`, `test_bundled_docs`, `test_integration_docs` are the
-  whole obligation). `-k <pattern>` is not the shortcut — it deselects but still
-  collects all ~9 000 tests, so it floors at 16 s. After a red run, `--lf`
-  re-runs only what failed.
-- **A red the suite already had is not yours to discover twice.** Before treating
-  a failure as a regression, check it against `HEAD` (`git stash -u`, run the
-  same file, pop). Record pre-existing reds once and move on.
+- **Run one file while you work, the suite before you commit.** Naming the file
+  is ~2 s; the full run is 70 s. `-k <pattern>` is not the shortcut — it
+  deselects but still collects all ~9 000 tests, so it floors at 16 s. After a
+  red run, `--lf` re-runs only what failed.
 - The entry point for local runs is `run_cli.py`, not `python -m sourcecode.cli`.