From 3c899babc063eac759834d00f2669fdda0a40175 Mon Sep 17 00:00:00 2001 From: rldyourmnd Date: Sat, 29 Aug 2026 04:50:09 +0500 Subject: [PATCH] chore(harness): stop naming the retired line in the bridge comment The comment explaining why the archived harness application line is absent named it anyway. The instruction was that archived material leaves the live system including its mentions, and a file that says "X is not named here" has named X. The explanation is kept and points at ADR 0037 and ADR 0036, which is where the history belongs. The bridge now contains no retired identity in any form. Claude-Session: https://claude.ai/code/session_01GFeam4oG1UnwF9r55pXEyp --- harnesses/module-bridge.yaml | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/harnesses/module-bridge.yaml b/harnesses/module-bridge.yaml index 9382d2b..b5bf387 100644 --- a/harnesses/module-bridge.yaml +++ b/harnesses/module-bridge.yaml @@ -9,13 +9,14 @@ evidence_owner: runtime_tests: required: false -# Seven harnesses, seven setup systems, one mapping each. The retired -# `nddev-*-app` line is archived and is not named here -- not as a module, -# not as an alias. A bridge is a statement about what exists. +# Seven harnesses, seven setup systems, one mapping each. The retired harness +# application line is archived and is deliberately not named in this file -- +# not as a module, not as an alias. A bridge is a statement about what exists; +# ADR 0037 holds the history. # # `harness_id` is the ai-stp contract value and is never derived from the -# module name. That derivation is how `antigravity-cli` and `cursor-cli` -# were once invented here. +# module name. Deriving it from a module name is how two identities here were +# once invented, which ADR 0036 records. mappings: - module_id: "antigravity-setup-system" harness_id: "antigravity"