[Feature]: Update PrimeNG stack to v22

[PascaleBeier]

Summary

Update the dashboard PrimeNG stack from PrimeNG 21 to PrimeNG 22 after PrimeUI license coverage is resolved.

Problem

HitKeep's dashboard already targets Angular 22, but frontend/dashboard/package.json still uses primeng ^21.1.9 with the current PrimeUI theme/icon stack. This leaves the dashboard on a cross-major UI dependency combination and defers the real PrimeNG 22 migration work to a separate follow-up from the licensing prerequisite in #217.

As of July 1, 2026, npm lists stable primeng as 21.1.9 and the v22 release candidate as 22.0.0-rc.1. The upgrade should proceed once #217 confirms license coverage and maintainers deliberately choose whether to wait for stable v22 or adopt the release candidate.

Who Benefits

Dashboard users, contributors, self-hosted operators, and managed cloud operators benefit from keeping the Angular dashboard on a supported, aligned PrimeNG stack.

Proposed Solution

Upgrade the dashboard's PrimeNG-related packages to the compatible v22 stack, then resolve any API, styling, theme, locale, and test changes needed by the migration.

The smallest useful version should include:

• Confirm [Feature]: Obtain PrimeUI license coverage for PrimeNG 22 #217 is complete before merging the PrimeNG 22 dependency update.
• Update primeng to v22 and align related PrimeUI packages such as @primeuix/themes, icon packages, and any required license-manager/runtime package.
• Refresh frontend/dashboard/package-lock.json from a clean install.
• Review providePrimeNG, theme preset configuration, PrimeNG locale synchronization, PrimeIcons styling, and Tailwind PrimeUI integration.
• Fix component API or style regressions across common dashboard controls: buttons, selects, tables, tabs, dialogs, drawers, menus, date pickers, popovers, tags, messages, skeletons, charts, file uploads, color pickers, and form inputs.
• Run focused visual smoke checks for the main dashboard, admin/settings surfaces, authenticated forms, dialogs/drawers, tables, and date-range controls.

User Workflow

1. A maintainer confirms the PrimeUI license prerequisite from [Feature]: Obtain PrimeUI license coverage for PrimeNG 22 #217 is satisfied.
2. The maintainer updates the dashboard PrimeNG stack and lockfile.
3. The maintainer runs the frontend checks and visual smoke coverage.
4. Reviewers verify the dashboard still behaves and renders correctly before merging the upgrade.

Success Criteria

• [Feature]: Obtain PrimeUI license coverage for PrimeNG 22 #217 is closed or otherwise clearly resolved before the PrimeNG 22 upgrade merges.
• frontend/dashboard/package.json and frontend/dashboard/package-lock.json use a compatible PrimeNG 22 stack.
• npm install does not report unresolved Angular/PrimeNG peer dependency conflicts.
• Existing dashboard routes using PrimeNG components compile and render without runtime errors.
• PrimeNG locale text continues to sync through PrimeLocaleSyncService for all supported dashboard languages.
• The dashboard theme, PrimeIcons usage, Tailwind PrimeUI utilities, dialogs, overlays, and form controls keep the current HitKeep visual direction instead of introducing an unplanned redesign.
• Frontend checks pass: npm run fmt:check, npm run lint, npm run test:ci, and npm run i18n:check from frontend/dashboard.
• No PrimeUI license keys, account details, procurement records, or private eligibility evidence are committed to the repository.

Alternatives Considered

Stay on PrimeNG 21 until stable PrimeNG 22 is published and license coverage is confirmed. This avoids release-candidate churn but leaves Angular 22 paired with the older PrimeNG major for longer.

Replace PrimeNG instead of upgrading. That would be a much larger design-system migration and should only be considered if the PrimeUI licensing path in #217 is unsuitable.

Constraints

• PrimeUI licensing must be handled before the upgrade merges, and private license/procurement details must stay out of the public repository.
• HitKeep should remain a single Go binary with the embedded Angular dashboard; this upgrade must not add hosted runtime dependencies.
• Dashboard copy and locale behavior must continue to use Transloco and the existing PrimeNG locale sync service.
• The migration should be dependency-focused and avoid broad dashboard redesign unless a v22 compatibility issue requires a targeted UI adjustment.

Release Notes

Not needed unless the migration changes visible dashboard behavior.

Docs Impact

Needed. Update maintainer/dependency upgrade notes if #217 adds a PrimeUI compliance checkpoint. Public docs are not needed unless the migration changes user-facing dashboard behavior or self-hosted build requirements.

Additional Context

• Follow-up to [Feature]: Obtain PrimeUI license coverage for PrimeNG 22 #217.
• Blocked by [Feature]: Obtain PrimeUI license coverage for PrimeNG 22 #217: PrimeUI license coverage for PrimeNG 22 must be resolved first.
• Current dashboard stack includes Angular 22, primeng ^21.1.9, @primeuix/themes ^2.0.3, primeicons ^7.0.0, and tailwindcss-primeui ^0.6.1.
• npm currently exposes primeng 22.0.0-rc.1 under the rc dist-tag, with stable latest still on 21.1.9 as of July 1, 2026.