@coolms/core-angular 2.0.0-alpha.4 → 2.0.0-alpha.6

package/CHANGELOG.md

@@ -9,6 +9,94 @@ currently serves. Earlier alphas are deliberately not reconstructed: entries are
 in the same commit as the work they describe, and inventing the ones that
 predate this file would be a worse record than not having them.
 
+### Changed
+
+- **A person's refused write opens the elevation prompt, and is sent again
+  once they elevate.** A write refused for want of elevation (a stamped 403)
+  holds the request and opens the prompt above whatever the person is in. An
+  edit dialog stays open beneath it, with its input. On a grant, the write is
+  sent once more and the caller receives that answer. If the session is
+  already elevated, it is sent once more without asking. A decline tells
+  `ELEVATION_NOTICE`, naming the action, and hands back the 403. The repeat
+  passes no prompt a second time. Reads and background requests still open
+  nothing.
+
+## 2.0.0-alpha.6 - 2026-10-22
+
+### Changed
+
+- **Breaking: `engines.node` names exactly the Node lines CI runs.** It moves from
+  `^22.22.3 || ^24.15.0 || >=26` to `^22.22.3 || ^24.15.0 || ^26.0.0`: Node 27
+  and later are not declared until CI runs them. Within each line the floor is
+  the highest one any package in the lockfile declares. CI checks both, from
+  the matrix and the lockfile. The published code does not change.
+
+### Added
+
+- **`ELEVATION_ACTION`, `ElevationService.canPrompt` and `apiBase`.** A caller
+  can name a write in the person's words ("Saving the menu entry") for the
+  elevation prompt and notice. `ElevationPromptRequest.action` and the notice's
+  optional second argument carry it. Without it, the action is the method's
+  verb and the resource the URL names ("Saving navi nodes").
+
+- **Navigation nodes carry the server's access state.** `NaviGraphNodeFlat.access`
+  is `'allowed'` or `'elevate'`. `'elevate'` marks a node that a member of admin
+  can open once the session is elevated; the admin shows it with a lock instead
+  of hiding it. A server that does not send the field is read as `'allowed'`
+  (`naviAccessOf`), so nothing changes against it.
+- `NaviGraphService.loadAdminNav(url, { fresh: true })` asks the server again
+  instead of answering from the per-URL cache: the answer differs before and
+  after a grant, so a change of elevation must re-ask.
+- **`ElevationState.mayElevate`** and `ElevationService.mayElevate()`: whether
+  this account may elevate at all, as the server answered it. Absent reads as
+  false.
+
+## 2.0.0-alpha.5 - 2026-10-09
+
+### Changed
+
+- **The elevation prompt opens only when a person asks for it.** A 403 that
+  the server stamps `X-Elevation-Required` no longer opens the prompt by
+  itself. `elevationInterceptor` now:
+  - leaves a refused read (`GET`, `HEAD`, `OPTIONS`: a page loading, a poll)
+    to its caller, which shows its own state;
+  - leaves a refused background request alone (see `BACKGROUND_REQUEST`);
+  - tells `ELEVATION_NOTICE` when a write a person made is refused, and hands
+    the 403 back at once. The application shows the refusal with an Elevate
+    button, and only that click opens the prompt (`ElevationService.offerFor`).
+    The refused action is not repeated by itself.
+- `ErrorHandlerService.humanize()` says "This needs an elevated session." for
+  a stamped refusal, and "You don't have access to this." in place of the
+  framework's bare "Access Denied." for any other 403. A sentence the server
+  wrote for the refused action is kept.
+- `ConfigService` no longer caches a failed read, so a page that was refused
+  reads again after the person elevates.
+- **The console opens for an account the server grants it to.** Once the
+  session is settled, the auth guard asks for the admin's endpoint map: a 200
+  merges it into the app config, and a 403 signs this sign-in out (on the
+  server too) and returns to the sign-in page, which says the account has no
+  access to the console. A failure to ask is not an answer: the console opens,
+  and each of its requests is still decided by the server.
+  - The map is read at `/api/v1/admin/manifest`, and at the older
+    `/api/v1/console/manifest` only when the server answers 404 there.
+  - An answer is kept only for the sign-in that asked. Nothing is asked while
+    nobody is signed in.
+  - A module route waits for the map when someone is signed in.
+  - The realtime connection opens after this check, and a refused sign-in
+    opens none.
+- The sign-in page shows its answer (a wrong password, or the console's
+  refusal) as soon as it arrives, without waiting for the person to type.
+
+### Added
+
+- `BACKGROUND_REQUEST`: an `HttpContextToken` marking a request no person
+  made. The realtime connection and subscription tokens and the preferences
+  sync carry it.
+- `ELEVATION_NOTICE` and `ElevationNoticePort`: how an application is told
+  that a person's write was refused for want of elevation.
+- `isElevationRefusal(err)`: the one test for a stamped 403.
+- `ConsoleAccessService` in the public API.
+
 ## 2.0.0-alpha.4 - 2026-09-27
 
 ### Changed

package/README.md

@@ -56,6 +56,10 @@ a relative symlink to the admin application's, so exactly one `@angular` tree is
 in play while the admin consumes this package from source: a second copy would
 give two type identities for the same class.
 
+## Tests
+
+This package has no test runner of its own, so CI finds no tests in it: only typecheck, lint and build guard it here, and a check of "the same number of tests before and after" proves nothing for it. Its 13 spec files run in the admin suite of [coolms/theme-admin](https://github.com/coolms/theme-admin), which compiles this package from source. A change here is tested there, not by this repository's CI.
+
 ## Status
 
 A pre-release: the shape is still moving and it carries no compatibility