heqiapp/platforms
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: resolve platform relation identities

Browse Source
This commit is contained in:
yanweidong
2026-07-27 10:11:07 +08:00
parent 98995d6968
commit 2e62238416
11 changed files with 437 additions and 80 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
.superpowers/sdd/2026-07-27-platform-admin-full-audit/task-6-report.md
View File

@@ -36,3 +36,10 @@ The tree page consumes `parent_identity`; the corresponding menu API must expose
- Safety disposal is a detail action on `saf_event` (`/safety/saf_event/:identity/disposals`) and has no standalone menu or page.
- `ec_category` and `platform_menu` use tree pages. The shared tree preserves identity-first behavior and uses backend `parent_id` only for in-memory hierarchy adaptation when `parent_identity` is unavailable.
- The audit transpiles and evaluates `resources.ts`, then compares the resulting definitions, allowlists, required identities, modes, page types, tree semantics, and identifier-safety rules to the complete expected contract.
## Fix round 3
- Added tested backend identity-to-key resolution for public account and relationship requests; clients send `*_identity`, while numeric keys remain internal persistence details.
- Platform-menu and e-commerce-category tree responses now expose `parent_identity` and omit `parent_id`; the front-end tree no longer falls back to numeric keys.
- Settlement input accepts `subject_identity` with supported gas, delivery, and staff subject types.
- The platform audit now cross-checks every front-end definition against the backend resource catalogue and registered route source.