fix(deploy): co-locate core and creative context Nitro chunks

[steve8708]

Summary

Fixes #2752 by keeping @agent-native/core and @agent-native/creative-context in one Nitro server chunk for Node-style presets. Their separate generated chunks form a live-binding cycle that crashes standalone Vercel and Netlify cold starts.

Verification

• corepack pnpm --filter @agent-native/core exec vitest run src/deploy/build.spec.ts - 166 passed
• corepack pnpm guards - all 66 checks passed
• Standalone Content Vercel build plus cold-start import - passed
• Standalone Content Netlify build and deploy guard plus cold-start import - passed
• Before fix: reproduced ReferenceError: Cannot access 'xee' before initialization from the generated Core chunk

Feedback handoff

Source: #product-agent-native-feedback (C0ATH3CCZT4), 263 parent messages across 3 history pages, 2026-08-29 00:00 PDT through 2026-09-03 05:31 PDT. A latest-message search found no newer parent.

Disposition	Items
Fixed	GitHub #2752 standalone deploy TDZ crash
Already owned or in progress	Clips recording failure matched existing PR #4225; Slides undo blank deck matched existing PR #4245; other active Clips and Slides threads retained with their owning fixes
Resolved	Calendar auth and Calendar error threads confirmed resolved
External or non-repo-owned	Design feedback routed to Sid; Content feedback remains with Alice; beta storage/configuration and deployment-only reports retained with their owners
Awaiting clarification	Only older reporter-specific threads whose requested run, trace, or product detail is still missing; no duplicate questions sent

One authorized Slack reply was posted for the Clips recording thread, ended with this was sent from a bot., and the complete thread was read back with no follow-up.

[github-actions]

Here's a visual recap of what changed:

Open the full interactive recap

[steve8708]

Addressed both review findings in 59dd977:

• Moved the package group into rolldownConfig, which is the Nitro 3 builder path. Added an integration test that invokes Nitros real builder and asserts one agent-native-core+...mjs` chunk contains both package markers.
• Included aws_amplify, aws-amplify, and awsAmplify in the grouping predicate. The existing Yjs predicate stays unchanged because Amplify uses its self-contained bundle path.

Local validation: Core build, 168 focused tests, and all 66 guards pass.

[builder-io-integration]

Builder reviewed your changes — looks good ✅

Review Details

Incremental Code Review Summary

The updated PR correctly addresses both previously reported issues. The code-splitting configuration now flows through rolldownConfig, and the grouping predicate includes all AWS Amplify aliases. The new integration coverage builds a temporary Nitro app and verifies that Core and Creative Context are emitted into the same package chunk, which directly tests the failure mode rather than only checking the helper or regex.

I resolved the two stale previous-review threads before this review. Two parallel incremental code-review passes found no new confirmed bugs. They verified Nitro 3's effective Rolldown merge order, checked the supported Node/Netlify/Vercel/AWS Lambda/AWS Amplify and edge preset coverage, and confirmed the new integration test passes. One agent noted unrelated pre-existing temporary-worker h3 resolution failures in the broader suite; the new Nitro test itself passes.

Risk remains standard because this changes shared deployment infrastructure, but the revised approach and targeted emitted-chunk assertion are sound.

🧪 Browser testing: Skipped — PR only modifies backend/build configuration and tests, with no user-facing UI impact.