claude-config: adjudicate the user-request-conflict axis as an I15 boundary reopen

[claude]

Context

Signed-off decision Q3/C9 of the context-engineering integration contract (2026-09-01):
audit-instructions I15 scopes conflict detection to resident-surface pairs BY RECORDED DESIGN
(its Source block cites the article's user-request clash example), so adding a
"standing instructions vs plausible user requests" axis is a boundary REOPEN, not an
extension. Filed OPINION-tier (no official doc defines such a check; the request population
is unbounded). This receipt is written to survive any outcome of the prior plan's Q15
disposition — if docs/topics/context-engineering-claude-5 closes, this item still carries
the full proposal.

Proposed work

• Adjudicate the reopen against I15's recorded rationale
  (plugins/claude-config/skills/audit-instructions/reference/conflict-criteria.md, five
  gates; criteria.md:769-805).
• The detectability answer to evaluate: gate-5-style realistic-prompt fixtures over an
  enumerated request population, OPINION-tier default-off per the prior plan's tier policy.
• Land the verdict either in the prior plan's detector catalog (if it proceeds per Q15) or
  as a standalone criteria decision recorded in conflict-criteria.md.

Acceptance criteria

• A recorded accept/reject with rationale engaging I15's participant-boundary design.
• If accepted: detector candidate spec with fixtures; if rejected: the boundary rationale
  updated to name this adjudication.

References

Both docs/topics/** paths this issue originally cited are gone, and neither will resolve.
The context-engineering-claude-5 slice was pruned from main by the topic-docs v3.0.0
adoption (#3557) before its corpus-input note was ever written, so payload 2 exists only as
this issue. The integration contract was contract tier and pruned before merge per that same
convention; it survives as the pasted body of #3588 (merged as ae3aa802), which is where its
Q3 answer and validation record are readable.

• feat(conventions): absorb the context-engineering corpus and add the instruction exception register #3588 — the merged pull request whose body carries the signed-off contract verbatim.
• plugins/claude-config/skills/audit-instructions/reference/conflict-criteria.md — I15's five
  gates and the participant-boundary rationale this adjudication has to engage.
• plugins/claude-config/skills/audit-instructions/reference/criteria.md — I15 itself, which
  since feat(conventions): absorb the context-engineering corpus and add the instruction exception register #3588 also carries the exception-register hold clauses on I1, I4 and I5. Those are Q2's
  categorical carve-out, not this issue's detection axis; do not conflate them.
• docs/specs/context-engineering-critical-apparatus.md — the corpus-side critique rows behind
  the reopen.