fixed issues w/ accessing website on other computers

README.md

@@ -31,7 +31,7 @@ Start with the [final report](docs/final_report.md). Supporting deliverables:
 - [Private-to-public architecture](docs/architecture.mmd)
 - [10-minute presentation outline](docs/presentation_outline.md)
 - [Dashboard demo script](docs/demo_script.md)
-- [Dashboard-only Bolt deployment](docs/bolt_deployment.md)
+- [Optional public-hosting notes](docs/bolt_deployment.md)
 
 The [data inventory](docs/data_inventory.md) and archived
 [project options](docs/project_options.md) provide source-discovery history;
@@ -142,17 +142,34 @@ checksums. It shows no estimates if the approved aggregate bundle fails its
 contract. Every checked-in asset is marked as a development preview and not a
 population estimate.
 
-## Publish through Bolt
+### Live demo from another computer
 
-Do **not** import this full source repository into Bolt. Create a separate
-deployment project or repository containing only the contents of `dashboard/`,
-so `index.html` is at that project's root. Do not copy `.env`, private data,
-artifacts, models, SQL, pipeline scripts, credentials, or unrelated repository
-history.
+When both computers are on the same network, start the LAN demo from the
+repository root. Stop any older dashboard process with `Ctrl-C` first:
 
-Follow the complete preflight, import, Bolt Hosting, and post-publication checks
-in [docs/bolt_deployment.md](docs/bolt_deployment.md). No publishing action is
-performed by this repository.
+```bash
+node dashboard/server.mjs --lan
+```
+
+The server prints a **This computer** URL and one or more interface-labeled
+**Other devices** URLs. Open the URL for the shared Wi-Fi or Ethernet interface
+on the second computer; do not use `0.0.0.0` as the browser address. Confirm the
+header reads **Validated sample aggregates**. Stop the server with `Ctrl-C`
+after the demo.
+
+The LAN page still checks every approved JSON asset against its SHA-256 digest.
+Browsers do not expose the SubtleCrypto digest API to a non-loopback plain-HTTP
+page, so the dashboard includes a dependency-free checksum implementation for
+that case. These checks validate bundle consistency; plain HTTP does not
+authenticate the network transport, so use a trusted demo network.
+
+## Public hosting is not required
+
+The current presentation plan is the same-network live demo above. Nothing
+needs to be uploaded or published, and the server exposes only the dashboard's
+explicit static-file allowlist. The older
+[public-hosting checklist](docs/bolt_deployment.md) is retained only in case the
+delivery requirements change later.
 
 ## Author