From 7096f749f01ddaaf6a826bb2ebcb022e9ccf6529 Mon Sep 17 00:00:00 2001 From: JDoc Date: Wed, 7 Oct 2026 13:32:14 -0400 Subject: [PATCH] docs(contributing): say when an enhancement is retired An enhancement leaves once the product ships an equivalent, or once a declined proposal no longer earns its place in demos. Upstream discussion is tracked outside this public repo. Closes #7 Co-Authored-By: Claude Opus 5.5 --- CONTRIBUTING.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 9defa4d..4ba12d9 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -22,6 +22,10 @@ Ordinary git and GitHub practice — opening an issue, naming a branch, writing See [`docs/security.md`](docs/security.md) for the extension's security model and a reviewer checklist. +## When an enhancement is retired + +An enhancement is a proposal, so it has an end. **Retire it once the product ships an equivalent** — delete its file and its registry entry in a small PR — or when the proposal is declined and it no longer earns its place in demos. Discussion with the product team about a proposal happens, and is tracked, **outside this repo**; nothing here links to it, and an enhancement's text does not record how it was received (see *Public repository* above). + ## Workflow Issue → worktree → PR → squash-merge → **reload the extension from the primary checkout**.