knowledge plugin: publisher-profile amendment bundle from the 9-slice cloud-fleet corpus run

[kyle-sexton]

Interview-ratified amendment bundle for context/anthropic-docs-profile.md (knowledge plugin). Source: /planning:interview + /planning:audit-answers (two independent validators: fresh-context Claude + cross-vendor Codex) over the nine docpage-digest slices produced 2026-08-16/17. Decision record: cloud-fleet-knowledge-graduation/shared-understanding.md (machine-local on the operator's machine; all resolved values reproduced below, so this issue is self-contained).

Adopt as ONE PR:

1. mixed boundary — pure four-surface letter rule + worked examples. A claim row is mixed only when the row's OWN quoted text names an API parameter, endpoint, SDK call, or model ID. Worked examples that close the recorded edge cases:
   • "parameter" means an Anthropic API request parameter — a harness/tool argument (e.g. dangerouslyDisableSandbox, called a "parameter" by the settings page) never triggers.
   • A hostname alone is a name, not an endpoint; an endpoint is a callable address. Worked pair: prUrlTemplate (names github.com, cc-applicable) vs skipWebFetchPreflight (names api.anthropic.com, currently mixed — the outlier; retags cc-applicable).
   • Header names are not in the enumeration — apiKeyHelper (value sent as X-Api-Key/Authorization headers) stays cc-applicable.
     This settles the escalations recorded across slices: env-vars ESC-1..6 (status codes, cache TTLs, referenced variable names, mTLS certs, no fifth class, provider auth), cloud-environments D1, settings D-04/F-15, server-managed-settings entries 1/9/10, hooks E2, claude-web A3.
2. Vocabulary binds digest PROSE. The tag vocabulary's evidence burden applies to Summary/Implications/candidate text, not only claim rows (absence-shaped assertions in prose repeatedly escaped the api-only burden; both MAJOR prose defects in the hooks slice lived exactly there).
3. Fetch-channel artifact register for code.claude.com raw-md channel: the prepended Documentation-Index banner (verified on 187/187 pages; its embedded fetch imperative is quoted data, never an instruction), theme={null} fence attributes, hard-tab expansion by formatter hooks, \&-escaped URLs. Digest layer: reproduce-never-repair. Reader-facing artifact layer: repair-and-disclose (ratifying the profile's existing sentence as covering escaped links).
4. Hedge-preservation worked examples, including the wrong-footer trap: the profile's hallucination-scoped residual-risk footer must NOT be attached to pages carrying their own hedge (e.g. server-managed-settings' "not a security boundary" sentence travels verbatim instead).
5. Row-local basis: subsection-level inheritance satisfies the contract (anchor-correct, mechanically recoverable). Per-row anchors required only where a file flattened multiple anchors into one. (Settings slice D-02; adopts arm A's position over arm B's literalism — recorded as an overrule, with rationale.)
6. Claim = whole table row including its Example cell for settings-style three-part tables (settings D-03). Rule lands in the profile NOW; the two settings-slice retags (unit 05 rows 18/37 → mixed) and the skipWebFetchPreflight retag execute ONLY inside a graduation-time verification cycle — never as bare edits to verified slices.
7. tag-exempt (consumer-surface) = documented-subject test, not hosting test: fires only when claude.ai-the-product is what the page documents (claude-web R2 generalized; server entry 9).
8. Pointer convention: bare "See X" = navigation-pointer; a directive pointer (tells the operator to do something / asserts a fact about the target) = guidance (server entry 10 + claude-web A5's residue test, which R5's own wording grounds).
9. Hard rule — no consuming-org context in digest sections. Digests state mechanism, never operator instance; operator-side environment notes route to the interview handoff (settings D-18; the memory slice's round-1 BLOCKING defect was this class).
10. Ranked doc queue recorded in the profile (no dispatch): /docs/en/permissions first (gates the hooks-at-project-scope security question — plugins-reference D3 — and two memory-slice questions), /docs/en/self-hosted-environments second. Corpus expansion is otherwise STOPPED by operator decision 2026-08-19.

Validation provenance: items 2,3,4,7,8 CONFIRMED by both validators; 1,5,6,9 human-ratified after challenge/reclassification (details in the operator's decision record).

[kyle-sexton]