@ti-engine/web-framework 1.19.0 → 1.20.0

package/CHANGELOG.md

@@ -1,353 +1,384 @@
-# ti-engine web-framework changelog
-
-This document will contain the list of changes made to the framework. The format is based on the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification.
-
-## Version 1.19.0
-
-`/static` was served with `max-age=1y, immutable` for every consumer of the framework. `immutable` is a promise that the bytes behind a URL will never change, and browsers honour it so completely that not even a manual reload revalidates — so the promise is only true for a content-addressed URL (`app.a1b2c3.css`). None of the framework's own assets are named that way (`/static/scripts/ti-framework.js`, the theme sheets), which made this an unsafe default that shipped to npm: a deployed CSS or JS fix would never reach anyone who had already visited, for up to a year, with no way to tell them otherwise. The standalone author's site had worked around it privately by fingerprinting its own asset URLs; every other consumer still inherited the bug.
-
-* fix(web-server)!: the default `/static` cache policy is now `public, max-age=0, must-revalidate` instead of `max-age=1y, immutable`, so a deployed asset change actually reaches a returning visitor. `express.static` still attaches an `ETag`/`Last-Modified`, so a revalidation of an unchanged asset is answered with a `304` — headers, no body. **A consumer whose asset filenames are content-addressed should opt back in** with `staticCache: { maxAge: 31536000, immutable: true }`; one that appends a content hash to its asset URLs (rather than to the filenames) is equally entitled to it
-* feat(web-server): add the `staticCache` configuration block — `maxAge` (whole **seconds**, mapping 1:1 onto the `Cache-Control` directive; an express-style `"1y"` duration string is reported rather than silently reinterpreted as milliseconds), `immutable`, and `immutablePaths` (path prefixes served long-lived and `immutable` regardless of the other two). `immutable` combined with a `maxAge` of 0 is a contradiction and is dropped with a warning, so a half-configured deployment costs a revalidation rather than a year of unreachable assets
-* feat(web-server): `staticCache.immutablePaths` defaults to `[ "/fonts/" ]` — a released `.woff2` is an artifact rather than something edited in place, and its filename already carries the family, weight and style. Configurable, and clearable with an explicitly empty array, because that is a statement about how a given deployment manages its font files
-* feat(web-framework): add the `TI_WEB_STATIC_MAX_AGE`, `TI_WEB_STATIC_IMMUTABLE`, and `TI_WEB_STATIC_IMMUTABLE_PATHS` environment overrides, so the cache policy is settable per deployment like every other web setting; `TI_WEB_STATIC_IMMUTABLE_PATHS` **replaces** the array, and an explicitly empty value means no long-lived paths
-* refactor(web-server): the `/static` mounts write `Cache-Control` per file through `express.static`'s `setHeaders` rather than its `maxAge`/`immutable` options, since the policy is no longer uniform across the tree; the decision itself lives in the pure, unit-tested `TiWebServer.resolveStaticCachePolicy()` (config → policy + warnings, which the caller logs) and `TiWebServer.staticCacheControlFor()` (policy + file → header). The `staticCache` defaults deliberately live on the class rather than in `web-server.json`, because the constructor's `_.merge` merges arrays by index and a consumer's empty `immutablePaths` could otherwise never clear a default entry
-* docs(web-framework): document the `staticCache` block, the revalidating default and the reasoning behind it, and the fingerprinting opt-in in the README
-* build(release): bump package version from `1.18.1` to `1.19.0`
-
-## Version 1.18.1
-
-Enabling Azure SSO took the instance down at startup: the OAuth2 callback was registered by handing the configured callback value straight to Express as a route path, and the installation docs tell operators to set that value to the full absolute URL registered with the identity provider. Express 5 parses route patterns with path-to-regexp v8, where `:` opens a parameter name — so `https://host/login/azure-callback` throws `Missing parameter name at index 6` and the web server never starts. Google was affected identically, which also made this a prerequisite for the competence Cloud Run deployment, whose `deploy.sh` patches in an absolute callback URL (CA-97).
-
-* fix(web-framework): register an OAuth2 callback by its **path** rather than by the configured value verbatim, so a callback given as the absolute URL registered with the provider no longer crashes startup; a callback that yields no usable path now logs a WARNING and skips that provider's endpoint instead of taking the instance down, matching how an enabled-but-unconfigured provider is already handled
-* feat(web-framework): add `AuthManager.getOAuth2CallbackPath( authMethod )` and the pure, unit-tested `AuthManager.toCallbackPath( callbackUrl )` — reduces an absolute, protocol-relative, path or bare relative callback to its route path (query string and fragment stripped), or `null` when no usable path can be derived. The `redirect_uri` sent to the provider is deliberately left as configured, so an absolute callback keeps matching the provider registration exactly instead of depending on the forwarded protocol/host being correct
-* docs(web-framework): document the OpenID Connect provider variables in the README, and state in the README, the competence `INSTALL.md` and `.env.example` that a callback URL may be given as either the absolute registered URL or a path — including what each implies for the `redirect_uri`, and that the path must be the one the app actually receives when a proxy strips a prefix
-* build(release): bump package version from `1.18.0` to `1.18.1`
-
-## Version 1.18.0
-
-Every web-server setting a container deployment needs could be supplied per environment except one: the admin allowlist. `auth.admins` was readable only from the config file baked into the image, so a containerized deployment had no way to name an administrator — leaving the admin configuration screens unreachable, or forcing a real identity to be committed to the repository. This closes that gap in the existing `TI_WEB_*` override set (CA-94).
-
-* feat(web-framework): add the `TI_WEB_AUTH_ADMINS` environment override — comma-separated, **replaces** `auth.admins` (matched against the session user's user ID, username or email), so the admin allowlist is configurable per environment like every other web setting; an explicitly empty value means no admins
-* docs(web-framework): document `TI_WEB_AUTH_METHODS` and `TI_WEB_TRUSTED_ORIGINS` in the README's environment-variable list, which had never listed them
-* build(release): bump package version from `1.17.1` to `1.18.0`
-
-## Version 1.17.1
-
-A validator that needs to compare its own config document against its previously committed state had no way to do so: `applyEdits`'s cross-document context resolves `getConfig` to the *pending* value for any document inside the current edit batch — by design, so a validator can check a sibling document's post-edit state — but a document is always part of its own edit batch, so calling `getConfig` on itself just hands back the same incoming value already passed as the validator's argument, never its prior state. This silently defeated the competence `research-consent` config's version-bump guard (CA-93).
-
-* feat(web-framework): add `getStoredConfig(key)` to the `applyEdits` validator context (`ConfigService`) — always resolves the current *committed* value from the store, even for the document currently under validation, so a validator comparing its own document against its previous state has a way to do it; purely additive — `getConfig`'s existing cross-document (pending-value) semantics are unchanged
-* build(release): bump package version from `1.17.0` to `1.17.1`
-
-## Version 1.17.0
-
-Route-registration seams so an application subclass can add its own Express routes and unprotected-route patterns — enabling public, content-driven sites (the first consumer being the standalone author's site) to layer a catch-all content resolver over the framework without reaching into private state.
-
-* feat(web-server): add `TiWebServer.registerRoute( method, path, ...handlers )` — registers a custom route on the underlying Express app from a `defineWebApplicationRoutes()` override (after `super()`), so a catch-all resolver can be mounted after the framework's own routes but before its `*splat` 404 handler. Limited to route-scoped verbs (get/post/put/patch/delete/options/head/all); raises `E_GEN_INVALID_ARGUMENT_TYPE` for any other method and `E_GEN_NOT_INITIALIZED` if called before the Express app exists. The method must be a **string** — a non-string is rejected outright rather than coerced, so a value whose `toString()` happens to yield a verb (`[ "get" ]`, `new String( "get" )`) cannot slip past the allowlist and register a route
-* feat(web-server): add `TiWebServer.addUnprotectedRoute( pattern )` — appends a string (exact-match) or RegExp (tested) pattern to the unprotected-routes list from a `defineUnprotectedRoutes()` override, so a public-by-default site can invert the framework's protect-by-default stance; non-string/non-RegExp values are ignored with a warning
-* refactor(web-server): extract the unprotected-route matching loop from `isUnprotectedRoute()` into the pure, unit-tested `isRouteInList()` helper (behavior unchanged, including the defensive `lastIndex` reset), and add the `normalizeRegistrableMethod()` helper — both exported for testing alongside the existing `RE_*` matcher constants
-* build(release): bump package version from `1.16.0` to `1.17.0`
-
-## Version 1.16.0
-
-Support explicitly trusted request origins so state-changing requests (e.g. login) work behind proxies that do not present the app's external host — most notably GitHub Codespaces port forwarding (CA-90).
-
-* feat(web-framework): add `TI_WEB_TRUSTED_ORIGINS` (comma-separated) / `config.trustedOrigins`. The `originRefererValidationHandler` now accepts a non-GET request whose `Origin`/`Referer` matches the server-reconstructed base URL **or** any configured trusted origin. Previously such a request behind a proxy that rewrote/omitted the forwarded host was rejected with `E_WEB_INVALID_REQUEST_PARAMETERS` (HTTP 403). Backward compatible (empty list = prior behavior); the CSRF double-submit token check is unchanged and still enforced
-* build(release): bump package version from `1.15.0` to `1.16.0`
-
-## Version 1.15.0
-
-A dedicated health endpoint, a `TI_WEB_AUTH_METHODS` env override, and login-page gating for every auth method — completing the container-friendly auth/health story for the competence deployment (CA-90).
-
-* feat(web-framework): add an unprotected `GET /health` endpoint (`healthHandler`) that returns `200` with `{ status, broker, uptime }` — a purpose-built liveness/readiness probe for container and orchestrator health checks, so probes no longer have to hit the user-facing login route; `broker` reports the Redis connection state
-* feat(web-framework): add the `TI_WEB_AUTH_METHODS` env override (comma-separated) which REPLACES `auth.enabledMethods` — a clean, 12-factor way to select enabled auth methods per deployment (the config-file merge is by-index and cannot cleanly override an array)
-* feat(web-framework): extend login-page auth gating from the OAuth buttons to every method — the `local` credentials form and the "or continue with" divider are now gated too, and a "no method configured" fallback is shown when nothing is enabled, so an SSO-only deployment presents no dead local form
-* build(release): bump package version from `1.14.1` to `1.15.0`
-
-## Version 1.14.1
-
-Security hardening for the web-server CodeQL findings raised after the scanner was modernized in CA-90 (CA-91).
-
-* fix(web-framework): rewrite the default unprotected static-asset route matchers from the ambiguous `(?:.+/)*` to segment-anchored `(?:[^/]+/)*` — the previous form backtracked exponentially and is evaluated against the raw request path in `isUnprotectedRoute()` before authentication, making it a pre-authentication denial-of-service vector (CodeQL js/redos); the matched language for realistic asset paths is unchanged, and the matchers are now the `RE_STATIC_UNPROTECTED` / `RE_WELL_KNOWN_UNPROTECTED` module constants
-* fix(web-framework): replace the login-fragment section stripper's `open[\s\S]*?close` global-regex removal with a linear `indexOf`-based `stripMarkerSpans()` helper (also used for the per-provider stripper), eliminating the polynomial-time rescan on hostile input (CodeQL js/polynomial-redos)
-* docs(web-framework): document that Helmet's built-in Content-Security-Policy is intentionally disabled because a per-request, nonce-based CSP is enforced by `cspHeaderHandler()` on the following middleware — added an explanatory comment and an inline CodeQL suppression (the alert is a false positive)
-* build(release): bump package version from `1.14.0` to `1.14.1`
-
-## Version 1.14.0
-
-`TI_WEB_*` environment-variable overrides for the web server configuration, enabling 12-factor container deployments without per-environment config files (CA-90).
-
-* feat(web-framework): add `applyWebConfigEnvOverrides( config, env = process.env )` (`#web-config-env`) — a pure helper applying `TI_WEB_HOST`, `TI_WEB_PORT`, `TI_WEB_USE_TLS`, `TI_WEB_TLS_CERT_PATH`, `TI_WEB_TLS_KEY_PATH`, and `TI_WEB_COOKIE_SECRET` overrides onto the merged `TiWebServer` configuration, only when each variable is defined (fully backward compatible)
-* fix(web-framework): skip an enabled OpenID Connect provider that has no client ID instead of crashing the instance during discovery — an OAuth-less deployment (e.g. a container started without OAuth credentials) now boots on its remaining methods, with a warning, and reports the dropped provider as unavailable so a sign-in attempt against it fails per-request rather than at startup
-* feat(web-framework): the login page now renders an OpenID provider button only when that provider is an effective enabled auth method — the web server passes the post-drop enabled methods to the app manager, which strips the Google/Azure button (and the whole "or continue with" section when no provider is available) from `frame-login.html` at render time
-* build(release): bump package version from `1.13.2` to `1.14.0`
-
-## Version 1.13.0
-
-A reusable role-based screen gate and a per-screen title override (back the competence screen-access work and the evaluation/scores screen split).
-
-* feat(web-framework): the default `TiWebAppManager.verifyAccess` now enforces a fragment's declared `roles` — a fragment registered (via `addFragment`) with a `roles` array is served only to sessions holding at least one of them (otherwise rejected `E_SEC_UNAUTHORIZED_ACCESS` 403), while a fragment with no `roles` stays public. This makes role-restricted screens unreachable by direct URL, not merely hidden in the UI; apps just declare `roles` on `addFragment` — no `verifyAccess` override needed. Backward compatible: all existing role-less fragments remain public
-* feat(web-framework): add `authorization.isAccessAllowed( requiredRoles, userRoles )` — a pure, unit-tested access decision (empty/absent roles = public; otherwise ≥1 overlap; no implicit hierarchy, so an `admin` gate is never satisfied by a numeric role) that backs the default `verifyAccess`
-* feat(web-framework): add `tiApplication.setScreenTitle( title )` — a per-screen topbar/document-title override (cleared automatically on navigation) so a screen can correct its own title at runtime (e.g. a manager viewing another user's scores must not read "My …")
-* build(release): bump package version from `1.12.0` to `1.13.0`
-
-## Version 1.12.0
-
-Chart primitives gain legends + value labels for grouped bars and a legend for radar (backs the leaner competence evaluation results view) (CA-61).
-
-* feat(web-framework): `ti-charts` grouped bars now render an optional swatch legend (`options.legend`) and per-bar value captions (`options.valueLabels`); radar charts render an optional legend, with a dashed swatch variant (`{ dashed: true }`) for dashed series such as an "expected" curve (CA-61)
-* feat(web-framework): add `.ti-chart-bar-seg.tone-info`, `.ti-chart-legend-swatch.tone-info`, and `.ti-chart-legend-swatch.is-dashed` so grouped/radar source series and their legends share one colour scale across both themes (CA-61)
-* feat(web-framework): `ti-charts` radar accepts an optional per-axis `tone`, applied as a `tone-*` class on the axis label so consumers can colour axis labels (e.g. by category) — threaded through `radarLayout` (CA-61)
-* feat(web-framework): `ti-charts` grouped bars accept optional `options.barThickness` (bar height) and `options.valueFontSize` (value-caption font); value captions carry a dedicated `ti-chart-bar-value` class that intentionally sets no CSS `font-size`, so the renderer's `font-size` presentation attribute (default 4) actually governs — previously the caption also carried `ti-chart-bar-label`, whose CSS `font-size: 4px` overrode the attribute and made `valueFontSize` a no-op (CA-61)
-* build(release): bump package version from `1.11.1` to `1.12.0`
-
-## Version 1.11.1
-
-Post-review fix from the CA-72 CodeRabbit review (PR #85) on the login test-user panel.
-
-* fix(web-framework): turning the "override roles (dev)" toggle OFF now always strips any persisted roles from the `ti-test-user` cookie — even when the selected employee is no longer in the panel's profile list — so a stale roles array can't keep overriding the app's org-derived roles on the next login (CA-72)
-* build(release): bump package version from `1.11.0` to `1.11.1`
-
-## Version 1.11.0
-
-Login test-user panel defaults to identity-only injection so the app derives roles itself (CA-72).
-
-* feat(web-framework): login test-user panel injects identity only by default (roles derived by the app); role injection becomes an opt-in dev override (CA-72)
-* docs(web-framework): clarify the augmentSession contract (derive vs. override) (CA-72)
-* build(release): bump package version from `1.10.4` to `1.11.0`
-
-## Version 1.10.4
-
-Login test-user fixture follow-up (CA-71).
-
-* chore(web-framework): login test-user `8` carries the `MANAGER` role (`[1, 2]`) so manager / self-manage scenarios (e.g. the competence Org Chart self-manage gate) can be exercised without re-seeding
-* build(release): bump package version from `1.10.3` to `1.10.4`
-
-## Version 1.10.3
-
-Developer-tooling and formatting touch-ups on the shared frontend bundle.
-
-* chore(web-framework): the login test-user panel offers more seeded employees (3, 8, 9 alongside 22/20/1/4) so manager / direct-report / skip-level scenarios can be exercised without re-seeding
-* style(web-framework): minor formatting of `formatException`'s return object
-* build(release): bump package version from `1.10.2` to `1.10.3`
-
-## Version 1.10.2
-
-Readability and scaling fixes for the chart primitives, surfaced while polishing the Statistics & Results screens (CA-61).
-
-* fix(web-framework): stacked bar charts now caption each row (the group/cycle label plus an optional per-row value) and render an optional swatch legend driven by `spec.options.legend`, so a coverage "By group" chart reads as labelled bars instead of anonymous colour blocks; the row labels also land on the cross-cycle trend bars
-* fix(css): horizontal bar charts opt out of the global `svg` `max-height` so bar thickness and label size stay identical regardless of row count — a tall org-wide chart is no longer uniformly scaled down and rendered finer than the same chart on a smaller subtree; the per-row geometry is trimmed for a cleaner look
-* feat(css): `.ti-chart-legend` / `.ti-chart-legend-item` / `.ti-chart-legend-swatch` — a chart swatch legend whose colours route through the inherited grade/ink chart tokens
-* build(release): bump package version from `1.10.1` to `1.10.2`
-
-## Version 1.10.1
-
-Review fixes for the ti-chart primitives (Statistics & Results, CA-61, PR #83 — CodeRabbit pass).
-
-* fix(web-framework): drillable heatmap/box marks get an accessible name; `renderChart` clears stale `data-ti-chart-empty`/`aria-label` on rerender; `renderStat` renders a missing value as an em dash; the provisional line-dot stroke follows its `tone-*` class
-* fix(css): `.ti-chart-sr` uses `clip-path: inset(50%)` instead of the deprecated `clip` property
-* build(release): bump package version from `1.10.0` to `1.10.1`
-
-## Version 1.10.0
-
-### Charting primitive library (Statistics & Results, CA-61)
-
-* feat(web-framework): new `ti-charts.js` — a CSP-safe SVG charting library backing the competence Statistics & Results reporting. Eight primitives via a single `renderChart(figure, spec)` dispatcher: `gauge`, `bars` (stacked / grouped / diverging modes), `stat`, `scatter`, `heatmap` (sequential / diverging scales), `box`, `radar`, and `line` (mean + p25–p75 band, sparkline, stacked, dashed-provisional trailing segment). The pure layout helpers (`gaugeArcPath`, `barSegments`, `scatterLayout`, `heatmapLayout`, `boxLayout`, `radarLayout`, `lineLayout`, …) are unit-tested in isolation
-* feat(web-framework): register the `x-ti-chart` Alpine CSP directive (binds a spec object to a host `<figure>`); every chart builds its SVG with `createElementNS` + `setAttribute` only (never `element.style.*` except `setProperty("--var")`) and ships a visually-hidden `.ti-chart-sr` accessibility table
-* feat(css): `.ti-chart-*` styles + per-type `figure[data-ti-chart-type]` size caps + `--chart-seq-1…5` sequential ramp tokens and grade/tone colours in both themes (daylight + black-glass)
-* build(release): bump package version from `1.9.3` to `1.10.0`
-
-## Version 1.9.3
-
-* feat(css): an empty `.ti-grade-chip` (a competency whose rating is still awaited) now renders an hourglass glyph via `::before` instead of a literal dash, so "awaiting rating" reads as a clear visual state wherever an empty grade chip is shown to a permitted viewer
-* build(release): bump package version from `1.9.2` to `1.9.3`
-
-## Version 1.9.2
-
-* feat(css): add `.ti-spacer` — a flexible spacer (`flex: 1 1 auto`) that pushes following siblings to the far end of a flex row/column. Promotes the bespoke per-screen `competence-empmgmt-actions-spacer` into a shared primitive, now consumed by the employee-management actions panel and the evaluation screen's team-feedback finalize bar
-* build(release): bump package version from `1.9.1` to `1.9.2`
-
-## Version 1.9.1
-
-* build(deps): upgrade `ajv` from ^6.15.0 to ^8.20.0 — ajv 8 renamed the validation-error `dataPath` (dot style) to `instancePath` (JSON Pointer)
-* fix(config-registry): normalize ajv 8's `instancePath` back to the dot/bracket data path the registry has always exposed on schema issues (e.g. `.competencies.E1-1.name`, array indices as `[0]`), so the public `ConfigValidationIssue.path` contract is unchanged across the upgrade; the ajv compile options (`meta`, `schemaId: "$id"`, `validateSchema: false`) and Draft-07 handling are unchanged
-* build(deps): update `helmet` from ^8.1.0 to ^8.2.0
-
-## Version 1.9.0
-
-* feat(css): add `.ti-panel-body-intro` — the canonical description/intro line under a `.ti-panel-head` (`--fs-sm`, secondary foreground, `0 var(--s-3) var(--s-5)` padding, 1.5 line-height); replaces the per-screen intro paragraphs that screens used to hand-style
-* refactor(css): tighten the key/value primitives — `.ti-kv-label` is now an uppercase `--fs-xs` 600-weight caption (0.05em letter-spacing); `.ti-kv-value` is `--fs-sm` 400-weight — for a consistent, scannable key/value rhythm across screens
-* refactor(css): drop the redundant `margin-left: auto` from `.ti-panel-head-aside` (the panel head already positions it via its flex layout)
-* fix(sidebar): the user-profile flyout actions (Profile, Settings, Logout) now actually fire. The menu items bind their `hx-*` attributes through Alpine (`x-bind`), which HTMX does not pick up on its initial document scan — so the buttons previously only closed the flyout. The flyout now runs `htmx.process` on its panel when it opens (idempotent on re-open), wiring up each button's `hx-get`/`hx-post`/`hx-target`/`hx-swap`
-* fix(sidebar): the role/department line under the user name no longer overflows the fixed-width sidebar — `.ti-sidebar-user-name` and `.ti-sidebar-user-sub` truncate with an ellipsis, and `.ti-sidebar-user-text` gets `flex: 1` so it bounds the text column
-* style(css): expand the `.ti-icon` size-modifier one-liners (`.xs`/`.sm`/`.md`/`.lg`/`.xl`) to block form for consistency with the rest of the sheet
-* build(release): bump package version from `1.8.0` to `1.9.0`
-
-## Version 1.8.0
-
-* feat(notifications): notifications can now show a secondary **details** line under the generic message. `tiApplication.formatException` returns `{ message, details }` (resolved from the exception's `data.details`, falling back to the raw text for non-localized messages) and `tiApplication.notify` accepts that payload — so an error like "The request parameters are not recognized or not supported." now also shows the specifics (e.g. "Competency codes not in the 'QE' pool: …") in a smaller, muted font. The returned object stringifies to its message, so existing string usages keep working unchanged
-* fix(css): raise the toast stack above the modal layer (`z-index` 1100 → 1300; the modal backdrop is 1200) so a notification raised while a modal is open is no longer hidden behind it
-
-## Version 1.7.1
-
-* fix(web-handlers): web-application request errors that carry no explicit `httpCode` are no longer reported as `500`. A new `resolveHttpCode` derives the status from the exception code — request-validation and application-logic errors (`E_WEB_*` / `E_APP_*`) map to `422 Unprocessable Content`, security (`E_SEC_*`) to `403`, resource not-found/already-exists to `404`/`409`, and method/URI/content errors to `405`/`404`/`415`; only genuine internal, communication, and unknown errors still default to `500`. An explicit `httpCode` on the exception always wins. Applied in both the `/app` request handler (`formatException`) and the default error handler
-
-## Version 1.7.0
-
-* feat(css): introduce `.ti-data-grid` family — `.ti-data-grid`, `.ti-data-grid-head`, `.ti-data-grid-rows`, `.ti-data-grid-row` with shared `--ti-grid-cols` template; row state modifiers `.is-current` (accent-soft, "current user") and `.is-selected` (accent-soft + left accent bar); wrapper variants `.bordered` (horizontal dividers for tabular displays) and `.compact` (denser padding); cell utilities `.ti-cell-center` / `.ti-cell-right` for per-cell alignment
-* feat(css): introduce `.ti-page-head` as a vertical block stack (eyebrow above title, subtitle below) using `--fs-xs` for the eyebrow and clamping subtitle width at 60ch
-* feat(css): introduce a reusable `.ti-form*` family — `.ti-form`, `.ti-form-section`, `.ti-form-section-title`, `.ti-form-grid` (with `.cols-1` / `.cols-3` modifiers), `.ti-form-row` (with `.wide` for grid-spanning), `.ti-form-readonly`, `.ti-form-hint`, `.ti-form-error`, `.ti-form-actions`, `.ti-form-state` (with `.saved` / `.unsaved`); single responsive collapse to one column under 720px
-* feat(css): extend `.ti-panel-head` with sub-elements — `.ti-panel-head-icon` (32x32 framed icon slot), `.ti-panel-head-text` (title + subtitle stack inside a flex row), `.ti-panel-title-aside` (inline qualifier next to the title), `.ti-panel-subtitle` (dimmed sub line), `.ti-panel-head-aside` (right-aligned read-only info with left-border separator), and the `.bar` modifier (sunken full-width banner)
-* feat(icons)!: rebase `.ti-icon` on `background-color: currentColor` so icons inherit the surrounding text colour; add size modifiers `.xs` (12px), `.sm` (14px), `.md` (16px), `.lg` (24px), `.xl` (32px); add `.legacy-gray` modifier to preserve the previous gray/hover behaviour for consumers that rely on the fixed colour scheme
-* feat(icons): add 21 new `.ti-icon` variants (lucide / feather style, 24x24 viewBox) — `plus`, `close`, `check`, `check-clipboard`, `send`, `search`, `clock`, `warning-triangle`, `info-circle`, `bell`, `check-circle`, `eye`, `calendar-blank`, `user`, `users`, `briefcase`, `folder`, `book`, `help-circle`, `bar-chart`, `chevron-left`, `chevron-right`, `dashboard-grid`, `cycles-loop`, `sun`
-* feat(icons): add `.ti-icon.moon` mask variant so theme toggles can mirror the target mode
-* feat(framework): add `tiApplication.hasRole(roleCode)` helper that does the array-shape check in plain JS (the Alpine CSP build does not expose `Array` to its expression evaluator, so `Array.isArray(...)` written inline in a template raises `Undefined variable: Array`)
-* feat(framework): add `tiApplication.topbarPrimaryCta` store slot plus `setTopbarPrimaryCta` / `setTopbarPrimaryCtaDisabled` API for per-screen CTA buttons in the topbar; auto-cleared on screen navigation so each screen owns its slot
-* feat(css): native select chevron replaced by a custom down-chevron SVG positioned at right: 10px / 14x14; padding-right reserves the slot; glass theme overrides the SVG stroke colour because `background-image` can't pick up `currentColor`
-* feat(css): subdue `::-webkit-calendar-picker-indicator` to opacity 0.7 (1 on hover) so date-input visual weight matches the chevron
-* feat(notification bar): replace inline toast SVGs with `.ti-icon` mask classes (success check, danger close, warn triangle, info circle, close button)
-* feat(sidebar): replace inline navigation SVGs with `.ti-icon` mask classes (collapse chevron, dashboard home, sun theme toggle)
-* refactor(css): drop the screen-specific page-header, form, and tabular-layout CSS that duplicated framework primitives; all in-tree screens (`frame-employees-list`, `frame-cycles`, `frame-cycle-setup`, `frame-competence-evaluation`, `frame-new-evaluation`, `frame-manager-calendar`, `frame-interview-schedule`, `frame-employee-management`) now consume `.ti-page-head`, `.ti-data-grid`, `.ti-form*`, and `.ti-panel-head*` instead
-* docs(modal): doc-block on `.ti-modal-*` confirming it as the canonical shared primitive (introduced in 1.6.3 via the competence cycle-setup work)
-* build(release): bump package version from `1.6.3` to `1.7.0`
-
-## Version 1.6.3
-
-* feat(css): add `--ti-internal-padding` CSS variable to the design token system
-* feat(css): add `--ti-border-color` CSS variable for consistent border theming
-* feat(icons): add `.ti-icon.calendar` and `.ti-icon.schedule` icon variants with hover states
-* feat(css): add `.ti-data-value.fill-space` modifier for flex-grow behavior in inline data value layouts
-* fix(css): remove `min-width: 120px` constraint from `.ti-button.inline` for more flexible sizing
-* fix(css): update z-index stacking values for dropdown and overlay elements to prevent layering conflicts
-* build(deps): update `openid-client` from ^6.8.2 to ^6.8.4
-* build(deps): update bundled `@alpinejs/csp` from ^3.15.11 to ^3.15.12
-* build(deps): update bundled `htmx.org` from ^2.0.8 to ^2.0.10
-* build(static): refresh bundled Alpine.js CSP and HTMX library files to match updated dependency versions
-
-## Version 1.6.2
-
-* feat(ui): replace Material Symbols usage with framework-native `.ti-icon` classes across sidebar flyouts, login actions, and notification bar
-* feat(sidebar): merge administration and user flyout menus into a single `sidebarApplicationMenu` with configurable menu icon and updated actions
-* feat(css): add embedded SVG mask icon variants (`app-menu`, `dashboard`, `settings`, `error`, `user-profile`, `login`, `logout`, `internet`) and increase default icon size to `24px`
-* refactor(theme): remove Material Symbols-specific icon styling from the black-glass theme
-* build(static): remove external Google Material Symbols stylesheet import from static `index.html`
-* build(release): bump package version from `1.6.1` to `1.6.2`
-
-## Version 1.6.1
-
-* feat(css): add inline button support via `.ti-button.inline` and new `--ti-button-inline-height` design token
-* refactor(ui): update sidebar flyout positioning logic to use shared `tiToolbox` viewport helpers (`getVisibleBox`, `clampToBox`)
-* fix(ui): fix the call to utility functions `getVisibleBox` and `clampToBox` in the sidebar flyout component
-* build(release): bump package version from `1.6.0` to `1.6.1`
-
-## Version 1.6.0
-
-* feat(toolbox): add Alpine.js `tiToolbox` store with shared utility methods (`deepMerge`, `deepFreeze`, `structuredClone`, `formatDate`, viewport helpers, and cookie access)
-* feat(ui): move sidebar menu configuration into `ti-framework.js` and register `tiComponentsConfig` during Alpine.js initialization
-* refactor(static): remove legacy `ti-user-interface.js` from static assets and stop loading it from `index.html`
-* refactor(components): update framework components to consume toolbox utilities through Alpine stores
-* refactor(docs): add and expand JSDoc typedefs and method-level documentation in `ti-framework.js`
-* build(release): bump package version from `1.5.3` to `1.6.0`
-
-## Version 1.5.3
-
-* feat(framework): add `openScreen` method for in-app navigation
-* fix(auth): add explicit HTTP `401` status to authentication failure
-
-## Version 1.5.2
-
-* feat(framework): expand application API by improving `sendRequest`, `notify`, and `getLabel` methods
-* feat(tooltip): add helper methods `getTooltipMessage`, `handleEnter`, `handleLeave`, `showTooltip`, `hideTooltip` to the tooltip component
-* feat(css): improve styles and style structure
-
-## Version 1.5.1
-
-* feat(framework): add `isValidDate` utility function for validating Date instances
-* feat(framework): add `deepFreeze` utility function for recursive object freezing
-* feat(framework): add `getLabel` method on application configuration for nested label resolution with dot notation
-* feat(framework): add Alpine.js directive `x-text-label` for runtime label translation
-* feat(framework): add a configuration object to replace labels object with enhanced structure
-* feat(config): add authentication state (`auth.isAuthenticated`) to config endpoint response
-* feat(placeholder): add inner content capture and injection for placeholder replacement
-* feat(tooltip): add a new tooltip component with Alpine.js integration and positioning
-* feat(css): add CSS custom properties for padding, margin, and font-family
-* feat(css): add tooltip styling variables (background, foreground, size, shadow, arrow)
-* feat(css): add `.ti-content.pane` block with flex layout and overflow handling
-* feat(css): add error color, flyout item shadows, and separator color variables
-* feat(css): add `.ti-glass-btn-black.large` variant with left-justified content
-* refactor(framework): change user initialization from `undefined` to `null`
-* refactor(framework): improve request failure handling with proper error rejection
-* refactor(css): replace hard-coded spacing with CSS variables across components
-* refactor(css): add `overflow: hidden` to body and `.ti-main` for better layout control
-* refactor(css): convert color and styling values to CSS variables throughout
-* refactor(handlers): add `convertUriToString` helper for safe URI object stringification
-* refactor(handlers): add a request context object (query, params, headers, url, method) to JSON responses
-* refactor(handlers): augment user data with default employeeID and roles in the user information handler
-* build(deps): update express from ^5.1.0 to ^5.2.1
-* build(deps): update express-session from ^1.18.2 to ^1.19.0
-* build(deps): update lodash from ^4.17.21 to ^4.17.23
-* build(deps): update openid-client from ^6.8.1 to ^6.8.2
-* build(deps): update `@alpinejs/csp` from ^3.15.2 to ^3.15.8
-* build(engines): update Node.js requirement from >=18.0.0 to >=20.0.0
-
-## Version 1.5.0
-
-* feat(web-app)!: change `TiWebAppManager` to be an abstract class
-* feat(web-app): rename class `WebAppManager` to `TiWebAppManager` and add a static file caching mechanism
-* feat(web-app): add `addFragment` method with override protection for custom HTML fragment registration
-* feat(web-app): add `webAppIdentifier` getter to expose application identifier
-* feat(web-server): add support for dynamic web application instantiation from config via `classPath`
-* feat(web-server): add `defineWebApplicationRoutes` and `defineUnprotectedRoutes` extension points
-* feat(web-server): add `endpointEnabled` flag to conditionally enable API endpoint proxy
-* feat(web-server): add serving for `.well-known` directory for web standards compliance
-* feat(package): add public exports for `./web-application` and `./web-server` subpaths
-* feat(package): add `files` whitelist and repository metadata (homepage, bugs URL, git repository)
-* feat(package): add Node.js version requirement (>=18.0.0) via the `engines` field
-* feat(build): add a post-install script to vendor HTMX and Alpine.js CSP libraries locally
-* refactor(web-app): replace `fullPublicPath` with `staticContentPaths` array for multi-path static content resolution
-* refactor(web-app): add file location search algorithm with caching via `#locateStaticFile` method
-* refactor(web-app): update `transformHtml` signature to remove `fullPublicPath` parameter
-* refactor(web-app): update `assembleHtmlView` to accept `staticContentPaths` instead of `fullPublicPath`
-* refactor(web-server): replace the single static path with configurable `staticContentPaths` array
-* refactor(web-server): merge web server default config with the provided service config in constructor
-* refactor(web-server): load web server default config directly from the package JSON import instead of the ENV configuration
-* refactor(web-server): improve TLS initialization error handling to reject promise instead of throw
-* refactor(package): reorganize imports from `./server/...` to `./bin/...` and `./components/...` paths
-* refactor(package): move `@alpinejs/csp` from dependencies to devDependencies
-* build(static): replace CDN script references with local copies for HTMX and Alpine.js CSP
-* build(env): remove `TI_INSTANCE_CONFIG` and update `TI_LOCALIZATION_LABELS_PATH` to use `bin/localization/` path
-* build(env): add `TI_AUDITING_LOG_MIN_LEVEL` configuration variable
-* fix(ui): change `aria-expanded` binding from string to boolean in the sidebar flyout component
-* fix(ui): remove incorrect `type="button"` attribute from `Home` anchor element
-* docs: improve various documentation comments and class descriptions
-
-## Version 1.4.0
-
-* feat(ui): add a notification bar component with Alpine.js integration and auto-dismiss functionality
-* feat(ui): add CSS variables and styles for the notification system
-* feat(routes): add `/not-found` fragment and route for 404 error pages
-* feat(routes): add `/app/error` route for error handling testing - will be removed later
-* feat(routes): add `/app/config` data endpoint for serving application configuration
-* feat(localization): add language property to `User` class with getter and JSON serialization
-* feat(localization): integrate localization module for label management and localized error messages
-* feat(session): add language property to session data populated from user or service configuration
-* feat(handlers): add response type detection helper `isAcceptingResponseType` for content negotiation
-* feat(handlers): enhance error responses with localized messages via localization module
-* feat(handlers): add HTMX-aware error handling with HX-Redirect and HX-Retarget headers
-* feat(handlers): implement `processDataRequest` method in WebAppManager for serving data resources
-* feat(config): add a language configuration option to the `WebServiceConfiguration` object
-* refactor(handlers): delegate error handling from resource protection to error middleware
-* refactor(handlers): improve 401/404 response handling by routing through exceptions and middleware
-* refactor(handlers): enhance CSRF and origin validation to use error middleware instead of direct responses
-* refactor(handlers): improve service call error handling to raise exceptions and delegate to middleware
-* refactor(handlers): refactor invalid route handler to raise exceptions instead of direct 404 responses
-* fix(types): correct ExpressRequest typedef from `import("express").req` to `import("express").Request`
-* build(config): update publicPath from `packages/web-framework/bin/static` to `bin/static`
-* build(config): update TLS certificate paths to use relative `bin/tls/` paths
-* build(env): update `TI_INSTANCE_CLASS` and `TI_INSTANCE_CONFIG` paths to use relative `bin/` paths
-* build(env): add `TI_LOCALIZATION_LABELS_PATH` environment variable for custom labels
-* build(run): update IDE run configuration to use relative paths and the correct working directory
-* build(labels): add an empty `web-server-labels.json` file for custom localization labels
-
-## Version 1.3.0
-
-* feat: first working prototype version
+# ti-engine web-framework changelog
+
+This document will contain the list of changes made to the framework. The format is based on the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification.
+
+## Version 1.20.0
+
+TypeScript declarations now ship with the package, verified against a consumer type-checking with `skipLibCheck: false`
+before they can be committed. See `@ti-engine/core` 1.9.0 for why the previous attempt was withdrawn.
+
+* feat(types): generate and publish `.d.ts` declarations for every module, wired through `types` conditions in both
+  `exports` and `imports`
+* feat(definitions): expose the shared type definitions as `@ti-engine/web-framework/definitions`
+* fix(session-store)!: the store's `set`, `get` and `touch` are typed against `express-session`'s `SessionData`, which
+  is what the `Store` contract hands them — not `TiSession`, which additionally requires `id`, `save`, `regenerate` and
+  `destroy`. The implementation only ever reads `cookie.maxAge`, so the annotation was describing a stricter input than
+  the base class can supply and than the code needs. Documentation only; no behaviour changes
+* fix(web-handlers): `ExpressResponse` referred to `import("express").res`, which express does not export. It is
+  `Response`
+* refactor(exports): the extras hung off `module.exports` after a class assignment — `instance`, `authMethod`,
+  `applyAuthMethodVisibility`, the static route matchers — are assigned to the class itself. `module.exports` *is* the
+  class, so this is the same object with the same properties at runtime; as a declaration it is the difference between
+  a namespace merge and an export assignment colliding with named exports, which is not valid TypeScript
+* fix(types): the same closure-style `{function(...)}` and `@private`-on-`#member` corrections as `core` 1.9.0
+* build(deps): add `@types/express`, `@types/express-session` and `@types/node`. The published declarations name types
+  from all three
+
+## Version 1.19.1
+
+Documentation and packaging only — no functional change.
+
+The `SemanticValidator` fix was found while attempting to generate TypeScript declarations from the framework's JSDoc. That work is **deferred to a later release**, but this correction stands on its own: the typedef was written as `function(Object, ValidatorContext): (ConfigValidationIssue[]|Promise<ConfigValidationIssue[]>)`, whose parenthesised return type inside the Closure form no parser can read. It described the validator contract correctly to a human reader and not at all to a machine.
+
+* fix(config-registry): rewrite the `SemanticValidator` typedef in arrow syntax
+* feat(package): declare `keywords`, which the package had none of — the terms npm search matches against
+
+## Version 1.19.0
+
+`/static` was served with `max-age=1y, immutable` for every consumer of the framework. `immutable` is a promise that the bytes behind a URL will never change, and browsers honour it so completely that not even a manual reload revalidates — so the promise is only true for a content-addressed URL (`app.a1b2c3.css`). None of the framework's own assets are named that way (`/static/scripts/ti-framework.js`, the theme sheets), which made this an unsafe default that shipped to npm: a deployed CSS or JS fix would never reach anyone who had already visited, for up to a year, with no way to tell them otherwise. The standalone author's site had worked around it privately by fingerprinting its own asset URLs; every other consumer still inherited the bug.
+
+* fix(web-server)!: the default `/static` cache policy is now `public, max-age=0, must-revalidate` instead of `max-age=1y, immutable`, so a deployed asset change actually reaches a returning visitor. `express.static` still attaches an `ETag`/`Last-Modified`, so a revalidation of an unchanged asset is answered with a `304` — headers, no body. **A consumer whose asset filenames are content-addressed should opt back in** with `staticCache: { maxAge: 31536000, immutable: true }`; one that appends a content hash to its asset URLs (rather than to the filenames) is equally entitled to it
+* feat(web-server): add the `staticCache` configuration block — `maxAge` (whole **seconds**, mapping 1:1 onto the `Cache-Control` directive; an express-style `"1y"` duration string is reported rather than silently reinterpreted as milliseconds), `immutable`, and `immutablePaths` (path prefixes served long-lived and `immutable` regardless of the other two). `immutable` combined with a `maxAge` of 0 is a contradiction and is dropped with a warning, so a half-configured deployment costs a revalidation rather than a year of unreachable assets
+* feat(web-server): `staticCache.immutablePaths` defaults to `[ "/fonts/" ]` — a released `.woff2` is an artifact rather than something edited in place, and its filename already carries the family, weight and style. Configurable, and clearable with an explicitly empty array, because that is a statement about how a given deployment manages its font files
+* feat(web-framework): add the `TI_WEB_STATIC_MAX_AGE`, `TI_WEB_STATIC_IMMUTABLE`, and `TI_WEB_STATIC_IMMUTABLE_PATHS` environment overrides, so the cache policy is settable per deployment like every other web setting; `TI_WEB_STATIC_IMMUTABLE_PATHS` **replaces** the array, and an explicitly empty value means no long-lived paths
+* refactor(web-server): the `/static` mounts write `Cache-Control` per file through `express.static`'s `setHeaders` rather than its `maxAge`/`immutable` options, since the policy is no longer uniform across the tree; the decision itself lives in the pure, unit-tested `TiWebServer.resolveStaticCachePolicy()` (config → policy + warnings, which the caller logs) and `TiWebServer.staticCacheControlFor()` (policy + file → header). The `staticCache` defaults deliberately live on the class rather than in `web-server.json`, because the constructor's `_.merge` merges arrays by index and a consumer's empty `immutablePaths` could otherwise never clear a default entry
+* docs(web-framework): document the `staticCache` block, the revalidating default and the reasoning behind it, and the fingerprinting opt-in in the README
+* build(release): bump package version from `1.18.1` to `1.19.0`
+
+## Version 1.18.1
+
+Enabling Azure SSO took the instance down at startup: the OAuth2 callback was registered by handing the configured callback value straight to Express as a route path, and the installation docs tell operators to set that value to the full absolute URL registered with the identity provider. Express 5 parses route patterns with path-to-regexp v8, where `:` opens a parameter name — so `https://host/login/azure-callback` throws `Missing parameter name at index 6` and the web server never starts. Google was affected identically, which also made this a prerequisite for the competence Cloud Run deployment, whose `deploy.sh` patches in an absolute callback URL (CA-97).
+
+* fix(web-framework): register an OAuth2 callback by its **path** rather than by the configured value verbatim, so a callback given as the absolute URL registered with the provider no longer crashes startup; a callback that yields no usable path now logs a WARNING and skips that provider's endpoint instead of taking the instance down, matching how an enabled-but-unconfigured provider is already handled
+* feat(web-framework): add `AuthManager.getOAuth2CallbackPath( authMethod )` and the pure, unit-tested `AuthManager.toCallbackPath( callbackUrl )` — reduces an absolute, protocol-relative, path or bare relative callback to its route path (query string and fragment stripped), or `null` when no usable path can be derived. The `redirect_uri` sent to the provider is deliberately left as configured, so an absolute callback keeps matching the provider registration exactly instead of depending on the forwarded protocol/host being correct
+* docs(web-framework): document the OpenID Connect provider variables in the README, and state in the README, the competence `INSTALL.md` and `.env.example` that a callback URL may be given as either the absolute registered URL or a path — including what each implies for the `redirect_uri`, and that the path must be the one the app actually receives when a proxy strips a prefix
+* build(release): bump package version from `1.18.0` to `1.18.1`
+
+## Version 1.18.0
+
+Every web-server setting a container deployment needs could be supplied per environment except one: the admin allowlist. `auth.admins` was readable only from the config file baked into the image, so a containerized deployment had no way to name an administrator — leaving the admin configuration screens unreachable, or forcing a real identity to be committed to the repository. This closes that gap in the existing `TI_WEB_*` override set (CA-94).
+
+* feat(web-framework): add the `TI_WEB_AUTH_ADMINS` environment override — comma-separated, **replaces** `auth.admins` (matched against the session user's user ID, username or email), so the admin allowlist is configurable per environment like every other web setting; an explicitly empty value means no admins
+* docs(web-framework): document `TI_WEB_AUTH_METHODS` and `TI_WEB_TRUSTED_ORIGINS` in the README's environment-variable list, which had never listed them
+* build(release): bump package version from `1.17.1` to `1.18.0`
+
+## Version 1.17.1
+
+A validator that needs to compare its own config document against its previously committed state had no way to do so: `applyEdits`'s cross-document context resolves `getConfig` to the *pending* value for any document inside the current edit batch — by design, so a validator can check a sibling document's post-edit state — but a document is always part of its own edit batch, so calling `getConfig` on itself just hands back the same incoming value already passed as the validator's argument, never its prior state. This silently defeated the competence `research-consent` config's version-bump guard (CA-93).
+
+* feat(web-framework): add `getStoredConfig(key)` to the `applyEdits` validator context (`ConfigService`) — always resolves the current *committed* value from the store, even for the document currently under validation, so a validator comparing its own document against its previous state has a way to do it; purely additive — `getConfig`'s existing cross-document (pending-value) semantics are unchanged
+* build(release): bump package version from `1.17.0` to `1.17.1`
+
+## Version 1.17.0
+
+Route-registration seams so an application subclass can add its own Express routes and unprotected-route patterns — enabling public, content-driven sites (the first consumer being the standalone author's site) to layer a catch-all content resolver over the framework without reaching into private state.
+
+* feat(web-server): add `TiWebServer.registerRoute( method, path, ...handlers )` — registers a custom route on the underlying Express app from a `defineWebApplicationRoutes()` override (after `super()`), so a catch-all resolver can be mounted after the framework's own routes but before its `*splat` 404 handler. Limited to route-scoped verbs (get/post/put/patch/delete/options/head/all); raises `E_GEN_INVALID_ARGUMENT_TYPE` for any other method and `E_GEN_NOT_INITIALIZED` if called before the Express app exists. The method must be a **string** — a non-string is rejected outright rather than coerced, so a value whose `toString()` happens to yield a verb (`[ "get" ]`, `new String( "get" )`) cannot slip past the allowlist and register a route
+* feat(web-server): add `TiWebServer.addUnprotectedRoute( pattern )` — appends a string (exact-match) or RegExp (tested) pattern to the unprotected-routes list from a `defineUnprotectedRoutes()` override, so a public-by-default site can invert the framework's protect-by-default stance; non-string/non-RegExp values are ignored with a warning
+* refactor(web-server): extract the unprotected-route matching loop from `isUnprotectedRoute()` into the pure, unit-tested `isRouteInList()` helper (behavior unchanged, including the defensive `lastIndex` reset), and add the `normalizeRegistrableMethod()` helper — both exported for testing alongside the existing `RE_*` matcher constants
+* build(release): bump package version from `1.16.0` to `1.17.0`
+
+## Version 1.16.0
+
+Support explicitly trusted request origins so state-changing requests (e.g. login) work behind proxies that do not present the app's external host — most notably GitHub Codespaces port forwarding (CA-90).
+
+* feat(web-framework): add `TI_WEB_TRUSTED_ORIGINS` (comma-separated) / `config.trustedOrigins`. The `originRefererValidationHandler` now accepts a non-GET request whose `Origin`/`Referer` matches the server-reconstructed base URL **or** any configured trusted origin. Previously such a request behind a proxy that rewrote/omitted the forwarded host was rejected with `E_WEB_INVALID_REQUEST_PARAMETERS` (HTTP 403). Backward compatible (empty list = prior behavior); the CSRF double-submit token check is unchanged and still enforced
+* build(release): bump package version from `1.15.0` to `1.16.0`
+
+## Version 1.15.0
+
+A dedicated health endpoint, a `TI_WEB_AUTH_METHODS` env override, and login-page gating for every auth method — completing the container-friendly auth/health story for the competence deployment (CA-90).
+
+* feat(web-framework): add an unprotected `GET /health` endpoint (`healthHandler`) that returns `200` with `{ status, broker, uptime }` — a purpose-built liveness/readiness probe for container and orchestrator health checks, so probes no longer have to hit the user-facing login route; `broker` reports the Redis connection state
+* feat(web-framework): add the `TI_WEB_AUTH_METHODS` env override (comma-separated) which REPLACES `auth.enabledMethods` — a clean, 12-factor way to select enabled auth methods per deployment (the config-file merge is by-index and cannot cleanly override an array)
+* feat(web-framework): extend login-page auth gating from the OAuth buttons to every method — the `local` credentials form and the "or continue with" divider are now gated too, and a "no method configured" fallback is shown when nothing is enabled, so an SSO-only deployment presents no dead local form
+* build(release): bump package version from `1.14.1` to `1.15.0`
+
+## Version 1.14.1
+
+Security hardening for the web-server CodeQL findings raised after the scanner was modernized in CA-90 (CA-91).
+
+* fix(web-framework): rewrite the default unprotected static-asset route matchers from the ambiguous `(?:.+/)*` to segment-anchored `(?:[^/]+/)*` — the previous form backtracked exponentially and is evaluated against the raw request path in `isUnprotectedRoute()` before authentication, making it a pre-authentication denial-of-service vector (CodeQL js/redos); the matched language for realistic asset paths is unchanged, and the matchers are now the `RE_STATIC_UNPROTECTED` / `RE_WELL_KNOWN_UNPROTECTED` module constants
+* fix(web-framework): replace the login-fragment section stripper's `open[\s\S]*?close` global-regex removal with a linear `indexOf`-based `stripMarkerSpans()` helper (also used for the per-provider stripper), eliminating the polynomial-time rescan on hostile input (CodeQL js/polynomial-redos)
+* docs(web-framework): document that Helmet's built-in Content-Security-Policy is intentionally disabled because a per-request, nonce-based CSP is enforced by `cspHeaderHandler()` on the following middleware — added an explanatory comment and an inline CodeQL suppression (the alert is a false positive)
+* build(release): bump package version from `1.14.0` to `1.14.1`
+
+## Version 1.14.0
+
+`TI_WEB_*` environment-variable overrides for the web server configuration, enabling 12-factor container deployments without per-environment config files (CA-90).
+
+* feat(web-framework): add `applyWebConfigEnvOverrides( config, env = process.env )` (`#web-config-env`) — a pure helper applying `TI_WEB_HOST`, `TI_WEB_PORT`, `TI_WEB_USE_TLS`, `TI_WEB_TLS_CERT_PATH`, `TI_WEB_TLS_KEY_PATH`, and `TI_WEB_COOKIE_SECRET` overrides onto the merged `TiWebServer` configuration, only when each variable is defined (fully backward compatible)
+* fix(web-framework): skip an enabled OpenID Connect provider that has no client ID instead of crashing the instance during discovery — an OAuth-less deployment (e.g. a container started without OAuth credentials) now boots on its remaining methods, with a warning, and reports the dropped provider as unavailable so a sign-in attempt against it fails per-request rather than at startup
+* feat(web-framework): the login page now renders an OpenID provider button only when that provider is an effective enabled auth method — the web server passes the post-drop enabled methods to the app manager, which strips the Google/Azure button (and the whole "or continue with" section when no provider is available) from `frame-login.html` at render time
+* build(release): bump package version from `1.13.2` to `1.14.0`
+
+## Version 1.13.0
+
+A reusable role-based screen gate and a per-screen title override (back the competence screen-access work and the evaluation/scores screen split).
+
+* feat(web-framework): the default `TiWebAppManager.verifyAccess` now enforces a fragment's declared `roles` — a fragment registered (via `addFragment`) with a `roles` array is served only to sessions holding at least one of them (otherwise rejected `E_SEC_UNAUTHORIZED_ACCESS` 403), while a fragment with no `roles` stays public. This makes role-restricted screens unreachable by direct URL, not merely hidden in the UI; apps just declare `roles` on `addFragment` — no `verifyAccess` override needed. Backward compatible: all existing role-less fragments remain public
+* feat(web-framework): add `authorization.isAccessAllowed( requiredRoles, userRoles )` — a pure, unit-tested access decision (empty/absent roles = public; otherwise ≥1 overlap; no implicit hierarchy, so an `admin` gate is never satisfied by a numeric role) that backs the default `verifyAccess`
+* feat(web-framework): add `tiApplication.setScreenTitle( title )` — a per-screen topbar/document-title override (cleared automatically on navigation) so a screen can correct its own title at runtime (e.g. a manager viewing another user's scores must not read "My …")
+* build(release): bump package version from `1.12.0` to `1.13.0`
+
+## Version 1.12.0
+
+Chart primitives gain legends + value labels for grouped bars and a legend for radar (backs the leaner competence evaluation results view) (CA-61).
+
+* feat(web-framework): `ti-charts` grouped bars now render an optional swatch legend (`options.legend`) and per-bar value captions (`options.valueLabels`); radar charts render an optional legend, with a dashed swatch variant (`{ dashed: true }`) for dashed series such as an "expected" curve (CA-61)
+* feat(web-framework): add `.ti-chart-bar-seg.tone-info`, `.ti-chart-legend-swatch.tone-info`, and `.ti-chart-legend-swatch.is-dashed` so grouped/radar source series and their legends share one colour scale across both themes (CA-61)
+* feat(web-framework): `ti-charts` radar accepts an optional per-axis `tone`, applied as a `tone-*` class on the axis label so consumers can colour axis labels (e.g. by category) — threaded through `radarLayout` (CA-61)
+* feat(web-framework): `ti-charts` grouped bars accept optional `options.barThickness` (bar height) and `options.valueFontSize` (value-caption font); value captions carry a dedicated `ti-chart-bar-value` class that intentionally sets no CSS `font-size`, so the renderer's `font-size` presentation attribute (default 4) actually governs — previously the caption also carried `ti-chart-bar-label`, whose CSS `font-size: 4px` overrode the attribute and made `valueFontSize` a no-op (CA-61)
+* build(release): bump package version from `1.11.1` to `1.12.0`
+
+## Version 1.11.1
+
+Post-review fix from the CA-72 CodeRabbit review (PR #85) on the login test-user panel.
+
+* fix(web-framework): turning the "override roles (dev)" toggle OFF now always strips any persisted roles from the `ti-test-user` cookie — even when the selected employee is no longer in the panel's profile list — so a stale roles array can't keep overriding the app's org-derived roles on the next login (CA-72)
+* build(release): bump package version from `1.11.0` to `1.11.1`
+
+## Version 1.11.0
+
+Login test-user panel defaults to identity-only injection so the app derives roles itself (CA-72).
+
+* feat(web-framework): login test-user panel injects identity only by default (roles derived by the app); role injection becomes an opt-in dev override (CA-72)
+* docs(web-framework): clarify the augmentSession contract (derive vs. override) (CA-72)
+* build(release): bump package version from `1.10.4` to `1.11.0`
+
+## Version 1.10.4
+
+Login test-user fixture follow-up (CA-71).
+
+* chore(web-framework): login test-user `8` carries the `MANAGER` role (`[1, 2]`) so manager / self-manage scenarios (e.g. the competence Org Chart self-manage gate) can be exercised without re-seeding
+* build(release): bump package version from `1.10.3` to `1.10.4`
+
+## Version 1.10.3
+
+Developer-tooling and formatting touch-ups on the shared frontend bundle.
+
+* chore(web-framework): the login test-user panel offers more seeded employees (3, 8, 9 alongside 22/20/1/4) so manager / direct-report / skip-level scenarios can be exercised without re-seeding
+* style(web-framework): minor formatting of `formatException`'s return object
+* build(release): bump package version from `1.10.2` to `1.10.3`
+
+## Version 1.10.2
+
+Readability and scaling fixes for the chart primitives, surfaced while polishing the Statistics & Results screens (CA-61).
+
+* fix(web-framework): stacked bar charts now caption each row (the group/cycle label plus an optional per-row value) and render an optional swatch legend driven by `spec.options.legend`, so a coverage "By group" chart reads as labelled bars instead of anonymous colour blocks; the row labels also land on the cross-cycle trend bars
+* fix(css): horizontal bar charts opt out of the global `svg` `max-height` so bar thickness and label size stay identical regardless of row count — a tall org-wide chart is no longer uniformly scaled down and rendered finer than the same chart on a smaller subtree; the per-row geometry is trimmed for a cleaner look
+* feat(css): `.ti-chart-legend` / `.ti-chart-legend-item` / `.ti-chart-legend-swatch` — a chart swatch legend whose colours route through the inherited grade/ink chart tokens
+* build(release): bump package version from `1.10.1` to `1.10.2`
+
+## Version 1.10.1
+
+Review fixes for the ti-chart primitives (Statistics & Results, CA-61, PR #83 — CodeRabbit pass).
+
+* fix(web-framework): drillable heatmap/box marks get an accessible name; `renderChart` clears stale `data-ti-chart-empty`/`aria-label` on rerender; `renderStat` renders a missing value as an em dash; the provisional line-dot stroke follows its `tone-*` class
+* fix(css): `.ti-chart-sr` uses `clip-path: inset(50%)` instead of the deprecated `clip` property
+* build(release): bump package version from `1.10.0` to `1.10.1`
+
+## Version 1.10.0
+
+### Charting primitive library (Statistics & Results, CA-61)
+
+* feat(web-framework): new `ti-charts.js` — a CSP-safe SVG charting library backing the competence Statistics & Results reporting. Eight primitives via a single `renderChart(figure, spec)` dispatcher: `gauge`, `bars` (stacked / grouped / diverging modes), `stat`, `scatter`, `heatmap` (sequential / diverging scales), `box`, `radar`, and `line` (mean + p25–p75 band, sparkline, stacked, dashed-provisional trailing segment). The pure layout helpers (`gaugeArcPath`, `barSegments`, `scatterLayout`, `heatmapLayout`, `boxLayout`, `radarLayout`, `lineLayout`, …) are unit-tested in isolation
+* feat(web-framework): register the `x-ti-chart` Alpine CSP directive (binds a spec object to a host `<figure>`); every chart builds its SVG with `createElementNS` + `setAttribute` only (never `element.style.*` except `setProperty("--var")`) and ships a visually-hidden `.ti-chart-sr` accessibility table
+* feat(css): `.ti-chart-*` styles + per-type `figure[data-ti-chart-type]` size caps + `--chart-seq-1…5` sequential ramp tokens and grade/tone colours in both themes (daylight + black-glass)
+* build(release): bump package version from `1.9.3` to `1.10.0`
+
+## Version 1.9.3
+
+* feat(css): an empty `.ti-grade-chip` (a competency whose rating is still awaited) now renders an hourglass glyph via `::before` instead of a literal dash, so "awaiting rating" reads as a clear visual state wherever an empty grade chip is shown to a permitted viewer
+* build(release): bump package version from `1.9.2` to `1.9.3`
+
+## Version 1.9.2
+
+* feat(css): add `.ti-spacer` — a flexible spacer (`flex: 1 1 auto`) that pushes following siblings to the far end of a flex row/column. Promotes the bespoke per-screen `competence-empmgmt-actions-spacer` into a shared primitive, now consumed by the employee-management actions panel and the evaluation screen's team-feedback finalize bar
+* build(release): bump package version from `1.9.1` to `1.9.2`
+
+## Version 1.9.1
+
+* build(deps): upgrade `ajv` from ^6.15.0 to ^8.20.0 — ajv 8 renamed the validation-error `dataPath` (dot style) to `instancePath` (JSON Pointer)
+* fix(config-registry): normalize ajv 8's `instancePath` back to the dot/bracket data path the registry has always exposed on schema issues (e.g. `.competencies.E1-1.name`, array indices as `[0]`), so the public `ConfigValidationIssue.path` contract is unchanged across the upgrade; the ajv compile options (`meta`, `schemaId: "$id"`, `validateSchema: false`) and Draft-07 handling are unchanged
+* build(deps): update `helmet` from ^8.1.0 to ^8.2.0
+
+## Version 1.9.0
+
+* feat(css): add `.ti-panel-body-intro` — the canonical description/intro line under a `.ti-panel-head` (`--fs-sm`, secondary foreground, `0 var(--s-3) var(--s-5)` padding, 1.5 line-height); replaces the per-screen intro paragraphs that screens used to hand-style
+* refactor(css): tighten the key/value primitives — `.ti-kv-label` is now an uppercase `--fs-xs` 600-weight caption (0.05em letter-spacing); `.ti-kv-value` is `--fs-sm` 400-weight — for a consistent, scannable key/value rhythm across screens
+* refactor(css): drop the redundant `margin-left: auto` from `.ti-panel-head-aside` (the panel head already positions it via its flex layout)
+* fix(sidebar): the user-profile flyout actions (Profile, Settings, Logout) now actually fire. The menu items bind their `hx-*` attributes through Alpine (`x-bind`), which HTMX does not pick up on its initial document scan — so the buttons previously only closed the flyout. The flyout now runs `htmx.process` on its panel when it opens (idempotent on re-open), wiring up each button's `hx-get`/`hx-post`/`hx-target`/`hx-swap`
+* fix(sidebar): the role/department line under the user name no longer overflows the fixed-width sidebar — `.ti-sidebar-user-name` and `.ti-sidebar-user-sub` truncate with an ellipsis, and `.ti-sidebar-user-text` gets `flex: 1` so it bounds the text column
+* style(css): expand the `.ti-icon` size-modifier one-liners (`.xs`/`.sm`/`.md`/`.lg`/`.xl`) to block form for consistency with the rest of the sheet
+* build(release): bump package version from `1.8.0` to `1.9.0`
+
+## Version 1.8.0
+
+* feat(notifications): notifications can now show a secondary **details** line under the generic message. `tiApplication.formatException` returns `{ message, details }` (resolved from the exception's `data.details`, falling back to the raw text for non-localized messages) and `tiApplication.notify` accepts that payload — so an error like "The request parameters are not recognized or not supported." now also shows the specifics (e.g. "Competency codes not in the 'QE' pool: …") in a smaller, muted font. The returned object stringifies to its message, so existing string usages keep working unchanged
+* fix(css): raise the toast stack above the modal layer (`z-index` 1100 → 1300; the modal backdrop is 1200) so a notification raised while a modal is open is no longer hidden behind it
+
+## Version 1.7.1
+
+* fix(web-handlers): web-application request errors that carry no explicit `httpCode` are no longer reported as `500`. A new `resolveHttpCode` derives the status from the exception code — request-validation and application-logic errors (`E_WEB_*` / `E_APP_*`) map to `422 Unprocessable Content`, security (`E_SEC_*`) to `403`, resource not-found/already-exists to `404`/`409`, and method/URI/content errors to `405`/`404`/`415`; only genuine internal, communication, and unknown errors still default to `500`. An explicit `httpCode` on the exception always wins. Applied in both the `/app` request handler (`formatException`) and the default error handler
+
+## Version 1.7.0
+
+* feat(css): introduce `.ti-data-grid` family — `.ti-data-grid`, `.ti-data-grid-head`, `.ti-data-grid-rows`, `.ti-data-grid-row` with shared `--ti-grid-cols` template; row state modifiers `.is-current` (accent-soft, "current user") and `.is-selected` (accent-soft + left accent bar); wrapper variants `.bordered` (horizontal dividers for tabular displays) and `.compact` (denser padding); cell utilities `.ti-cell-center` / `.ti-cell-right` for per-cell alignment
+* feat(css): introduce `.ti-page-head` as a vertical block stack (eyebrow above title, subtitle below) using `--fs-xs` for the eyebrow and clamping subtitle width at 60ch
+* feat(css): introduce a reusable `.ti-form*` family — `.ti-form`, `.ti-form-section`, `.ti-form-section-title`, `.ti-form-grid` (with `.cols-1` / `.cols-3` modifiers), `.ti-form-row` (with `.wide` for grid-spanning), `.ti-form-readonly`, `.ti-form-hint`, `.ti-form-error`, `.ti-form-actions`, `.ti-form-state` (with `.saved` / `.unsaved`); single responsive collapse to one column under 720px
+* feat(css): extend `.ti-panel-head` with sub-elements — `.ti-panel-head-icon` (32x32 framed icon slot), `.ti-panel-head-text` (title + subtitle stack inside a flex row), `.ti-panel-title-aside` (inline qualifier next to the title), `.ti-panel-subtitle` (dimmed sub line), `.ti-panel-head-aside` (right-aligned read-only info with left-border separator), and the `.bar` modifier (sunken full-width banner)
+* feat(icons)!: rebase `.ti-icon` on `background-color: currentColor` so icons inherit the surrounding text colour; add size modifiers `.xs` (12px), `.sm` (14px), `.md` (16px), `.lg` (24px), `.xl` (32px); add `.legacy-gray` modifier to preserve the previous gray/hover behaviour for consumers that rely on the fixed colour scheme
+* feat(icons): add 21 new `.ti-icon` variants (lucide / feather style, 24x24 viewBox) — `plus`, `close`, `check`, `check-clipboard`, `send`, `search`, `clock`, `warning-triangle`, `info-circle`, `bell`, `check-circle`, `eye`, `calendar-blank`, `user`, `users`, `briefcase`, `folder`, `book`, `help-circle`, `bar-chart`, `chevron-left`, `chevron-right`, `dashboard-grid`, `cycles-loop`, `sun`
+* feat(icons): add `.ti-icon.moon` mask variant so theme toggles can mirror the target mode
+* feat(framework): add `tiApplication.hasRole(roleCode)` helper that does the array-shape check in plain JS (the Alpine CSP build does not expose `Array` to its expression evaluator, so `Array.isArray(...)` written inline in a template raises `Undefined variable: Array`)
+* feat(framework): add `tiApplication.topbarPrimaryCta` store slot plus `setTopbarPrimaryCta` / `setTopbarPrimaryCtaDisabled` API for per-screen CTA buttons in the topbar; auto-cleared on screen navigation so each screen owns its slot
+* feat(css): native select chevron replaced by a custom down-chevron SVG positioned at right: 10px / 14x14; padding-right reserves the slot; glass theme overrides the SVG stroke colour because `background-image` can't pick up `currentColor`
+* feat(css): subdue `::-webkit-calendar-picker-indicator` to opacity 0.7 (1 on hover) so date-input visual weight matches the chevron
+* feat(notification bar): replace inline toast SVGs with `.ti-icon` mask classes (success check, danger close, warn triangle, info circle, close button)
+* feat(sidebar): replace inline navigation SVGs with `.ti-icon` mask classes (collapse chevron, dashboard home, sun theme toggle)
+* refactor(css): drop the screen-specific page-header, form, and tabular-layout CSS that duplicated framework primitives; all in-tree screens (`frame-employees-list`, `frame-cycles`, `frame-cycle-setup`, `frame-competence-evaluation`, `frame-new-evaluation`, `frame-manager-calendar`, `frame-interview-schedule`, `frame-employee-management`) now consume `.ti-page-head`, `.ti-data-grid`, `.ti-form*`, and `.ti-panel-head*` instead
+* docs(modal): doc-block on `.ti-modal-*` confirming it as the canonical shared primitive (introduced in 1.6.3 via the competence cycle-setup work)
+* build(release): bump package version from `1.6.3` to `1.7.0`
+
+## Version 1.6.3
+
+* feat(css): add `--ti-internal-padding` CSS variable to the design token system
+* feat(css): add `--ti-border-color` CSS variable for consistent border theming
+* feat(icons): add `.ti-icon.calendar` and `.ti-icon.schedule` icon variants with hover states
+* feat(css): add `.ti-data-value.fill-space` modifier for flex-grow behavior in inline data value layouts
+* fix(css): remove `min-width: 120px` constraint from `.ti-button.inline` for more flexible sizing
+* fix(css): update z-index stacking values for dropdown and overlay elements to prevent layering conflicts
+* build(deps): update `openid-client` from ^6.8.2 to ^6.8.4
+* build(deps): update bundled `@alpinejs/csp` from ^3.15.11 to ^3.15.12
+* build(deps): update bundled `htmx.org` from ^2.0.8 to ^2.0.10
+* build(static): refresh bundled Alpine.js CSP and HTMX library files to match updated dependency versions
+
+## Version 1.6.2
+
+* feat(ui): replace Material Symbols usage with framework-native `.ti-icon` classes across sidebar flyouts, login actions, and notification bar
+* feat(sidebar): merge administration and user flyout menus into a single `sidebarApplicationMenu` with configurable menu icon and updated actions
+* feat(css): add embedded SVG mask icon variants (`app-menu`, `dashboard`, `settings`, `error`, `user-profile`, `login`, `logout`, `internet`) and increase default icon size to `24px`
+* refactor(theme): remove Material Symbols-specific icon styling from the black-glass theme
+* build(static): remove external Google Material Symbols stylesheet import from static `index.html`
+* build(release): bump package version from `1.6.1` to `1.6.2`
+
+## Version 1.6.1
+
+* feat(css): add inline button support via `.ti-button.inline` and new `--ti-button-inline-height` design token
+* refactor(ui): update sidebar flyout positioning logic to use shared `tiToolbox` viewport helpers (`getVisibleBox`, `clampToBox`)
+* fix(ui): fix the call to utility functions `getVisibleBox` and `clampToBox` in the sidebar flyout component
+* build(release): bump package version from `1.6.0` to `1.6.1`
+
+## Version 1.6.0
+
+* feat(toolbox): add Alpine.js `tiToolbox` store with shared utility methods (`deepMerge`, `deepFreeze`, `structuredClone`, `formatDate`, viewport helpers, and cookie access)
+* feat(ui): move sidebar menu configuration into `ti-framework.js` and register `tiComponentsConfig` during Alpine.js initialization
+* refactor(static): remove legacy `ti-user-interface.js` from static assets and stop loading it from `index.html`
+* refactor(components): update framework components to consume toolbox utilities through Alpine stores
+* refactor(docs): add and expand JSDoc typedefs and method-level documentation in `ti-framework.js`
+* build(release): bump package version from `1.5.3` to `1.6.0`
+
+## Version 1.5.3
+
+* feat(framework): add `openScreen` method for in-app navigation
+* fix(auth): add explicit HTTP `401` status to authentication failure
+
+## Version 1.5.2
+
+* feat(framework): expand application API by improving `sendRequest`, `notify`, and `getLabel` methods
+* feat(tooltip): add helper methods `getTooltipMessage`, `handleEnter`, `handleLeave`, `showTooltip`, `hideTooltip` to the tooltip component
+* feat(css): improve styles and style structure
+
+## Version 1.5.1
+
+* feat(framework): add `isValidDate` utility function for validating Date instances
+* feat(framework): add `deepFreeze` utility function for recursive object freezing
+* feat(framework): add `getLabel` method on application configuration for nested label resolution with dot notation
+* feat(framework): add Alpine.js directive `x-text-label` for runtime label translation
+* feat(framework): add a configuration object to replace labels object with enhanced structure
+* feat(config): add authentication state (`auth.isAuthenticated`) to config endpoint response
+* feat(placeholder): add inner content capture and injection for placeholder replacement
+* feat(tooltip): add a new tooltip component with Alpine.js integration and positioning
+* feat(css): add CSS custom properties for padding, margin, and font-family
+* feat(css): add tooltip styling variables (background, foreground, size, shadow, arrow)
+* feat(css): add `.ti-content.pane` block with flex layout and overflow handling
+* feat(css): add error color, flyout item shadows, and separator color variables
+* feat(css): add `.ti-glass-btn-black.large` variant with left-justified content
+* refactor(framework): change user initialization from `undefined` to `null`
+* refactor(framework): improve request failure handling with proper error rejection
+* refactor(css): replace hard-coded spacing with CSS variables across components
+* refactor(css): add `overflow: hidden` to body and `.ti-main` for better layout control
+* refactor(css): convert color and styling values to CSS variables throughout
+* refactor(handlers): add `convertUriToString` helper for safe URI object stringification
+* refactor(handlers): add a request context object (query, params, headers, url, method) to JSON responses
+* refactor(handlers): augment user data with default employeeID and roles in the user information handler
+* build(deps): update express from ^5.1.0 to ^5.2.1
+* build(deps): update express-session from ^1.18.2 to ^1.19.0
+* build(deps): update lodash from ^4.17.21 to ^4.17.23
+* build(deps): update openid-client from ^6.8.1 to ^6.8.2
+* build(deps): update `@alpinejs/csp` from ^3.15.2 to ^3.15.8
+* build(engines): update Node.js requirement from >=18.0.0 to >=20.0.0
+
+## Version 1.5.0
+
+* feat(web-app)!: change `TiWebAppManager` to be an abstract class
+* feat(web-app): rename class `WebAppManager` to `TiWebAppManager` and add a static file caching mechanism
+* feat(web-app): add `addFragment` method with override protection for custom HTML fragment registration
+* feat(web-app): add `webAppIdentifier` getter to expose application identifier
+* feat(web-server): add support for dynamic web application instantiation from config via `classPath`
+* feat(web-server): add `defineWebApplicationRoutes` and `defineUnprotectedRoutes` extension points
+* feat(web-server): add `endpointEnabled` flag to conditionally enable API endpoint proxy
+* feat(web-server): add serving for `.well-known` directory for web standards compliance
+* feat(package): add public exports for `./web-application` and `./web-server` subpaths
+* feat(package): add `files` whitelist and repository metadata (homepage, bugs URL, git repository)
+* feat(package): add Node.js version requirement (>=18.0.0) via the `engines` field
+* feat(build): add a post-install script to vendor HTMX and Alpine.js CSP libraries locally
+* refactor(web-app): replace `fullPublicPath` with `staticContentPaths` array for multi-path static content resolution
+* refactor(web-app): add file location search algorithm with caching via `#locateStaticFile` method
+* refactor(web-app): update `transformHtml` signature to remove `fullPublicPath` parameter
+* refactor(web-app): update `assembleHtmlView` to accept `staticContentPaths` instead of `fullPublicPath`
+* refactor(web-server): replace the single static path with configurable `staticContentPaths` array
+* refactor(web-server): merge web server default config with the provided service config in constructor
+* refactor(web-server): load web server default config directly from the package JSON import instead of the ENV configuration
+* refactor(web-server): improve TLS initialization error handling to reject promise instead of throw
+* refactor(package): reorganize imports from `./server/...` to `./bin/...` and `./components/...` paths
+* refactor(package): move `@alpinejs/csp` from dependencies to devDependencies
+* build(static): replace CDN script references with local copies for HTMX and Alpine.js CSP
+* build(env): remove `TI_INSTANCE_CONFIG` and update `TI_LOCALIZATION_LABELS_PATH` to use `bin/localization/` path
+* build(env): add `TI_AUDITING_LOG_MIN_LEVEL` configuration variable
+* fix(ui): change `aria-expanded` binding from string to boolean in the sidebar flyout component
+* fix(ui): remove incorrect `type="button"` attribute from `Home` anchor element
+* docs: improve various documentation comments and class descriptions
+
+## Version 1.4.0
+
+* feat(ui): add a notification bar component with Alpine.js integration and auto-dismiss functionality
+* feat(ui): add CSS variables and styles for the notification system
+* feat(routes): add `/not-found` fragment and route for 404 error pages
+* feat(routes): add `/app/error` route for error handling testing - will be removed later
+* feat(routes): add `/app/config` data endpoint for serving application configuration
+* feat(localization): add language property to `User` class with getter and JSON serialization
+* feat(localization): integrate localization module for label management and localized error messages
+* feat(session): add language property to session data populated from user or service configuration
+* feat(handlers): add response type detection helper `isAcceptingResponseType` for content negotiation
+* feat(handlers): enhance error responses with localized messages via localization module
+* feat(handlers): add HTMX-aware error handling with HX-Redirect and HX-Retarget headers
+* feat(handlers): implement `processDataRequest` method in WebAppManager for serving data resources
+* feat(config): add a language configuration option to the `WebServiceConfiguration` object
+* refactor(handlers): delegate error handling from resource protection to error middleware
+* refactor(handlers): improve 401/404 response handling by routing through exceptions and middleware
+* refactor(handlers): enhance CSRF and origin validation to use error middleware instead of direct responses
+* refactor(handlers): improve service call error handling to raise exceptions and delegate to middleware
+* refactor(handlers): refactor invalid route handler to raise exceptions instead of direct 404 responses
+* fix(types): correct ExpressRequest typedef from `import("express").req` to `import("express").Request`
+* build(config): update publicPath from `packages/web-framework/bin/static` to `bin/static`
+* build(config): update TLS certificate paths to use relative `bin/tls/` paths
+* build(env): update `TI_INSTANCE_CLASS` and `TI_INSTANCE_CONFIG` paths to use relative `bin/` paths
+* build(env): add `TI_LOCALIZATION_LABELS_PATH` environment variable for custom labels
+* build(run): update IDE run configuration to use relative paths and the correct working directory
+* build(labels): add an empty `web-server-labels.json` file for custom localization labels
+
+## Version 1.3.0
+
+* feat: first working prototype version