release: codev-types@3.3.0 is published on npm but stale relative to source at the same version

[amrmelsayed]

@cluesmith/codev-types@3.3.0 is published on npm as latest, but the source package is also at 3.3.0 while carrying exports the published tarball lacks. Verified 2026-08-12: npm view shows 3.3.0/latest; source packages/types/package.json says 3.3.0; the published tarball is missing constants present in source (surfaced by PR #1421's Package Install Verification failure — the packaged afx crashed at module load because CI's verify-install resolves the stale registry copy of codev-types rather than a workspace tarball).

Consequences:

1. Any PR adding a runtime value-import of a new codev-types export fails Package Install Verification until the registry copy catches up (PR Enforce request authentication on the Tower local API #1421 is the live case; the Stream Deck: hands-free comment submit/cancel in review mode (dictation workflow) #1420 canvas-command union addition is also unpublished).
2. The next release will hit a version collision: pnpm publish of codev-types at 3.3.0 will be rejected (version exists), or a publish flow that skips-if-exists would silently ship the stale copy to consumers.

Needs a decision for the v3.3.0 cut: bump codev-types past the burned version (and align the workspace versioning story), and consider whether CI's verify-install should include the codev-types tarball rather than resolving it from the registry so workspace-consistent installs are what get verified.