Refresh v1 preview readiness blocker status and cross-repository tracking

[TheSilkky]

Refresh v1 preview readiness blocker status and cross-repository tracking

Priority

P2

Type

documentation

Labels

Suggested GitHub labels:

• backlog
• documentation
• maintenance

Branch scope

• Current branch: develop
• Current HEAD: 3555d1fd531ecd4b51b85779618bf4717514aa25
• Target branch: develop
• Original reviewed branch/ref: upgrade-codex-reports-and-repo-full-validation-security-review
• Original reviewed commit SHA: e609ff86028c81bd149839e03d1ffc0eb2ee9e4a
• Merged source pull request: #378
• Target release/version: unreleased
• Scope classification: planning-only
• Revalidation status: Revalidated against develop at 3555d1fd531ecd4b51b85779618bf4717514aa25 on 2026-07-12; repeat if develop moves before issue creation.

Summary

Refresh the server v1 preview readiness checklist so issue state, implementation state, cross-repository evidence, and release-gate status are recorded separately.

Context

The current checklist is the source of truth for v1 preview, v1.0.0, and real-user evidence-upload readiness claims. Some linked tracking items are closed while companion-repository documentation still marks corresponding product surfaces as planned or incomplete.

Issue #249 and PR #255 created the checklist and release gate. Issue #369 refreshed general Proofline documentation and reusable workflows. This draft is a narrow status-reconciliation pass, not another readiness design or product implementation issue.

Proposed change

Review every hard blocker against current commit-addressed server evidence and the latest default-branch website and web-client documentation. For each item, distinguish:

• implementation status
• validation status
• linked issue/PR state
• owning repository
• remaining evidence needed

Retain the Not ready boundary while any hard blocker lacks implementation or required validation evidence.

Acceptance criteria

• Every hard blocker distinguishes implementation status from issue/PR state.
• Closed issues are not treated as proof that a requirement is complete.
• Cross-repository entries name the owning repository and cite current commit-addressed evidence.
• Planned client, key-custody, decryption, and incident-mode behavior remains clearly future where not implemented.
• Current implemented recipient-key, trusted-contact, wrapped-key, and post-quantum server behavior is neither erased nor overstated.
• The checklist retains pre-v1 experimental and Not ready wording while any hard blocker remains.
• Stale or broken tracking links are corrected.
• Server changes do not edit sibling repository files.

Tests / validation

• Read docs/v1-preview-direction.md in full.
• Read docs/post-quantum-envelope.md in full.
• Read docs/v1-preview-readiness-checklist.md.
• Inspect current companion-repository evidence read-only at named commits.
• Run scripts/check-markdown-links.py.
• Run git diff --check.
• Perform a public-claims and source-of-truth review.
• Revalidate against the target branch before public issue creation.

Out of scope

• Implementing web, iOS, Android, protocol, recording, notification, key-custody, or decryption features.
• Editing website or web-client files from the server issue.
• Treating issue closure, ordinary tests, or a technical review as production or preview readiness.
• Weakening the current ciphertext-only, private-API, listener-separation, or public-viewer boundaries.
• Replacing project-level website governance/public-voice sources with server-local claims.

Notes

Report reference: docs/reports/2026-07-10-proofline-unreleased-technical-review.md, public documentation follow-up.

Related completed work: issue #249 and PR #255; issue #369.