release(v0.9.0): bump versions to 0.9.0 + CHANGELOG + STATUS/ROADMAP/spec sync

Org GUI (read+write) + pluggable second factor feature-complete (all 5 streams
merged at 6d6e9f8). Versions: extension manifests + core/cli/wasm -> 0.9.0
(manifest.firefox.json 0.7.0-drift corrected); relicario-server stays 0.1.1.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Hc6Rvdz3DxLucqNtPE2iP

docs/superpowers/specs/2026-06-20-extension-org-gui-design.md

@@ -38,6 +38,8 @@ The spike (Dev-C, commit `426b82a`; evidence in `docs/superpowers/spikes/2026-06
 
 **Decision (user, 2026-06-25): build the universal packfile-push write path now, in v0.9.0** — not the deferred fallback. A3 (Plan C) is re-scoped: a small SSHSIG-through-isomorphic-git mini-spike, then the universal `commitSigned`, then the write handlers + UI (held until A0–A2 land). A focused `/security-review` on the push path is mandatory before merge.
 
+**SHIPPED in v0.9.0 (merged `6d6e9f8`, 2026-06-27):** org read (A0–A2 + A4-read) and org write (A3) both landed end-to-end. The mini-spike confirmed SSHSIG through isomorphic-git `onSign` against the real pre-receive hook (member accepted / non-member rejected); the write handlers honor the manifest-no-wipe landmine + a client-side grant check; the mandatory `/security-review` passed, and the independent merge-time review additionally caught + fixed a critical empty-id data-loss bug on org add (`new_item_id` is now minted server-side-style in the handler). An "add-org config" write flow was added (Dev-B) since `org_list_configs` read `orgConfigs` but nothing wrote them. Org admin remains CLI-only per scope.
+
 **Latent bug noted (separate follow-up):** `extension/src/service-worker/gitea.ts` `putBlob` calls nonexistent Gitea `/git` write endpoints — large attachments would 404 on a Gitea host (pre-existing ~v0.8.2).
 
 ## Architecture