docs(release): require one shared product version

[DecisionNerd]

Closes #292.

Summary

• accept ADR 0017: all public Rust crates, Python/Node/native adapters, CLI, and skills share one exact release version
• document coordinated recovery and preserve immutable partial-release records
• make repository preflight and candidate tests reject adapter/core version divergence
• publish ADR 0017 through both decision indexes and the Starlight allowlist/navigation

Validation

• python3 scripts/ci/test-release-publish-preflight.py
• python3 scripts/ci/test-release-candidate.py
• python3 scripts/set_release_version.py --check
• pnpm docs:build
• pnpm docs:check-links
• make pre-push-fast

No versions, tags, releases, packages, or registry state are changed.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

Summary by CodeRabbit

• Documentation

  • Added the “Unified Release Version” architecture decision record to the published documentation and navigation.

• Tests

  • Added coverage ensuring release validation rejects artifacts with mismatched versions.
  • Added coverage for registry-specific Node version mismatches during publish preflight validation.

Note

Document and enforce a single shared product version across all release surfaces

• Adds ADR 0017 establishing that Rust crates, Python/Node adapters, CLI, and agent skills must share one version at every release, forbidding registry-specific patch versions.
• Updates release process, publication order, and v0.5.0 operator runbook docs to reference ADR 0017 and describe valid recovery dispositions.
• Adds test cases in test-release-candidate.py and test-release-publish-preflight.py that assert validation fails when any adapter version diverges from the expected release version.
• Registers ADR 0017 in the docs site sidebar and content sync allowlist so it appears in the published documentation.

^{Macroscope summarized 9aad072.}

[coderabbitai]

Walkthrough

The documentation site now publishes ADR 0017 and links it in ADR navigation. Release validation tests cover mismatched npm artifact versions and registry-specific Node versions.

Changes

Unified Release Version

Layer / File(s)	Summary
Publish ADR 0017 docs-site/astro.config.mjs, docs-site/scripts/sync-content.mjs	ADR 0017 is added to navigation and the published documentation page list. The allowlist comment reflects the accepted ADR set.
Validate version unity scripts/ci/test-release-candidate.py, scripts/ci/test-release-publish-preflight.py	Regression tests reject npm artifact and Node registry version mismatches.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related issues

• release: ship GraphForge v0.5.1 with fast-fail recovery #192 — Concerns ADR 0017 and unified version enforcement across release artifacts.
• ci: keep v0.5.1 publication automation small and resumable #288 — Covers unified release-version validation across published artifacts.

Possibly related PRs

• CurateLabs/graphforge#258 — Modifies release-version validation and related tests.

Suggested labels: core, testing

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Linked Issues check	❓ Inconclusive	Regression tests and documentation publishing updates are evidenced, but core ADR and release-guidance requirements are in filtered Markdown files.	Review the excluded ADR, release-guidance, runbook, index, and changelog files to verify all issue #292 acceptance criteria.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Out of Scope Changes check	✅ Passed	All summarized changes support ADR 0017 publication or regression coverage for shared release-version validation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title clearly summarizes the main change: enforcing one shared product version across release surfaces.
Description check	✅ Passed	The description clearly covers the objective, implementation areas, validation commands, linked issue, and release impact.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/292-shared-release-version

---

_{Comment @coderabbitai help to get the list of available commands.}