chore(release): patch v4.1.1 tag date 2026-06-09

[abitofhelp]

Summary

F2-tag-prep slice of the functional publishability repair
sequence. Replaces the <YYYY-MM-DD pending tag> placeholders
introduced by F2 (#7) with the actual intended tag date
2026-06-09 UTC.

Scope is deliberately 3 files, 4 placeholder swaps —
reversible, no release execution.

This is the immediate pre-tag PR. The annotated v4.1.1 tag
will be created on the squash-merge commit produced by this PR,
after explicit owner + Codex authorization. No tag, GitHub
Release, or alr publish is performed in or by this PR.

Commit map

#	SHA	Subject	Files
1	6340b24	chore(release): patch v4.1.1 tag date 2026-06-09	3 files (CHANGELOG.md, README.md, config/README.md)

Diff total: 3 files, +4 / -4.

What the change does (mechanical)

Four placeholder swaps:

File	Line	Before	After
CHANGELOG.md	4 (top metadata Date)	**Date:** <YYYY-MM-DD pending tag><br>	**Date:** 2026-06-09<br>
CHANGELOG.md	21 ([4.1.1] section heading)	## [4.1.1] - <YYYY-MM-DD pending tag>	## [4.1.1] - 2026-06-09
README.md	6 (top metadata Date)	**Date:** <YYYY-MM-DD pending tag><br>	**Date:** 2026-06-09<br>
config/README.md	4 (top metadata Date)	**Date:** <YYYY-MM-DD pending tag><br>	**Date:** 2026-06-09<br>

No other files touched.

Position in the publishability sequence

This PR is F2-tag-prep in the Codex-reviewed sequence:

1. F1 — .gitmodules HTTPS repair (merged in fix(gitmodules): switch submodule URLs from SSH to HTTPS for publishability #6)
2. F2 — 4.1.1 version-prep PR (merged in chore(release): prep v4.1.1 (publishability patch on the 4.1.0 line) #7)
3. F2-tag-prep — date patch (this PR)
4. F2-tag — annotated v4.1.1 tag push (separate gate; first
   irreversible-ish step in the F-sequence)
5. F3 — alr publish --skip-submit dry-run; review manifest
6. F4 — alr publish submit to Alire community index
7. F5 — confirm index visibility (alr search --crates functional)
8. Resume clara T1 sanity at branch 3144709 after the new
   functional version is consumable

Each subsequent gate is owner-authorized and Codex-reviewed
independently.

What this PR does NOT do

• No tag, no GitHub Release, no alr publish.
• No version-surface changes — alire.toml, test/alire.toml,
  src/version/functional-version.ads already at 4.1.1 from F2;
  unchanged here.
• No .gitmodules edit — F1 invariant maintained.
• No src/ / test/ / formal-doc / Makefile / GPR / CI changes.
• No LICENSE / NOTICE / THIRD_PARTY changes.
• No dependency unpinning anywhere.
• No clara T1 changes — branch preserved local-only at 3144709.

Validation (performed before PR open)

Codex-mandated checks (all green):

1. Diff scope — exactly the 3 expected files modified, +4 / -4.
2. Tree-wide placeholder check — git grep "YYYY-MM-DD pending tag"
   returns empty across the entire repo.
3. Date count — git grep -c "2026-06-09" returns 2 in
   CHANGELOG.md, 1 in README.md, 1 in config/README.md; total = 4
   (matching the 4 placeholders that were replaced).
4. Version surfaces unchanged — alire.toml / test/alire.toml /
   functional-version.ads still 4.1.1.
5. F1 invariant — .gitmodules URLs still HTTPS-only; zero
   git@github.com: occurrences.
6. F2 invariant — root alire.toml has zero [[pins]] blocks.
7. Tag-name / manifest-version parity — intended tag v4.1.1
   matches alire.toml version = "4.1.1".
8. v4.1.1 absence — no local/remote tag, no GitHub Release,
   no community-index manifest.
9. alr build in dev container — green, 0.32s, exit 0.

Follow-ups deliberately deferred

• F2-tag — annotated v4.1.1 tag push to origin. Separately
  gated with its own Codex review at tag-push time. Tag is
  created on the squash-merge commit produced by this PR, NOT on
  the F2-tag-prep branch tip.
• F3 alr publish --skip-submit — Codex-reviewed before submit.
  Manifest must point at the exact v4.1.1 tag SHA (NOT a moving
  branch), have no [[pins]], no path = ..., no SSH URLs.
• F4 alire-index submission — separately gated; irreversible
  once the alire-index PR opens.
• F5 visibility check — informational.
• clara T1 resumption — gated on F4 + F5 visibility.
• No-drift policy reminder — if the actual tag date slips
  beyond 2026-06-09 for any reason, file a follow-up CHANGELOG /
  README / config/README date patch before the tag gate. NO
  tagging on a date that disagrees with the documented surfaces.

Refs: adafmt#42