fix: preserve initiating CLI for lifecycle children

[patrickleet]

Summary

• carry the canonical absolute executable that initiated a discovered lifecycle through build, dev, UI, and framework child processes
• make lifecycle-owned SvelteKit compilation use that identity even when a project command or an older distributed binary appears first on PATH
• fail closed when lifecycle ownership is declared without a valid absolute executable identity
• in lifecycle-owned mode invoke that initiating executable directly; standalone launcher prefixes are intentionally not forwarded into the trusted lifecycle command
• keep standalone Vite command selection and the compatibility file-adapter path unchanged

Verification

• cargo test -p distributed_cli lifecycle:: --lib -- --nocapture (27 passed)
• npm run check
• npm run build
• node --test tests/sveltekit-vite.test.mjs (21 passed)
• executor regression covers an initiating executable path containing spaces, a shadowing older PATH executable, and lifecycle-owned execution without a standalone launcher prefix

This stacks on the lifecycle-obligation fix in PR #243.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: c90e88f8-1f2c-4266-a8cf-e1de707c776d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.}