# Reused-corpus release deployed, 2026-09-10

Release `20260909-175028-829c4bb` was activated successfully after the owner ran
the governed launcher. Application commit: `829c4bb551bdbe9ce777ed7f446b8f2d35c574fb`.
Deployment tooling commit: `963fb43915018951f034ef9a439743962032e32a`.

The Execute runner reports `Ok: true`, `Outcome: Executed`, no thrown failure and
12/12 checks passed. Execution ran from 00:01:10 to 00:02:23 UTC on September 10.
Transaction: `bdd03e01-4236-49d6-b932-4d875b65bec0`.
Evidence: `local/artifacts/persistence-regression-260909/release/E2-Execute-20260910-000057-result.json`
and its journal/transcript companions.

Independent post-deployment verification confirmed all three CURRENT pointers
name the release, the worker service is Running, and web `/`, API `/health`, API
`/health/ready` and documentation `/naming-glossary.md` return HTTP 200. The runner
also verified the activated web/API processes, worker release, API schema,
authentication redirect/PKCE and documentation repository-internal protections.
These checks do not establish a new live extraction or a completed credential
save/test/activate lifecycle.

Earlier ownership failures and the UTC-midnight budget refusal remain preserved.
The [ownership correction](docs-ownership-deployment-fix-260909.md) shares the
renamed legacy-path rule between the input validator and IIS adapter. The corrected
module passed 1,266 tests and read-only live ownership checks before activation.

The [40-document regression](persistence-regression-run-260909.md) remains a reused
development corpus with recorded retries, not independent acceptance. Deployment
does not authorize C6 cutover: NP Group's 52 historical sync runs remain protected.