docs: add pre-v1 release navigation

Author: Shaelz

README.md

@@ -46,6 +46,26 @@ The v1 architecture direction is **evolve, not rewrite**:
 - address large-repo pressure with scoped views and graceful limits before
   considering Canvas or WebGL.
 
+## Pre-v1 release status
+
+This repository is still pre-public and pre-tag. For release navigation:
+
+- Active roadmap: [`docs/V1_RELEASE_PLAN.md`](docs/V1_RELEASE_PLAN.md)
+- Current candidate evidence:
+  [`docs/releases/M6_RELEASE_CANDIDATE_VALIDATION.md`](docs/releases/M6_RELEASE_CANDIDATE_VALIDATION.md)
+- Public-switch checklist:
+  [`docs/releases/PUBLIC_RELEASE_CHECKLIST.md`](docs/releases/PUBLIC_RELEASE_CHECKLIST.md)
+- Medium/large pressure evidence:
+  [`docs/releases/MEDIUM_LARGE_PRESSURE_VALIDATION.md`](docs/releases/MEDIUM_LARGE_PRESSURE_VALIDATION.md)
+- Remaining questions:
+  [`docs/ai/OPEN_QUESTIONS.md`](docs/ai/OPEN_QUESTIONS.md)
+
+Current `main` is deterministic-check ready for the remaining human and
+publication gates, not public-release complete. Independent cold-user
+validation, final manual GitHub UI-only checks, public-only security/ruleset
+setup, and the final tag/release/publication decision remain. If new commits
+land before tagging, exact-candidate validation must be refreshed.
+
 ## Current feature scope
 
 - Scan a target repository directory.

docs/V1_RELEASE_PLAN.md

@@ -6,6 +6,31 @@ Current release state: pre-v1 development
 
 Last reviewed: 2026-06-05
 
+## Release Document Roles
+
+This plan remains the active pre-v1 roadmap until public `v1.0.0` publication
+is complete. It should not be compacted into a historical pointer until the
+final validation record is frozen.
+
+| Document | Role |
+| --- | --- |
+| `docs/V1_RELEASE_PLAN.md` | active roadmap and release criteria |
+| `docs/releases/M6_RELEASE_CANDIDATE_VALIDATION.md` | current deterministic candidate evidence |
+| `docs/releases/PUBLIC_RELEASE_CHECKLIST.md` | public-switch order, GitHub settings target, and remaining publication actions |
+| `docs/releases/MEDIUM_LARGE_PRESSURE_VALIDATION.md` | current medium/large map pressure evidence |
+| `docs/releases/M5_VALIDATION_RECORD.md` | historical local validation baseline |
+| `docs/releases/M6_GITHUB_EXPOSURE_AUDIT.md` | GitHub exposure and hosted-surface audit record |
+| `docs/releases/M6_HISTORY_REWRITE_PLAN.md` | historical controlled rewrite procedure |
+| `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 |
+
+Current `main` is deterministic-check ready for independent cold-user
+validation and final publication preparation. It is not public-release complete
+until independent validation, manual GitHub UI-only checks, public-only
+security/ruleset setup, and the final tag/release/publication decision finish.
+If any new commits land before tagging, refresh exact-candidate validation for
+the new tip.
+
 ## 1. V1 definition
 
 `codebase-visualize` is v1-worthy when it is:

docs/ai/OPEN_QUESTIONS.md

@@ -15,9 +15,10 @@ Last refreshed: 2026-06-06
   the publishable-history audit passes, private-safe GitHub settings are
   applied, and the current private `main` tip has deterministic
   release-candidate validation from both the working tree and a fresh private
-  clone. M6 still needs independent cold-user validation, public-only
-  security/ruleset setup, and the final publication decision before visibility
-  changes.
+  clone. Remaining gates are independent cold-user validation, final manual
+  GitHub UI-only checks, public-only security/ruleset setup, and the final
+  tag/release/publication decision. If new commits land before tagging, refresh
+  exact-candidate validation for the new tip.
 - **Manual GitHub UI checks:** The maintained API audit is in
   `docs/releases/M6_GITHUB_EXPOSURE_AUDIT.md`. Before changing visibility,
   manually glance at UI-only surfaces such as social preview and any package