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

package/CHANGELOG.md

@@ -9,6 +9,48 @@ 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

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