# BONE FLOW #024 v1.0.301 Local install vs server QR

- The LOCAL installation verifies Calendar assets and completes even if the separate HTTPS sync service is absent. It reports `LOCAL_CALENDAR_INSTALL_PASS / SYNC_API_NOT_CONFIGURED`, not QR PASS.
- The SERVER installation remains strict: private API, Apache proxy, HTTPS `/health` and QR operator must pass. Server failures remain FAILED.
- For `localhost` that does not host the API, enter the actual HTTPS sync API URL in 接続先 and use the QR button; the browser navigates to that server's management page where the administrator session is available. No server domain is hardcoded.
- `localhost` alone cannot serve a registration URL a smartphone can reach. Never claim phone pairing works until an actual HTTPS server is configured.
- Existing SQLite records, user data, and Frozen component runtimes are not changed by this patch.
- Windows PowerShell 5.1 / Apache / live smartphone end-to-end test are still NOT RUN in this environment.