docs: correct stale build, forge and layer facts

BUILDING.md never mentioned the floret-kit submodule, so its instructions
could not produce a working build — a plain clone fails to configure. It
also understated the SDK requirement: compileSdk is 37, not the "36+" it
claimed. Both matter now that the Codeberg move is meant to make an
outside clone viable.

The docs map advertised superpowers/specs/ and superpowers/plans/, neither
of which exists any more, while omitting BUILDING.md and RELEASING.md.
Dropped the dead rows and listed what is actually there. Purged the
remaining superpowers references in .planning/ and ARCHITECTURE.md's
dangling "see plan 03" the same way — a pointer to a deleted file is worse
than no pointer.

ARCHITECTURE.md still called OptionCard "the app's only sanctioned
selection-dialog style", which the 2026-07-07 flip to full-screen pickers
reversed, and described no layer for floret-kit despite it being a
compiled-from-source composite build. Its CI note credited Gitea Actions;
contributor CI runs on Codeberg now.

PROJECT.md's Source section described the old world outright ("hosted on
self-hosted Gitea") and now records the split: Codeberg canonical, Gitea
build infrastructure.

.planning/PROJECT.md

@@ -40,5 +40,9 @@ shows a stylized "1" on a slate squircle.
 
 ## Source
 
-Hosted on self-hosted Gitea, released through self-hosted F-Droid repo on
-Hetzner. Same infrastructure as `HouseHoldKeaper`.
+**Codeberg (`jlmakiola/calendula`) is canonical** — git, issues, PRs, tags and
+releases, plus contributor CI. The self-hosted Gitea instance is build
+infrastructure only: it holds the signing key, runs the release pipeline, and
+publishes the self-hosted F-Droid repo on Hetzner. Codeberg push-mirrors `main`
+and tags to Gitea, where a bumped `versionName` triggers the release. Also
+published to the official F-Droid repo. See `docs/RELEASING.md`.

.planning/REQUIREMENTS.md

@@ -1,6 +1,6 @@
 # Calendula — Requirements
 
-See full design spec: `docs/superpowers/specs/2026-06-08-calendar-app-design.md`
+Architecture reference: [`../docs/ARCHITECTURE.md`](../docs/ARCHITECTURE.md)
 
 ## V1 Scope (Variant "B") — shipped in full (v1.0.0, 2026-06-11)
 

.planning/ROADMAP.md

@@ -55,9 +55,8 @@ after v0.6 (full event read) plus the onboarding-screen polish pass.
 
 ## v2.0 — Write Support (complete, shipped 2026-06-11)
 
-Delivered in four releasable slices (plan:
-`docs/superpowers/plans/2026-06-11-03-write-support.md`). The V1 spec is a
-guide here, not a contract — scope per slice is decided as we go.
+Delivered in four releasable slices. The V1 spec is a guide here, not a
+contract — scope per slice is decided as we go.
 
 | Version | Milestone | Status |
 |---|---|---|
@@ -244,8 +243,7 @@ pass on the existing controls; new toggles ride in with their own features.
     sequential branches: `feat/ics-export` (write side + UID-on-create precursor)
     then `feat/ics-import` (parser, restore, dedup by UID). Import is
     liberal-in/strict-out: skip-and-report foreign `VTIMEZONE` / `RECURRENCE-ID`
-    / guest lists it can't model. Plans:
-    `docs/superpowers/plans/2026-06-18-05-ics-export.md` + `…-06-ics-import.md`.
+    / guest lists it can't model.
 11. **Snooze / dismiss notification actions** *(merged into release/v2.8.0)* —
     followed the `.ics` work; inherits v2.6's deferred exact-alarm/WorkManager
     decision (snooze must re-fire an alarm).

.planning/STATE.md

@@ -25,7 +25,7 @@ release-cut.
 
 ## Progress
 
-- [x] Design spec written and committed (`docs/superpowers/specs/2026-06-08-calendar-app-design.md`)
+- [x] Design spec written and committed (2026-06-08)
 - [x] V1 design decisions resolved (App name "Calendula", icon, seed color)
 - [x] Plan 01 written and executed — foundation lands (theme, icon, i18n, Hilt, DataStore, CI green)
 - [x] Plan 02 written and executed — data layer + permission flow + debug screen