docs: point RELEASE.md at centralized workspace release procedure

[bernardladenthin]

The maintainer-facing release procedure is now centralized in workspace/workflows/release-process.md (see the workspace PR). This replaces the plugin's duplicated copy with a pointer to it — a pure single-module repo, so no repo-specific supplement.

De-stales the old copy, which said "commit directly to main (no PR)", omitted the CHANGELOG.md finalization step, and never mentioned the publish_to_central=true deploy gate.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QEgh6vtcPWAgQ6scK8pJk7

---

Generated by Claude Code

[claude]

Review: docs: point RELEASE.md at centralized workspace release procedure

✅ Approved — this is a clean consolidation of duplicated documentation.

Summary

This PR replaces an outdated, duplicated release procedure with a reference to the centralized workspace version. The change removes 27 lines of stale documentation and adds a 3-line pointer plus context about the project's single-module structure.

Strengths

1. Eliminates duplication — removes maintenance burden of keeping two copies of the release procedure in sync
2. De-stales docs — the original had incorrect/incomplete guidance ('commit directly to main', missing CHANGELOG.md finalization, no mention of the deploy gate)
3. Clear scope explanation — explicitly documents that this is a single-module Maven project, so no repo-specific supplement is needed
4. Correct relative path — the markdown link uses ../workspace/workflows/release-process.md which correctly points upward from docs/RELEASE.md to the sibling workspace repo

Considerations (all non-blocking)

• No local testing possible — I cannot verify that the workspace repo and the referenced file both exist and are accessible in CI/deployment contexts. This should work if:

  • Workspace is checked out as a sibling directory (standard for multi-repo structures)
  • The documentation build process includes workspace files
  • Readers have access to the workspace repo

  If this setup differs from your CI, the link may break. Recommend verifying the link resolves in CI before merging.

Risk Assessment

Low risk. Documentation-only change, no code changes, no build/test impact. Maintainers will catch any accessibility issues when they next perform a release.

No further changes needed.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud