chore(release): prepare 0.40.0-beta.7

.github/scripts/verify-forbidden-release-artifacts.mjs

@@ -77,13 +77,13 @@ function expectFailure(action, pattern) {
 }
 
 function selfTest() {
-  const tag = 'v0.40.0-beta.6'
+  const tag = 'v0.40.0-beta.7'
   expectFailure(
     () => assertTagAbsent({ status: 128, stdout: '', stderr: 'network error' }, tag),
     /Unable to prove forbidden git tag/,
   )
   expectFailure(
-    () => assertTagAbsent({ status: 0, stdout: 'deadbeef refs\/tags\/v0.40.0-beta.6\n', stderr: '' }, tag),
+    () => assertTagAbsent({ status: 0, stdout: 'deadbeef refs\/tags\/v0.40.0-beta.7\n', stderr: '' }, tag),
     /forbids git tag/,
   )
   expectFailure(

.github/scripts/verify-packed-retrieval-parity.mjs

@@ -58,7 +58,8 @@ function assertPackageMeasurement(record, tarballPath) {
   const evaluationTooling = manifest.items?.find((item) => item.id === 'evaluation-tooling')
   const activePhase = manifest.items?.find((item) => item.id === manifest.current?.active_phase)
   const budget = activePhase?.npm_package_budget ?? evaluationTooling?.npm_package_budget
-  const receipt = activePhase?.terminal_language_corrective?.package_candidate
+  const receipt = activePhase?.terminal_language_release?.package_candidate
+    ?? activePhase?.terminal_language_corrective?.package_candidate
     ?? activePhase?.corrective_release?.package_candidate
     ?? activePhase?.corrective?.package_candidate
     ?? manifest.current

.github/workflows/release.yml

@@ -54,8 +54,8 @@ jobs:
             exit 1
           fi
 
-          if [[ "$VERSION" != "0.40.0-beta.6" ]]; then
-            echo "This release candidate is authorized only for 0.40.0-beta.6"
+          if [[ "$VERSION" != "0.40.0-beta.7" ]]; then
+            echo "This release candidate is authorized only for 0.40.0-beta.7"
             exit 1
           fi
 
@@ -164,8 +164,8 @@ jobs:
           PACKAGE_NAME="$(node -pe 'require("./package.json").name')"
           VERSION="$(node -pe 'require("./package.json").version')"
           SPEC="$PACKAGE_NAME@$VERSION"
-          EXPECTED_SHASUM="4c98dd99cd321e741cabd689f0803d99e519f389"
-          EXPECTED_INTEGRITY="sha512-o6L/BiJ1wrTWCaK537p60pGUC5i8zY0Zqz7NqD1zW4fJl/ewjF3cgysf4dbOkY4y49DkYDTG2qoUh1DGvq2Q0Q=="
+          EXPECTED_SHASUM="1aafe5952aea2f353711d5af36fa564a147312f5"
+          EXPECTED_INTEGRITY="sha512-K5CEUr2lRR1IoNCS9O74jMA7PDDgQMkdx3QM/cF+h17jyAj6Gt3Gpk8vkzKSz7SKFR44KgpnJeLkV5lXyzdgYw=="
           VERIFIED=false
 
           for attempt in 1 2 3 4 5 6; do

CHANGELOG.md

@@ -4,6 +4,12 @@ All notable changes to the TypeScript package will be documented in this file.
 
 ## [Unreleased]
 
+## [0.40.0-beta.7] - 2026-08-02
+
+### Fixed
+
+- **Natural finished-report workflow questions now retain the complete authenticated corridor.** Complete, unquoted `finished report` and `done report` terminals normalize without changing identifiers, active persistence operations, compound terminals, locator semantics, graph/index/query schemas, CLI, MCP, dependencies, or retrieval budgets. Formal installed-package and comparator qualification remains open in #631.
+
 ## [0.40.0-beta.6] - 2026-08-02
 
 ### Fixed

README.md

@@ -12,14 +12,14 @@ The result is a complete, ordered answer dossier backed by exact source evidence
 
 MCP advertises only the tools capability. It exposes no resources or prompts.
 
-[![npm next](https://img.shields.io/npm/v/%40lubab%2Fmadar/next?label=npm%20next)](https://www.npmjs.com/package/@lubab/madar/v/0.40.0-beta.6)
+[![npm next](https://img.shields.io/npm/v/%40lubab%2Fmadar/next?label=npm%20next)](https://www.npmjs.com/package/@lubab/madar/v/0.40.0-beta.7)
 [![node >=20](https://img.shields.io/badge/node-%E2%89%A520-3c873a)](https://nodejs.org/)
 [![local first](https://img.shields.io/badge/local--first-no%20cloud%20required-0f766e)](#local-by-design)
 [![license MIT](https://img.shields.io/badge/license-MIT-16a34a)](https://github.com/mohanagy/madar/blob/next/LICENSE)
 
 ## What's new
 
-See [beta.6 changes](https://github.com/mohanagy/madar/blob/next/CHANGELOG.md#0400-beta6---2026-08-02). This corrective manual-test candidate precedes #631 qualification; it makes no comparative performance or retention claim.
+See [beta.7 changes](https://github.com/mohanagy/madar/blob/next/CHANGELOG.md#0400-beta7---2026-08-02). This terminal-language corrective manual-test candidate precedes #631 qualification; it makes no comparative performance or retention claim.
 
 ## Start in three steps
 

docs/claims-and-evidence.md

@@ -22,7 +22,7 @@ Those experiments answer different questions. Neither is a universal claim about
 
 ## Beta boundary
 
-The completed Core Reset product path, semantic execution index #632, and obligation-driven retrieval #630 support manual-test prereleases for JavaScript/TypeScript repositories. Capability Validation and the earlier Native-vs-Graphify comparator were cancelled before any campaign, provider request, paid spend, or result. `0.40.0-beta.5` is immutable published manual-test history; its owner test led to the bounded correction merged in PR #637. `0.40.0-beta.6` is authorized under npm `next` so that correction can be tested before #631 qualification. Neither beta is comparative evidence, and beta.6 makes no comparative correctness, token, latency, cost, activation, retention, or external-user claim.
+The completed Core Reset product path, semantic execution index #632, and obligation-driven retrieval #630 support manual-test prereleases for JavaScript/TypeScript repositories. Capability Validation and the earlier Native-vs-Graphify comparator were cancelled before any campaign, provider request, paid spend, or result. `0.40.0-beta.5` and `0.40.0-beta.6` are immutable published manual-test history; beta.6 failed the installed finished-report and zero-fallback gate. Terminal-language corrective PR #641 then merged to protected `next` at `e84d266734344397eec9a6bcd2e1a3a5070dc3ea`, preserving reviewed tree `5ffed3bc25cb537aafd3bb905ed9df08a7143d69`. `0.40.0-beta.7` is owner-authorized under npm `next` for installed manual testing after its release gates pass, but remains unpublished, unqualified, and non-comparative until then. None of these betas proves comparative correctness, token, latency, cost, activation, retention, or external-user outcomes, and #631 remains open.
 
 The historical evaluation contracts remain development records. A future comparison or stable-release claim requires a new issue, fresh owner authorization, and new reproducible evidence.