build: emit 0.5.0 + gen 0.2.1 — single emitter version across the tree

[ryandmonk]

The Studio integration for the dspack-emit@0.5.0 foundation release (dspack-emit#29, published with gitHead 84031a5), unblocked by dspack-gen#50 / dspack-gen@0.2.1.

What this changes

Dependency ranges and the lockfile. Nothing else — no code, no contracts, no profiles, no catalogs.

package	before	after
packages/contracts	emit 0.4.1 (exact)	emit 0.5.0 (exact)
apps/agent	emit ^0.4.1, gen ^0.2.0	emit ^0.5.0, gen ^0.2.1
apps/composer	emit ^0.4.1 (devDeps), gen ^0.2.0	emit ^0.5.0, gen ^0.2.1
apps/web	gen ^0.2.0	gen ^0.2.1

Why it matters beyond the version bump

This retires a trace-risk on the register since July: the tree previously resolved two emitter versions (0.4.1 direct + 0.3.1 via dspack-gen), the exact divergence that could evade gate A3. Now:

'@aestheticfunction/dspack-emit@0.5.0'   ← the only emit key in pnpm-lock.yaml
'@aestheticfunction/dspack-gen@0.2.1'    ← the only gen key

Regenerated from the npm registry; zero file:/tarball/override references (the composer's emit dep hid in devDependencies — the single-version proof caught it).

Proof the swap is behaviorally invisible

• Committed catalogs rebuild byte-identically under 0.5.0 (git status clean over packages/contracts/out/ after build:catalogs) — v1 profiles are byte-frozen by the emitter's own pinned gates, proven upstream and re-proven here.
• Contract pin intact and self-announcing: PINNED shadcn-ui.dspack.json v2.3.0 @ 805732c (sha256 verified).
• Unit suites: a2ui-ingest 3 · agui-bridge 6 · replay 21 · scenarios 5 · shadcn-renderers 16 (parity) · composer-core 50 · wireframe-renderers 4 · agent 44 · web 6 = 155.
• Typechecks clean; both static exports build; exhibit Playwright 106; composer agent-mode + accessibility 42.

Boundaries

Studio's profiles remain v1 (byte-identical); no v2 authoring is consumed here. No contract pin moves, no shadcn-v3 migration, no T1–T5. Merge and deploy remain separate decisions.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Updates the Studio workspace dependency graph to align on @aestheticfunction/dspack-emit@0.5.0 and @aestheticfunction/dspack-gen@0.2.1, ensuring a single resolved emitter version across the monorepo via updated package manifests and a regenerated pnpm-lock.yaml.

Changes:

• Bump @aestheticfunction/dspack-emit to 0.5.0 (contracts pinned; agent/composer via range).
• Bump @aestheticfunction/dspack-gen to ^0.2.1 where used (agent/composer/web).
• Regenerate lockfile so dspack-gen@0.2.1 resolves dspack-emit@0.5.0 and no older emitter versions remain.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
pnpm-lock.yaml	Regenerated lockfile reflecting dspack-emit@0.5.0 and dspack-gen@0.2.1 resolution across importers/snapshots.
packages/contracts/package.json	Pin @aestheticfunction/dspack-emit from 0.4.1 to 0.5.0.
apps/agent/package.json	Update deps to @aestheticfunction/dspack-emit@^0.5.0 and @aestheticfunction/dspack-gen@^0.2.1.
apps/composer/package.json	Update dep @aestheticfunction/dspack-gen@^0.2.1 and devDep @aestheticfunction/dspack-emit@^0.5.0.
apps/web/package.json	Update dep @aestheticfunction/dspack-gen from ^0.2.0 to ^0.2.1.

Files not reviewed (1)

• pnpm-lock.yaml: Generated file

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.