Defame1297/holocron
0
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

docs(adr): add ADR-0017 — Gitea as exclusive issue tracker

Browse Source 
Supersedes ADR-0011 (provider-agnostic issue tracker with file-based
default). Gitea MCP is now configured and in active use; the file-based
fallback is removed. All local docs/issues/ files will be migrated to
Gitea as part of the great refactoring (issue #15).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Defame1297
2026-06-28 16:22:31 +00:00
parent e362c01d6b
commit 5834be3030
1 changed files with 17 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/adr/0017-gitea-canonical-issue-tracker.md Normal file
View File

@@ -0,0 +1,17 @@
# Gitea is the exclusive issue tracker — file-based fallback removed
ADR-0011 established a provider-agnostic model with `docs/issues/NNNN-<slug>.md` as the file-based default, switching to Gitea MCP at runtime when available. The interim model was justified because Gitea would not be configured until after Chunk 3, and the repo needed to work before then.
Gitea is now configured and in active use. The condition in ADR-0011 has been met. This ADR supersedes it.
Gitea is now the exclusive issue tracker for this repo. The file-based fallback is removed entirely:
- `docs/issues/` is deleted; all 28 local issue files are migrated to Gitea (completed → closed, open → open)
- `docs/prd/` is deleted; PRD files are migrated to Gitea as closed issues
- Skills and workflows create and reference issues exclusively via Gitea MCP — no runtime backend detection, no file-based path
Three alternatives were rejected. Keeping the file-based fallback adds code complexity with no benefit — Gitea MCP is a hard dependency for this repo on every machine that works with it. A provider-agnostic model with Gitea as the default but file-based as a fallback is the same problem: the fallback path exists but is never exercised, which means it will rot silently. Keeping `docs/issues/` as an archive alongside live Gitea issues creates a split-brain risk where two sources of truth diverge; git history already preserves the full text of migrated issues.
The file-based model also had a structural weakness: issues in `docs/issues/` were invisible from the Gitea UI, making it impossible to track work, assign milestones, or filter by label without opening the repo locally. Gitea provides all of that natively.
The "Provider-agnostic issue tracker" glossary entry in CONTEXT.md is updated in the same workstream to remove the file-based phase framing. The `providers/gitea/` adapter path described in ADR-0011 was never implemented — Gitea integration runs entirely via MCP, not a provider adapter.