shard-wiki/workplans
tegwick dbc42f05db research: git-forge wikis deep dive (Gitea/GitLab/GitHub); UC-76-77
SHARD-WP-0003 T5. The home case: a forge wiki is a separate .wiki.git repo of
Markdown -> page model, history, coordination journal map 1:1 with near-zero
adapter. git-clone universal across all three; wiki content API
capability-varying (GitLab/Gitea yes, GitHub git-only). git IS the canonical
store (not a mirror), so write-by-commit is safe -- resolves the UC-68/Q22
race for this case. UC-76 (clone .wiki.git attach), UC-77 (forge wiki API,
capability varies). Enriched UC-40/02/68/38. Marks T5 done.
Feeds SHARD-WP-0002 T14/T11.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-14 19:40:46 +02:00
..
SHARD-WP-0001-yawex-requirements.md Reorganize documentation into canonical repository layout 2026-06-08 13:55:27 +02:00
SHARD-WP-0002-federation-architecture.md synthesis v2: extend shard spectrum to full dive set (13 spectra); re-fold into SHARD-WP-0002 2026-06-14 17:25:32 +02:00
SHARD-WP-0003-engine-dives-batch.md research: git-forge wikis deep dive (Gitea/GitLab/GitHub); UC-76-77 2026-06-14 19:40:46 +02:00
SHARD-WP-0004-computational-knowledge-systems.md plan: persist state-hub workstream/task IDs for SHARD-WP-0003 and SHARD-WP-0004 2026-06-14 18:29:15 +02:00