feat(client): add tracked option for env IPC

[wan9chi]

Motivation

Some tools need to ask the runner for env values without making those reads cache dependencies. The default should stay safe, but callers need an explicit opt-out for env reads that only affect diagnostics or optional behavior.

Scope

Add a tracked flag to both getEnv and getEnvs IPC requests and Rust/Node clients. The option defaults to true; tracked: false still serves the env value or match set but filters that read out of the post-run cache fingerprint. IPC records keep the tracked flag monotonic so a later tracked read of the same name or pattern wins over an earlier untracked read.

This PR is intentionally placed after the getEnvs fingerprint PR so the opt-out is implemented against both env APIs at once.

Verification

• cargo check -p vite_task
• cargo test -p vite_task_server --test integration
• cargo test -p vite_task_bin --test e2e_snapshots fetch_env_untracked_does_not_invalidate -- --ignored
• cargo test -p vite_task_bin --test e2e_snapshots fetch_envs_untracked_does_not_invalidate -- --ignored
• cargo clippy --locked --all-targets --all-features -- -D warnings

[wan9chi]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• feat(cache): consume runner ignore reports for auto outputs #431
• test(e2e): verify real Vite env cache tracking #451
• feat(client): add tracked option for env IPC #458 👈 (View in Graphite)
• feat(cache): fingerprint getEnvs match sets #450
• feat(client): serve getEnvs over runner IPC #449
• feat(cache): fingerprint tracked getEnv reads #454
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fb19a127bf

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Add the changelog entry for tracked env opt-outs

This exposes { tracked } to the public Node client, which is a user-facing behavior change. The root AGENTS.md instruction says user-facing features or behavior changes must add an entry to CHANGELOG.md via /update-changelog, but this diff leaves CHANGELOG.md unchanged; release notes will omit the new getEnv(..., { tracked: false }) behavior.

Useful? React with 👍 / 👎.