hanarang/hanarang-dashboard
5
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

feat: implement SPRINT-016 isometric office dashboard #14

Open
nabomhalang wants to merge 0 commits from feature/sprint-016-office-dashboard-plan into main
pull from: feature/sprint-016-office-dashboard-plan
merge into: hanarang:main
Conversation 0 Commits - Files Changed -
nabomhalang commented 2026-04-07 12:46:16 +09:00
Owner
Copy Link

Summary

  • add the Sprint 016 office dashboard at /office with 4 fixed sister seats
  • visualize 17 subagents with state-derived motion, direct chat UI, and integrated workflow/server health panels
  • keep live/snapshot/fallback source labels explicit across the office scene and ops panels

Verification

  • frontend: npm run build
  • backend: npm run lint
  • backend: npm test -- --runInBand
  • backend: npm run build

Notes

  • fallback labels remain intentionally because live backend data could not be fully validated in this environment when MariaDB rejected hanarang@10.10.10.216
  • direct chat is implemented as Gateway-pending UI until realtime session wiring is available
  • desktop/tablet/mobile real-browser QA could not be run here because this environment has no supported browser runtime
  • root cause of the missing 1 subagent: the static office scene translation initially carried only 16 positioned nodes, and the QA-side code-reviewer node was dropped from the first pass
## Summary - add the Sprint 016 office dashboard at `/office` with 4 fixed sister seats - visualize 17 subagents with state-derived motion, direct chat UI, and integrated workflow/server health panels - keep live/snapshot/fallback source labels explicit across the office scene and ops panels ## Verification - frontend: `npm run build` - backend: `npm run lint` - backend: `npm test -- --runInBand` - backend: `npm run build` ## Notes - `fallback` labels remain intentionally because live backend data could not be fully validated in this environment when MariaDB rejected `hanarang@10.10.10.216` - direct chat is implemented as Gateway-pending UI until realtime session wiring is available - desktop/tablet/mobile real-browser QA could not be run here because this environment has no supported browser runtime - root cause of the missing 1 subagent: the static office scene translation initially carried only 16 positioned nodes, and the QA-side `code-reviewer` node was dropped from the first pass
nabomhalang added 1 commit 2026-04-09 08:51:36 +09:00
fix: resolve 8 review/security issues (SPRINT-016 hotfix) 54535e7b5e 
Security:
- JwtGuard + RoleGuard on all sisters endpoints
- Admin-only access for config/sessions/subagents/activity
- ThrottlerGuard on /auth/refresh
- HttpOnly SameSite cookies + CSRF (replaces localStorage)

Code Quality:
- Per-sister draft input (Record<SisterName, string>)
- crypto.randomUUID for optimistic message ids (dedupe ready)
- Polling disabled while WebSocket connected
- SVG keyboard accessibility (role/tabIndex/onKeyDown)
nabomhalang force-pushed feature/sprint-016-office-dashboard-plan from 90968810ff to 54535e7b5e 2026-04-09 08:51:36 +09:00 Compare
This branch is already included in the target branch. There is nothing to merge.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feature/sprint-016-office-dashboard-plan:feature/sprint-016-office-dashboard-plan
git checkout feature/sprint-016-office-dashboard-plan
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
darang erang harang nabomhalang narang
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: hanarang/hanarang-dashboard#14
Delete Branch "feature/sprint-016-office-dashboard-plan"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?