Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

docs(local-setup): drop the unused FRONTIER_ENDPOINT from client-demo env

client-demo reaches the backend over Connect-RPC only. FrontierProvider
sets its single base URL from `config.connectEndpoint || '/frontier-connect'`,
and the built client SDK contains just two URL literals, "/" and
"/frontier-connect" — no /api request exists.

The `/api` proxy and `endpoint: '/api'` in src/config/frontier.ts are both
inert: `endpoint` is not a field on FrontierClientOptions, and it survives
only because client-demo builds with vite and no tsc step. Document that
so neither gets treated as required, and leave the code cleanup separate.