Release TestForge 1.1.7 completion governor

ARCHIVE-CUSTODY.md

@@ -1,20 +1,24 @@
 # TestForge archive custody
 
-TestForge v1.1.6 is one two-skill Augment with several distinct distribution objects. Keep their identity and evidence states separate: source presence is not installation, a valid archive is not discovery, discovery is not invocation, and none of those states proves healthy behavior or directory publication.
+TestForge v1.1.7 is one two-skill Augment with several distinct distribution objects. Keep their identity and evidence states separate: source presence is not installation, a valid archive is not discovery, discovery is not invocation, and none of those states proves healthy behavior or directory publication.
 
-## Current v1.1.6 objects
+## Current v1.1.7 candidate objects
 
 | Object | Canonical location | Observed state and use |
 |---|---|---|
-| Maintained package | `testforge/` | Current two-skill source, tools, schemas, examples, evals, adapters, and customer documentation |
+| Maintained package | `testforge/` | Current v1.1.7 two-skill source, tools, schemas, examples, evals, adapters, and customer documentation |
 | Codex marketplace plugin | `plugins/testforge/` plus `.agents/plugins/marketplace.json` | Repository-native plugin source for `testforge@cd-testforge`; static structure is repository-tested |
-| Claude operator upload | `claude-ai/software-verification-v1.1.6.zip` | Current one-skill upload archive; SHA-256 `3485f982d9d7f770b9077bc9da122498ff5ce135ae60e07e7aa8fa8209d5a52f` |
-| Claude reviewer upload | `claude-ai/verification-reviewer-v1.1.6.zip` | Current one-skill upload archive; SHA-256 `c882eacec514e23647e1e298b9919a89e3b85ded06649041cf924c91994308ba` |
-| Frozen v1.1.6 customer kit | `releases/v1.1.6/TestForge-v1.1.6.zip` | Canonical published release object retained unchanged; SHA-256 `4dd052672923192f59ec2866eb2fedef697ca1f98f00a99341c3d8fe062b0594` |
-| Frozen v1.1.6 receipts | `releases/v1.1.6/` | Static package, source-parity, and portable archive evidence; no fresh-host activation or customer-outcome claim |
-| Source release | Git tag `v1.1.6` and [GitHub release](https://github.com/Stunspot/TestForge/releases/tag/v1.1.6) | Published 2026-08-12; versioned public source and release boundary |
+| Claude operator upload | `claude-ai/software-verification-v1.1.7.zip` | Current one-skill upload candidate; SHA-256 `41f2d92cf4cf44c91fb6c204364989772ed0c1d0a376c2dfd982d97117da6714` |
+| Claude reviewer upload | `claude-ai/verification-reviewer-v1.1.7.zip` | Current one-skill upload candidate; SHA-256 `c882eacec514e23647e1e298b9919a89e3b85ded06649041cf924c91994308ba` |
+| Local v1.1.7 customer kit | `releases/v1.1.7/TestForge-v1.1.7.zip` | Deterministic local candidate; the adjacent `.sha256` file is canonical because this document is itself packaged inside the archive |
+| Local v1.1.7 receipts | `releases/v1.1.7/` | Static package, source-parity, and portable archive evidence; no fresh-host activation, customer-outcome, tag, GitHub release, or publication claim |
+| Source state | Local `main` commits after published v1.1.6 | Release source prepared locally; not tagged, pushed, or published by this maintenance pass |
 
-The current `claude-ai/` archives and the frozen archives inside `releases/v1.1.6/claude/` are separate deterministic builds and are not byte-identical. Use the current `claude-ai/` objects for the repository installation guide. Use the frozen release directory to inspect the exact evidence and bytes retained for the v1.1.6 release event.
+The current `claude-ai/` archives and the archives inside `releases/v1.1.7/claude/` are separate deterministic builds and are not expected to be byte-identical. Use the current `claude-ai/` objects for repository installation. Use the candidate release directory to inspect the exact evidence and bytes retained for this local release candidate.
+
+## Published v1.1.6 objects
+
+The prior published release remains immutable: Git tag and GitHub release `v1.1.6`, published 2026-08-12. Its frozen customer kit is `releases/v1.1.6/TestForge-v1.1.6.zip`, SHA-256 `4dd052672923192f59ec2866eb2fedef697ca1f98f00a99341c3d8fe062b0594`. Its retained receipts establish static package and byte-parity evidence only.
 
 ## OpenAI directory packet
 
@@ -25,13 +29,13 @@ The latest retained skills-only portal payload is still v1.1.4:
 - SHA-256: `9aecec78e407e6f368d0a5c613facbc4252a3f3ef545ba6686e74cf7f2404a46`;
 - state: built and repository-tested, not claimed uploaded, approved, published, or discoverable.
 
-There is no retained v1.1.6 portal archive or custody object. The repository-native v1.1.6 plugin remains the current Codex installation surface; the v1.1.4 portal packet is a separately governed historical submission candidate.
+There is no retained v1.1.7 portal archive or custody object. The repository-native v1.1.7 plugin is the current local installation candidate; the v1.1.4 portal packet is a separately governed historical submission candidate.
 
 ## Maintenance rules
 
 - Rebuild current derivatives from maintained source; never edit ZIP members in place.
-- Do not alter `releases/` merely to make present documentation agree with a historical release.
-- Record archive name, byte size, SHA-256, member inventory, source revision, and claim boundary for each new object.
+- Do not alter historical release directories merely to make present documentation agree with a later release.
+- Record archive name, byte size, SHA-256, member inventory, source revision, and claim boundary in the release receipts for each new object.
 - Verify extraction topology and package-relative dependencies before publication.
 - After publication, download the public asset and compare it with the governed local object.
 - Treat upload, automated scan, review submission, approval, publication, installation, discovery, invocation, and health as separate observed states.

BUILD-NOTE.md

@@ -1,6 +1,6 @@
 # Historical TestForge v1.1.0 maintenance build note
 
-> Historical record: this file describes the v1.1.0 maintenance event. It is not the current installation, archive-custody, or validation authority. Use `README.md`, `RELEASE-NOTES-v1.1.6.md`, `RELEASE-NOTES.md`, `ARCHIVE-CUSTODY.md`, and the current `testforge/docs/` guides.
+> Historical record: this file describes the v1.1.0 maintenance event. It is not the current installation, archive-custody, or validation authority. Use `README.md`, `RELEASE-NOTES-v1.1.7.md`, `RELEASE-NOTES.md`, `ARCHIVE-CUSTODY.md`, and the current `testforge/docs/` guides.
 
 ## Result
 

BUILD-WEEK.md

@@ -27,7 +27,7 @@ A later Codex task used TestForge to design and harden the CD Augment behavioral
 
 ## Build evidence
 
-> Historical snapshot: the counts and release identity in this section describe the original v1.0.2 Build Week entry. They are not current v1.1.6 package or validation evidence; use the current README, release notes, archive custody, and validation guides for that.
+> Historical snapshot: the counts and release identity in this section describe the original v1.0.2 Build Week entry. They are not current v1.1.7 package or validation evidence; use the current README, release notes, archive custody, and validation guides for that.
 
 - Primary Codex build Session ID: `019f6a6e-8556-75c0-919c-0738a3cb1f84`
 - Primary build model recorded by Codex: `gpt-5.6-sol`

README.md

@@ -2,7 +2,7 @@
 
 # TestForge
 
-TestForge is a free Collaborative Dynamics Augment that gives inexpensive local coding Agents a verification discipline they do not reliably improvise on their own. It turns software changes, repositories, defects, and release candidates into risk-ranked evidence instead of a comforting pile of green checkmarks.
+TestForge is a free Collaborative Dynamics Augment that gives inexpensive local coding Agents a verification discipline they do not reliably improvise on their own. It attacks an explicitly submitted, frozen release candidate with risk-ranked evidence instead of turning ordinary implementation into a comforting?and endless?pile of green checkmarks.
 
 The bundled Augment testbed generalizes the same discipline beyond code. Every capability you build can carry behavioral evals, run isolated trials, expose the exact failed dimensions, guide reengineering, seal the evidence, promote a reviewed passing baseline, and detect regression later. TestForge makes “I should check this” an operative capability and “it worked before” a durable record.
 
@@ -30,7 +30,7 @@ This repository also includes the CD Augment evaluation testbed used to run isol
 ## What you can do with it
 
 - Give a limited local coding Agent a reusable risk model, oracle discipline, evidence vocabulary, and skeptical second pass.
-- Hand an Agent a bug, diff, feature or failing test and get a risk-driven verification plan.
+- Hand an Agent a frozen candidate and bounded readiness claim and get one risk-driven verification verdict.
 - Generate tests that try to expose consequential failure rather than merely exercise edited lines.
 - Distinguish product defects, test defects, environment failures, flaky behavior and insufficient evidence.
 - Produce `READY`, `READY_WITH_RESIDUAL_RISK`, `NOT_READY`, `INSUFFICIENT_EVIDENCE` or `BLOCKED_BY_ENVIRONMENT` with a reproducible evidence trail.
@@ -43,9 +43,9 @@ TestForge is advisory verification machinery. It does not prove defect freedom,
 ## Repository map
 
 - [`docs/`](docs/) - the tailored GitHub Pages site, generated hero artwork, and site-source boundary.
-- [`testforge/`](testforge/) - the complete portable TestForge Augment v1.1.6.
+- [`testforge/`](testforge/) - the complete portable TestForge Augment v1.1.7.
 - [`testforge/docs/QUICK-START.md`](testforge/docs/QUICK-START.md) - install and first-use guide.
-- [`RELEASE-NOTES-v1.1.6.md`](RELEASE-NOTES-v1.1.6.md) - metered-verification safeguards and exact evidence boundary.
+- [`RELEASE-NOTES-v1.1.7.md`](RELEASE-NOTES-v1.1.7.md) - metered-verification safeguards and exact evidence boundary.
 - [`ARCHIVE-CUSTODY.md`](ARCHIVE-CUSTODY.md) - canonical Augment, plugin, standalone-skill, Claude, GitHub, and backup custody.
 - [`PLUGIN-DIRECTORY-SUBMISSION-v1.1.4.md`](PLUGIN-DIRECTORY-SUBMISSION-v1.1.4.md) - exact OpenAI draft listing, portal-specific upload custody, reviewer cases, and owner-only submission gate.
 - [`testforge/docs/SALES-DEMO.md`](testforge/docs/SALES-DEMO.md) - a compact proof-of-value scenario.
@@ -59,18 +59,18 @@ codex plugin marketplace add Stunspot/TestForge
 codex plugin add testforge@cd-testforge
 ```
 
-Start a new Codex task, then invoke `$software-verification` or `$verification-reviewer`. The plugin bundles the two self-contained TestForge v1.1.6 skills so their doctrine, tools, examples, and status vocabulary stay aligned. The separate Augment behavioral-evaluation harness remains in this repository rather than the skills-only plugin. Its marketplace namespace is product-specific, so TestForge can coexist with other Collaborative Dynamics plugin repositories.
+Start a new Codex task, then invoke `$software-verification` or `$verification-reviewer`. The plugin bundles the two self-contained TestForge v1.1.7 skills so their doctrine, tools, examples, and status vocabulary stay aligned. The separate Augment behavioral-evaluation harness remains in this repository rather than the skills-only plugin. Its marketplace namespace is product-specific, so TestForge can coexist with other Collaborative Dynamics plugin repositories.
 
 ## Quick start: use the standalone Agent SKILLs
 
 Download the latest release, unzip it and keep the `testforge/` tree together. Expose both directories under `testforge/skills/` through your Agent host's skill mechanism. Host-specific notes are included for [Codex](testforge/adapters/codex.md), [Claude Code](testforge/adapters/claude-code.md), [GitHub](testforge/adapters/github.md), [local shell](testforge/adapters/local-shell.md) and [copy-paste chat](testforge/adapters/copy-paste-chat.md).
 
-The frozen v1.1.6 release kit preserves the complete Augment, Codex plugin source, and both Claude skill archives with static package receipts. The maintained repository separately exposes current Claude upload archives. The latest retained OpenAI skills-only portal packet is v1.1.4; it is built and repository-tested, but this repository does not claim it was uploaded, scanned by the current portal, approved, published, or made discoverable. See [archive custody](ARCHIVE-CUSTODY.md) for exact object identities and boundaries.
+The frozen v1.1.7 release kit preserves the complete Augment, Codex plugin source, and both Claude skill archives with static package receipts. The maintained repository separately exposes current Claude upload archives. The latest retained OpenAI skills-only portal packet is v1.1.4; it is built and repository-tested, but this repository does not claim it was uploaded, scanned by the current portal, approved, published, or made discoverable. See [archive custody](ARCHIVE-CUSTODY.md) for exact object identities and boundaries.
 
 Then start with:
 
 ```text
-$software-verification Verify this change. Reconstruct what could break, create the smallest credible evidence set, run only safe authorized checks, and give me an evidence-backed release assessment.
+$software-verification Verify this completed frozen candidate for release. Reconstruct what could break, run only decision-changing authorized checks, and give me one evidence-backed assessment.
 ```
 
 After the evidence package exists, use a fresh context when practical:

RELEASE-NOTES-v1.1.7.md

@@ -0,0 +1,13 @@
+# TestForge v1.1.7
+
+## What changed
+
+TestForge now activates only for an explicit TestForge or release-readiness verdict on a frozen candidate. Ordinary implementation keeps its smallest proportionate native check and finishes without inheriting TestForge release apparatus.
+
+Every check, artifact, retry, reviewer pass, and receipt must be capable of changing the bounded verdict. Product defects and newly exposed requirements end the cycle and return to builder custody. Test, tooling, and environment failures receive at most one materially different low-cost recovery path; another support-layer failure closes the branch with the exact lost guarantee.
+
+Discovery metadata, activation examples, Codex defaults, and the fileless fallback now teach the same boundary. The v1.1.6 safeguards for quota-limited verification remain unchanged.
+
+## Evidence boundary
+
+This release changes routing and stopping doctrine. Deterministic source, mirror, package, archive, and documentation checks can establish that the new doctrine is present and synchronized. They do not establish universal model compliance, fresh-host activation, hosted-provider behavior, customer outcomes, or defect freedom.

RELEASE-NOTES.md

@@ -1,15 +1,17 @@
 # TestForge release notes
 
-The current package release is **v1.1.6**. See [RELEASE-NOTES-v1.1.6.md](RELEASE-NOTES-v1.1.6.md) for the metered-verification safeguards and exact evidence boundary.
+The current package release is **v1.1.7**. See [RELEASE-NOTES-v1.1.7.md](RELEASE-NOTES-v1.1.7.md) for the completion-governor change and exact evidence boundary.
 
-## Current release boundary
+## Current release
 
-Version 1.1.6 treats finite verification capacity as part of the test plan. Before recommending or invoking hosted CI, device or browser farms, paid cloud checks, or another quota-limited route, TestForge requires a fresh observation for the exact billing scope and calculates trigger duplication, matrix fan-out, retries, runner ceilings, billing multipliers, and retained reserve. Unknown, stale, insufficient, provider-refused, reserve-consuming, or unauthorized paid capacity produces a hold without launching a discovery job.
+Version 1.1.7 makes TestForge an explicit release-grade assessment of a frozen candidate, not the default tail of implementation. Every check, artifact, retry, reviewer pass, and receipt must be capable of changing the bounded verdict.
 
-The v1.1.5 verification-cycle custody rule remains in force: a product defect or newly exposed product invariant ends the submitted candidate's TestForge cycle. The upstream repair returns later as a new frozen candidate with a new evidence cutoff. Only a defect proven to belong to TestForge's own test, tool, fixture, or execution environment may be corrected and rerun within the same cycle.
+A product defect or newly exposed requirement still ends the submitted candidate cycle and returns repair to builder custody. A test, tooling, or environment failure now receives at most one materially different low-cost correction or fallback. If that path fails or encounters another support-layer failure, TestForge classifies the lost guarantee and exits instead of turning verification infrastructure into a new project.
 
-The maintained repository includes synchronized v1.1.6 package and plugin source plus current Claude upload archives. Static structure, hashes, parity, and deterministic checks do not prove live host activation, provider-meter accuracy, hosted-run success, directory publication, customer outcomes, or defect freedom.
+The v1.1.6 metered-verification safeguards remain in force. Unknown or unavailable hosted capacity produces a hold and a bounded substitute; it does not authorize a probe job or reinterpret provider refusal as a product defect.
+
+The maintained repository includes synchronized v1.1.7 package and plugin source plus current Claude upload archives. Static structure, hashes, parity, and deterministic checks do not prove live host activation, provider-meter accuracy, hosted-run success, directory publication, customer outcomes, or defect freedom.
 
 ## Historical notes
 
-Version-specific records remain available as `RELEASE-NOTES-v*.md`. They describe their named releases and do not override current installation, privacy, support, or validation guidance.
+Version-specific records remain available as RELEASE-NOTES-v*.md. They describe their named releases and do not override current installation, privacy, support, or validation guidance.