docs(per-role-context): bundle patch — add contradiction #6 (C11 vs S8/S11/S12)

[artyhoo]

What

Single-row addition to the bundle's §5 contradictions table (file: docs/superpowers/specs/2026-07-27-per-role-context-bundle-for-opus.md).

Why

Host-side inventory check (operator's question «все ли вытащил?») caught a load-bearing gap. The bundle task 98b1e249 honestly noted «no new rows added by §3 because substrate-doc C-IDs are not visible to this container». But its own §3.2 (deep-research summary) carries S8/S11/S12 findings that directly contradict addendum C11:

• C11 (addendum, on staging): "no per-role filtering at any layer"
• S8/S11/S12 (deep-research §3.2, inline in bundle): "per-role shaping DOES exist via agents/*.md (35 agent files), CLAUDE.md Task-tier routing, reviewer-discipline rule, 4 skills, plugin templates"

These are two different definitions of "per-role context":

• (a) auto-injected at session start (uniform — C11 right)
• (b) hand-authored role-specific content the agent loads via kickoff/template (differentiated — S8/S11/S12 right)

The operator's verbatim question «inject only needed» maps to (a); the framing «roles receive different» could map to either. Opus must resolve this definition fork before any fabla decision — this is the highest-load-bearing contradiction in the bundle.

Fidelity verdict

FIDELITY: GO
Basis: PR adds 1 row to bundle §5 contradictions table (preserves both sides of a contradiction the bundle task couldn't see because its container couldn't reach substrate doc 4's C11)
Round: 1
Audited-SHA: 2411481a4d32b7fe13f3c63c42acb0f1aabb734f
Evidence: docs/superpowers/specs/2026-07-27-per-role-context-bundle-for-opus.md:222 — new row 6 cites C11 (substrate doc 4 host path) and S8+S11+S12 (bundle §3.2 inline) with explicit definition-fork framing for Opus to resolve
- docs/superpowers/specs/2026-07-27-per-role-context-bundle-for-opus.md:222 — "Highest-load-bearing contradiction" label per the operator's verbatim-question mapping

Findings:
- missing: (none — gap from bundle task's container isolation now closed)
- extra: (none — single row, scoped to §5)
- diverged: (none — bundle §3.2 unchanged, only §5 row added)

Cold auditor: host GLM session (this PR is a host-side patch to a container-produced artifact; the container's own fidelity verdict from PR #1179 covered the original bundle structure, this patch only extends §5). Dialogue-blind. Verdict consumed by pr-body-fidelity CI gate.

§1.7 Forward-check

• recommendation-laziness-discipline.md §3: row 6 surfaces a definition fork, does NOT resolve it. "Opus must resolve" — not "we should resolve".
• phase-research-coverage.md §1.7: contradiction preserved with both sides; mapping to operator's verbatim question explicit.
• doc-authority-hierarchy.md: header unchanged from PR docs(per-role-context): final bundle for Opus — assembled from 4 staging docs + 3 task outputs + DeepWiki cross-check #1179.

§1.7 Backward-check

Class = single-row addition to an existing bundle file's contradictions table. Surfaces: 1 file (2026-07-27-per-role-context-bundle-for-opus.md). SWEPT-CLEAN — no scope creep.

Out of scope

• No new claims, no shape picks, no fork resolution. Pure gap-closing patch from operator's inventory check.