docs: point every surface at the public docs domain

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: mstrathman

README.md

@@ -122,7 +122,7 @@ reaches **0.89 MASE** where the teacher sits at ~0.80 and every classical
 method is above 1.0, and the distilled `gbt` student **matches or beats tuned
 XGBoost** on most TabArena tasks. The [Models](#models) section covers the
 student architectures and soft-label distillation; the
-[distillation guide](https://purestorage-openconnect.github.io/sqlite-predict/guides/distillation/)
+[distillation guide](https://code.purestorage.com/sqlite-predict/guides/distillation/)
 walks the whole flow.
 
 ## Why
@@ -171,7 +171,7 @@ parameters, and `GROUP BY` all compose naturally, from the CLI or from an ORM
 written, so they run on read-only databases and inside views. Each group
 returns one JSON document; expand it with `forecast_rows()` /
 `anomaly_rows()`, or `JSON.parse` it in your app. Each language's
-[getting-started guide](https://purestorage-openconnect.github.io/sqlite-predict/getting-started/python/)
+[getting-started guide](https://code.purestorage.com/sqlite-predict/getting-started/python/)
 shows the pattern through its native ORM (SQLAlchemy, Drizzle, Diesel).
 
 `backtest`, `predict`, and the `distill_*` operations take read-only SELECT

bindings/node/package.json

@@ -29,5 +29,6 @@
     "sqlite-predict-linux-x64": "0.0.1-alpha.6",
     "sqlite-predict-linux-arm64": "0.0.1-alpha.6",
     "sqlite-predict-windows-x64": "0.0.1-alpha.6"
-  }
+  },
+  "homepage": "https://code.purestorage.com/sqlite-predict/"
 }

bindings/python/pyproject.toml

@@ -22,6 +22,7 @@ classifiers = [
 [project.urls]
 Homepage = "https://github.com/PureStorage-OpenConnect/sqlite-predict"
 Source = "https://github.com/PureStorage-OpenConnect/sqlite-predict"
+Documentation = "https://code.purestorage.com/sqlite-predict/"
 
 [tool.setuptools]
 packages = ["sqlite_predict"]

bindings/rust/Cargo.toml

@@ -5,6 +5,7 @@ edition = "2021"
 license = "MIT OR Apache-2.0"
 description = "Prediction as a SQL primitive for SQLite: forecast, detect_anomalies, and predict. The zero-dependency C core compiles into this crate."
 repository = "https://github.com/PureStorage-OpenConnect/sqlite-predict"
+documentation = "https://code.purestorage.com/sqlite-predict/"
 keywords = ["sqlite", "forecasting", "anomaly-detection", "time-series"]
 categories = ["database", "science"]
 include = ["src/**", "build.rs", "csrc/**", "README.md"]

website/astro.config.mjs

@@ -4,13 +4,13 @@ import starlight from "@astrojs/starlight";
 
 // GitHub Pages serves this project at different URLs depending on visibility: a
 // random *.pages.github.io ROOT while the repo is internal (private Pages), and
-// purestorage-openconnect.github.io/sqlite-predict once it is public. The deploy
+// code.purestorage.com/sqlite-predict once it is public. The deploy
 // workflow reads the live Pages config (actions/configure-pages) and passes the
 // correct origin + base in via env, so one build works for either URL. Locally
 // we default to root. Internal doc links are path-relative, so only asset and
 // nav paths depend on `base`.
 const base = process.env.PAGES_BASE_PATH || "/";
-const site = process.env.PAGES_ORIGIN || "https://purestorage-openconnect.github.io";
+const site = process.env.PAGES_ORIGIN || "https://code.purestorage.com";
 
 export default defineConfig({
   site,