chore(knowledge): retire best-practices doc-queue entry after slice completion

[kyle-sexton]

Summary

• Removes the code.claude.com best-practices entry from the docpage-digest Anthropic profile's doc queue — its slice completed end-to-end (fetch through interview handoff) per the queue's remove-on-completion rule. It was the sole "Applies across all of the above" entry, so the emptied category heading goes with it.
• Channel: raw-md (.md appended to the page URL; HTTP 200, 610 lines / 39,668 bytes — channel re-verified for this page, no degradation); provenance recorded in the slice checklist.
• Slice verification: Verifier A (same-vendor, fresh context) CORRECTION-NEEDED (1+3); Verifier B (cross-vendor Codex CLI 0.146.0 via the issue Restore cross-vendor Verifier B when openai/codex#32655 and #35871 are fixed (working invocation available now) #1740 elevated recipe, no degraded fallback) CORRECTION-NEEDED (8+1). One correction round (session-default agents — cross-model harness doc, no model pin per the profile's model-matching table); re-verified REVERIFY: PASS by both verifiers, 12/12 findings resolved, zero new findings. Records under .work/code-claude-com-docs-en-best-pr-9686dc16/verification/.
• Profile applicability-filter clarification codified from that verification: a digested page that is itself a live code.claude.com harness doc serves as its own row-local basis for intrinsic harness-guidance claims; the boundary rule still routes API-surface-naming claims to mixed, with third-party APIs (e.g. the GitHub API) counting as API surfaces.
• Knowledge plugin 0.10.4 → 0.10.5 with matching CHANGELOG entry.

Verification

• markdownlint-cli2 on changed markdown: 0 errors
• check-skill.sh docpage-digest (CHECK_SKILL_SKILLS_ROOT=plugins/knowledge/skills, base origin/main): PASS (1 pre-existing soft warning, SKILL.md length)
• check-changelog-parity.sh --check-bump origin/main: PASS
• Independent fresh-context reviewer on the diff: APPROVE (traced the changelog claims to the slice checklist and verification records; its one info-level attribution observation was applied before commit)
• Base freshness: fetched origin/main immediately before commit; zero commits behind

No linked issue — this PR closes no GitHub issue; the doc queue is tracked in the profile file itself.

Related

• chore(knowledge): retire sonnet-5 guide doc-queue entry after slice completion #1761 (previous doc-queue completion in this series — sonnet-5 prompting-guide slice)
• Restore cross-vendor Verifier B when openai/codex#32655 and #35871 are fixed (working invocation available now) #1740 (Verifier B elevated recipe used for cross-vendor verification)

🤖 Generated with Claude Code

[claude]

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

---

PR Review

• Gather context and understand request
• Read changed files and diff
• Review plugin.json version bump
• Review CHANGELOG.md entry
• Review anthropic-docs-profile.md changes
• Post findings

---

Three-file, three-concern diff: queue entry removal, filter-rule addition, and version bookkeeping. All three hang together correctly.

plugin.json — version bump (permalink): 0.10.4 → 0.10.5 is the right patch increment — profile prose update, no schema or API surface change.

CHANGELOG.md — [0.10.5] section (permalink): Format is consistent with all prior entries (version heading, ### Changed, bold item labels). The two bullet points accurately mirror the two diffs in the profile: queue entry removal and filter-rule addition. The queue-entry bullet correctly notes that the emptied category heading goes with it — that's precisely what the diff shows.

anthropic-docs-profile.md — filter-rule addition (permalink): The new "Harness docs are their own live basis" bullet integrates cleanly as a fifth item in the filter list and is internally coherent — it scopes the own-basis rule to intrinsic harness-guidance claims while explicitly preserving the API-surface → mixed boundary and extending it to third-party APIs with a concrete example. Provenance attribution "(From the best-practices slice…)" follows the same pattern as the sonnet-5 ruling that precedes it.

anthropic-docs-profile.md — queue entry removal (permalink): The "Applies across all of the above:" heading and its sole entry are removed together, leaving a clean blank-line separator before "Blog posts:". No orphaned whitespace or list-structure gap.

Model-matching table (line 60): The parenthetical example "best practices" in the cross-model/harness-doc row still stands correctly as a category example independent of the queue — no update needed there.

REVIEW.md checks: No high-risk security actions, no multi-record writes with atomicity concerns — both mandatory checks from REVIEW.md are inapplicable to this all-markdown diff. Security lane has its own workflow; nothing to flag here.

No findings. The diff is correct, self-consistent, and follows the project's conventions. Ready to merge.

[claude]

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

---

Security Review — PR #1765

• Gather context: read PR diff and changed files
• Analyze for security issues (logic flaws, injection, secrets, auth gaps, trust-boundary issues)
• Post findings

---

No security findings.

The three changed files are pure documentation/prose:

1. plugin.json — patch version bump (0.10.4 → 0.10.5), no schema, dependency, or permission changes.
2. CHANGELOG.md — changelog prose only; no executable content.
3. anthropic-docs-profile.md — two changes:
   • Removes a completed doc-queue URL entry (https://code.claude.com/docs/en/best-practices) and its now-empty category heading. The removal is consistent — no orphaned heading, no dangling cross-references.
   • Adds an applicability-filter clarification bullet. The new rule codifies that third-party APIs (e.g. the GitHub API) count as API surfaces with "no vendor exemption." This tightens the existing boundary rule rather than relaxing it, closing a potential loophole where a third-party API claim could have been argued into the narrower cc-applicable tag.

Checked and found nothing in scope for this review lane:

• No secrets, tokens, credentials, or PII in any changed file.
• No new outbound URLs, webhooks, or network call surfaces introduced.
• No injection surfaces — the profile is prompt/instruction content authored by the repo maintainer with no user-controlled interpolation paths.
• No trust-boundary relaxations in the applicability-filter rules.
• No plugin manifest permission widening.
• No GitHub Actions workflow files touched.