Ruling needed: per-app launcher praxis field vocabulary before the 21-descriptor migration #1226

#42 follow-through: standards-owned descriptor vocabulary ruling requested

Following AC2's owner ruling to migrate the 21 per-app descriptors to DEED, launch-scaffolder has a local design, not a deployed migration: docs/per-app-launcher-descriptor-deed.adoc chooses <app>.launcher_praxis.deed and #u5"estate/chora", maps typed fields and has local valid/invalid parsing fixtures. The runner still only consumes legacy TOML-named .launcher.a2ml; there is no read/write/read descriptor writer, dual accept, reviewed rename manifest, or conversion of estate repos. This is not AC2 execution.

The standard must name the per-app praxis vocabulary once before we can convert data without loss. In particular: [integration] and [exceptions] are currently untyped toml::Value in crates/launcher-common/src/config.rs; the local design marks them F1/F2, proposes an opaque quoted carry for integration and ordered repeated (override ...) for exceptions, but does not claim authority to turn these proposals into a normative estate vocabulary. Please rule the field set, exact opaque/typed encoding and escaping, unknown-field behaviour, list/override order, and ownership of that declaration. A TOML key with no deed equivalent should block conversion rather than vanish. Pair independent positive/negative conformance fixtures with the ruling, and require an old/new path manifest reviewed before any move, followed by a stated dual-accept overlap.

Current standards/main 3108c1b: the normative ABNF under 1-formats/deed/spec/abnf/deed.abnf has advanced to v1.1.0 (2026-10-07; UUIDv8 added, UUIDv5 remains legal). The local design's v1.0.0 citation is now dated but its UUIDv5 shape is not invalidated. Launcher :standard-version is separately 0.6.0; local conformance fixture/document still cite 0.4.0 and must be refreshed deliberately after canon alignment. No changes to canonical documents or live descriptors are asserted by this comment.

Refs hyperpolymath/launch-scaffolder#42, #41, #65; standards#1225 for the separate canonical launcher metadata/fallback ruling.