Summary

Date-correction slice of the functional publishability repair
sequence. Aligns the release-date surfaces with the actual UTC
tag date.

The earlier F2-tag-prep PR (#8) baked in 2026-06-09 as a
conservative placeholder target. The release-process invariant is
release date surfaces == actual UTC tag date, not a fixed
calendar target. Since we're ready to tag today (2026-06-08
UTC), the surfaces are corrected to match.

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

This is the corrected pre-tag PR. The annotated v4.1.1 tag will
be created on the squash-merge commit produced by THIS PR — which
will replace the prior planned tag-target SHA 53d5374 — after
explicit owner + Codex authorization. No tag, GitHub Release,
or alr publish is performed in or by this PR.

Commit map

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

What the change does (mechanical)

Four date swaps (2026-06-09 → 2026-06-08):

No other files touched.

Position in the publishability sequence

This PR is F2-tag-date 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 — initial date placeholder → 2026-06-09 (merged in chore(release): patch v4.1.1 tag date 2026-06-09 #8)
4. F2-tag-date — date correction 2026-06-09 → 2026-06-08 (this PR)
5. F2-tag — annotated v4.1.1 tag push on the squash-merge SHA
   produced by this PR (separate gate; first irreversible-ish step)
6. F3 — alr publish --skip-submit dry-run; review manifest
7. F4 — alr publish submit to Alire community index
8. F5 — confirm index visibility
9. Resume clara T1 sanity at branch 3144709

Each subsequent gate is owner-authorized and Codex-reviewed
independently. The prior tag-gate snapshot (which named SHA
53d5374 and date 2026-06-09) is now stale and must be
regenerated after this PR merges.

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 remain at 4.1.1.
• 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)

Required local 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. Zero 2026-06-09 in the 3 expected date surfaces.
4. Exactly four 2026-06-08 in the 3 expected date surfaces
   (CHANGELOG ×2, README ×1, config/README ×1).
5. Version surfaces unchanged — alire.toml / test/alire.toml /
   functional-version.ads still 4.1.1.
6. F1 invariant — .gitmodules URLs still HTTPS-only;
   zero git@github.com: occurrences.
7. F2 invariant — root alire.toml has zero [[pins]] blocks.
8. v4.1.1 absence — no local/remote tag, no GitHub Release,
   no community-index manifest.
9. alr build in dev container — green, 0.21s, exit 0.

Follow-ups deliberately deferred

• F2-tag — annotated v4.1.1 tag push to origin on the
  squash-merge SHA produced by THIS PR. Separately gated with
  its own Codex review at tag-push time. Tag target SHA will be
  regenerated; the prior 53d5374-targeted snapshot is stale.
• F3 alr publish --skip-submit — Codex-reviewed before submit.
• 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.

Refs: adafmt#42