Add shared control primitives

[brxs]

Summary

• release @protocol-works/ui 0.2.0 with reusable checkbox, switch, slider, number field, segmented control, empty state, section header, modal, popover, and tooltip primitives
• keep the package’s established Button, Input, Card, Tag, Note, and typography variants canonical instead of importing Rabbithole-specific variants
• extend Note with optional action and dismissal support for product toast adapters
• add Radix Tooltip as a package-owned accessibility dependency
• document every new direct subpath export and retain the no-barrel package contract

Why

Rabbithole and the protocol.works website should consume one shared primitive layer. Product repositories should own only runtime adapters, domain composites, and genuinely product-specific visual recipes such as Rabbithole’s instrument Select.

Verification

• npm ci
• npm run check
• npm pack --dry-run --workspace @protocol-works/ui
• Rabbithole integration tested against the generated 0.2.0 tarball
• Rabbithole formatting, lint, 37 frontend tests, production build, and dark-theme browser validation pass