[Feature]: Obtain PrimeUI license coverage for PrimeNG 22

[PascaleBeier]

Summary

Obtain the appropriate PrimeUI license coverage before upgrading HitKeep's dashboard to PrimeNG 22.

Problem

HitKeep's dashboard currently depends on PrimeNG 21 (primeng ^21.1.9). PrimeTek's PrimeUI announcement says future major versions, including PrimeNG 22, will be distributed under the PrimeUI license and will no longer be released as open source. Existing MIT-licensed versions remain MIT, so this is not urgent for the current PrimeNG 21 dependency, but it must be resolved before any PrimeNG 22 upgrade.

Who Benefits

HitKeep maintainers, contributors, self-hosted operators, and managed cloud operators benefit from a clear licensing path that keeps dashboard dependency upgrades compliant and predictable.

Proposed Solution

Decide whether HitKeep qualifies for the PrimeUI Community License or requires the Commercial Suite, then register or purchase the needed per-developer license coverage before starting a PrimeNG 22 upgrade.

The smallest useful version should include:

• Confirm HitKeep's eligibility against the Community License thresholds.
• Determine how many developer seats need coverage for maintainers who write, modify, or maintain dashboard code using PrimeNG.
• Obtain the license through PrimeUI's official flow.
• Document where maintainers can find renewal/procurement details without committing license keys or sensitive account data.
• Add a release/upgrade checklist item that blocks PrimeNG 22 adoption until license coverage is confirmed.

User Workflow

1. A maintainer plans or opens a dependency update from PrimeNG 21 to PrimeNG 22.
2. The maintainer checks the PrimeUI license status and confirms whether Community or Commercial coverage applies.
3. The maintainer obtains/renews the required license coverage before merging the PrimeNG 22 upgrade.
4. The upgrade proceeds with license keys or procurement details handled outside the public repository.

Success Criteria

• HitKeep has a documented decision on Community vs. Commercial PrimeUI licensing for PrimeNG 22.
• Required per-developer seats are identified and covered before a PrimeNG 22 upgrade is merged.
• No PrimeUI license key, account credential, procurement record, or private eligibility evidence is committed to the public repository.
• The PrimeNG 22 upgrade path includes a compliance checkpoint for license coverage and renewal timing.
• Current PrimeNG 21 usage remains unchanged unless and until a separate upgrade issue/PR moves the dashboard to PrimeNG 22.

Alternatives Considered

Stay on the current MIT-licensed PrimeNG 21 line until a license decision is complete. This avoids immediate licensing changes but does not provide a long-term Angular/PrimeNG upgrade path.

Evaluate replacing PrimeNG before the PrimeNG 22 upgrade. This would be a larger product and design-system migration and should only be considered if PrimeUI licensing is unsuitable.

Constraints

• HitKeep is an open-source project with public issue tracking, so license keys, procurement details, private account data, and eligibility evidence must stay out of the repository.
• Community licenses are per developer, have eligibility thresholds, and require annual renewal.
• Commercial licensing may be required if HitKeep or its operating organization exceeds the Community thresholds.
• Self-hosted and managed deployments should not gain a runtime dependency on PrimeTek services; PrimeUI describes license verification as offline-first.
• This task should not imply that existing MIT-licensed PrimeNG versions lose their current rights.

Release Notes

Docs Impact

Needed. Document the internal upgrade/procurement checkpoint if PrimeNG 22 adoption becomes part of the roadmap. Public docs are not needed until there is a user-facing dependency or deployment impact.

Additional Context

• PrimeUI announcement: https://primeui.dev/nextchapter
• PrimeUI Community License: https://primeui.dev/licenses/community
• The announcement states the new license applies to future major versions including PrimeNG 22, while existing MIT-licensed versions remain MIT.
• The Community License page, last updated June 30, 2026, lists eligibility thresholds, a maximum of 4 developer seats per organization, and a 12-month renewal term.