HF-329: re-port the license key reader to the entitlement key format

Upstream handsontable/license-key 4.0.0 (DEV-2512) deleted src/typed-key/
and replaced the tagged key format with the entitlement key format:
<prose>, blank line, [<base64url-payload><sha512-checksum>]. The tagged
format was never issued to anyone (its 3.5.0 carrier was never released),
so the old reader is removed rather than kept alongside.

Re-vendored from src/entitlement-key/ at tag 4.0.0: detect-format and
extract-key-data are new ports; sha512 and utils are byte-identical
upstream and carry over. The reader is schema-free by upstream design,
so default-schema is no longer vendored and TIER_TO_CAPABILITY_TOKEN
(the tagged format's tier adapter) is gone with the format that fed it.

Resolution reads HyperFormula's own product entry only: capabilities
verbatim, exactly one of usage_until/release_until (the reader enforces
the shape), notice/grace, flags (trial + the three silent spellings).
Legacy 25-character keys and the literals are untouched; the invariant
stands - only a VALID entitlement key may restrict the entitlement.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019pxNP45obT2LZfjitaCv9o

Author: marcin-kordas-hoc

CHANGELOG.md

@@ -15,6 +15,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 ### Changed
 
 - Changed `getAvailableFunctions()` and `getFunctionDetails()` to describe only the functions the instance's license key includes, so they no longer advertise a function that would evaluate to a `#LIC!` error. A missing, invalid, or expired key does not shorten the list. [#1731](https://github.com/handsontable/hyperformula/pull/1731)
+- Changed the parser for the new proprietary license keys to the entitlement key format (a human-readable text ending with a machine-readable block in square brackets), following its upstream specification. This replaces the tagged key format, which was never issued to anyone. Classic 25-character license keys and `gpl-v3` are unaffected.
 
 ## [3.4.0] - 2026-08-10
 

docs/guide/license-key.md

@@ -29,17 +29,30 @@ const options = {
 }
 ```
 
+### Proprietary license key formats
+
+Your proprietary license key is in one of two formats, and both work the same way:
+
+* A classic key: 25 characters, for example `xxxx-xxxx-xxxx-xxxx-xxxx`.
+* An entitlement key: a short, human-readable license text that ends with a machine-readable
+  block in square brackets. Assign the whole text to the `licenseKey` option, or just the
+  bracketed block — the block is the only part HyperFormula reads, so both work. The text may be
+  re-wrapped or re-formatted on its way to you (for example, by an email client) without
+  affecting the key.
+
 ### Proprietary license key validation
 
 ::: tip
 HyperFormula doesn't use an internet connection to validate your proprietary license key.
 :::
 
 To determine whether a user is still entitled to use a particular
-version of the software, HyperFormula compares the time between
-two dates:
-* The HyperFormula build date
-* The date in your proprietary license key
+version of the software, HyperFormula compares the date in your
+proprietary license key against one of two references, depending on
+the license you purchased:
+* The HyperFormula build date, when the key ends maintenance on a set
+  date (versions released before that date keep working indefinitely)
+* The current date (in UTC), when the key ends usage on a set date
 
 This process doesn't require any connection to the server.
 

src/Config.ts

@@ -341,7 +341,7 @@ export class Config implements ConfigParams, ParserConfig {
 
   /**
    * Whether gate B (the entitlement check in the interpreter) needs to run at all for this
-   * config. `false` — the common case, for `gpl-v3`, legacy keys, and an unrestricted typed
+   * config. `false` — the common case, for `gpl-v3`, legacy keys, and an unrestricted entitlement
    * key — is a single boolean read, cheaper than the string-enum comparison it replaces.
    *
    * @internal

src/helpers/licenseKeyValidator.ts

@@ -74,7 +74,7 @@ export function resetLicenseKeyNotificationForTests(): void {
 /**
  * Prints the console message for a non-valid license key state, at most once per page load.
  *
- * Extracted so the typed-key path in `src/license/licenseResolution.ts` reports the same states
+ * Extracted so the entitlement-key path in `src/license/licenseResolution.ts` reports the same states
  * with the same wording and the same once-only behaviour, without duplicating the message table
  * or getting a second `_notified` flag of its own — two flags would let a page print two
  * warnings for one key.
@@ -95,7 +95,7 @@ export function notifyLicenseKeyState(state: LicenseKeyValidityState, keyValidit
 }
 
 /**
- * Prints a one-time notice that a VALID typed key's usage-until expiry is approaching, at most
+ * Prints a one-time notice that a VALID entitlement key's usage-until expiry is approaching, at most
  * once per distinct license key string.
  *
  * Called from `src/license/licenseResolution.ts`'s `resolveLicense`, alongside
@@ -154,7 +154,7 @@ export function checkLicenseKeyValidity(licenseKey: string): LicenseKeyValidityS
  * Formats a Date instance to hard-coded format MMMM DD, YYYY.
  *
  * Read in UTC, not local time. Every date reaching this function is built at UTC midnight — the
- * legacy path from a whole number of days since the epoch, the typed-key path from a calendar
+ * legacy path from a whole number of days since the epoch, the entitlement-key path from a calendar
  * date in the payload — so local getters shifted the day backwards for anyone west of UTC and
  * printed an expiry one day earlier than the one the key actually carries.
  *

src/license/LicenseEntitlement.ts

@@ -84,7 +84,7 @@ export interface LicenseEntitlement {
 /**
  * The unrestricted entitlement: legacy keys and `gpl-v3` resolve to this today.
  *
- * HF-307 decision D3 (fail-closed, silent) means a typed key whose tokens this library version
+ * HF-307 decision D3 (fail-closed, silent) means an entitlement key whose tokens this library version
  * does not recognize at all no longer maps here — it resolves to an entitlement with an empty,
  * silent capability set instead of falling back to unrestricted access. Do not reuse this
  * function for that case.

src/license/capabilities.ts

@@ -27,9 +27,9 @@ export const NAMED_EXPRESSIONS_FEATURE_TOKEN = 'feat:named_expressions'
 export const BATCHING_FEATURE_TOKEN = 'feat:batching'
 
 /**
- * Every feature token, in one list, for the shipped-shape adapter: the shipped key vocabulary
- * predates feature tokens entirely, so a commercial tier is translated into its functions token
- * PLUS all of these — see `licenseTermsOf` for the reasoning.
+ * Every feature token, in one list, for the opt-in rule in `licenseTermsOf`: a key naming no
+ * `feat:*` token at all is granted all of these, because no key vocabulary in circulation can
+ * express "no features" — see that function for the reasoning.
  */
 export const ALL_FEATURE_TOKENS = [
   CRUD_FEATURE_TOKEN, UNDO_REDO_FEATURE_TOKEN, CLIPBOARD_FEATURE_TOKEN,
@@ -79,7 +79,7 @@ const OPERATOR_FUNCTIONS = [
 ]
 
 // An earlier revision granted all five features from CORE_TOKEN, which made feature gating inert
-// by construction: no typed key could ever lose an API area. Kuba's call (task comment, 12.08):
+// by construction: no restricted key could ever lose an API area. Kuba's call (task comment, 12.08):
 // "Feature gating should work, but the legacy keys should grant all feat:* capabilities" — legacy
 // keys already resolve to the unrestricted entitlement, so the carve-out costs nothing, and the
 // five features moved onto their own `feat:*` tokens below.
@@ -201,9 +201,9 @@ const functions4Grant: CapabilityGrant = {
  * in `unit/license/capability-registry.spec.ts` fails on.
  *
  * The five `feat:*` tokens carry the gated API areas, one feature each, spelled after the draft
- * vocabulary in the task. A rev-5 key states them explicitly; the shipped-shape adapter grants
- * all five alongside the tier (that vocabulary predates feature tokens); legacy keys resolve to
- * the unrestricted entitlement and never consult this table.
+ * vocabulary in the task. A key may state them explicitly; a key naming none is granted all five
+ * (the opt-in rule in `licenseTermsOf`); legacy keys resolve to the unrestricted entitlement and
+ * never consult this table.
  *
  * The two add-on tokens, wired per the 2026-08-12 packages meeting: `spreadsheet` backs the
  * 'Spreadsheet Bundle' add-on and grants {@link FeatureId.Crud}, {@link FeatureId.UndoRedo},