docs(12.1-04): update state and roadmap after the groups and organisations plan

This commit is contained in:
Jakub Zych
2026-10-05 14:10:11 +02:00
parent 3f4a01ddf8
commit 52f864ebfc
3 changed files with 16 additions and 10 deletions

View File

@@ -649,7 +649,7 @@ Plans:
5. The new code has unit tests, delivered in the phase's last plan.
**Open questions (discuss-phase):** impersonate user in or out of scope (security-sensitive); a separate permission for granting the `admin` group (it makes a site admin); whether convert-guest is needed for the application's data.
**Plans:** 3/5 plans executed
**Plans:** 4/5 plans executed
Plans:
@@ -663,7 +663,7 @@ Plans:
- [x] 12.1-03-PLAN.md — Plugin foundation and the Users screen (sm-user-plugin): additive migrations, permissions, navigation, list, filters, preview, form, bulk and record actions, delete semantics, password and invite, avatar, frontend permission resolver, `last_seen`, and the takeover guard for members of privileged groups (D-30)
**Wave 4** *(blocked on Wave 3 completion)*
- [ ] 12.1-04-PLAN.md — User Groups and Organisations screens, the `members` relation manager, the privileged-group guard on every `users_groups` write path (T-12-18), and the application's parity allow-list entry and submodule pointer on framework v0.1.3
- [x] 12.1-04-PLAN.md — User Groups and Organisations screens, the `members` relation manager, the privileged-group guard on every `users_groups` write path (T-12-18), and the application's parity allow-list entry and submodule pointer on framework v0.1.3
**Wave 5** *(blocked on Wave 4 completion)*
- [ ] 12.1-05-PLAN.md — Unit tests last: full coverage in both repos, `scripts/check-phase12.1.sh`, the security review and the validation sign-off, then the plugin push (only when v0.1.3 is on origin)