Gate: G5 — Packaging, hardening, and release
Planning source: validated implementation plan PR #1
- Depends on: OC-001, OC-055, OC-058.
- Deliverable: README front matter,
SECURITY.md, compatibility table, threat/metadata limits, key-storage mode, courier v1/v2 distinction, panic limits, “powered and awake” wording, and bridge feature gating.
- Acceptance: every material caveat in
upstream-validation.md is represented; no secure-enclave, physical-wipe, standard-Nostr, blanket Android, or unconditional 24/7 claim remains.
- Excludes: legal advice or unsupported name clearance.
Maintainer reconciliation — 2026-09-04
Next closure evidence/work: Reconcile upstream caveats, stale implementation claims, IPC security wording and supported-runtime evidence.
Baseline reviewed: main 87c3bcb7d65e3e2ab8ae317694b751f8efe9a8ed. Implementation presence is not a live conformance claim.
Gate: G5 — Packaging, hardening, and release
Planning source: validated implementation plan PR #1
SECURITY.md, compatibility table, threat/metadata limits, key-storage mode, courier v1/v2 distinction, panic limits, “powered and awake” wording, and bridge feature gating.upstream-validation.mdis represented; no secure-enclave, physical-wipe, standard-Nostr, blanket Android, or unconditional 24/7 claim remains.Maintainer reconciliation — 2026-09-04
Next closure evidence/work: Reconcile upstream caveats, stale implementation claims, IPC security wording and supported-runtime evidence.
Baseline reviewed: main
87c3bcb7d65e3e2ab8ae317694b751f8efe9a8ed. Implementation presence is not a live conformance claim.