# 260614 — git-forge wikis deep dive (Gitea · GitLab · GitHub)

Deep dive on the **git-forge-hosted Markdown wikis** as one grouped memo: each is a
**dedicated git repository of Markdown** exposed through a forge, attachable by **cloning
the wiki repo directly** *or* (where offered) through the **forge's wiki API**. INTENT names
**Gitea wikis** explicitly as a shard participant — this dive confirms the **git-native
file-store** as a first-class, and the *simplest*, backend.

- `findings.md` — the three forges compared, the `.wiki.git` model, API matrix, capability
  profile, INTENT mapping, UC seeds (UC-76/77), architecture notes for SHARD-WP-0002, open
  questions (resolves the UC-68 source-of-truth question for this case), sources,
  traceability.

Catalog yield: UC-76 (attach a forge wiki by cloning its dedicated `.wiki.git` — git **is**
the native store and the coordination journal), UC-77 (attach/write via the forge wiki API
where git-clone is unavailable/undesired — capability varies by forge). Enriched
UC-40/02/68/38. Feeds SHARD-WP-0002 T14 (attachment binding).