chore: migrate packages/intelligence/ to synapt-private per boundary policy

[laynepenney]

Context

packages/intelligence/ was shipped in extract (OSS) during Sprint 32 (PR #15). Per CLAUDE.md's Premium Boundary Policy, intelligence queries (entity timeline, goal tracking, cross-extraction entity matching, theme trends) are differentiated workflow behavior -- the value-add layer that Conversa and other consumers would pay for.

"Identity, org semantics, entitlements, quality scoring, automated improvement, advanced orchestration = premium"
"When in doubt, it's premium."

The schema, validators, prompts, and dogfood example remain OSS in extract for adoption. The intelligence query layer becomes premium.

Violation protocol

Per CLAUDE.md: "if premium code lands in OSS, fix is a migration PR, not a revert."

Plan

1. Remove packages/intelligence/ from extract entirely
2. Move source to synapt-private (preservation, not productization)
3. Update CHANGELOG with boundary correction note
4. Bump extract to v0.2.1 patch
5. Open corresponding PR in synapt-private for the addition

Productization of the intelligence library (persistence, identity-tied queries, semantic search) is Sprint 33 scope.

Premium boundary: intelligence queries are premium (differentiated workflow behavior). Schema + validators stay OSS.