Files
shard-wiki/.claude/ralph-loop.local.md
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

22 lines
722 B
Markdown

---
active: true
iteration: 2
session_id: b24b53ca-a25b-4a18-8331-925c4100d39f
max_iterations: 20
completion_promise: "HEUREKA"
workplan_id: SHARD-WP-0003
workplan_file: workplans/SHARD-WP-0003-engine-dives-batch.md
started_at: "2026-06-14T16:37:36Z"
---
Read the workplan at `workplans/SHARD-WP-0003-engine-dives-batch.md`.
If every task has `status: done` AND frontmatter `status: done`:
run `rm -f .claude/ralph-loop.local.md` first (deactivates the loop so the stop hook exits cleanly),
then output <promise>HEUREKA</promise>.
Otherwise implement the next `todo` task as described in the workplan.
Set task `in_progress` when starting, `done` when complete.
When all tasks are done set frontmatter `status: done`.