Context: Seven JSS packages (Angular, Angular Schematics, Vue, Forms, React Forms, React Native, Rendering Host) have no Content SDK equivalent. Teams using these packages have no Sitecore-provided migration path to Content SDK. Clearly marking them as archived prevents confusion and communicates that these technologies are end-of-line for Sitecore's headless story.
Steps:
1. For each of the 7 packages: add `"deprecated": "This package is archived. JSS reaches EOL June 2026. No Content SDK equivalent exists."` to `package.json`
2. Update each package's `README.md` with an "Archived" banner
3. Consider adding a `packages/archived/` directory and moving these packages there (update workspace config in root `package.json` to `packages/archived/*`)
4. Run `npm deprecate` for the published npm packages with appropriate messaging
5. Update root `README.md` package listing to distinguish active vs. archived packages
Acceptance criteria:
All 7 packages carry deprecation markers in `package.json`
npm deprecation messages published
READMEs updated with archive notices
Root README distinguishes active vs. archived packages
Risks: Moving packages to `packages/archived/` will change import paths in the Lerna workspace configuration. Verify `yarn build` still works after the move. If too disruptive, skip the directory move and rely on `package.json` deprecation markers.