Defame1297
05bb9d6e9f
Complete ADR refactoring for issue #15: ## Changes 1. **Triage archival** — deleted chunk-era ADRs (0001–0003, 0006–0011, 0013); kept active decisions (0004, 0005, 0012, 0014+) 2. **ADR-0004 rewrite** — now reflects plugin-based skill distribution (`plugins/<name>/skills/` + `claude plugin install`) instead of monolithic `.agents/skills/` deployment 3. **Renumber to 0001–0009** — sequential clean slate after archival; all cross-references updated 4. **Content audit** — verified all 9 remaining ADRs for alignment with plugin model, removed stale chunk/deployment language Kept ADRs: 0001–0009 - 0001: Skills distributed via plugins - 0002: Two-tier CLAUDE.md (always-on + on-demand) - 0003: AGENTS.md as provider-agnostic entry point - 0004: INFO finding level in skill-audit - 0005: agent-author dual provider scaffold - 0006: Plugin version parity (version in both manifests) - 0007: Gitea as exclusive issue tracker - 0008: agent-audit single-file invocation - 0009: agent-audit field inventory reference All decisions are active and aligned with current repository state (marketplace/plugin model). Closes #15 (ADR section of acceptance criteria) Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
2.1 KiB
Gitea is the exclusive issue tracker — file-based fallback removed
Supersedes: ADR-0011 (provider-agnostic issue tracker with file-based default — archived during refactoring)
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.