docs: make release documentation links portable

Author: acgetchell

README.md

@@ -39,8 +39,10 @@ while keeping the API intentionally small and explicit.
 - ✅ Stack storage only (no heap allocation in core types)
 - ✅ `unsafe` forbidden
 
-See [CHANGELOG.md](CHANGELOG.md) for release history and
-[docs/roadmap.md](docs/roadmap.md) for current release planning.
+See [CHANGELOG.md](https://github.com/acgetchell/la-stack/blob/v0.4.3/CHANGELOG.md)
+for release history and
+[docs/roadmap.md](https://github.com/acgetchell/la-stack/blob/v0.4.3/docs/roadmap.md)
+for current release planning.
 
 ## 🚫 Anti-goals
 
@@ -371,9 +373,10 @@ finite-storage invariant directly, so kernels do not revalidate stored entries.
 
 ## 📊 Benchmarks (vs nalgebra/faer)
 
-![LU solve (factor + solve): median time vs dimension](docs/assets/bench/vs_linalg_lu_solve_median.svg)
+![LU solve (factor + solve): median time vs dimension](https://raw.githubusercontent.com/acgetchell/la-stack/v0.4.3/docs/assets/bench/vs_linalg_lu_solve_median.svg)
 
-Raw data: [docs/assets/bench/vs_linalg_lu_solve_median.csv](docs/assets/bench/vs_linalg_lu_solve_median.csv)
+Raw data:
+[docs/assets/bench/vs_linalg_lu_solve_median.csv](https://github.com/acgetchell/la-stack/blob/v0.4.3/docs/assets/bench/vs_linalg_lu_solve_median.csv)
 
 Representative benchmark: `lu_solve` factors the matrix and solves one
 right-hand side. Median time is lower-is-better, and the “la-stack vs
@@ -382,9 +385,10 @@ nalgebra/faer” columns show the % time reduction relative to each baseline
 operations.
 
 For the full per-kernel comparison methodology, input construction, and
-release-comparison workflow details, see [docs/BENCHMARKING.md](docs/BENCHMARKING.md).
+release-comparison workflow details, see
+[docs/BENCHMARKING.md](https://github.com/acgetchell/la-stack/blob/v0.4.3/docs/BENCHMARKING.md).
 For the current release-to-release performance snapshot, see
-[docs/PERFORMANCE.md](docs/PERFORMANCE.md).
+[docs/PERFORMANCE.md](https://github.com/acgetchell/la-stack/blob/v0.4.3/docs/PERFORMANCE.md).
 
 <!-- BENCH_TABLE:lu_solve:median:new:BEGIN -->
 
@@ -445,23 +449,30 @@ to an explicit allowlist, and kept with readable version comments for review.
 CI runs `just ci` on Ubuntu, macOS, and Windows to keep platform coverage
 aligned with the local comprehensive validation path.
 
-For coverage commands and report locations, see [`docs/COVERAGE.md`](docs/COVERAGE.md).
-For the full contributor workflow, see [CONTRIBUTING.md](CONTRIBUTING.md).
+For coverage commands and report locations, see
+[`docs/COVERAGE.md`](https://github.com/acgetchell/la-stack/blob/v0.4.3/docs/COVERAGE.md).
+For the full contributor workflow, see
+[CONTRIBUTING.md](https://github.com/acgetchell/la-stack/blob/v0.4.3/CONTRIBUTING.md).
 
 ## 📝 Citation
 
-If you use this library in academic work, please cite it using [CITATION.cff](CITATION.cff) (or GitHub's
-"Cite this repository" feature). Tagged releases are archived on Zenodo.
+If you use this library in academic work, please cite it using
+[CITATION.cff](https://github.com/acgetchell/la-stack/blob/v0.4.3/CITATION.cff)
+(or GitHub's "Cite this repository" feature). Tagged releases are archived on
+Zenodo.
 
 ## 📚 References
 
-For canonical references to the algorithms used by this crate, see [REFERENCES.md](REFERENCES.md).
+For canonical references to the algorithms used by this crate, see
+[REFERENCES.md](https://github.com/acgetchell/la-stack/blob/v0.4.3/REFERENCES.md).
 
 ## 🤖 AI Agents
 
-AI coding assistants should read [AGENTS.md](AGENTS.md) before proposing or
-applying changes. See [CONTRIBUTING.md](CONTRIBUTING.md) for the repository's
-AI-assisted development note.
+AI coding assistants should read
+[AGENTS.md](https://github.com/acgetchell/la-stack/blob/v0.4.3/AGENTS.md)
+before proposing or applying changes. See
+[CONTRIBUTING.md](https://github.com/acgetchell/la-stack/blob/v0.4.3/CONTRIBUTING.md)
+for the repository's AI-assisted development note.
 
 ## 📄 License
 

scripts/README.md

@@ -14,60 +14,35 @@ uv sync --group dev
 
 ## How to use it
 
-### Comparing latest performance against the last release
+### Comparing performance
 
 The comparison script reads Criterion output and writes a local report to
 `target/bench-reports/performance.md` by default:
 
 ```bash
-# Save a full release baseline named "last"
-just bench-save-last
-
-# Run exact benches plus la-stack rows from vs_linalg, then compare to last
-just bench-latest-vs-last
-
-# Run only non-exact la-stack rows from vs_linalg, then compare to last
-just bench-vs-linalg-latest-vs
-
 # Re-render from existing Criterion output
 just bench-compare
 ```
 
 Use `uv run bench-compare --snapshot` for a no-baseline snapshot, or
 `uv run bench-compare <baseline>` to compare against a named saved baseline.
 
-For release PRs, promote one curated release-to-release comparison into
-committed docs and archive the previous committed report. Benchmark generation
-runs locally in temporary worktrees:
-
-```bash
-just performance-release
-```
-
-For local development regression checks, compare the current in-tree code
-against the latest published release:
+Use the top-level `just` workflows for routine release and local comparisons:
 
 ```bash
+# Local development: compare the current tree with the latest release
 just performance-local
-```
-
-For a faster non-exact kernel check that skips current nalgebra/faer and exact
-benchmark runs, compare current la-stack `vs_linalg` rows against a release
-baseline:
 
-```bash
-just performance-local-vs-linalg v0.4.3 v0.4.2
-```
-
-To compare stored GitHub Actions release benchmark assets without local cargo
-runs:
+# Release PR: update docs/PERFORMANCE.md and archive the previous report
+just performance-release
 
-```bash
+# GitHub Actions release assets, without local cargo benchmark runs
 just performance-github-assets
 ```
 
-For explicit release repair, pass both tags:
-`just performance-release v0.4.3 v0.4.2`.
+See `docs/BENCHMARKING.md` for the current command matrix, local saved-baseline
+workflow, explicit tag arguments, output locations, and release-artifact
+comparison details.
 
 ### Plotting Criterion benchmarks (la-stack vs nalgebra/faer)