dl/aid report which install they are

[blooop]

Destination

dl --version (and aid --version) says which install it is — the released pixi-global build or the editable dev install from a working tree — so that "I pulled main but aid still does the old thing" diagnoses itself instead of reading as a failed merge.

Done looks like: running dl --version and dl-next --version on the same machine produces visibly different output, with the dev build naming the tree it resolves to.

Notes

Single-ticket map: known work, no fanning.

Motivating incident: PR #82 merged and was pulled, but aid blooop/devlaunch@t1 "test prompt" still failed with claude: command not found. Both builds report bare dl 0.0.9, so nothing at runtime distinguished the released binary (which predated the fix) from the tree (which had it). Roughly 20 minutes went into re-diagnosing a bug that was already fixed. The two-install split is deliberate and documented in CLAUDE.md — this ticket does not change it, only makes it observable.

Discriminator is PEP 610 direct_url.json, already present for both installs and containing no hardcoded user path in the check itself:

• dev: {"url": "file:///…/devlaunch", "dir_info": {"editable": true}}
• released: {"dir_info": {}, "url": "file:///home/runner/work/…"}

Constraint from CLAUDE.md: never hardcode a /home/<user> path. Read the path from metadata, never assume it.

[blooop]

Resolution

Done. The only ticket, #84, is closed — PR #85 merged.

dl --version and dl-next --version now produce visibly different output on the same machine, with the dev build naming the tree it resolves to, so a stale released binary is self-diagnosing instead of reading as a failed merge.

Closing the map with its ticket.