Sync Repo-docs-ACCESS-EXTRACTION-PLAN from project files
@@ -1,4 +1,4 @@
|
||||
<!-- codex-wiki-sync:4fbc13be387367ca523f2e4f -->
|
||||
<!-- codex-wiki-sync:383d3d92109026630c5a40ed -->
|
||||
|
||||
> Mirrored from `/mnt/DATA/git/govoplan-core/docs/ACCESS_EXTRACTION_PLAN.md`.
|
||||
> Origin: `repository`.
|
||||
@@ -302,18 +302,23 @@ Move access administration UI/API ownership into modules.
|
||||
|
||||
Tasks:
|
||||
|
||||
- Move users, groups, roles, API keys, and access settings pages into
|
||||
- [x] Move users, groups, roles, API keys, and access settings pages into
|
||||
`govoplan-access`.
|
||||
- Move tenant-specific pages to `govoplan-tenancy` when that module exists, or
|
||||
- [ ] Move tenant-specific pages to `govoplan-tenancy` when that module exists, or
|
||||
keep them temporarily in access with clear boundaries.
|
||||
- Register admin navigation through module contributions.
|
||||
- Keep core shell, layout, route rendering, and generic components only.
|
||||
- [x] Move overview, system settings, and governance-template panels into
|
||||
`govoplan-admin`.
|
||||
- [x] Register admin navigation and admin sections through module
|
||||
contributions.
|
||||
- [x] Keep core shell, layout, route rendering, and generic components only.
|
||||
|
||||
Acceptance criteria:
|
||||
|
||||
- Core WebUI shell renders admin/access pages from module contributions.
|
||||
- Core does not import access page components directly.
|
||||
- Module nav and route metadata remain serializable.
|
||||
- The access admin shell consumes module-owned `admin.sections` capability
|
||||
contributions without importing sibling module panels.
|
||||
|
||||
### Stage 6: Decouple Feature Modules
|
||||
|
||||
@@ -424,6 +429,8 @@ Acceptance criteria:
|
||||
- [x] Replace files/mail/campaign direct cross-module SQL lookups with
|
||||
provider/capability contracts.
|
||||
- [x] Move access admin WebUI pages to module route contributions.
|
||||
- [x] Move generic admin-owned WebUI panels into `govoplan-admin` and register
|
||||
them through the `admin.sections` UI capability.
|
||||
- [x] Remove transitional boundary checker allowlist entries as each contract
|
||||
lands.
|
||||
- [ ] Move campaign-scoped mail policy ownership fully behind an API/event
|
||||
|
||||
Reference in New Issue
Block a user