#1165 Make a vetted subset of the library declarable

[williamthorsen]

What

Vetted guidance artifacts (skills, subagents, and rulebooks) are now organized into two nascent collections: recommended (generally applicable) and williamthorsen (the maintainer's personal rulebooks). The triage collection contains all unvetted guidance. The all set continues to deploy all guidance.

Why

collections.use: [all] was the only declaration that deployed a usable set, so a consumer took the whole catalog including artifacts they had no use for. Anything narrower deployed almost nothing, and no collection said anything about why its members belonged to it, so there was nothing to choose between.

Details

🎉 Features

• recommended is now the vetted general set, williamthorsen the vetted personal set, and triage the default home for content nobody has read yet. Each collection body states what its membership claims and why each member qualifies.
• Collections enumerate every member rather than their dependency roots. Roots-only membership would let an unexamined artifact enter through an edge and be treated as examined, which is the outcome the closure check exists to prevent.
• The criteria deciding an artifact's disposition are recorded in the codeassembly-content-specification rulebook (version 7 → 8), so promoting an artifact is a delegable act rather than a judgment re-derived each time. The criteria name two reading passes, because environment coupling hides in a default value rather than in prose and survives a read that looks only for doctrine.
• An artifact in no collection is standalone: deliberate, declared directly where wanted, and too rarely invoked to repay a standing line in the skill index. canary, codeassembly-content-specification, and migrate-feedback-memories start there.

🐛 Bug fixes

• init --global seeds recommended and triage, and its comment explains what each collection claims.
• common-mistakes, design-and-plan, and wrap-up declare edges for the skills their prose names, so those skills survive a declaration narrower than all.
• capture-event documents the kb.yaml registry prerequisite alongside its Node version floor, so a reader learns of it before invoking rather than on refusal.
• Four enforcement notes in the content specification named test files without their tier suffix.

🧪 Tests

• A coverage check fails when an artifact carries no disposition, more than one, or a disposition naming an artifact the library no longer holds.
• A closure check fails when a vetted collection reaches an artifact of lesser standing, and when any collection's closure reaches a standalone artifact. Standalone buys a skill-index line nobody pays for unless they ask, and that survives only while no closure reaches the artifact.
• Both checks run against fixture content roots that reproduce the failures, and assert on message text so a message that stops naming the artifact fails.

🤖 Agentic support

• AGENTS.md states that the repository is public, and that the package manifests' private: markers describe registry publication rather than who can read the source.

📚 Documentation

• The package README describes the four shipped collections and the claim each carries, and points at the rulebook holding the promotion criteria.
• all documents that it is the escape hatch rather than the expected declaration: it deploys the vetted, the unexamined, and the deliberately omitted alike, and a new artifact joins it before anyone has read it.

Closes #1165

[github-actions]

Dependency audit

Production dependency audit passed.