fix(launcher): cite the .deed standard at v0.4.0 (standards#960 AC3)

[hyperpolymath]

19 citations in this repo named launcher-standard.a2ml v0.3.0. That file was deleted upstream on 2026-09-22 by hyperpolymath/standards#952 (be6c9580, owner ruling D73-C) and translated to launcher/launcher-standard_praxis.deed. Every one of these pointed at a path that no longer resolves.

This is AC3 of hyperpolymath/standards#960.

Why the v0.4.0 claim is earned, not assumed

Rewriting v0.3.0 → v0.4.0 is a compliance claim, not a rename, so it had to be checked rather than swept. The deed states its own delta at lines 22–24:

Bumped 0.3.0 -> 0.4.0 because the resolution ladders below now name the .deed file, which is consumer-visible.

That delta lands entirely in (resolution (standard-search — the ladder a consumer uses to locate the standard at runtime. This launcher never reads the standard at runtime: it inlines the (resolution (desktop-tools-search ladder, whose six priorities match the deed's in the same order and are untouched by 0.4.0. So nothing 0.4.0 added is unimplemented here. If that had not held, the honest move would have been to name 0.4.0 and record the gap — it did hold.

Why this is safe

Comments only, with one deliberate exception: the --version output prints a Standards Compliance: line, rewritten because a compliance claim has to name the standard that exists. The deed's (version-output clause constrains only :first-line-format, which is untouched and still conforms.

bash -n passes. The launcher was not executed — it sources keepopen.sh unconditionally at top level.

No consumer breaks. launch-scaffolder's metadata parser keys on a literal # @a2ml-metadata begin delimiter (metadata_block.rs:109); this launcher has no such line and is not parseable by it today, before or after this change. All eleven fields the deed's (metadata-block :required-fields demands are present and untouched.

Clause notation

§x → (x ...), the deed's s-expression heads. Three were not mechanical and were each verified against the deed rather than guessed:

was	now	why
§a2ml-metadata-block	(metadata-block ...)	the deed's only clause rename, authorised by its own comment: "A2ML is a dead format name and the deed era does not carry it forward"
§disinteg.remove	(disinteg :remove ...)	:remove is a key on (disinteg, not a subclause — deed:228
"ladder from launcher-standard.a2ml"	(resolution (desktop-tools-search ...))	the deed has two ladders; this one resolves .desktop-tools, so it is the first, not (fallback-ladder

The old filename is deliberately not carried as a "formerly …" gloss. The #960 AC4 gate flags a retired filename at any version, by design — the history belongs in the commit message, not in the source.

Proved

The AC4 gate (scripts/check-launcher-standard-currency.sh, hyperpolymath/standards#983) run against this worktree:

• before: 23 defect rows over 19 lines, rc=1 — four lines carry both a retired-filename and a stale-version defect, which is why 19 lines yield 23 rows
• after: No stale launcher-standard references., rc=0

This is also the gate's first run against a hand-written launcher rather than a generated descriptor.

What is deliberately left alone

dev-notes/HANDOVER.adoc keeps its two v0.3.0 citations. It carries :revdate: 2026-08-13 on its face and is a historical record; the gate allowlists it by path for exactly that reason. Rewriting a handover to name a file that did not exist at handover time would falsify the record.

Refs hyperpolymath/standards#960 · hyperpolymath/standards#952 · hyperpolymath/standards#983

🤖 Generated with Claude Code

https://claude.ai/code/session_01WPSJ7fBhVAMcpSffCBWUDo

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: e1775d57-9fcd-4a72-ad18-554c21b1174e

📥 Commits

Reviewing files that changed from the base of the PR and between 805da6d and 26b032f.

📒 Files selected for processing (2)

• docs/IMPLEMENTATION-STATUS.adoc
• scripts/trigger-launcher.sh

 __________________________________________________________________
< Series-B funding secured. Now, I can afford to review your code. >
 ------------------------------------------------------------------
  \
   \   (\__/)
       (•ㅅ•)
       / 　 づ

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• 🔴 Error committing to branch - (🔄 Check to retry)
• Create a new PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

❌ Failed to create Coding Agent finishing-touch task. Please try again.