feat(knowledge): land the harness-surface definition and bare-name boundary in the docs profile

[kyle-sexton]

Lands two adopted Sitting-2 decisions in the anthropic-docs publisher profile — the campaign's consumer-facing tag-selection doctrine. knowledge 0.10.16 -> 0.10.17.

PA-M — the harness-surface definition

New bullet appended to the near-miss rule: a harness surface is a surface a user can reach, with three non-falsifying sub-shapes that harness-doc text can take without establishing one. Both the definition sentence and sub-shape (3) carry explicit [campaign-owned amendment] labels — the record shows the campaign making the selection-over-support choice, not inheriting an adjudication. Sub-shape (3) rests on its single attested instance (env-vars.md:394, a retry/fallback row) and carries its own over-broadening boundary: a doc line describing some other model's tier fails the sub-shape's own test.

The landing site was derived three independent ways: the profile already uses "harness surface" as its negative-claim term (:34, :54); the adopted row's own text says "write into the profile"; and the 0.10.16 CHANGELOG deliberately held this exact question (J-12) for the dispositions interview this answers.

PA-V — the bare-name boundary

The cc-applicable/mixed boundary bullet now carries the fourth API surface (model ID) and the negative half the profile never stated: bare names are not API surfaces — a product name, display name, or docs-path slug never by itself triggers mixed. Ratified from the de facto standard 15+ rows already stood on (cross-vendor retag applied in-slice). Deliberately excluded: a [campaign-owned amendment] label (this ratifies an evidence-carried standard, not a campaign-invented definition) and "feature names" (present only in one slice's wording, not the adopted row — widening the enumeration would exceed the adopted authority).

Verification

Both commits independently verified by a second model with the implementer's rationale withheld: the PA-M landing audited across landing-site derivation, amendment fidelity (verbatim vs the adopted blockquote), self-fire (no profile or checklist conflict; no live campaign artifact violates the definition), and mechanics; the PA-V text was authored by that verifier from the adopted row and applied verbatim, with the producer re-confirming the authority citations at the bytes before editing. The one enumeration of the API-surface list repo-wide is this bullet — no drift introduced. markdownlint 0 errors; CHANGELOG newest-first, both entries folded into the unreleased 0.10.17.

Downstream, already discharged against these rules: the four slice-local api-only ratifications (memory-tier) now cite the landed definition and route their three disclosed near-miss hits per these bullets.

No linked issue

Related

• Sitting 2 of the doc-corpus decision block, ADOPTED 2026-08-03 after adversarial validation (21/21 CONFIRMED); PA-M ordered first carrying its amendment flags, exactly as the adoption block specifies.
• Siblings this session: feat(claude-config,review): promote I8-b to unscoped and give severity.md enumerable tier criteria #1881, feat(claude-config): ship the IA consumer rule cluster — I17, I18, I19, I20 #1882, feat(claude-config): ship I21 and I22 — the agnostic halves of the ratified Q8 split #1884, docs(playbooks,philosophy): ship DOC bundle 1 — surface-scoped claims, effort lane rules, Haiku delegation boundary #1885, docs(playbooks): ship DOC bundle 2 — thinking cost doctrine under EC-1, effort dial seam #1887 (open); standards#311 + ADR-0002; dotfiles#394, feat(source-control): unify native-hook + /worktree-skill worktree creation via one shared helper #399 (open).
• The J-12 hold this closes: knowledge 0.10.16's CHANGELOG (PR chore(knowledge): land the near-miss disclosure rule and the blog-channel extraction artifacts #1879).

[claude]

Claude finished @kyle-sexton's task in 45s —— View job

---

Security Review — PR #1888

• Gather context (PR diff, changed files)
• Review plugins/knowledge/.claude-plugin/plugin.json
• Review plugins/knowledge/CHANGELOG.md
• Review plugins/knowledge/skills/docpage-digest/context/anthropic-docs-profile.md
• Post findings

No security issues found.

All three changed files are non-executable content: a version-string bump in plugin.json (0.10.16 → 0.10.17), a changelog entry, and prose additions to a Markdown classification profile (anthropic-docs-profile.md) consumed by the docpage-digest skill as tag-selection doctrine for an LLM performing documentation classification.

Reviewed for the categories in scope for this lane:

• Injection surfaces (command/SQL/path/template): none — no shell, SQL, or template code is added or touched.
• Secrets/tokens/credentials: none present or referenced.
• GitHub Actions patterns (pull_request_target/workflow_run, script injection via github context, permission widening): not applicable — no workflow files are touched by this PR.
• Supply-chain / unpinned actions: not applicable — no action or dependency pins are touched (deferred to zizmor's lane regardless).
• Authorization/access-control logic: not applicable — no code paths, only doctrine text that shapes future human/LLM judgment calls when tagging documentation slices; it has no runtime effect and executes nothing.

plugin.json's diff is scoped to the version field only; no userConfig, permissions, or execution-relevant fields changed.

[claude]

Claude finished @kyle-sexton's task in 1m 30s —— View job

---

Code Review — PR #1888

• Gather context (PR diff, changed files)
• Review plugins/knowledge/.claude-plugin/plugin.json
• Review plugins/knowledge/CHANGELOG.md
• Review plugins/knowledge/skills/docpage-digest/context/anthropic-docs-profile.md
• Post findings

Note: Per REVIEW.md's lane split, security review is out of scope here (handled by the dedicated security-review workflow already running on this PR). This review covers correctness and maintainability only.

Summary

This is a clean, well-scoped docs-only change: a version bump, a CHANGELOG entry, and 22 added lines in the Anthropic docs publisher profile. No code, no plugin logic, no schema changes.

Findings

Nothing blocking. A few observations, none requiring action:

1. Cross-references check out. The PR body's claims about the landing site are verifiable in the diff itself:

   • anthropic-docs-profile.md:34 and :54 already use "harness surface" as the negative-claim term, consistent with the new definition being appended there rather than introduced cold.
   • The [campaign-owned amendment] labels appear exactly where the PR body says: on the definition sentence (anthropic-docs-profile.md:84) and on sub-shape (3) (:88) — sub-shapes (1) and (2) correctly carry no label, matching the "selection over support, not inherited" distinction the PR draws.
   • The API-surface enumeration at :98-105 is the only such list in the file (confirmed via grep) — the PR body's "no drift introduced" claim holds.

2. Numbering convention is consistent with the rest of the file. The new (1)/(2)/(3) enumeration matches the existing (a)/(b) style used earlier in the same file (lines 18, 25) for parenthetical sub-enumeration — no new convention introduced.

3. CHANGELOG format matches precedent. ## [0.10.17] sits above ## [0.10.16] (newest-first, as claimed), uses the same ### Changed heading and bold-lead-sentence bullet style as prior entries, and the plugin.json version bump (0.10.16 → 0.10.17) is a matching semver bump per the docs/PLUGIN-PHILOSOPHY.md/CLAUDE.md "Versioned" rule.

4. Minor, non-blocking: the CHANGELOG's PA-M entry mentions the amendment is "labelled as the campaign's own choice" but doesn't explicitly restate that sub-shape (3) alone (not the whole definition) carries the second label — a reader relying solely on the CHANGELOG (not the profile diff) would need to open the profile file to see that only shape (3) is new/campaign-owned versus (1)/(2) being independently corroborated. This is implicit but recoverable from the CHANGELOG's own wording ("The third... is new"), so not a real defect — just a note if a future editor wants the CHANGELOG to be fully self-contained.

5. Could not run markdownlint-cli2 in this sandbox (no local binary, npx requires network approval that isn't available here) to independently verify the "0 errors" claim. The diff's formatting (dash bullets, asterisk emphasis, bold lead-ins) visually matches the repo's .markdownlint-cli2.jsonc style config, but this should be confirmed by CI rather than taken solely on my read.

No changes requested.

[github-actions]

Claude has reviewed this PR 1 time. The lane skips further automatic reviews after 5; deleting this comment resets the count.