revert(site): withdraw the language support and canon pages for rework [CORE-1929] [CORE-1930]

Reverts #199 (34e437e). The pages need another design pass before they
ship; the branch is retained locally for the rework.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: Madi (Pfaff) Edgar <madiedgar@users.noreply.github.com>

Author: madiedgar

CHANGELOG.md

@@ -28,21 +28,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 
-- **Language support page** at [/languages](https://www.legesher.io/languages) listing every human language
-  Legesher ships a Python language pack for, the maturity stamp each one carries, and what moves a language
-  up the ladder. Every language is `experimental` today and the page says so plainly rather than presenting
-  a ladder and letting a reader assume the languages are spread across it. Promotion criteria are described
-  as still being defined with the language communities, because they are — no threshold is implied.
-  (CORE-1929)
-- **Language canon page** at [/canon](https://www.legesher.io/canon) covering the dataset of vocabulary
-  Legesher actually ships, and answering "how is this different from the corpus?" at the top of the page
-  rather than leaving a reader to compare two dataset cards. Links both artifacts, each labelled for who it
-  is for: the canon for developers, the corpus for researchers. (CORE-1930)
-- Language and tier data is **generated, not hand-written**. `npm run sync:languages` derives
-  `src/data/language-packs.json` from the language registry and the pack export's own manifest — the same
-  two inputs the published dataset is built from — and fails if the two disagree about which locales exist
-  or how they are distributed across the ladder. The counts and stamps rendered on both pages are read from
-  that file, so the site cannot advertise a review standard the packs no longer hold. (CORE-1929)
 - **Campaign attribution on newsletter subscriptions.** When someone reaches the site through a
   link carrying `utm_source` / `utm_campaign`, those values are recorded with their subscription
   as `last_touch_channel` and `last_touch_release`, so an announcement can be credited with the

package.json

@@ -20,8 +20,7 @@
     "build": "astro build",
     "preview": "astro preview",
     "astro": "astro",
-    "contributors:generate": "all-contributors generate",
-    "sync:languages": "node scripts/sync-language-data.mjs"
+    "contributors:generate": "all-contributors generate"
   },
   "dependencies": {
     "@astrojs/mdx": "^6.0.3",

scripts/sync-language-data.mjs

@@ -46,9 +46,7 @@ const currentYear = new Date().getFullYear();
         </a>
       </div>
       <div class="text-sm text-brand-gray flex flex-col md:items-end gap-1">
-        <div class="flex flex-wrap items-center justify-center gap-x-4 gap-y-1 md:justify-end">
-          <a href="/languages" class="hover:text-brand-cyan transition-colors duration-300">Language Support</a>
-          <a href="/canon" class="hover:text-brand-cyan transition-colors duration-300">Language Canon</a>
+        <div class="flex items-center gap-4">
           <a href="/privacy" class="hover:text-brand-cyan transition-colors duration-300">Privacy Policy</a>
           <a href="/terms" class="hover:text-brand-cyan transition-colors duration-300">Terms of Service</a>
         </div>

src/components/Footer.astro

@@ -5,7 +5,6 @@ import { LINKS } from '@/lib/links';
 // Single source for both the desktop nav and the mobile menu so the two can't
 // drift apart as links are added.
 const navLinks = [
-  { href: '/languages', label: 'Languages' },
   { href: LINKS.github, label: 'Roadmap' },
   { href: LINKS.slack, label: 'Community' },
   { href: LINKS.docs, label: 'Docs' },