D73-C downstream: 21 launcher descriptors + trigger/ still name the deleted launcher-standard.a2ml

[hyperpolymath]

21 downstream launcher descriptors now name a file that no longer exists

D73-C (owner ruling, #787) translated launcher/launcher-standard.a2ml to launcher/launcher-standard_praxis.deed and deleted the source. #952 merged 2026-09-22T10:10:04Z as be6c9580, verified against origin/main: launcher/launcher-standard.a2ml is absent, launcher/launcher-standard_praxis.deed is present.

That closes the standards side. It does not touch the downstream surface, which this issue records so it is not lost. These references are now dangling, not merely stale.

Measured 2026-09-22

A. *.launcher.a2ml descriptors — 21 distinct, 31 on-disk paths

Found with rg --files -g '*.launcher.a2ml', excluding .claude/worktrees/. The path count exceeds the distinct count because several repos are cloned twice (once under meta-repos/, once under hyper-repos/metadatastician/).

688-attack-hub   aerie   berrywiki   boj-server-mk2   burble   cadastra
canonical-ums    cerro-torre   chronicles-of-slavia   enaction-engine
f117a-stealth-glider   f19-stealth-glider   game-server-admin   gossamer
idaptik-ums   nqc   paint-type   panll   progblocks   stapeln
the-nash-equilibrium

Every one sampled carries the same two lines:

# Compliant with launcher-standard.a2ml v0.3.0
...
# Per launcher-standard.a2ml [runtime] section:

So each names both the deleted file and the TOML [section] notation that the DEED form replaces with (runtime ...) clauses.

⚠ A prior note in this campaign recorded this population as 10. That was a 2× undercount — the real figure is 21 distinct. Recorded because the estate has hit "a census is wrong in both directions at once" repeatedly, and the corrected number is the one to work from.

B. The trigger repo is a live consumer

hyper-repos/trigger has 3 files naming launcher-standard.a2ml, and one of them is an actual launcher implementation, not documentation:

• scripts/trigger-launcher.sh — cites launcher-standard.a2ml v0.3.0 and resolves desktop tools "using ladder from launcher-standard.a2ml"; also names §a2ml-metadata-block, §default-mode, §required-modes.
• dev-notes/HANDOVER.adoc
• docs/IMPLEMENTATION-STATUS.adoc

This one matters more than the descriptors: it is code that claims compliance with a standard whose canonical form has changed.

Acceptance criteria

1. No file in a writable repository outside hyperpolymath/standards names launcher-standard.a2ml except in a dated historical record that says so on its face. An archived repository is out of scope by definition — it is read-only, so the criterion would demand an impossible write (AGENTS.md §6: refusing an impossible operation is required, not optional). (Wording amended 2026-09-22 by owner ruling; see the AC1 closure comment.)
2. The 21 descriptors either migrate to the .deed form or are explicitly declared out of scope for D73-C with a reason recorded here — decided, not left to decay.
3. trigger/scripts/trigger-launcher.sh cites launcher-standard_praxis.deed and DEED clause notation, and its claimed version is the current one.
4. A check that fails if a repo claims launcher-standard compliance while naming a version or filename that no longer exists upstream.

Deliberately not asserted

These 21 files are part of the wider superseded-A2ML surface (owner ruling 2026-09-08, executed by a2ml#2), not solely a D73-C consequence. This issue records the launcher-shaped subset and its true size; it does not claim the whole A2ML migration.

Refs #837 · #952 · owner ruling D73-C in #787

🤖 Generated with Claude Code

https://claude.ai/code/session_01WPSJ7fBhVAMcpSffCBWUDo

[hyperpolymath]

Status: AC3 and AC4 are done and merged. AC1 is done for trigger only. AC2 is an owner decision and is the one thing outstanding.

AC3 — ✅ MERGED

trigger/scripts/trigger-launcher.sh now cites launcher-standard_praxis.deed, DEED clause notation, and the current version. Landed as hyperpolymath/trigger#14, merged 2026-09-22T13:13:56Z.

AC4 — ✅ MERGED

scripts/check-launcher-standard-currency.sh fails a repo that claims compliance while naming a version or filename that no longer exists upstream. Landed as #983, squash edac0d6a on main.

Verified against the merged tree (git archive origin/main), not just the PR branch:

check-launcher-standard-currency: canonical=launcher-standard_praxis.deed expected=v0.4.0
No stale launcher-standard references.
gate rc=0

=== summary: 19 passed, 0 failed ===

⚠ Vocabulary, per AGENTS.md §6 — implemented and tested, but NOT wired.

• Its 19 controls do run in CI: scripts/tests/…-test.sh is discovered by scripts/run-shell-test-suite.sh, which self-test.yml invokes. Green on edac0d6a itself.
• The gate is invoked by no workflow in any repo. It is a tool that works and is tested; it is not yet enforcing anything on anybody. Wiring it is separate work and is not claimed here.

The historical-record exemption is a path allowlist, never a content heuristic. Test section 7 asserts the allowlist absorbs exactly the four in-tree occurrences (the conversion mapping doc, two dated audit records, the deed's own ;; provenance header) and has not been widened into a blanket.

AC1 — ✅ for trigger, ❌ for the descriptors

trigger's remaining occurrence is in dev-notes/HANDOVER.adoc, which carries :revdate: 2026-08-13 — a dated historical record that says so on its face, which is exactly what AC1 exempts.

The 26 citing descriptor paths are not exempt and are the open part of AC1.

The census — this issue's own figure of 21 was right

I published a corrected figure of "23 distinct descriptors" in #983 and in the conversion mapping doc. That was wrong and this issue was right. #984 corrects it on main, in place and dated. Measured scoped to hyper-repos + meta-repos, with nested worktrees verified absent:

metric	value
*.launcher.a2ml paths on disk	31
distinct descriptor basenames	21 ← matches this issue
paths citing the deleted launcher-standard.a2ml	26
distinct descriptors citing it	17
distinct upstream repositories affected	18 ← this is the PR count
citing lines	66

Path counts are dated and decay as clones are added; the distinct counts do not.

The 18 repos: hyperpolymath/the-nash-equilibrium, and under metadatastician/ — 688-attack-hub, berrywiki, boj-server-mk2, burble, cadastra, canonical-ums, cerro-torre, chronicles-of-slavia, enaction-engine, f117a-stealth-glider, f19-stealth-glider, gossamer, idaptik-ums, paint-type, progblocks, stapeln, universal-modding-studio.

⭐ The fact that makes AC2 decidable: every citation is a # comment

All 66 lines, in six shapes:

25 × # Compliant with launcher-standard.a2ml v0.3.0
17 × # Per launcher-standard.a2ml [version-output] section
17 × # Per launcher-standard.a2ml [runtime] section:
 2 × # Use standard defaults from launcher-standard.a2ml §integration.linux.
 2 × # Standard: launcher-standard.a2ml v0.2.0
 2 × #           (developer-ecosystem/standards/launcher/launcher-standard.a2ml)

Nothing structural. Verified that no template or emitter in launch-scaffolder writes any of these strings, so hand-edits would not be regenerated away — this is not the generator-defect shape.

Two further defects visible in the text, fixable in the same pass:

• [version-output] / [runtime] is doubly wrong — wrong file and wrong clause notation. The deed uses s-expression heads; (version-output and (runtime are real clause heads in launcher-standard_praxis.deed at lines 115 and 122.
• developer-ecosystem/standards/launcher/launcher-standard.a2ml is a path that does not exist.

This separates AC2 into two things one framing conflates

	blocked?
(a) the file extension .launcher.a2ml → something else	Yes — by R-G's dual-accept rule, until the @a2ml-metadata compat reader lands (launch-scaffolder#40)
(b) the citation text inside them	No — comment-only, independent of the extension, structurally identical to the trigger fix already merged in AC3

AC2 as written asks whether the 21 descriptors migrate to the .deed form or are declared out of scope for D73-C with a reason recorded here — decided, not left to decay. Note that a .deed filename is a closed dispatch set of four (estate_chora / ATLAS / *_praxis / *_chora), so "convert <app>.launcher.a2ml to .deed" cannot yield <app>.launcher.deed; and a deed admits no key = value and no [section], so converting these TOML-shaped descriptors is a rewrite, not a rename.

Both halves are now going to the owner through the selection UI. Nothing further is blocked on measurement.

Also out of scope, recorded so it is not lost

docs/UX-standards/launcher-standard.adoc declares no version, yet two files cite it at v0.2.0 — docs/audits/launcher-standard-review-2026-05-26.adoc:33 and docs/UX-standards/LM-LA-LIFECYCLE-STANDARD.adoc:61. Deliberately outside AC4's scope.

Related: #983, #984, launch-scaffolder#40, launch-scaffolder#41, hyperpolymath/trigger#14.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WPSJ7fBhVAMcpSffCBWUDo

[hyperpolymath]

⚠ Correction to the line-shape table in my comment above

The six shapes and the total of 66 are right; four of the six counts were not. I derived them by subtracting the worktree duplicates rather than re-measuring, and they sum to 65. Measured:

25 × # Compliant with launcher-standard.a2ml v0.3.0
19 × # Per launcher-standard.a2ml [version-output] section
19 × # Per launcher-standard.a2ml [runtime] section:
 1 × # Use standard defaults from launcher-standard.a2ml §integration.linux.
 1 × # Standard: launcher-standard.a2ml v0.2.0
 1 × #           (developer-ecosystem/standards/launcher/launcher-standard.a2ml)
                                                              sum = 66 ✓

Two things this makes clearer than the wrong table did:

• The three one-off lines are all in the same file — the-nash-equilibrium.launcher.a2ml, the single hyperpolymath/-owned descriptor and the only one still at v0.2.0. It is the sole outlier; the other 17 descriptors are uniform.
• The wrong [version-output] / [runtime] bracket notation appears 19 times each, in 19 of the 26 citing paths — so the doubly-wrong clause notation is the bulk of the work, not an edge case.

Nothing else in the comment above changes: 31 paths, 21 distinct descriptors, 26 citing paths, 17 distinct citing, 18 upstream repos.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WPSJ7fBhVAMcpSffCBWUDo

[hyperpolymath]

⚖ Owner rulings 2026-09-22 — AC1 and AC2 are both decided

Both outstanding decisions on this issue have been ruled through the owner selection UI. With these, all four acceptance criteria are settled in principle; what remains is execution on AC1.

AC	state after these rulings
AC1 — no file outside standards names launcher-standard.a2ml except in a dated historical record	RULED: fix now. ✅ done for trigger; execution pending for the descriptors
AC2 — the 21 descriptors either migrate to .deed or are declared out of scope for D73-C	✅ CLOSED by this ruling: migrate to .deed
AC3 — trigger-launcher.sh cites launcher-standard_praxis.deed + DEED clause notation + current version	✅ MERGED (trigger#14, 2026-09-22T13:13:56Z)
AC4 — a check that fails if a repo claims compliance while naming a version/filename that no longer exists upstream	✅ MERGED (#983 → squash edac0d6a)

⚠ AC4 vocabulary, per AGENTS.md §6: the gate is implemented and tested — its 19 controls run green in self-test.yml via scripts/run-shell-test-suite.sh — but it is not wired. No workflow in any repo invokes the gate itself. It is a tool that works and is tested; it enforces nothing yet. That is a separate piece of work and is not claimed here.

---

Ruling 1 — AC2: migrate all 21 descriptors to .deed

AC2 asks for a decision, not for a conversion. Its own wording is "decided, not left to decay" — so this comment closes AC2. The conversion is a separate, gated workstream.

The gate is already ruled, and this is consistent with it

The earlier owner ruling on the emitted @a2ml-metadata launcher header was "compat reader, then convert." This ruling has the same shape: the destination is .deed, and the conversion runs after the compat reader lands (launch-scaffolder#40), under the dual-accept rule — do not migrate extensions before dual-accept, and a dry-run manifest first, never a bulk pass.

Two design questions the migration must answer before a single file moves

Both are measured, not speculative:

1. The name. A .deed filename is a closed dispatch set of four — estate_chora.deed, ATLAS.deed, *_praxis.deed, *_chora.deed. So <app>.launcher.a2ml → <app>.launcher.deed is not an available name. The migration needs either a fifth dispatch case or a mapping onto <app>_chora.deed.
2. The grammar. A deed admits no key = value and no [section]; tabs are invalid; uuid5 only. The descriptors are TOML-shaped ([runtime], [version-output]). This is a rewrite, not a rename — and launch-scaffolder has no per-app config deed grammar today.

These will be filed as one design issue on launch-scaffolder with acceptance criteria, cross-referenced from #40 and #41 and from here, per the standing rule that a new finding becomes an issue rather than a blocker. It sequences behind #40.

---

Ruling 2 — AC1: fix the citation lines now, one small PR per repo

The citation fix is comment-only and entirely independent of the file extension, so it does not wait on the compat reader — which is undated, and coupling a ready fix to an undated one is exactly the decay AC2 forbids. It is structurally identical to the already-merged trigger#14.

The census these rulings act on — final, measured 2026-09-22

Scoped to hyper-repos + meta-repos, with nested worktrees verified absent from the result:

metric	value
*.launcher.a2ml paths on disk	31
distinct descriptor basenames	21 — matches this issue's own figure exactly
paths citing the deleted launcher-standard.a2ml	26
distinct descriptors citing it	17
distinct upstream repos affected	18
citing lines	66

Publish the distinct counts; date the path counts. Fixing a silently-failing worktree exclusion moved only the path counts (36→31, 29→26, 71→66) and left 21 / 17 / 18 unchanged — which is exactly what removing duplicate checkouts should do.

The edit, per line shape

All 66 are # comments. The complete replacement table:

from	to
# Compliant with launcher-standard.a2ml v0.3.0	# Compliant with launcher-standard_praxis.deed v0.4.0
# Per launcher-standard.a2ml [version-output] section	# Per launcher-standard_praxis.deed (version-output ...) clause
# Per launcher-standard.a2ml [runtime] section:	# Per launcher-standard_praxis.deed (runtime ...) clause:
# Use standard defaults from launcher-standard.a2ml §integration.linux.	# Use standard defaults from launcher-standard_praxis.deed (integration ...) clause, linux.
# Standard: launcher-standard.a2ml v0.2.0	# Standard: launcher-standard_praxis.deed v0.4.0
# (developer-ecosystem/standards/launcher/launcher-standard.a2ml)	# (hyperpolymath/standards launcher/launcher-standard_praxis.deed)

The bracket notation is doubly wrong — wrong file and wrong clause notation. The correct s-expression heads are verified present in launcher/launcher-standard_praxis.deed: (version-output at line 115, (runtime at 122, (integration at 184. developer-ecosystem/standards/launcher/launcher-standard.a2ml is a path that does not exist at all.

v0.4.0 is earned, not asserted. Each PR body will state the same delta trigger#14 used: these descriptors do not resolve the standard — the standard's own resolution clause does not apply to them — so citing the current version is a statement of conformance, not of a resolution path.

✅ No generator defect

No template or emitter in launch-scaffolder writes any of these strings. Positive control: the same search restricted by extension fires on five Rust files (deed.rs, standard.rs, lib.rs, metadata_block.rs, deed_corpus.rs), none of which is an emitter; template.rs writes no such string. ⚠ The control was necessary — src/ is absent at that repo's root (the crate lives under crates/), so an unguarded search there would have returned a false negative. Hand-edits to these 26 paths will not be regenerated away.

Scope: 17 PRs + 1 issue

⚠ hyperpolymath/the-nash-equilibrium gets an issue, not a PR. It is on the do-not-merge list (two corrupt remote branches, guard-defective), so a PR there is motion that cannot land. It is also the sole outlier in the corpus: the only hyperpolymath/-owned descriptor, the only one still at v0.2.0, and the carrier of all three one-off line shapes. AC1 will record that one exemption with its reason rather than leaving it as an unexplained residue.

Definition of done for AC1

rg --no-ignore-vcs --hidden -l 'launcher-standard\.a2ml' \
   -g '!**/.claude/worktrees/**' -g '!**/worktrees/**' \
   hyper-repos meta-repos

returns exactly the the-nash-equilibrium paths and the dated historical records (trigger/dev-notes/HANDOVER.adoc, :revdate: 2026-08-13) — nothing else.

⚠ Put a positive control on the filter itself, not only on the query: the output must contain zero worktrees/ paths. A ripgrep -g exclude without a leading **/ matches only at the search root and fails silently — that trap corrupted two generations of this census before it was caught by reading the output rather than trusting the count.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WPSJ7fBhVAMcpSffCBWUDo

[hyperpolymath]

⚠ CORRECTED 2026-09-22. This comment originally cited standards/deed/spec/abnf/deed.abnf:24. That file is a v0.1.0 DRAFT in a peer branch's working tree; the sole normative grammar is 1-formats/deed/spec/abnf/deed.abnf (v1.0.0) on origin/main. The closed-set conclusion is unchanged, but two substantive points below were wrong and are corrected in place. The original text is preserved beneath the corrections.

What changed

1. The recommended name is now <app>.launcher_praxis.deed, not <app>_praxis.deed.

deed.abnf:71 is stem = 1*( ALPHA / DIGIT / "-" / "." / "_" ) — dots are legal in a stem — and :62-64 says so explicitly: "Do NOT split on . — the stem may contain dots." So myapp.launcher_praxis.deed is a legal deed filename with stem myapp.launcher. That makes the rename a suffix swap (.launcher.a2ml → .launcher_praxis.deed) with the existing .launcher infix preserved, rather than a reshaping of every descriptor name. Strictly better than what this comment first proposed, and I missed it only because I read the draft.

2. "Needs no grammar change and is semantically correct" was an overstatement.

That is true of the filename and head only. It is not true of the document. DEED-GRAMMAR-SPEC.adoc:379-414 makes :beholding-chora a required field on a praxis deed, as a uuid5 — "a tool may not declare its own vocabulary, so it must name the chora it reads. A UUID, never a bare filename — a bare filename resolves against nothing." And a WARNING at :405-414 marks the praxis field set provisional for v0.1: fields beyond the required three are "a v0.2 question", because "inventing them is precisely the failure this document exists to stop."

A launcher descriptor's actual substance — [runtime], [version-output], [integration] — has no specified praxis fields. So arm B does not walk in for free; it needs a field vocabulary ruled once.

What makes it tractable anyway: origin/main:launcher/launcher-standard_praxis.deed already beholds #u5"estate/chora" and already carries :standard-version, :standard-date and :compliance beyond the required three. So the question is not whether a praxis deed may carry more fields — it demonstrably does — but which fields, named once, for all 21. That is now the substance of launch-scaffolder#42, and #42's body has been rewritten accordingly.

Net effect on AC2: none. AC2 is closed by the ruling, and the conversion stays gated behind #40. What moved is the design recommendation inside #42.

---

Original comment, as posted

AC2 follow-through: the design issue is filed as hyperpolymath/launch-scaffolder#42.

Writing it up sharpened the naming constraint into something better evidenced than I stated above, and in a way that changes the recommended route — so recording it here rather than only in the issue.

The closed-set claim is confirmed normative, not convention. standards/deed/spec/abnf/deed.abnf:24 carries a closed filename production:

deed-filename = estate-file / atlas-file / praxis-file / repo-file

and the spec marks filename dispatch normative in its own right — the chora-dispatch-exclusion side condition exists precisely because estate_chora.deed also matches *_chora.deed, and it notes that "the grammar alone is not sufficient to dispatch a filename." So <app>.launcher.deed is genuinely unavailable.

What changed is the recommended arm. Above I framed the options as "a fifth dispatch case or a mapping onto <app>_chora.deed". The stem→head table makes _chora the wrong choice: repo-deed means "Noun. What a repo IS. A record." A launcher descriptor is not that.

*_praxis.deed → praxis-deed means "Verb. What a tool DOES. Rules." — which is exactly what a per-app launcher descriptor is. So <app>_praxis.deed needs no grammar change and is semantically correct, and it composes with what already exists: launcher-standard_praxis.deed states the general rules, <app>_praxis.deed states that app's conforming praxis. That is the ⭐ arm in #42.

For completeness, the honest cost of the fifth-head alternative is six sites across three repos — the spec, the ABNF, deed/README.adoc, deed-ecosystem's validator regex and conformance corpus, and launch-scaffolder's pub const DOC_HEADS: [&str; 4] (a fixed-size array, so a typed change in one repo and a silent one in the others). It would also need an owner ruling, since all four existing heads are owner rulings — praxis-deed was ruled on #752 as "a genuine fourth head, not a facet of repo-deed."

None of this affects AC1, which is comment-only and proceeding independently.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WPSJ7fBhVAMcpSffCBWUDo

[hyperpolymath]

⚠ CORRECTION — the AC1 census published on this issue is superseded

The figures I posted earlier (18 repos / 26 files / 66 lines, scoped as
"17 PRs + 1 issue") are wrong in both directions. Measured scope is
25 repos / 30 files / 63 lines, of which 19 repos are actually PR-able.

Recording the correction rather than silently patching, per estate practice.

Why the published figures were wrong — three independent defects

1. Scope error — the sweep was narrower than the criterion.
AC1 says no file names launcher-standard.a2ml. My census ran
rg -g '*.launcher.a2ml', counting only launcher descriptors.

sweep	paths
-g '*.launcher.a2ml' (what I ran)	26
unrestricted (what AC1 says)	76

The 50 extra paths held the damaging citations. A descriptor comment is
inert; live prose is an instruction. The worst example —
hyperpolymath/claude-memory/launch-scaffolder-architecture.adoc — tells future
agents, in the imperative:

How to apply: when editing the prose launcher-standard.adoc, edit
standards/launcher/launcher-standard.a2ml in the same commit.

That instructs an edit to a file standards#952 deleted. No descriptor
citation was ever that harmful.

2. Working-tree error — the census measured peer branches, not main.
Of 34 clone directories holding a citation, exactly one was on main.
Every other sat on a peer session's WIP branch. The tell:
trigger/scripts/trigger-launcher.sh showed 8+ stale citations on disk while
AC3 was recorded MERGED — both were true. The clone was on
chore/bump-standards-pins at c5afab9; origin/main was 7ff9c0a with
0 a2ml mentions and 18 _praxis.deed ones. AC3 is genuinely merged.

Every figure below is now git grep <pattern> origin/main, never a checkout.

3. Repo-identity errors — two archived repos and one rename-redirect.
Found only by probing every repo in the list rather than the two I suspected:

repo	defect
hyperpolymath/tma-mark2	archived — read-only, no PR possible
metadatastician/canonical-ums	archived — read-only, no PR possible
metadatastician/idaptik-ums	redirects to universal-modding-studio — one repo double-counted as two

The historical-record exemption is larger than assumed — and it inverts the ranking

AC1 exempts a dated historical record. Read in context, two repos are already
AC1-compliant, and both are repos a naive count ranked as offenders:

• hyperpolymath/trigger — both hits are in dev-notes/HANDOVER.adoc,
  :revdate: 2026-08-13.
• hyperpolymath/launch-scaffolder — all three hits are provenance:
  standards/launcher-standard_praxis.deed:7 names the translation authority
  ("Translated from launcher/launcher-standard.a2ml under the authority of …
  standards#837, owner ruling D73-C"), and both .machine_readable/6a2/META.a2ml
  hits sit inside dated ADRs — ADR-003 (status = "accepted", superseded)
  and ADR-008 (date = "2026-09-22", supersedes = "ADR-003"), whose own
  text narrates that A2ML was retired and standards#952 deleted the path.

Editing any of those five lines would destroy the record of the migration.
The repo that performed the conversion correctly is the one that looks worst to
a grep -c. Count is not compliance — the exemption has to be decided by
reading context, never by a content heuristic.

Corrected scope

	published	measured on origin/main
repos citing	18	25
files	26	30
lines	66	63
PRs	17	19
issues	1	1
recorded exemptions	1	5

19 PRs · 22 files · 44 lines. The five exemptions:

repo	f/L	reason
hyperpolymath/trigger	1/2	dated historical record — already AC1-compliant
hyperpolymath/launch-scaffolder	2/3	dated ADRs + translation provenance — already AC1-compliant
hyperpolymath/tma-mark2	2/5	archived, read-only
metadatastician/canonical-ums	1/3	archived, read-only
hyperpolymath/the-nash-equilibrium	1/3	DO-NOT-MERGE list (2 corrupt remote branches) — issue, not PR

The two archived repos cannot be brought into AC1 compliance without
unarchiving them. That is an owner call, not mine; flagging rather than acting.

Line shapes — the replacement table was also incomplete

Of the 63 lines, 41 are the six descriptor comment shapes my table covers.
The other 22 are shapes no table existed for: URLs to
standards/tree/main/launcher/launcher-standard.a2ml (now 404), AsciiDoc prose,
a DEBT.adoc governance claim, an emitted # @a2ml standards-compliance
header, and three absolute /var/mnt/eclipse/... paths that never existed at
that path. Those are being classified line by line, not swept by pattern.

⚠ The emitted @a2ml header in tma-mark2/scripts/etma-handler-launcher is
moot here — that repo is archived — but the same header shape is gated behind
the compat reader (launch-scaffolder#40), so its value is a citation fix
while its key stays untouched under the dual-accept rule.

Unchanged

AC2 remains closed by the ruling above (migrate all 21 to .deed, gated behind
launch-scaffolder#40). AC3 ✅ merged and re-verified on origin/main.
AC4 ✅ merged. Only AC1 execution remains.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WPSJ7fBhVAMcpSffCBWUDo