From 45e0f6e896b2c34de25d5c3aa18474c79d6a1e72 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Mon, 15 Jun 2026 10:24:40 -0500 Subject: docs: move specs to docs/specs/ with lifecycle-status filenames Separate the 27 formal specs from working notes. Specs move to docs/specs/, notes stay in docs/design/. Each spec carries its lifecycle in the filename (-spec, -spec-doing, -spec-implemented, -spec-superseded) plus an authoritative ID and STATUS property drawer. The status came from checking each spec against the code, not the doc's own field: 6 implemented, 8 in progress, 12 not started, 1 superseded. Inbound links become org-id links so future status renames don't break them; code-comment paths repoint to docs/specs/. Working notes, inventories, reviews, and brainstorms stay in docs/design/. --- modules/coverage-core.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'modules/coverage-core.el') diff --git a/modules/coverage-core.el b/modules/coverage-core.el index 0a8b2464f..687a042fe 100644 --- a/modules/coverage-core.el +++ b/modules/coverage-core.el @@ -17,7 +17,7 @@ ;; intersects the results, and displays a report buffer. Languages ;; plug in via the backend registry (see `cj/coverage-backends'). ;; -;; See docs/design/coverage.org for the design rationale. +;; See docs/specs/coverage-spec-implemented.org for the design rationale. ;;; Code: -- cgit v1.2.3