Drop stale Astro and merge-rule claims from the docs

Andrew Dunnrequested to merge
docs/drop-stale-astro-claims into main

What does this MR do and why?

I want the docs to claim only what the repository does, because fifteen places said Astro 6 while both package.json files require astro ^7.0.0, and CONTRIBUTING.md described merge controls the project does not enforce.

The prose now names no Astro major, so package.json is the one place the version is set. ARCHITECTURE.md stops calling the docs template an Astro and Starlight site, and the template's README.md says the site loads its chrome, fonts and icons from the reference's Pages origin, which an airgapped project vendors instead.

CONTRIBUTING.md said a merge needs one CODEOWNERS approval the author cannot give, and that squash-on-merge keeps the history linear. The project requires no approval and merges with a merge commit, squash off by default, so the merge request rules now say a merge needs a passing pipeline and a maintainer merges it, and that each commit reaches main as written. The CODEOWNERS header now says GitLab shows the owners on a merge request without requiring their approval, and CONTRIBUTING.md says a branch behind main takes main by a merge and is never force-pushed once its MR is open. "Before you write code" now lets a maintainer's own MR skip the issue and carry its two sentences in the summary, as this one does.

References

site/package.json and templates/docs/site/package.json, "astro": "^7.0.0". The project's approval, protected branch and merge settings, read through the API.

Standards affected

standards/design/SKILL.md loses the "6" from one sentence in its Templates section. No assertion, tier or status changes.

Exemption implications

None.

Test plan

  • just ship passes on the branch merged with main: TOTAL: 21 standard(s) passed, 0 exempt, 0 failed.
  • Outside CHANGELOG.md, git grep 'Astro 6' finds nothing, and each remaining Starlight mention says the template has none or tells a site not to add one.
  • The merge rules match the settings: 0 approvals required, author approval off, no code owner approval on main, a merge only after a passing pipeline and only by a maintainer, merge method merge and squash default_off.

An AI tool wrote this change and ran the checks above.

Merge request reports