feat(website): skills and crons as first-class .t27 specs; Queen modules SKILLS (7) and CRONS (8)

[gHashTag]

Summary

Skills and crons become spec-first on t27.ai. Every published agent skill (26) and every scheduled job (33) is now stated by a .t27 module; the site generates its catalogs from those specs through the vendored compiler wasm at build time, and the Explorer cards open on the spec — bytes, sha256, compiler verdict — before the code the sync script found. The Queen gains two modules, SKILLS (7) and CRONS (8), that embed the two Explorers the way SPECS embeds the corpus.

Companion PR in the canonical spec home: gHashTag/t27#3543 (feat/specs-skills-crons), tracking issue gHashTag/t27#3544.

Language (LANG-EN) and translations through a spec. t27 CI (bootstrap/build.rs) rejects Cyrillic in any spec, so SUMMARY_RU is gone from all 59 vendored specs (rg -l '[\p{Cyrillic}]' public/t27/files/specs → nothing; copies byte-identical with t27). Russian is connected through a spec: public/t27/files/specs/i18n/agents-ru.t27 (module i18n_agents_ru, KIND="i18n") declares LOCALE, SCOPE (specs/skills, specs/crons), FIELDS (SUMMARY, NAME), BUNDLE_REPO="trinity", BUNDLE_PATH="apps/website/i18n/agents.ru.json", KEY="ID", FALLBACK="en", COVERAGE_REQUIRED=false, ORPHANS_ALLOWED=false, ENABLED=true. The Cyrillic payload is only in apps/website/i18n/agents.ru.json ({$spec, locale, entries: {ID: {SUMMARY}}}, 59 entries). The generator discovers specs/i18n/*.t27 through the wasm, loads each declared bundle, validates it against its contract (locale / $spec match, keys ⊆ FIELDS, orphan entry → build fails, missing translation → coverage only, duplicate LOCALE → fails) and emits summary: {en, ru} / name: {en, ru} plus i18n: [{locale, spec, sha256, bundle, enabled, fields, scope, coverage: {n, total}, missing}] per catalog. No locale is enumerated in code: agents-de.t27 etc. are one file each. check:agents prints ru via specs/i18n/agents-ru.t27: skills 26/26, crons 33/33, orphans 0. The SPEC panel shows translations: ru via specs/i18n/agents-ru.t27 (n/total).

Data flow

gHashTag/t27  specs/skills/*.t27, specs/crons/*.t27          (canonical, edited there)
      │  vendored copy
      ▼
apps/website/public/t27/files/specs/{skills,crons}/*.t27
      │  scripts/agents-from-specs.mjs   (prebuild, after skills-core index)
      │    · runs each spec through public/t27/t27.wasm  → typecheck.ok, discarded
      │    · checks the field schema (ID/KIND/HOST/… types, ranges, enums)
      │    · joins with public/skills/manifest.json + public/crons/manifest.json
      │    · labels spec+code / spec-only / code-only; dup ID → build fails;
      │      RUNS id unresolved → health:'fail'
      ▼
public/skills/spec-skills.json, public/crons/spec-crons.json   (committed, --check pins them)
      │
      ├─ src/lib/agentSpecs.ts  → loaders, witness labels, URL builders, optional control client
      ├─ src/components/AgentSpecPanel.tsx  → spec panel + cross-links + CONTROL strip (EN+RU)
      ├─ SkillExplorer (layer "Spec" first) · CronExplorer (spec panel first)
      └─ Queen tabs 7/8 (QueenAgents.tsx, iframe #/skills|#/crons?embed=1)
qa/agents-spec-contract.mjs  (npm run check:agents)  pins catalogs ↔ specs ↔ Queen modules ↔ HUD_VIEWS

Witness

Check	Command	Result
Specs written	—	26 skills + 33 crons = 59 .t27
Compiler typecheck (vendored wasm 4d9c0447b5ca2887…)	node scripts/agents-from-specs.mjs	typecheck ok 59/59, discarded 0
Witness split	same	skills spec+code 26/26, crons spec+code 33/33, spec-only 0, code-only 0, RUNS resolved 0 (all specs carry RUNS = [] + RUNS_NOTE)
Generated entries	public/skills/spec-skills.json, public/crons/spec-crons.json	26 + 33; run-now targets: github-actions 12, inngest 6, railway 1, timer (disabled) 14
Catalogs match specs	node scripts/agents-from-specs.mjs --check	match
Generator tests	node --test scripts/agents-from-specs.test.mjs	13 pass / 0 fail
npm run prebuild		exit 0 (only the new files change under public/)
npm run typecheck ratchet	node scripts/typecheck-ratchet.mjs	179 errors / 26 files = baseline; no file gained errors
npm run lint		180 problems, identical to main (none in changed/new files)
npm run build		exit 0
npm run check:agents		PASS — skills 26, crons 33, Queen views 8, modules 8
check:spec-catalog, check:skills-catalog, check:crons-catalog		PASS / PASS / PASS
check:explorer-languages, check:queen-languages		PASS (4 pages) / PASS (258 EN, 258 RU keys)
check:shared-core, check:queen-{atlas,treasury,catalog,continuous,spec-mirrors,coverage,worlds,city,construction,hardware,responsive}		PASS
check:queen-{honesty,cycle,factory,review}		FAIL — identical failures on untouched main @ 50d11a5, unrelated to this PR
check:queen-viewport and other Chromium gates		not run here (no Chromium in the sandbox); count updated 5/6 → 8

Note on the wasm gate: the vendored typecheck.ok is lenient (it stays true for str = 5 or u16 = 70000), so the generator's schema check is the real gate. "typecheck ok" is necessary, not sufficient — the PR says so in the generator header and the README.

What changed where

• public/t27/files/specs/{skills,crons,i18n}/*.t27 + README.md — vendored specs (canonical home is gHashTag/t27); i18n/agents-ru.t27 is the Russian translation contract.
• i18n/agents.ru.json — the Russian bundle the contract points to (the only place Cyrillic for these specs lives).
• scripts/agents-from-specs.mjs (+ .test.mjs) — generator; package.json prebuild/prebuild:ci += generator; new check:agents, test:agents-specs.
• scripts/railway-services.json — Railway projectId and per-service serviceId so "run now" resolves at build time (test:sync-crons still 8/8).
• src/lib/agentSpecs.ts, src/components/AgentSpecPanel.tsx — loaders, witness labels, panel, CONTROL strip; SkillExplorer.tsx, CronExplorer.tsx wired (spec first; tags witness/*, enabled/*; badges ⟲ N / ◷ N; embed=1 kept).
• docs/agent-control-api.md, .env.example.queen — optional VITE_AGENT_CONTROL_URL contract (POST {url}/crons/<id>/run|enable|disable, POST {url}/skills/<id>/run, body {id, requestedAt}); unset → muted "control plane not connected". .gitignore gains !apps/website/docs/** so the doc can be committed.
• Queen: queenHud.ts HUD_VIEWS now lists all eight views; queenModules.ts entries 7 ⟁ SKILLS/СКИЛЛЫ, 8 ◷ CRONS/КРОНЫ; Queen.tsx union → HudView, command items, EN+RU dicts, render branches, aria; QueenAgents.tsx; ModulesBlock six → eight (EN+RU); QueenCommand.tsx comments.
• qa/queen-viewport-contract.mjs — command-button count 5 (readiness) / 6 (assert) → 8. Ratchet moved because the panel it counts has eight buttons; the readiness probe was already stale at 5 while the panel had 6.

Pre-existing bug fixed on the way: HUD_VIEWS omitted specs, so ?tab=specs fell back to the comb and the digit shortcuts pointed one view off from the digits the panel printed. Explained in the commit.

CI on this PR (pre-existing, infra, not addressed here): claude-review (curl failure), pr-opened ("Bad credentials"), Brain Health ("not implemented") fail independently of this diff.

Boundaries (what this PR does not claim)

• No live control plane is deployed. VITE_AGENT_CONTROL_URL is a documented contract only; with it unset the UI says so and offers only spec-edit and host links.
• The vendored specs are not in public/t27/manifest.json yet (inSpecCorpus = false for 59/59); the "Open in Spec Explorer" link stays hidden until sync-t27-specs is re-run after the t27 PR merges. The panel shows a muted "not in vendored corpus manifest yet" instead.
• In-process timers (14 crons) have no outside handle; their "run now" is disabled with a stated reason.
• RUNS is empty in every cron spec (with a RUNS_NOTE); no cron → skill edge is asserted yet.
• Chromium-based QA gates were not run in this environment.
• The bootstrap compiler on t27 master was not run against these specs — only the vendored wasm.

Do not merge without review.