all public dashboard stuff changed to static dashboard stuff

docs/data_inventory.md

@@ -112,7 +112,7 @@ possible, but must never appear in public outputs.
 - Extreme repeat counts exist and require invalid/shared-identifier filtering.
 
 Use a salted one-way internal token if a stable identifier is needed during
-feature engineering. Never send VINs or plates to the browser or Bolt.
+feature engineering. Never send VINs or plates to the browser.
 
 ## Operational and sensitive relations
 

docs/final_report.md

@@ -222,4 +222,3 @@ ranking, production model, diagnosis, or individual decision tool.
 - [Private-to-public architecture](architecture.mmd)
 - [10-minute presentation outline](presentation_outline.md)
 - [Dashboard demo script](demo_script.md)
-- [Optional public-hosting notes](bolt_deployment.md)

docs/project_options.md

@@ -162,7 +162,7 @@ Use option 1 as the main story and option 6 as its data-engineering foundation:
 3. Compare a transparent logistic baseline with a tree model.
 4. Validate on a later time period and separately by county/source.
 5. Export only aggregate scorecards, curves, and de-identified model outputs.
-6. Build the public Bolt dashboard over those safe outputs.
+6. Build the static dashboard over those safe outputs.
 
 This gives the project a coherent end-to-end narrative across data engineering,
 analytics, machine learning, responsible validation, and product design.