[clbotdev]

Why

CourseLit needs tag management (contact counts, rename everywhere, delete) and would otherwise re-implement the dashboard's Tags page, which is how the last round of copies drifted. The screen now lives in @sendlit/email-blocks and the dashboard uses the same export.

What

• TagManager in @sendlit/email-blocks: lists every tag with its contact count, renames a tag everywhere it's used, and deletes one after showing the segments, broadcasts, sequences and signup forms that still name it. The host passes:
  • listTags, getTagReferences, renameTag, deleteTag (its calls to SendLit's /tags endpoints, made through its own backend);
  • optional sequenceHref and linkComponent for the "still used in" links, a loadingIndicator, and an errorMessage mapper.
• The dashboard's Contacts → Tags page is now TagManager with the dashboard's API calls, Link, Loading and ApiError messages. Behaviour and copy are unchanged.
• Tag types (TagSummary, TagReferences, RenameTagResult, DeleteTagResult) are declared in the package and exported. Importing them from the private @sendlit/api-contract made the published .d.ts point at a chunk that doesn't exist; a test checks the local types match the contract.
• Docs page and a minor changeset for @sendlit/email-blocks.

Tests

• bun --filter @sendlit/email-blocks test: 22 pass, including new tests for the notice text and for the types matching the contract.
• tsc --noEmit clean for the package and apps/web; bun run build of the package emits tag-manager.d.ts resolving to tag-manager-types.
• Not checked in a browser here: the dashboard page is a thin wrapper over the component, and CourseLit's local test of the component was blocked by an older local SendLit API without /tags.