Define stable-v1 release controls

[AndriGitDev]

Summary

• freeze an explicit stable-v1 profile for installation, contact establishment, pairwise text, bounded groups and attachments, backup/recovery, blocking, delivery semantics, supported platforms, optional services, and exclusions
• add the release evidence ledger for all P0 gates and stable public claims, with accountable owners, evidence levels, artifacts, gaps, and review dates
• record the founder's keep-and-monitor Komms name decision, including the observed komms.app overlap, confusion surfaces, migration cost, cadence, and qualified-advice triggers
• make founder authority, unassigned independent roles, continuity gaps, and incident handling explicit
• correct remaining in-repository overclaims while retaining “Private messaging that keeps working.”
• validate relative documentation links, P0/claim coverage, the product promise, and bounded public terminology in CI and the local release matrix

Baseline

• PR Harden core trust boundaries and delivery reliability #77 is merged as 4fda544739c0665b6a324256d858c16c1d73d992
• its final head and merge commit have the same repository tree
• synchronized main contained no commits after PR Harden core trust boundaries and delivery reliability #77 when this branch was created

Evidence

• python3 scripts/check-docs.py
• python3 scripts/check-release-version.py
• node --check apps/desktop/ui/main.js
• bash -n scripts/local-release-matrix.sh
• git diff --check
• CI run #199: all nine jobs passed and the retained result is recorded in the ledger
• CI run #200: all nine jobs passed on final head c8bf34c, including documentation controls, workspace tests, both no_std builds, dependency policy, Android, iOS, desktop, and fuzz smoke

Remaining external blockers

• stable release remains unauthorized; every P0 gate is still open
• independent cryptography, interoperability, operator, field/accessibility, release, and sensitive-surface reviewers remain unassigned
• the backup steward role and credential-recovery rehearsal remain open
• qualified trademark advice and registry similarity/class/jurisdiction review remain unassigned; the recorded name decision is not legal clearance
• the current P0 protocol ADRs still require implementation and acceptance
• komms.org, the repository description, and retained release/package listings require out-of-repository copy follow-up