From ba7cec7672ba58c0886ee683a37519bc3c6d9372 Mon Sep 17 00:00:00 2001 From: Defame1297 Date: Mon, 17 Aug 2026 10:10:24 +0000 Subject: [PATCH] docs(adr): amend ADR-0007 and ADR-0015 for the CONTEXT.md trim MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Why: b9c7762 gave dated amendments to ADR-0013, ADR-0015 and ADR-0017, but two pointers were missed. ADR-0007 cited the "Provider-agnostic issue tracker" glossary entry, which the trim renamed to "Issue". ADR-0015 cited the "lint plugin" entry, which the trim deleted outright — and ADR-0015 was amended for its other CONTEXT.md pointer in the same commit, so this one was missed inside an already-edited file. Implementation notes: ADR-0007 gets a dated parenthetical matching the pattern the other three carry, confirming the entry survived under a new name rather than being dropped. ADR-0015's Considered-options parenthetical is re-pointed at docs/spec/architecture.md's plugin scope table, which now carries the repo-agnostic-versus-marketplace-specific argument the deleted entry held, and its existing 2026-08-17 supersession note is extended to record that second redirect in one place. Impact: all four ADRs that referenced moved CONTEXT.md content now say where the content went. No decision is altered. --- docs/adr/0007-gitea-canonical-issue-tracker.md | 2 +- docs/adr/0015-apm-replaces-plugin-marketplace-authoring.md | 6 ++++-- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/adr/0007-gitea-canonical-issue-tracker.md b/docs/adr/0007-gitea-canonical-issue-tracker.md index 7cd7d7a..e79313b 100644 --- a/docs/adr/0007-gitea-canonical-issue-tracker.md +++ b/docs/adr/0007-gitea-canonical-issue-tracker.md @@ -18,4 +18,4 @@ Three alternatives were rejected. Keeping the file-based fallback adds code comp 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. +The "Provider-agnostic issue tracker" glossary entry in CONTEXT.md is updated in the same workstream to remove the file-based phase framing. (Amended 2026-08-17: the CONTEXT.md trim renamed that entry to **Issue**; it still records Gitea as this repo's canonical tracker and still tells skills to say "linked issue" generically.) The `providers/gitea/` adapter path described in ADR-0011 was never implemented — Gitea integration runs entirely via MCP, not a provider adapter. diff --git a/docs/adr/0015-apm-replaces-plugin-marketplace-authoring.md b/docs/adr/0015-apm-replaces-plugin-marketplace-authoring.md index d8fb9d3..eedcc21 100644 --- a/docs/adr/0015-apm-replaces-plugin-marketplace-authoring.md +++ b/docs/adr/0015-apm-replaces-plugin-marketplace-authoring.md @@ -57,7 +57,9 @@ new hand-maintained manifest format. - `CONTEXT.md`'s "Plugin"/"Plugin marketplace" glossary entries were rewritten in issue #90 to describe the compiled-output model directly, rather than carrying a forward-pointer to this ADR. Superseded 2026-08-17: CONTEXT.md was cut back to one-line definitions, and the compiled-output - model is now described in `docs/spec/architecture.md`. + model is now described in `docs/spec/architecture.md`. The same trim deleted the "lint plugin" + entry cited under Considered options below; that pointer now reads `docs/spec/architecture.md`'s + plugin scope table, which carries the repo-agnostic-versus-marketplace-specific argument. ## Considered options @@ -68,7 +70,7 @@ maintenance in place unchanged. **New standalone `plugins/apm/` plugin (rejected).** `plugins/lint/` was split out of `kyberforge` specifically because Vale tooling is generic and repo-agnostic, not holocron-marketplace-specific -(see `CONTEXT.md`'s "lint plugin" entry) — the same argument applies to a generic `apm` CLI +(see `docs/spec/architecture.md`'s plugin scope table) — the same argument applies to a generic `apm` CLI wrapper. The shipped `apm-install`/`apm-workflow` skills are, in fact, generic, repo-agnostic APM CLI documentation with no holocron-specific content, so a standalone `plugins/apm/` would have been a defensible split on artifact content alone. Rejected anyway, in favor of `kyberforge`,