QA case: external-byo-context-activation-resilience is missing its ## Evidence section

[Gandy2025]

packages/qa/cases/runtime/external-byo-context-activation-resilience.md has no ## Evidence section. 45 of the 52 committed cases have one. This case instead ends its Operate And Observe section with an inline paragraph:

Record provider version, Plugin adapter version/digest and Core release digest, resolved project kind/reason, exact Team identifier, hook transcript, operation output, endpoint fault used, attempt count, and latency. Redact credentials and private Context content.

The content is right; the placement is the problem. The BYO release-qualification gate in docs/context-integration.md files evidence per the case file's Evidence section, and this case backs two of its 11 items — item 5 (membership revocation, binding movement, offline authority, scope-commit movement) and item 9 (legacy full Plugin migration plus the Claude next-session adoption gate). Right now those items have no conforming place to file against.

Suggested fix: promote that paragraph to a ## Evidence section positioned as in the sibling cases — after Operate And Observe, before Expected Result — matching external-context-hook-status and provider-readiness. No change to the validation question, so the case ID stays stable per packages/qa/cases/README.md.

Small and self-contained, but it is a prerequisite for filing item 5 and item 9 evidence. Case-library maintenance is a separate task from a QA run ("formal QA never edits the committed library"), hence this issue rather than an inline fix.

[Gandy2025]

Correcting the rationale above after #2242 merged — the ask is unchanged, its framing is not.

This issue originally justified the missing ## Evidence section by pointing at items 5 and 9 of the 11-item release gate in docs/context-integration.md. That gate no longer exists. #2242 replaced it with a Qualification status section carrying a three-check release bar, and the scenarios this case backs — membership revocation, binding movement, offline authority, scope-commit movement, legacy full Plugin migration and the Claude next-session adoption gate — are now change-triggered qualification rather than release blockers.

So this is no longer release-blocking. It still stands on its own: the case is the one place those scenarios are defined, and when a change touches them it needs a conforming place to file evidence. 45 of 52 cases have an ## Evidence section; this one does not.

The suggested fix is unchanged — promote the trailing "Record provider version, Plugin adapter version/digest…" paragraph to a ## Evidence section between Operate And Observe and Expected Result, matching external-context-hook-status and provider-readiness. Case ID stays stable per packages/qa/cases/README.md.

#2239 now owns the three-check bar and its per-scenario status.