tamperward 2.19.0 → 2.20.1

package/README.md

@@ -89,6 +89,9 @@ judged. In architectural terms, Tamperward separates **steering** from
 "pristine" verification restores the protected verification state from the
 trusted starting point and runs the checks again.
 
+For the complete component map, trust boundaries, data flows, and deployment
+surfaces, see [the full architecture diagram](./docs/architecture.md).
+
 > **Core invariant:** the agent may author the candidate tree, but it must not
 > choose the trusted baseline, the governing policy, the verifier, or the final
 > verdict.
@@ -110,31 +113,28 @@ trusted starting point and runs the checks again.
 ### The local enforcement envelope
 
 ```mermaid
-flowchart TB
-    subgraph R["tamperward run — outer enforcement envelope"]
-        E["Capture entry state"]
-        subgraph U["Agent-controlled lifecycle"]
-            H["In-loop steering hooks"]
-            A["Agent runtime"]
-            W["Candidate HEAD and worktree"]
-            H -.-> A
-            A --> W
-        end
-        J["Post-exit adjudication"]
-        C["Committed and worktree checks"]
-        V["Visible and pristine verification"]
-        Q["Ancestry, dependency drift, quiescence"]
-        X["Final exit verdict"]
-        E --> A
-        E --> J
-        W --> J
-        J --> C
-        J --> V
-        J --> Q
-        C --> X
-        V --> X
-        Q --> X
-    end
+graph TD
+    entry["Trusted entry snapshot"]
+    hooks["In-loop hooks and observer"]
+    agent["Agent runtime"]
+    tree["Candidate commit and worktree"]
+    adjudicate["Post-exit adjudication"]
+    checks["Diff and worktree checks"]
+    verify["Visible and pristine verification"]
+    integrity["Ancestry dependency and quiescence"]
+    verdict["Final exit verdict"]
+
+    entry --> agent
+    hooks --> agent
+    agent --> tree
+    entry --> adjudicate
+    tree --> adjudicate
+    adjudicate --> checks
+    adjudicate --> verify
+    adjudicate --> integrity
+    checks --> verdict
+    verify --> verdict
+    integrity --> verdict
 ```
 
 Before starting the agent, the envelope
@@ -577,12 +577,12 @@ option can never be reinterpreted as the agent command.
 
 ### The rules
 
-Seventeen rules are specified and sixteen ship (see the table in
+Eighteen rules are specified and seventeen ship (see the table in
 [SPEC.md](./SPEC.md)). The families: test protection (`test-deletion`,
 `test-skip`, `test-content-removal`, plus the warning-only JS/TS
 `assertion-weakening` heuristic), verification-signal protection
 (`coverage-lowering`, `snapshot-rewrite`, `snapshot-only-rewrite`), suppression
-(`ts-any-cast`, `ts-any-launder`, `lint-suppression`), pipeline protection
+(`ts-any-cast`, `ts-any-launder`, `ts-cast-growth`, `lint-suppression`), pipeline protection
 (`ci-tampering`, `hook-tampering`, `no-verify`), and the effect/outcome layers
 (`transient-protected-mutation`, `pristine-verification`, plus the `run` envelope).
 `test-skip` keeps the established regex coverage for diff-only inputs and non-JS
@@ -598,6 +598,12 @@ specificity removed, or a pure assertion removed from the same suite-qualified
 test. It measured 12/12 true-positive fires with 0/20 false positives on the
 committed detector-specific replay and remains `warn`; `guard-removal` is still
 reserved with no detector, and `ts-any-launder` is a permanent warn.
+`ts-cast-growth` (2.20.0) is the assertion budget: net growth of ordinary `as T` /
+`<T>x` / `x!` assertions in non-test source, counted on the AST net of casts the same
+change removed, reported as a warning that never blocks by default. It fires on 8.7%
+of legitimate mainline pairs across four real TypeScript libraries
+(`harness/fp-study/CAST-GROWTH-CORPUS.md`), so block is closed by corpus; the same
+pass removed every assertion from TamperWard's own `src/` (`docs/CAST-INVENTORY.md`).
 
 ## What Tamperward does not do