docs: refresh exact candidate validation

Author: Shaelz

CHANGELOG.md

@@ -2,6 +2,9 @@
 
 ## Unreleased
 
+- Refresh exact-candidate validation for the current private `main` tip after
+  the final readiness docs, including working-tree, fresh-clone, CLI help,
+  public-history, audit, and WSL2 quick-check evidence.
 - Add pre-v1 generated-map polish: cold-user guidance, honest large/low-signal
   notices, copyable agent briefings, clearer graph controls, selected-node
   centering, and reduced graph label clutter.

docs/V1_RELEASE_PLAN.md

@@ -2,9 +2,10 @@
 
 Status: active roadmap for `v1.0.0`
 
-Current release state: pre-v1 development
+Current release state: exact private candidate validated; manual/public-only
+publication gates remain
 
-Last reviewed: 2026-06-05
+Last reviewed: 2026-06-07
 
 ## Release Document Roles
 
@@ -25,11 +26,9 @@ final validation record is frozen.
 | `docs/releases/M6_REWRITE_DRY_RUN_RECORD.md` | historical rewrite dry-run evidence |
 | `docs/ai/OPEN_QUESTIONS.md` | remaining non-blocking questions and final gates |
 
-The latest validated candidate content is deterministic-check ready for final
-publication preparation. An agent-mediated cold-user rehearsal now proves the
-README/SKILL acquisition, install, invocation, interpretation, and rerun path
-from a clean private GitHub clone, and a final pre-public API/readiness pass
-found no new hosted-surface blocker. It is not public-release complete until
+The current validated candidate content is deterministic-check ready for final
+publication preparation. It includes the agent-mediated cold-user rehearsal and
+the final pre-public API/readiness pass. It is not public-release complete until
 external human validation or explicit maintainer acceptance, manual GitHub
 UI-only checks, public-only security/ruleset setup, and the final
 tag/release/publication decision finish. If maintainers choose a later content
@@ -574,21 +573,21 @@ Every criterion below is required unless explicitly marked preferred.
 
 ### Release hygiene
 
-- [ ] Full local release check passes.
-- [ ] `npm audit --audit-level=high` passes.
-- [ ] `git diff --check` passes.
-- [ ] Worktree is clean.
+- [x] Full local release check passes.
+- [x] `npm audit --audit-level=high` passes.
+- [x] `git diff --check` passes.
+- [x] Worktree is clean.
 - [ ] Public release candidate passes independent cold-user validation.
 - [x] Agent-mediated cold-user rehearsal from a disposable GitHub clone passes.
 - [x] Exact public release-candidate checkout passes the final deterministic
   and platform validation matrix.
-- [ ] Public-surface sanitation passes for tracked and candidate-reachable
+- [x] Public-surface sanitation passes for tracked and candidate-reachable
   content.
 - [x] Reachable pre-public history is generalized and passes
   `npm run check:public:history`.
 - [ ] GitHub repository settings match the documented sibling-grade public
   target before visibility changes.
-- [ ] Complete GitHub exposure audit records what is retained, generalized,
+- [x] Complete GitHub exposure audit records what is retained, generalized,
   removed, deleted, or rewritten before visibility changes.
 - [ ] Final version identifiers and tag are aligned intentionally.
 
@@ -730,10 +729,9 @@ are complete; the maintainer can either accept the rehearsal as sufficient for
 v1 or perform an additional external human-through-agent validation pass.
 
 The initial GitHub exposure inventory, controlled rewrite plan, rewrite dry
-run, real private-history rewrite, private-safe GitHub settings pass, and
-validated-candidate deterministic release-candidate evidence are complete. The
-agent-mediated pre-public rehearsal and final API/readiness pass are also
-complete. The next M6 execution slice is final manual/public-only release
-preparation; visibility remains private throughout. If maintainers choose a
-later content commit for tagging, exact-candidate validation must be refreshed
-again.
+run, real private-history rewrite, private-safe GitHub settings pass,
+agent-mediated pre-public rehearsal, final API/readiness pass, and current
+exact-candidate deterministic validation are complete. The next M6 execution
+slice is final manual/public-only release preparation; visibility remains
+private throughout. If maintainers choose a later content commit for tagging,
+exact-candidate validation must be refreshed again.

docs/ai/OPEN_QUESTIONS.md

@@ -13,7 +13,7 @@ Last refreshed: 2026-06-06
   available.
 - **Final publication gates:** The private remote history has been rewritten,
   the publishable-history audit passes, private-safe GitHub settings are
-  applied, and the latest validated candidate content has deterministic
+  applied, and the current validated candidate content has deterministic
   release-candidate evidence from both the working tree and a fresh private
   clone. An agent-mediated cold-user rehearsal from a disposable GitHub clone is
   recorded in `docs/releases/M6_PRE_PUBLIC_REHEARSAL.md`. A final pre-public

docs/releases/M6_RELEASE_CANDIDATE_VALIDATION.md

@@ -2,12 +2,12 @@
 
 Status: current private release candidate validated; final publication pending
 
-Date: 2026-06-06
+Date: 2026-06-07
 
 ## Candidate Content
 
-- Revision: `ea12abe1a6499b69ffaafe66dbe233d213960808`
-- Tree: `bbe6422f8b8217500203cdb5620506c5bbc6c56b`
+- Revision: `c7855e07c40df5220df446d81e5639c5ecc55aa5`
+- Tree: `e89eb71dc952ab1bc077c67c8a74f0c516f966ec`
 - Product version: `0.0.1`
 - Graph schema version: `1.0.0`
 - Repository visibility during validation: private
@@ -20,15 +20,15 @@ The current candidate was validated from the maintainer worktree and from a
 fresh private GitHub clone outside the repository. Raw local clone paths and
 command logs are intentionally not recorded in maintained documentation.
 
-This candidate includes the README sister-skill alignment pass that reshaped
-the README around the same user-first quickstart, first-use separation,
-authority-boundary, validation, and reference structure as `codebase-orient`.
+This candidate includes the README sister-skill alignment pass, the
+agent-mediated pre-public rehearsal record, and the final pre-public
+GitHub/API readiness pass.
 
 This record validates the candidate content revision above. The commit that
 updates this evidence record necessarily follows the validated candidate
 revision and should not be confused with a self-referential release-candidate
-proof. If maintainers choose a later commit as the tag target, exact-candidate
-validation must be refreshed for that later content.
+proof. If maintainers choose a later content commit as the tag target,
+exact-candidate validation must be refreshed for that later content.
 
 ## Environment
 
@@ -64,8 +64,8 @@ validation must be refreshed for that later content.
 
 The fresh private GitHub clone matched the candidate exactly:
 
-- Revision: `ea12abe1a6499b69ffaafe66dbe233d213960808`
-- Tree: `bbe6422f8b8217500203cdb5620506c5bbc6c56b`
+- Revision: `c7855e07c40df5220df446d81e5639c5ecc55aa5`
+- Tree: `e89eb71dc952ab1bc077c67c8a74f0c516f966ec`
 - Branch: `main`
 - Worktree after checks: clean
 
@@ -91,15 +91,8 @@ Linux-native Node:
 The Windows fresh GitHub clone remains the authoritative clean-clone evidence
 for this refreshed record.
 
-Later release-tracking docs record additional pre-public readiness evidence
-after this exact candidate content:
-
-- `M6_PRE_PUBLIC_REHEARSAL.md`
-- `PUBLIC_RELEASE_CHECKLIST.md`
-- `M6_GITHUB_EXPOSURE_AUDIT.md`
-
-If maintainers choose one of those later documentation commits as the final tag
-target, refresh exact-candidate validation for that later content.
+The pre-public rehearsal, public release checklist, and GitHub exposure audit
+are included in this exact candidate content.
 
 ## Live-Fire And Visual Evidence
 

docs/releases/PUBLIC_RELEASE_CHECKLIST.md

@@ -211,8 +211,9 @@ Maintained M6 records:
 
 Current deterministic candidate status:
 
-- Latest validated candidate content has fresh working-tree and clean-clone
-  deterministic validation evidence.
+- Current validated candidate content has fresh working-tree and clean-clone
+  deterministic validation evidence for revision
+  `c7855e07c40df5220df446d81e5639c5ecc55aa5`.
 - Agent-mediated cold-user and pre-public rehearsal evidence is recorded.
 - Final pre-public API/readiness pass was performed while private; no new
   hosted-surface blocker was found.