docs(beta-docs-showcase): retire «Plan→top tier» — aif runs GLM only (operator directive)

[artyhoo]

Summary

Operator directive 2026-08-17: aif runs GLM only — the Claude runtime is not used there. This retires the beta-docs-showcase deliverable «per-mode defaults Plan→top tier» in the three places that mandated it, and records why it is retired rather than deferred.

The directive is a mechanism now, not a memo: Claude Opus (plan+review) (41315ef6-…) is enabled: false on the live instance. It was safe to disable and it changes no running work — measured, not assumed:

$ curl -s localhost:3009/projects | jq -r '.[] | "\(.name) plan=\(.defaultPlanRuntimeProfileId)"'
rules-as-tests-aif  plan=53eca24c-…      # Z.AI GLM-5.2 SDK
timeliner           plan=53eca24c-…
getff-landing       plan=53eca24c-…
$ curl -s localhost:3009/settings | jq '{defaultPlanRuntimeProfileId}'   # app-level
{ "defaultPlanRuntimeProfileId": null }

All three projects route every mode to GLM and the app-level defaults are null, so the resolution chain (task_override → project_default → system_default, packages/data/src/index.ts:3197-3204) never reached the Claude profile. Nor had it ever run: lastUsageAt: null since creation on 2026-07-20, and the container's ~/.claude/.credentials.json (dated Aug 9) carries expiresAt: 0. The BS-pre smoke task cf894220 died on exactly that — Claude Code returned an error result: Not logged in · Please run /login — which is what surfaced the question.

Changes

• .claude/orchestrator-prompts/beta-docs-showcase/kickoff.md:18 — Tier line: all aif modes on the executor tier, with the reason and the escape (a top-tier seat is a host-side CC session, never an aif dispatch).
• .claude/orchestrator-prompts/beta-docs-showcase/kickoff.md:51 — BS-pre deliverable: «all three modes → executor tier», «retired, not deferred».
• .claude/orchestrator-prompts/beta-docs-showcase-meta-launch/kickoff.md:205 — same, in the Stage 1 dispatch instruction.
• docs/superpowers/specs/2026-07-23-beta-docs-showcase-design.md:217 — B-D6, with the ownership split spelled out.

What is deliberately NOT changed

The tier criteria. tier-home.md owns them and is a shipped consumer artefact; CLAUDE.md's «Task-tier routing» already assigns which model fills which tier to the aif runtime-profile config — which is exactly the layer that changed. Editing the shipped criteria would widen an operator's machine-level directive into a consumer-facing design change.

Backward-check sweep

Class of this change: a dispatch input mandating Plan→top tier for aif dispatch. Enumerated by grep -rn "Plan→top" --include='*.md' — 4 surfaces beyond this umbrella, none corrected here, each for a stated reason:

• beta-delivery-ux/kickoff-s4.md:49,92,244,312 and beta-delivery-ux-meta-launch/kickoff.md:234 — CLOSED umbrella (merged 2026-08-10, done.md written). Historical artefact, read-only for subsequent sessions per the Artifact Ownership Contract.
• docs/superpowers/specs/2026-07-23-beta-program-design.md:252 — the parent frame, a different owner; its statement is about the beta programme's design intent, not this machine's config.
• packages/core/templates/shared/tier-home.md:61 — shipped, generic, describes the mechanism rather than this instance. See «NOT changed» above.

One live defect surfaced, not patched here

.claude/skills/pipeline/references/mode-overrides.md:172 maps the aif mode-override preset to the marker value Claude Opus (plan+review) — now a disabled profile. This does not fail loudly: packages/runtime-bridge/src/AifHandoffBackend.ts:132 resolves a bridge-profile marker from an unfiltered GET /runtime-profiles (the API does support ?enabledOnly=true, and does not use it here), so a disabled profile still matches by name, the dispatch reports success, and the task blocks later on runtime auth — the same blocked_external shape as cf894220. Fixing it belongs to the pipeline skill's owner and carries a real design question (with Claude gone, aif and economy would collapse onto the same marker, which makes the preset meaningless — repoint vs retire). Surfaced per the CLAUDE.md PR-strategy rule against drive-by cross-umbrella PRs.

§1.7 Skipped: documentation-only correction recording an operator runtime directive — no rule, principle, template, skill or agent semantics change; the three edited files are dispatch inputs and a design spec owned by this umbrella.

Test plan

• bash scripts/host-verify.sh beta-docs-showcase — the umbrella kickoff's opt-out is intact
• markdownlint clean on all three files (pre-commit, 0 errors)
• Backward sweep run and recorded above (grep -rn "Plan→top", 4 sibling surfaces adjudicated)
• The disable is reversible: PUT /runtime-profiles/41315ef6-… {"enabled": true} restores it

Fidelity verdict

FIDELITY: skipped — non-stage documentation PR, no stage kickoff or acceptance package to audit against.