The gate count and the reference-feature LOC table were hand-typed and drifted from the code, so they are removed; the LOC table now names the files and the command that measures them. .env.example pointed to layers.md for runtime profiles, which never described them; it now points to the README section that does. ci-quality-gates.md lists the three things DOCUMENTATION_READY checks, so the gate name is not read as a general documentation-accuracy guarantee. The route list (③) and the README config location (④) were already fixed by 14-03 and 13-15. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
26 lines
1.1 KiB
Bash
26 lines
1.1 KiB
Bash
# Build-time inputs (§6.1). These are compiled into the bundle by Vite, so
|
|
# everything here is public by definition. Never put a secret in this file or in
|
|
# any `.env*` file: a frontend has no confidential storage, and a value that
|
|
# reaches the browser has been published.
|
|
#
|
|
# Runtime configuration — API endpoints, auth mode, telemetry, capability
|
|
# switches — is NOT here. It lives in `config/runtime/<profile>.json` and is
|
|
# materialized into `dist/config.json` at build time, so it can be changed
|
|
# without rebuilding. See the "Runtime configuration" section of README.md.
|
|
#
|
|
# Copy to `.env.local` (git-ignored) to override locally.
|
|
|
|
# Identifies the build in release manifests and the runtime document.
|
|
# CI supplies the real value; a developer build falls back to "local-build".
|
|
VITE_BUILD_ID=local-build
|
|
|
|
# Source revision the bundle was produced from.
|
|
VITE_COMMIT_SHA=local
|
|
|
|
# Sub-path the app is served under. Must start and end with "/".
|
|
# Feeds the router, the Service Worker scope and Vite's asset base together.
|
|
VITE_ROUTER_BASE_PATH=/
|
|
|
|
# Where the browser fetches the runtime document from at boot.
|
|
VITE_RUNTIME_CONFIG_URL=/config.json
|