Discovered immediately while stacking Walk #67 on merged Leash #94/#95. The CLI accepts --idmap-volume, but leash version --json still advertises only the prior capability set and contract 1, so Walk cannot safely distinguish a supporting Leash from an older binary before launch. Scraping --help would be a brittle workaround and is rejected. Acceptance: add a stable machine-readable idmap-volume capability to the existing version document for builds that support the flag; keep capability ordering/deduplication deterministic; add version JSON and CLI regression coverage; preserve the existing contract version unless the repository rules require a bump for additive capabilities; document the capability where the version contract is enumerated. Walk #67 must probe this capability and fail before workload execution when absent.
Discovered immediately while stacking Walk #67 on merged Leash #94/#95. The CLI accepts --idmap-volume, but
leash version --jsonstill advertises only the prior capability set and contract 1, so Walk cannot safely distinguish a supporting Leash from an older binary before launch. Scraping--helpwould be a brittle workaround and is rejected. Acceptance: add a stable machine-readableidmap-volumecapability to the existing version document for builds that support the flag; keep capability ordering/deduplication deterministic; add version JSON and CLI regression coverage; preserve the existing contract version unless the repository rules require a bump for additive capabilities; document the capability where the version contract is enumerated. Walk #67 must probe this capability and fail before workload execution when absent.