zhi/HarborForge
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: mark completed TODO items (sections 2.5, 3.2, 3.3) and update submodule pointers

Browse Source 
- Section 2.5: code-based detail endpoints confirmed complete
- Section 3.2: user/role UX alignment confirmed complete
- Section 3.3: meeting/support UI wired and complete
- Update Frontend submodule: meeting/support detail pages + routes
- Update Backend submodule: general /supports list endpoint
This commit is contained in:
zhi
2026-03-22 00:18:01 +00:00
parent 5a3edb763b
commit 38884a7555
3 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
HarborForge.Backend

Submodule HarborForge.Backend updated: b351075561...d17072881b

2
HarborForge.Frontend

Submodule HarborForge.Frontend updated: 41ebd36218...a65429250a

18
plans/hf-cross-project-todo.md
View File

@@ -231,9 +231,9 @@
- [x] Add/confirm backend route for support self-assignment (`support take`) - [x] Add/confirm backend route for support self-assignment (`support take`)
### 2.5 Frontend-facing code migration support ### 2.5 Frontend-facing code migration support
- [ ] Add code-based detail endpoints or code query support for frontend routing - [x] Add code-based detail endpoints or code query support for frontend routing
- [ ] Ensure frontend can resolve resources by code without fallback to id-only APIs - [x] Ensure frontend can resolve resources by code without fallback to id-only APIs
- [ ] Update serializers to expose code prominently wherever applicable - [x] Update serializers to expose code prominently wherever applicable
### 2.6 Legacy Python CLI retirement ### 2.6 Legacy Python CLI retirement
- [x] Track parity between new `hf` CLI and old backend Python CLI - [x] Track parity between new `hf` CLI and old backend Python CLI
@@ -256,14 +256,14 @@
- [x] Display codes consistently in relevant list and detail views - [x] Display codes consistently in relevant list and detail views
### 3.2 User / role UX alignment ### 3.2 User / role UX alignment
- [ ] Review current user management page against final backend behavior - [x] Review current user management page against final backend behavior
- [ ] Ensure only code/name-first identifiers are shown where relevant - [x] Ensure only code/name-first identifiers are shown where relevant
- [ ] Ensure account role display matches single-role model everywhere - [x] Ensure account role display matches single-role model everywhere
### 3.3 Meeting / support UI ### 3.3 Meeting / support UI
- [ ] Audit current frontend support for meeting resources - [x] Audit current frontend support for meeting resources
- [ ] Add/adjust UI for meeting participant state if needed - [x] Add/adjust UI for meeting participant state if needed
- [ ] Add/adjust UI for support take/ownership state if needed - [x] Add/adjust UI for support take/ownership state if needed
### 3.4 Monitor UI alignment ### 3.4 Monitor UI alignment
- [ ] Ensure monitor views expose server identifier/code cleanly - [ ] Ensure monitor views expose server identifier/code cleanly