Skip to content

docs: restamp first-touch docs to 1.1.4 and correct version state - #469

Merged
dmealing merged 2 commits into
mainfrom
fm/mo-post-1-1-4
Oct 26, 2026
Merged

dmealing merged 2 commits into
mainfrom
fm/mo-post-1-1-4

Conversation

@dmealing

Copy link
Copy Markdown
Member

What Changed

  • Restamp version mentions in README.md language table and docs/ports/{typescript,java,kotlin,csharp}.md install/dependency snippets from 1.1.3 / 8.1.3 to 1.1.4 / 8.1.4.
  • AGENTS.md: refresh the status date to 2026-10-26, and update the version picture to list 1.1.0 through 1.1.4 as released with latest at 1.1.4 / 8.1.4.
  • AGENTS.md: correct metamodelVersion prose to read 1.1 from 1.1.0 through 1.1.3 and 1.2 from 1.1.4, replacing the stale "On main it now reads 1.2" wording.
  • AGENTS.md: update the 1.1.0 release line to point at the current latest (1.1.4 / 8.1.4).
Validation

Risk Assessment

✅ Low: Docs-only restamp of 1.1.3/8.1.3 to 1.1.4/8.1.4 plus a factual AGENTS.md correction; no stale version strings remain and the round-1 fix is applied as instructed.

Testing

  • ⏭️ Test - skipped

Pipeline

Updates from git push no-mistakes

✅ **Intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

🔧 **Review** - 1 issue found → auto-fixed ✅
  • ⚠️ AGENTS.md:49 - The version-number restamp is complete, but AGENTS.md (CLAUDE.md is a symlink to it) still carries false version-state prose that the intent says to correct. Line 49 says metamodelVersion read 1.1 "from 1.1.0" and "On main it now reads 1.2". CHANGELOG 1.1.4 records that the bump to 1.2 shipped in 1.1.4, and expected-registry.json at v1.1.4 reads 1.2. It is therefore a released fact: it read 1.1 from 1.1.0 through 1.1.3, and 1.1.4 moved it to 1.2. Line 25, _Last refreshed 2026-10-14._, also predates this restamp. Smallest fix: reword line 49 to say metamodelVersion read 1.1 from 1.1.0 through 1.1.3 and reads 1.2 from 1.1.4 (calendar-aligned startOf windows), and update the refresh date to 2026-10-26. Wording-only; no other stale 1.1.3 / 8.1.3 strings remain in tracked files outside CHANGELOG and the intentional "1.1.0, 1.1.1, 1.1.2, 1.1.3 and 1.1.4 are released" list.

🔧 Fix applied.
✅ Re-checked - no issues remain.

⏭️ **Test** - skipped

Step was skipped.

⏭️ **Document** - skipped

Step was skipped.

⏭️ **Lint** - skipped

Step was skipped.

✅ **Push** - passed

✅ No issues found.

@dmealing
dmealing merged commit 1878943 into main Oct 26, 2026
1 check passed
@dmealing
dmealing deleted the fm/mo-post-1-1-4 branch October 26, 2026 19:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant