release(v5.10.1): drop gemini-bridge from the pipeline; correct the T1 §6 PoC status

gemini-bridge is dropped by operator directive (three repetitions). The drop is
permanent, not a wait-for-SDK-upgrade state, so the change clears every LIVE
surface that could still steer a run toward the agent and leaves the historical
record alone.

Live surfaces cleared: agents/gemini-bridge.md deleted; trekresearch (bridge
launch block, --local help, high-effort always-on pair, stats record,
degradation list), trekplan, trekbrief, research-orchestrator (mode table,
agent table, prompting block, summary line), README (feature prose, mode table,
agent prose, mermaid EXTERNAL node, conditional legend, optional-MCP
requirement, --local section), CLAUDE.md, settings.json (the whole
trekresearch.geminiBridge block), both templates, architecture.md,
command-modes.md.

trekplan high-effort Adversarial Pass 2 now degrades EXPLICITLY: it emits its
section with status "unavailable, skipped" instead of failing or vanishing. A
high-effort plan carrying no Pass 2 marker is indistinguishable from one whose
Pass 2 crashed, which is the failure mode this wording exists to prevent.

gemini_used is deliberately KEPT as a vestigial trekresearch stats field pinned
to false. Removing it would break the observability export schema for existing
consumers, and the directive was about the agent, not the field.

Not touched: CHANGELOG history and the measurement/decision docs keep their
gemini references. They record what a past version did or what was measured
then; rewriting them is the same defect class as bumping a version string
inside a measurement doc.

Driven test-first. Five new pins in tests/lib/doc-consistency.test.mjs, verified
RED before the edits, including a KNOWN-POSITIVE CONTROL asserting the
historical records still DO carry gemini references — so the empty result on
live surfaces is a measurement and not a broken query (Verifiseringsloven
ansikt 4). Agent inventory 24 -> 23 (20 spawnable + 3 orchestrator reference
docs); the <example>-block floor moves 34 -> 32 because an agent legitimately
left the inventory, not because examples went missing from a surviving one.

Docs: docs/T1-cc26-delegated-orchestration.md §8 item 3 claimed both the §6
synthesis-agent PoC and the §5 bake-off were "designed but unbuilt". That was
written in S7 and falsified the same afternoon by S12, which ran the §6 PoC and
recorded Δ main-context (faithful flow) = 0.0%, NEGATIVE. The stale wording is
what caused the settled PoC to be re-ordered as new work on 2026-09-02, so it is
struck rather than deleted and §6 gained a RUN AND DECLINED status block. The
finding is structural, not stochastic: Phase 5 spawns the exploration swarm
foreground (trekplan.md:158,338-341), so the outputs are already resident in
main before Phase 7 — delegating only the Phase-7 digest evicts nothing.

Also measured 2026-09-03 (CC 2.1.259): claude -p --output-format stream-json
runs on subscription auth with no ANTHROPIC_API_KEY and now emits a
subagent_stats block, so S12's environment-block premise is half stale. Recorded
in §8 item 4. It lowers the cost of §5; it changes nothing about §6.

Suite 1041 (1039/0/2), up from 1036 by exactly the five tests added.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

commands/trekbrief.md

@@ -386,8 +386,8 @@ The mapping table is canonical:
 - `high → {effort: high, model: opus}` (force opus for the high-confidence path)
 - `fable → {effort: high, model: fable}` (force Fable 5 for the max-quality path)
 
-The fable tier reuses `effort: high` semantics — full swarm, contrarian +
-gemini always-on; `EFFORT_LEVELS` is unchanged (Voyage effort is orchestration
+The fable tier reuses `effort: high` semantics — full swarm, contrarian
+always-on; `EFFORT_LEVELS` is unchanged (Voyage effort is orchestration
 shape, not model reasoning effort). Model reasoning effort is inherited from
 the session: Fable 5's default effort is `high`, NOT xhigh. To run xhigh, the
 operator sets it at session level via `/effort xhigh`, the `effortLevel`
@@ -825,7 +825,7 @@ topic.
 > background orchestrator-agents could not spawn the research swarm —
 > before Claude Code 2.1.172 the harness did not expose the Agent tool to
 > sub-agents, so a background run silently degraded to single-context
-> reasoning without WebSearch / Tavily / WebFetch / Gemini (see v2.4.0
+> reasoning without WebSearch / Tavily / WebFetch (see v2.4.0
 > release notes). As of CC 2.1.172 sub-agents can spawn sub-agents (up to 5
 > levels deep), so a delegated redesign is under evaluation (see
 > `docs/cc-upgrade-2.1.181-decision-matrix.md`, W1/CC-26). Until then,