docs: repo-and-ci roadmap Done table omits today's action-pin alignments (#394, #398) #402

Problem

planning/roadmaps/repo-and-ci.md's Done table does not record two CI fixes that merged today, 2026-10-20. The repo's planning rule (planning/templates/roadmap-item.md: "When an item ships or is dropped, move its row to the Done table at the bottom of the file with the date and the PR or reason. Do not delete rows.") is what the earlier roadmap-staleness issues (#386, #388, #396) enforced.

Evidence (verified on main 2b9b424a)

• grep -c "#394" planning/roadmaps/repo-and-ci.md = 0 and grep -c "#398" = 0; the Done table's newest rows are dated 2026-10-19 (CI: add timeout-minutes caps to every job in every workflow #293).
• ci: goreleaser and both Jules daily workflows pin checkout/setup-go three majors behind the repo (v4 vs v7) #394 was closed by PR ci: bump lagging checkout/setup-go pins from v4 to repo-standard v7 #395, MERGED 2026-10-20T07:01:26Z ("ci: bump lagging checkout/setup-go pins from v4 to repo-standard v7").
• ci: mcpx-conformance downloads artifacts with v8 what its own leg job uploads with v7 — one major for the flow #398 was closed by PR ci: align mcpx-conformance download-artifact to v7 (#398) #399, MERGED 2026-10-20T07:43:28Z ("ci: align mcpx-conformance download-artifact to v7").
• Both are repo-wide CI/automation items, the exact scope this roadmap file declares for itself (.github/workflows and PR automation), matching existing Done rows (timeout caps CI: add timeout-minutes caps to every job in every workflow #293, concurrency ci: add concurrency groups to cancel superseded runs #289/ci: key auto-assign concurrency group by issue/PR number (#302) #303, PR-gate drift ci(id): PR gate's hard-coded flake-check list can silently drift from pkgs/id/flake.nix — new checks get no PR coverage #300/ci(id): guard the PR check list against flake drift #318).

Why it matters

The Done table is the record the sweeps and Drew read to know what CI work has already landed; two same-day action-pin alignments missing from it invite duplicate filings (the pin-skew class has already been filed four times across the repos today).

Acceptance criteria

• Done table in planning/roadmaps/repo-and-ci.md gains one row for the ci: goreleaser and both Jules daily workflows pin checkout/setup-go three majors behind the repo (v4 vs v7) #394 checkout/setup-go v7 alignment (result: ci: bump lagging checkout/setup-go pins from v4 to repo-standard v7 #395 or ci: goreleaser and both Jules daily workflows pin checkout/setup-go three majors behind the repo (v4 vs v7) #394) dated 2026-10-20.
• Done table gains one row for the ci: mcpx-conformance downloads artifacts with v8 what its own leg job uploads with v7 — one major for the flow #398 mcpx-conformance download-artifact v7 alignment (result: ci: align mcpx-conformance download-artifact to v7 (#398) #399 or ci: mcpx-conformance downloads artifacts with v8 what its own leg job uploads with v7 — one major for the flow #398) dated 2026-10-20.
• No Now/Next rows change (neither item was listed there); existing rows byte-identical apart from table padding.
• Single-repo: the other repos' roadmaps are separate files with their own Done tables.