docs(v0.44): role-neutral phrasing in Beta.2 closure evidence (#1288)

Author: DevBot

docs/evidence/2026-09-04-v044-beta2-closure-verification.md

@@ -1,7 +1,7 @@
 # v0.44 Beta.2 Closure Verification — independent verifier record
 
 - Date: 2026-09-04
-- Verifier: fresh `kimi-code` session, profile `.agents/v044-kimi-release-verifier.md` (no implementer/thinker session reuse)
+- Verifier: fresh release-verifier session per the configured release-verifier profile under `.agents/` (no implementer/thinker session reuse)
 - Stage issue: #1288 (umbrella #1155, authority ADR-0151, Beta.1 record #1150)
 - Candidate SHA: `aa3dd70ff8e5c8dbee602f8f7acd8e3b9d3c2b2b` (dev tip, tree clean at session start)
 - CI at candidate: AutoFlow CI run 33871051171 SUCCESS, CodeQL run 33871051092 SUCCESS — both at the exact candidate SHA (verified via `gh run view … --json headSha`).

docs/evidence/2026-09-04-v044-beta2-reverification.md

@@ -1,7 +1,7 @@
 # v0.44 Beta.2 Re-Verification Addendum — narrow F1-closure pass
 
 - Date: 2026-09-04
-- Verifier: fresh `kimi-code` session, profile `.agents/v044-kimi-release-verifier.md` (independent of the first verifier session and of the implementer)
+- Verifier: fresh release-verifier session per the configured release-verifier profile under `.agents/` (independent of the first verifier session and of the implementer)
 - Scope: narrow re-verification of the sole NO-GO finding (F1) from `docs/evidence/2026-09-04-v044-beta2-closure-verification.md` after remediation PR #1313 (issue #1312), plus a regression screen over everything the remediation touched.
 - First-report integrity note: the first closure record was read in full. Its wide padded table column alignment is a `deno fmt` reflow artifact; the content itself (battery rows, F1 finding, fingerprints, residual risks) is coherent, internally consistent, and matches what the remediation targeted. Nothing beyond formatting appears altered.