refactor: correct references from VERSIONS.MD to VERSIOND.md in documentation and code

Author: flemming-n-larsen

.ai/README.md

@@ -15,7 +15,7 @@ current task.
 | `cross-platform.md`     | ~55   | ~600        | Bot API, Java, Python, .NET, C#, cross-platform, port, reference implementation |
 | `coding-conventions.md` | ~35   | ~350        | style, conventions, naming, format, PEP 8, immutability                         |
 | `testing-and-build.md`  | ~40   | ~450        | test, build, Gradle, gradlew, compile, validation                               |
-| `documentation.md`      | ~30   | ~300        | docs, README, markdown, mermaid, VERSIONS.MD, Javadoc, docstring, changelog     |
+| `documentation.md`      | ~30   | ~300        | docs, README, markdown, mermaid, VERSIOND.md, Javadoc, docstring, changelog     |
 | `standards.md`          | ~25   | ~250        | encoding, UTF-8, standards, file format, characters                             |
 
 **Total if all loaded:** ~225 lines, ~2350 tokens
@@ -92,7 +92,7 @@ Note: A colon (e.g., "Remember: ...") makes it more command-like.
 | Bot API, Java/Python/.NET, porting | `cross-platform.md`     |
 | Style, naming, language-specific   | `coding-conventions.md` |
 | Tests, Gradle, build               | `testing-and-build.md`  |
-| README, VERSIONS.MD, docs          | `documentation.md`      |
+| README, VERSIOND.md, docs          | `documentation.md`      |
 | Encoding, file formats             | `standards.md`          |
 
 ### Best Practices
@@ -121,7 +121,7 @@ Build and test procedures: Gradle commands, test requirements, validation steps.
 
 ### `documentation.md`
 
-Documentation standards: README updates, VERSIONS.MD format, Javadoc/docstring alignment.
+Documentation standards: README updates, VERSIOND.md format, Javadoc/docstring alignment.
 
 ### `standards.md`
 

.ai/documentation.md

@@ -15,11 +15,11 @@
 **Files to update:**
 
 - `/README.md` - Project overview and getting started
-- `/VERSIONS.MD` - Version history and changelog
+- `/VERSIOND.md` - Version history and changelog
 - Module-specific `README.md` files
 - API documentation (Javadoc/docstrings)
 
-## VERSIONS.MD Format
+## VERSIOND.md Format
 
 **Follow existing format:**
 

AGENTS.md

@@ -35,7 +35,7 @@ Load specific instruction files from `.ai/` based on your task:
 | Bot API changes, Java/Python/.NET  | `.ai/cross-platform.md`     |
 | Java, Python, C# style conventions | `.ai/coding-conventions.md` |
 | Testing, building, Gradle          | `.ai/testing-and-build.md`  |
-| Docs, VERSIONS.MD, Javadoc         | `.ai/documentation.md`      |
+| Docs, VERSIOND.md, Javadoc         | `.ai/documentation.md`      |
 | File encoding, standards           | `.ai/standards.md`          |
 | **Planning, specs, proposals**     | `@/openspec/AGENTS.md` ⚠️   |
 

VERSIONS.md

@@ -1,4 +1,4 @@
-## 📦 0.35.0 - **BREAKING**: Python Bot API Converted to Synchronous API & Refactored to Use Properties - 25-Jan-2026
+## 📦 0.35.0 - **BREAKING**: Python Bot API Converted to Synchronous API & Refactored to Use Properties - 26-Jan-2026
 
 ### 💥 Breaking Changes (Python Bot API)
 

buildSrc/src/main/kotlin/build/release/GenerateReleaseNotes.kt

@@ -9,7 +9,7 @@ import java.nio.file.Files
 
 fun generateReleaseNotes(projectDir: File, version: String): String {
 
-    val versionsFilename = File(projectDir, "VERSIONS.MD").absolutePath
+    val versionsFilename = File(projectDir, "VERSIOND.md").absolutePath
 
     val extractedVersion = extractVersion(versionsFilename)
     check(extractedVersion == version) {

openspec/changes/archive/2025-12-21-document-gui-installers/proposal.md

@@ -19,7 +19,7 @@ potentially leading to confusion and support issues.
 
 ## What Changes
 
-- Update `VERSIONS.MD` to document the availability of native GUI installer packages
+- Update `VERSIOND.md` to document the availability of native GUI installer packages
 - Update `buildSrc/src/main/resources/release/release-docs-template.md` to include:
     - Information about native installer packages for Windows, macOS, and Linux
     - Java 11+ requirement and JAVA_HOME setup instructions
@@ -32,7 +32,7 @@ potentially leading to confusion and support issues.
 ## Impact
 
 - **Affected documentation files**:
-    - `VERSIONS.MD` - Add note about new installer packages in the latest version section
+    - `VERSIOND.md` - Add note about new installer packages in the latest version section
     - `buildSrc/src/main/resources/release/release-docs-template.md` - Add installer section before "Running Robocode"
     - `docs-build/docs/articles/installation.md` - Add new section for native installers
 

openspec/changes/archive/2025-12-21-document-gui-installers/specs/user-documentation/spec.md

@@ -52,7 +52,7 @@ become available.
 
 #### Scenario: User checks version history
 
-- **WHEN** a user reads the VERSIONS.MD file
+- **WHEN** a user reads the VERSIOND.md file
 - **THEN** they SHALL find an entry documenting the availability of native GUI installer packages
 - **AND** they SHALL see which platforms are supported (Windows, macOS, Linux)
 - **AND** they SHALL see which package formats are available (msi, pkg, rpm, deb)

openspec/changes/archive/2025-12-21-document-gui-installers/tasks.md

@@ -1,6 +1,6 @@
 # Implementation Tasks
 
-## 1. Update VERSIONS.MD
+## 1. Update VERSIOND.md
 
 - [x] 1.1 Add entry in the latest version section documenting the new GUI installer packages
 - [x] 1.2 Mention available formats: Windows (msi), macOS (pkg), Linux (rpm and deb)
@@ -41,6 +41,6 @@ Notes:
 - The release docs template (`buildSrc/.../release-docs-template.md`) and the installation guide (
   `docs-build/.../installation.md`) were updated and aligned. Filenames and download links now use the `{VERSION}`
   placeholder and include platform-specific installer guidance and `JAVA_HOME` setup instructions.
-- Remaining work: update `VERSIONS.MD` to document the new GUI installer packages (see section 1). Also consider
+- Remaining work: update `VERSIOND.md` to document the new GUI installer packages (see section 1). Also consider
   gradually replacing remaining `x.y.z` occurrences across other docs (some tutorials and READMEs still reference
   `x.y.z`).

openspec/specs/user-documentation/spec.md

@@ -56,7 +56,7 @@ become available.
 
 #### Scenario: User checks version history
 
-- **WHEN** a user reads the VERSIONS.MD file
+- **WHEN** a user reads the VERSIOND.md file
 - **THEN** they SHALL find an entry documenting the availability of native GUI installer packages
 - **AND** they SHALL see which platforms are supported (Windows, macOS, Linux)
 - **AND** they SHALL see which package formats are available (msi, pkg, rpm, deb)