chore: update submodules and mark completed TODO items
- Backend: remove legacy Python CLI, update docs - Frontend: code-first navigation across all pages - TODO: mark sections 2.2, 2.3, 2.6, 3.1 as completed
This commit is contained in:
Submodule HarborForge.Backend updated: 3ff9132596...b351075561
Submodule HarborForge.Frontend updated: fb5658739b...41ebd36218
@@ -211,17 +211,17 @@
|
||||
- [x] Ensure CLI-related list payloads always include canonical code fields
|
||||
|
||||
### 2.2 User / account-manager flow
|
||||
- [ ] Review current `account-manager` permission implementation
|
||||
- [ ] Add dedicated backend flow for account-manager-based account creation if current `/users` route is insufficient
|
||||
- [ ] Ensure `hf user create` maps cleanly to backend account-manager permission model
|
||||
- [ ] Ensure new accounts default to `guest`
|
||||
- [ ] Ensure admin role cannot be assigned through normal user management APIs
|
||||
- [x] Review current `account-manager` permission implementation
|
||||
- [x] Add dedicated backend flow for account-manager-based account creation if current `/users` route is insufficient
|
||||
- [x] Ensure `hf user create` maps cleanly to backend account-manager permission model
|
||||
- [x] Ensure new accounts default to `guest`
|
||||
- [x] Ensure admin role cannot be assigned through normal user management APIs
|
||||
|
||||
### 2.3 Permission introspection for CLI help
|
||||
- [ ] Decide how CLI will query effective permissions
|
||||
- [ ] Add/extend backend endpoint(s) for current-user permission introspection if needed
|
||||
- [ ] Ensure CLI can cheaply determine whether a subcommand is permitted
|
||||
- [ ] Support permission-aware help rendering without excessive API chattiness
|
||||
- [x] Decide how CLI will query effective permissions
|
||||
- [x] Add/extend backend endpoint(s) for current-user permission introspection if needed
|
||||
- [x] Ensure CLI can cheaply determine whether a subcommand is permitted
|
||||
- [x] Support permission-aware help rendering without excessive API chattiness
|
||||
|
||||
### 2.4 Task / meeting / support actions
|
||||
- [x] Add/confirm backend route for task self-assignment (`task take`)
|
||||
@@ -236,22 +236,22 @@
|
||||
- [ ] Update serializers to expose code prominently wherever applicable
|
||||
|
||||
### 2.6 Legacy Python CLI retirement
|
||||
- [ ] Track parity between new `hf` CLI and old backend Python CLI
|
||||
- [ ] Once parity is acceptable, remove legacy Python CLI from backend repo
|
||||
- [ ] Remove backend docs referencing the old Python CLI
|
||||
- [x] Track parity between new `hf` CLI and old backend Python CLI
|
||||
- [x] Once parity is acceptable, remove legacy Python CLI from backend repo
|
||||
- [x] Remove backend docs referencing the old Python CLI
|
||||
|
||||
---
|
||||
|
||||
## 3. HarborForge.Frontend
|
||||
|
||||
### 3.1 Code-first UI migration
|
||||
- [ ] Audit current routes and identify every place still using raw ids
|
||||
- [ ] Move project detail lookup toward `project-code`
|
||||
- [ ] Move milestone detail lookup toward `milestone-code`
|
||||
- [ ] Move task detail lookup toward `task-code`
|
||||
- [ ] Move meeting detail lookup toward `meeting-code`
|
||||
- [ ] Move support detail lookup toward `support-code`
|
||||
- [ ] Move propose detail lookup toward `propose-code`
|
||||
- [x] Audit current routes and identify every place still using raw ids
|
||||
- [x] Move project detail lookup toward `project-code`
|
||||
- [x] Move milestone detail lookup toward `milestone-code`
|
||||
- [x] Move task detail lookup toward `task-code`
|
||||
- [x] Move meeting detail lookup toward `meeting-code`
|
||||
- [x] Move support detail lookup toward `support-code`
|
||||
- [x] Move propose detail lookup toward `propose-code`
|
||||
- [x] Stop surfacing raw ids as the main visible identifier in lists/details
|
||||
- [x] Display codes consistently in relevant list and detail views
|
||||
|
||||
|
||||
Reference in New Issue
Block a user