Context: Content SDK packages inconsistently declare their Node.js engine requirement. `core`, `content`, `react`, `nextjs`, `search`, `cli`, and `create-content-sdk-app` all specify `"engines": { "node": ">=24" }`, but `analytics-core`, `events`, and `personalize` lack this field entirely. These packages depend on `core` (which requires Node 24) and use modern APIs, so they effectively require Node 24 but do not declare it.
Steps:
1. Add `"engines": { "node": ">=24" }` to `packages/analytics-core/package.json`
2. Add the same to `packages/events/package.json`
3. Add the same to `packages/personalize/package.json`
4. Run `yarn install` and verify no warnings
Acceptance criteria:
All 10 packages in the monorepo declare `"engines": { "node": ">=24" }`
`npm pack --dry-run` shows engines field in each package
Risks: None identified.