docs(specs): drop the spec names used before the renumbering

- The specs index no longer carries a table mapping the three original spec names to the renumbered ones, and spec headers no longer record a feature branch or "first written as" name.
- A task that pointed at research under the old 001 directory now points at its current path, so every reference resolves to a spec that exists.
- The constitution's 1.4.1 amendment still records that the specs were split and renumbered, without listing the retired names.

.specify/memory/constitution.md

@@ -229,5 +229,4 @@ stops when the user quits entirely (feature 014-mac-app-store-mode, research R-0
 stays a separate process, so a crash in the window still disturbs no connection.
 
 Amendment 1.4.1 (2026-09-27): wording only. The specifications were split into one per
-capability and renumbered by topic, so the features named above are cited by their new names:
-the Windows port was 002-windows-support and the App Store mode 003-mac-app-store-mode.
+capability and renumbered by topic, and the features named above cite the current specs.

specs/001-service-and-clients/contracts/cli-interface.md

@@ -1,6 +1,6 @@
 # Contract: Command-Line Interface
 
-**Feature**: 001-service-and-clients, first written as 001-midi-connectivity-manager | **Version**: 1.0 | **Date**: 2026-09-20
+**Feature**: 001-service-and-clients | **Version**: 1.0 | **Date**: 2026-09-20
 
 The user-facing contract for the `midi-harbor` executable. Governed by FR-039 through FR-039h and
 FR-042. Every command here is a thin projection of the [IPC protocol](./ipc-protocol.md); the CLI

specs/001-service-and-clients/contracts/ipc-protocol.md

@@ -1,6 +1,6 @@
 # Contract: Daemon gRPC Protocol
 
-**Feature**: 001-service-and-clients, first written as 001-midi-connectivity-manager | **Protocol**: `midiharbor.v1` | **Date**: 2026-09-20
+**Feature**: 001-service-and-clients | **Protocol**: `midiharbor.v1` | **Date**: 2026-09-20
 
 The contract between `midi-harbor daemon` and its clients (the GUI and the CLI). Governed by
 FR-036, FR-037, FR-039c, FR-040, FR-041 and Constitution Principle II.

specs/001-service-and-clients/data-model.md

@@ -1,6 +1,6 @@
 # Data Model: Midi Harbor
 
-**Feature**: 001-service-and-clients, first written as 001-midi-connectivity-manager | **Date**: 2026-09-20
+**Feature**: 001-service-and-clients | **Date**: 2026-09-20
 
 This document defines the domain entities, their fields, relationships, validation rules, and
 state transitions. It is the vocabulary shared by the daemon, the IPC contract, the CLI, and the

specs/001-service-and-clients/plan.md

@@ -1,6 +1,6 @@
 # Implementation Plan: Midi Harbor — MIDI Connectivity Manager
 
-**Branch**: `001-midi-connectivity-manager`, this spec's original name | **Date**: 2026-09-20 | **Spec**: [spec.md](./spec.md)
+**Date**: 2026-09-20 | **Spec**: [spec.md](./spec.md)
 
 **Input**: Feature specification from `/specs/001-service-and-clients/spec.md`
 
@@ -108,7 +108,7 @@ decisions strengthened compliance rather than eroding it:
 ### Documentation (this feature)
 
 ```text
-specs/001-service-and-clients/   # first written as 001-midi-connectivity-manager
+specs/001-service-and-clients/
 ├── plan.md              # This file, the architecture of the whole project
 ├── spec.md              # The service and its clients; the original input
 ├── research.md          # Architecture findings and the tracked risks

specs/001-service-and-clients/quickstart.md

@@ -1,6 +1,6 @@
 # Quickstart & Validation Guide: Midi Harbor
 
-**Feature**: 001-service-and-clients, first written as 001-midi-connectivity-manager | **Date**: 2026-09-20
+**Feature**: 001-service-and-clients | **Date**: 2026-09-20
 
 Runnable scenarios that prove the feature works end to end. Each maps to user stories and success
 criteria in the spec it validates. Scenarios are ordered so that each is useful on its own — you can

specs/001-service-and-clients/research.md

@@ -1,6 +1,6 @@
 # Research: Service and Clients
 
-**Feature**: 001-service-and-clients, first written as 001-midi-connectivity-manager | **Date**: 2026-09-20
+**Feature**: 001-service-and-clients | **Date**: 2026-09-20
 
 All crate versions below were resolved against crates.io on 2026-09-20. Findings marked
 **VERIFIED** were proven empirically in this repository's environment (macOS 15.6, Apple Silicon,

specs/001-service-and-clients/spec.md

@@ -1,7 +1,5 @@
 # Feature Specification: Midi Harbor — Service and Clients
 
-**Feature Branch**: `001-midi-connectivity-manager` (this spec's original name)
-
 **Created**: 2026-09-20
 
 **Status**: Implemented

specs/001-service-and-clients/tasks.md

@@ -46,7 +46,7 @@ any dependency is committed to.
 ### Stage 0 spikes (retire RISK-2 and RISK-3 before committing dependencies)
 
 - [x] T009 [P] Spike in `spikes/platform-midi/` proving direct `coremidi` 0.9 virtual endpoint creation with `kMIDIPropertyUniqueID` retrieval and `MIDINotifyProc` device notifications, and the `alsa` 0.12 sequencer equivalent — validates the R-003 decision to skip `midir`
-- [x] T010 Record spike outcomes in `specs/001-midi-connectivity-manager/research.md`, updating R-003, R-005, R-006 status from ASSUMED to VERIFIED or switching to the documented fallback; if the BLE peripheral spike fails, add the Complexity Tracking row in `plan.md` and the declared limitation in `.specify/memory/constitution.md`
+- [x] T010 Record spike outcomes in `specs/001-service-and-clients/research.md`, updating R-003, R-005, R-006 status from ASSUMED to VERIFIED or switching to the documented fallback; if the BLE peripheral spike fails, add the Complexity Tracking row in `plan.md` and the declared limitation in `.specify/memory/constitution.md`
 
 **Checkpoint**: Dependencies are proven, not assumed. Fallbacks are chosen explicitly.
 

specs/013-windows-support/plan.md

@@ -1,6 +1,6 @@
 # Implementation Plan: Windows support
 
-**Branch**: `002-windows-support`, this spec's original name | **Date**: 2026-09-26 | **Spec**: [spec.md](./spec.md)
+**Date**: 2026-09-26 | **Spec**: [spec.md](./spec.md)
 
 **Input**: Feature specification from `/specs/013-windows-support/spec.md`
 

specs/013-windows-support/research.md

@@ -1,6 +1,6 @@
 # Research: Windows support
 
-**Feature**: 013-windows-support, first written as 002-windows-support | **Date**: 2026-09-26
+**Feature**: 013-windows-support | **Date**: 2026-09-26
 
 Numbered after the original specification's research, whose last entry was R-082, so every R number in the
 project names one entry. Findings marked **VERIFIED** were measured on the Windows test machine:

specs/013-windows-support/spec.md

@@ -1,7 +1,5 @@
 # Feature Specification: Windows support
 
-**Feature Branch**: `002-windows-support`, this spec's original name
-
 **Created**: 2026-09-26
 
 **Status**: Implemented

specs/014-mac-app-store-mode/plan.md

@@ -1,6 +1,6 @@
 # Implementation Plan: Mac App Store mode
 
-**Branch**: `003-mac-app-store-mode`, this spec's original name | **Date**: 2026-09-27 | **Spec**: [spec.md](./spec.md)
+**Date**: 2026-09-27 | **Spec**: [spec.md](./spec.md)
 
 **Input**: Feature specification from `/specs/014-mac-app-store-mode/spec.md`
 
@@ -95,7 +95,7 @@ design below: no change.
 ### Documentation (this feature)
 
 ```text
-specs/014-mac-app-store-mode/   # first written as 003-mac-app-store-mode
+specs/014-mac-app-store-mode/
 ├── plan.md              # This file
 ├── research.md          # R-094 to R-100
 ├── data-model.md        # Window state at quit, login item status

specs/014-mac-app-store-mode/research.md

@@ -1,6 +1,6 @@
 # Research: Mac App Store mode
 
-**Feature**: 014-mac-app-store-mode, first written as 003-mac-app-store-mode | **Date**: 2026-09-27
+**Feature**: 014-mac-app-store-mode | **Date**: 2026-09-27
 
 Numbered after the Windows port's research (013), whose last entry is R-093. Findings marked **VERIFIED**
 were measured on the development Mac (macOS 15, Darwin 24.6, Apple silicon) with the app

specs/014-mac-app-store-mode/spec.md

@@ -1,7 +1,5 @@
 # Feature Specification: Mac App Store mode
 
-**Feature Branch**: `003-mac-app-store-mode`, this spec's original name
-
 **Created**: 2026-09-27
 
 **Status**: Implemented

specs/README.md

@@ -136,13 +136,3 @@ exception is 014, whose task list started again at T001: its T001 to T034 are ci
 - **Success criteria**: SC-S01
 - **Research**: R-103
 - **Tasks**: T245
-
-## Earlier names
-
-Until 2026-09-27 there were three specs. Branches, commit messages and older notes use these names.
-
-| Earlier | Now |
-|---|---|
-| `001-midi-connectivity-manager` | Split into 001 to 010: the service and command line stayed in [001](001-service-and-clients/spec.md), each capability moved to its own spec, and the tasks added since for the MIDI service crash and the test note became 011 and 012 |
-| `002-windows-support` | [013-windows-support](013-windows-support/spec.md) |
-| `003-mac-app-store-mode` | [014-mac-app-store-mode](014-mac-app-store-mode/spec.md) |