[sylvesterkaczmarek]

Summary

Package deployment metadata under Vite's resolved build.outDir rather than always using dist.

The plugin currently documents a default-directory restriction. Configuring Vite to write a build to build/client, for example, leaves the deployment without its hosting configuration and migrations while the plugin still replaces dist/.openai.

Capture the resolved output directory alongside the project root, update the documentation, and include a patch changeset. Relative paths resolve against the Vite root; absolute paths are supported. Default builds continue to use dist.

Validation

• pnpm check passed: formatting, lint, type checks, builds, and 47 tests across both workspace packages.
• All three new real-Vite-build cases fail on unchanged production code. They cover relative, nested, and absolute output directories; metadata and migrations; stale migration cleanup; and leaving unrelated dist/.openai content untouched.
• The complete check ran from an isolated temporary checkout to avoid unrelated ancestor-level @types/chai packages. Its changed source files were byte-checked against the publication checkout.
• Node 26.8.1, Vite 8.0.14, macOS arm64. No hosted deployment was performed.

The plugin lifecycle and build.write behavior are unchanged; #7 addresses that separately.

Reproduced against 7eb9d4b9cf93ad7e64aebc8a5ca70e29ec2cfb94.