sourcecode 4.11.0__tar.gz → 4.12.0__tar.gz

{sourcecode-4.11.0 → sourcecode-4.12.0}/CHANGELOG.md

@@ -2,6 +2,68 @@
 
 ## [Unreleased]
 
+## [4.12.0] — 2026-08-08
+
+**Field evaluation #16 — the third round on the same repository and commit, and the
+first A/B/C of three of our own releases (4.10.6 → 4.10.7 → 4.11.0, 7,0 → 7,0 →
+6,5).** The three value axes did not move: correctness 9,5, unique value 9,0,
+epistemic honesty 10, with `endpoints.json`, `servlets.json` and `validation.json`
+**byte-identical across all three builds**. What fell is engineering, and the
+sentence is about us: *"no es que haya regresiones — es que no hay nada que las
+detecte."* Nine rows close here, one commit each.
+
+**Behaviour changes to read before upgrading a pipeline:**
+
+- **`risk_score` and `risk_score_raw` are `null`, not `0.0`, when the container
+  invokes the queried component** (`@Configuration`, `@Aspect`, a registered
+  filter). The band already said `high` for these while the number said `0.0` — the
+  worst possible value for the most critical symbol in a system, from the same
+  object. `risk_score_basis` says why and names the surfaces that do measure such a
+  component. Affects `impact-chain`, `impact`, `plan` and `compare`; a consumer
+  reading the field with a `0.0` default now sees `null`.
+- **`ASK_MAX_ANALYSIS_SECONDS` actually stops a `spring-audit` rule pass.** It was
+  only ever checked between the three phases, and the last one holds ~85 % of the
+  time, so a 420 s budget produced a 2 351 s run and no `partial` anywhere. A cut
+  run now publishes `metadata.rules_not_run`, a `PARTIAL:` limitation, and
+  `_partial.phases_stopped_inside`. `metadata.rules_run` is present on every run.
+- **`migrate-check` no longer creates `<scope>/.ask/` unless you pass `--snapshot`.**
+  A read-only run left a git-ignored directory in the audited repository — invisible
+  to `git status`, visible only to `git status --ignored`.
+- **`verify` gains `--allow-unverified`** (exit 0 while the verdict stays
+  `unverified`) and publishes `unverified_reason`: `no_contracts_declared` or
+  `gate_could_not_run`. Exit codes are unchanged; the remedy is now the first reason.
+- **The parse cache retires generations.** Entries live under the producing
+  analyzer's fingerprint, and a run purges the generations that can never be read
+  again — the field measured +142,53 MB per release, three copies of one repository,
+  427,59 MB after three runs. `cache status` publishes the composition.
+
+**Also in this release:**
+
+- The rule pass reports the family it is on, counted against the total, and names
+  the two stages that have no population (`spring-audit` and `risk`). The ETA is
+  withheld there on purpose: rule families are not comparable units.
+- `risk` checkpoints — after the audit and every 25 composed rows — with the partial
+  file built by the same assembler as the answer, so it is the same document over
+  fewer rows.
+- The budget message stops quoting a class constant in the grammar of a
+  measurement. It carries this command's measured anchors and the size of the
+  repository in hand, and says plainly that no projection is offered. Anchors
+  recalibrated: `spring-audit` 408 s → 2 351 s at 3 342 files, `endpoints` 4,2 → 5,0,
+  `migrate-check --compact` 26,7 and `posture` 38,0 (both previously recorded as not
+  finishing), `risk` 3 232.
+- The MCP stack's incomplete-model warning no longer reaches stderr, and the models
+  it complains about are rebuilt rather than only muted.
+- A 772-line temp file (`cache.tmp_new`) was shipping inside the wheel; removed, and
+  the package contents are now asserted by allow-list.
+
+**Measured and not fixed, deliberately:** the block performance regression the
+evaluation reports (seven commands 2–3,4× slower on a minor) **does not reproduce
+here** — the A/B of 4.10.7 against 4.11.0 on a 2 985-file repository lands within
+1 % on six commands, with `posture --resolve-environments` byte-identical, and
+`risk` could not be A/B'd because the *4.10.7* side alone passed 61 minutes. Its
+cost is structural, not new. The numbers are in the ledger; the row waits on a
+Windows runner rather than on a guess.
+
 ## [4.11.0] — 2026-08-07
 
 **The queue behind Tier D: five ledger rows, and three batteries that were red in

{sourcecode-4.11.0 → sourcecode-4.12.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sourcecode
-Version: 4.11.0
+Version: 4.12.0
 Summary: Persistent structural context and ultra-fast repeated analysis for AI coding agents
 License-File: LICENSE
 Keywords: agents,ai,codebase,context,developer-tools,llm
@@ -42,7 +42,7 @@ Description-Content-Type: text/markdown
 
 **Context · Impact · Migration · Architecture · Review — everything from one structural model.**
 
-![Version](https://img.shields.io/badge/version-4.11.0-blue)
+![Version](https://img.shields.io/badge/version-4.12.0-blue)
 ![Python](https://img.shields.io/badge/python-3.9%2B-green)
 
 > **ASK Engine** is the product. The CLI command is **`ask`**. The legacy **`sourcecode`**
@@ -108,7 +108,7 @@ brew tap haroundominique/sourcecode && brew install sourcecode
 # pip / pipx
 pipx install sourcecode        # or: pip install sourcecode
 
-ask version                    # ask 4.11.0 — and, on a build that has aged,
+ask version                    # ask 4.12.0 — and, on a build that has aged,
                                # how many releases have probably shipped since
 ```
 

{sourcecode-4.11.0 → sourcecode-4.12.0}/README.md

@@ -4,7 +4,7 @@
 
 **Context · Impact · Migration · Architecture · Review — everything from one structural model.**
 
-![Version](https://img.shields.io/badge/version-4.11.0-blue)
+![Version](https://img.shields.io/badge/version-4.12.0-blue)
 ![Python](https://img.shields.io/badge/python-3.9%2B-green)
 
 > **ASK Engine** is the product. The CLI command is **`ask`**. The legacy **`sourcecode`**
@@ -70,7 +70,7 @@ brew tap haroundominique/sourcecode && brew install sourcecode
 # pip / pipx
 pipx install sourcecode        # or: pip install sourcecode
 
-ask version                    # ask 4.11.0 — and, on a build that has aged,
+ask version                    # ask 4.12.0 — and, on a build that has aged,
                                # how many releases have probably shipped since
 ```
 

{sourcecode-4.11.0 → sourcecode-4.12.0}/pyproject.toml

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

{sourcecode-4.11.0 → sourcecode-4.12.0}/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__ = "4.11.0"
+__version__ = "4.12.0"

{sourcecode-4.11.0 → sourcecode-4.12.0}/src/sourcecode/architectural_baseline.py

@@ -30,6 +30,7 @@ the perf baselines do.
 from __future__ import annotations
 
 import json
+import os
 import subprocess
 from datetime import datetime, timezone
 from pathlib import Path
@@ -365,21 +366,40 @@ def _baseline_filename(baseline: dict) -> str:
 #: a 14 587-entry structural inventory of the code. A self-confined
 #: `.ask/.gitignore` is the honest form: it never touches the user's own
 #: `.gitignore`, and it stops applying the moment they delete the directory.
+#: C3-74 corrected the last line. It used to read *"Delete this file to version
+#: them deliberately"*, and deleting it is the one action that would commit a
+#: baseline carrying `env.hostname_hash`, `cpu` and `cores` — an invitation to do
+#: the thing the file exists to prevent. It now states the consequence instead.
 _ASK_DIR_GITIGNORE = (
     "# Written by `ask` the first time it created this directory.\n"
     "# These are local analysis artefacts: a structural inventory of your code\n"
     "# and, if you asked for it, the machine that measured it. Nothing here\n"
-    "# belongs in a commit. Delete this file to version them deliberately.\n"
+    "# belongs in a commit.\n"
+    "#\n"
+    "# Removing this file makes everything here committable, including any\n"
+    "# recorded machine fingerprint (`--record-env`: hostname hash, CPU, cores).\n"
+    "# Version these deliberately only if you intend to publish that.\n"
     "*\n"
 )
 
 
-def protect_ask_dir(out_dir: Path) -> None:
+def protect_ask_dir(out_dir: Path, *, announce: bool = True) -> None:
     """Give a freshly created `.ask/` its own `.gitignore` (C3-68).
 
     Best-effort and never overwriting: a user who edited it decided something,
     and a tool that re-imposes its default on every run is worse than one that
     never wrote it.
+
+    **Call this where the write happens, never where the path is computed.** This
+    function *creates* the directory in order to protect it, so calling it
+    speculatively is a write — which is how `migrate-check` came to leave a
+    `.ask/.gitignore` inside a repository it had only read (C3-74).
+
+    `announce` puts one line on stderr the first time the directory is created,
+    with its path. A side effect inside somebody else's repository is exactly what
+    I-8 says must be declared, and this one hides from the check an auditor makes:
+    `git status --porcelain` is clean because the ignore file ignores itself, and
+    only `--ignored` reveals `!! <scope>/.ask/`.
     """
     try:
         ask_dir = Path(out_dir)
@@ -391,12 +411,35 @@ def protect_ask_dir(out_dir: Path) -> None:
             return
         marker = ask_dir / ".gitignore"
         if not marker.exists():
+            created = not ask_dir.exists()
             ask_dir.mkdir(parents=True, exist_ok=True)
             marker.write_text(_ASK_DIR_GITIGNORE, encoding="utf-8")
+            if announce and created:
+                _announce_ask_dir(ask_dir)
     except OSError:
         return
 
 
+def _announce_ask_dir(ask_dir: Path) -> None:
+    """One line, on stderr, naming what was created and how to move it (C3-74)."""
+    import sys
+
+    try:
+        # No flag is named here on purpose: the commands that write under `.ask/`
+        # spell the override differently (`baseline capture --dir`,
+        # `migrate-check --history-dir`), and a message that names the wrong one
+        # is the class of defect this ledger is about.
+        sys.stderr.write(
+            f"[ask] created {ask_dir}{os.sep} for this run's local artefacts — "
+            f"git-ignored by its own .gitignore, so `git status` will not show it "
+            f"(`git status --ignored` will). The command's directory option takes a "
+            f"path outside the repository if you want them elsewhere.\n"
+        )
+        sys.stderr.flush()
+    except Exception:
+        pass
+
+
 def write_baseline(baseline: dict, out_dir: Path) -> Path:
     """Write `baseline` as deterministic JSON under `out_dir`; return the file path."""
     out_dir.mkdir(parents=True, exist_ok=True)

{sourcecode-4.11.0 → sourcecode-4.12.0}/src/sourcecode/cache_model.py

@@ -75,10 +75,17 @@ class CommandCache:
     warm_seconds: "Optional[float]" = None
     #: The other measured point: this command on the field repository
     #: (3 342 Java files, Windows 11 / PowerShell 5.1 / pipx, cold), from field
-    #: evaluations #13 and #14. Seconds where a run finished; `field_blocked`
+    #: evaluations #13, #14 and #16. Seconds where a run finished; `field_blocked`
     #: where it did not — the harness promoted the process and the session died,
     #: which is a measurement of a different kind and is never written as a
     #: duration. Rows with neither were not attempted there.
+    #:
+    #: C3-72: where two evaluations of the same command at this size disagree, the
+    #: figure here is the **most recent** one, because it describes the build a
+    #: reader is about to run — and the previous figure is kept in the comment
+    #: beside it rather than dropped, since a cost that moved by 5,8× between two
+    #: releases (spring-audit, 408 s in #13 against 2 351 s in #16) is itself the
+    #: measurement C3-76 exists for.
     field_seconds: "Optional[float]" = None
     field_blocked: bool = False
 
@@ -93,19 +100,26 @@ REFERENCE_REPOSITORY = (
 REFERENCE_JAVA_FILES = 2000
 
 #: The other end of the measured range, and the reason this module publishes a
-#: *class* rather than a projected duration (C4-19). Field evaluation #13, on
+#: *class* rather than a projected duration (C4-19). Field evaluation #16, on
 #: Windows 11 / PowerShell 5.1 / pipx / Python 3.10: `spring-audit` on a
-#: 3 342-file repository ran **408 s** — 46× the 8.8 s the same command takes on
-#: the 2 000-file reference. Cost does not scale with file count in any way this
-#: product has measured, so a projected "~15 s on your repository" would be a
-#: confident falsehood of exactly the kind the ledger exists to prevent. What can
-#: be said honestly is the class, the two measured anchors, and how to run it.
+#: 3 342-file repository ran **2 351 s** — 267× the 8.8 s the same command takes
+#: on the 2 000-file reference, for a repository 1,7× the size. Cost does not
+#: scale with file count in any way this product has measured, so a projected
+#: "~15 s on your repository" would be a confident falsehood of exactly the kind
+#: the ledger exists to prevent. What can be said honestly is the class, the two
+#: measured anchors, and how to run it.
+#:
+#: C3-72 replaced evaluation #13's 408 s with #16's 2 351 s here: the same command
+#: on the same repository at the same commit, measured three releases later
+#: (2 557 s in 4.10.6, 2 398 s in 4.10.7, 2 351 s in 4.11.0). The older figure was
+#: the one a budget message quoted as "~600s" for three releases while the
+#: measurement stood four times higher.
 FIELD_ANCHOR = (
-    "field evaluation #13: spring-audit on 3 342 Java files took 408 s "
-    "(Windows, pipx, cold) against 8.8 s on the 2 000-file reference"
+    "field evaluation #16: spring-audit on 3 342 Java files took 2 351 s "
+    "(Windows, pipx, warm cache) against 8.8 s on the 2 000-file reference"
 )
 FIELD_ANCHOR_JAVA_FILES = 3342
-FIELD_ANCHOR_SECONDS = 408.0
+FIELD_ANCHOR_SECONDS = 2351.4
 
 
 #: Every layer keys on `cache.worktree_signature` — the exact tree state (C1-9).
@@ -176,14 +190,15 @@ COMMANDS: tuple[CommandCache, ...] = (
                  "Resolves the conditional bean graph on every run, over the shared CIR a warm "
                  "builds — the parse it used to repeat for itself. `--diff` compares two profile "
                  "sets over that one IR, so the second side costs the resolution only.",
-                 "10.1 s → 1.6 s", analysis_class="repo-wide", cold_seconds=10.1, warm_seconds=1.6, field_blocked=True),
+                 "10.1 s → 1.6 s", analysis_class="repo-wide", cold_seconds=10.1, warm_seconds=1.6, field_seconds=38.0),
     CommandCache("risk", ("cir", "parse"), "shared", False,
                  "Composes what the audit, impact-chain and the posture already answer, so it "
                  "pays each of their costs once over the shared CIR a warm builds — one parse "
                  "for the whole composition, and the reachability query is cached per symbol "
                  "within the run.",
                  "not measured on the battery yet — the composition is bounded by the "
-                 "`spring-audit` + `impact-chain` costs listed here, not by new analysis", analysis_class="deep"),
+                 "`spring-audit` + `impact-chain` costs listed here, not by new analysis",
+                 analysis_class="deep", field_seconds=3232.2),
     CommandCache("enrich", ("cir", "parse"), "shared", False,
                  "Runs the same composition as `risk` over the repository, then joins a SARIF "
                  "log to it. Reading the log is negligible; everything a warm helps with is the "
@@ -213,14 +228,14 @@ COMMANDS: tuple[CommandCache, ...] = (
                  "Recomputes the endpoint surface on every run, over a parse a warm has already "
                  "paid for. Until 3.7.0 the extractor parsed every file itself instead of reading "
                  "the shared parse cache, and a warm measurably bought it nothing (C3-6).",
-                 "3.3 s → 1.4 s (re-measured on 3.7.0; was 2.8 s → 2.9 s)", analysis_class="repo-wide", cold_seconds=3.3, warm_seconds=1.4, field_seconds=4.2),
+                 "3.3 s → 1.4 s (re-measured on 3.7.0; was 2.8 s → 2.9 s)", analysis_class="repo-wide", cold_seconds=3.3, warm_seconds=1.4, field_seconds=5.0),
     CommandCache("spring-audit", ("ris", "parse"), "shared", False,
                  "Recomputes every run, but over a parse a warm has already paid for.",
-                 "8.8 s → 3.7 s", analysis_class="repo-wide", cold_seconds=8.8, warm_seconds=3.7, field_seconds=408.0),
+                 "8.8 s → 3.7 s", analysis_class="repo-wide", cold_seconds=8.8, warm_seconds=3.7, field_seconds=2351.4),
     CommandCache("migrate-check", ("cir",), "none", False,
                  "Computes its own inventory and shares nothing a warm builds. Only `--blast-radius` "
                  "reuses the shared CIR.",
-                 "4.8 s → 4.8 s", analysis_class="repo-wide", cold_seconds=4.8, warm_seconds=4.8, field_blocked=True),
+                 "4.8 s → 4.8 s", analysis_class="repo-wide", cold_seconds=4.8, warm_seconds=4.8, field_seconds=26.7),
     CommandCache("impact-chain", ("cir", "parse"), "shared", False,
                  "The CIR is the expensive half — this is where a warm pays most.",
                  "9.9 s → 1.7 s", analysis_class="core", cold_seconds=9.9, warm_seconds=1.7),