refactor(execute): reshape for IPC server lifecycle

[branchseer]

Reshape vite_task::session::execute (and the supporting modules:
spawn, fingerprint, cache, tracked_accesses, event, and the
summary reporter) to accommodate a per-task IPC server. The server
itself is a placeholder on this branch: instead of actually calling
vite_task_server::serve(...), we construct an empty Recorder
whose driver future resolves immediately with no traffic, and bind
a StopAccepting::noop(). The downstream plumbing — async-join of
the child with the server, Reports flowing into post-run
fingerprinting and into the cache update — is fully in place but
sees only the empty Reports, so behaviour is byte-for-byte
identical to today's runner.

The follow-up wires up the real serve(...), embeds the napi
addon, and injects VP_RUN_NODE_CLIENT_PATH into the child. That
PR's serve(Recorder::new(env_map)) is the only call that changes
from "future::ready(Ok(recorder))" to the real bind.

Adds StopAccepting::noop() to vite_task_server for the same
placeholder use case; it's a tiny helper that's also useful for
tests that need a value of the type without running a server.

Also folds in the unrelated-but-blocking output-config refactor
(output: Option<UserInputsConfig> instead of
Option<Vec<UserOutputEntry>>) — both sides now route through
ResolvedGlobConfig::from_user_config. The 80-odd plan-snapshot
updates are mechanical consequences of that type change.

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

[branchseer]

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

• test(cache): real-vite integration fixtures + playground #408
• feat(cache): integrate runner-aware IPC reports #407
• refactor(execute): reshape for IPC server lifecycle #406 👈 (View in Graphite)
• feat(client): napi binding + JS wrapper #405
• feat(ipc): protocol + Rust transport #404
• 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: dd2800e233

ℹ️ 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]

Populate IPC envs before spawning

When automatic tracking is enabled, this constructs a completed dummy recorder and injects no VP_RUN_IPC_NAME into the child environment (ipc_envs is empty). Any runner-aware child using the provided client (Client::from_envs(std::env::vars_os())) will conclude it is outside the runner, so calls such as disableCache, ignoreInput, ignoreOutput, or tracked env reads are never reported; the parent then updates the cache with incomplete reports, which can leave watch/dev tasks cached or archive outputs the tool explicitly tried to exclude. This path needs to bind vite_task_server::serve(...) and pass its env entries to spawn() before enabling cache updates for runner-aware reporting.

Useful? React with 👍 / 👎.

[branchseer]

Superseded by restructured 2-PR stack:

• feat(client): vite-task-client JS package #409 — vite-task-client JS package
• feat(ipc): protocol + Rust transport #410 — Rust crates + runner integration (5 commits, one per closed PR)