54 lines
3.2 KiB
Markdown
54 lines
3.2 KiB
Markdown
# Task: Integrate mobile leadership dashboard
|
||
|
||
## Identity
|
||
|
||
- Task ID: 20260902-dashboard-mobile-integration-e28c
|
||
- Mode: Integration
|
||
- Branch: main
|
||
- Worktree: /Users/inmanx/Documents/lwltAPI
|
||
- Base commit: 1b277cf3732a666a05993416a656237936ee181f
|
||
- Owner: codex
|
||
- Status: Ready for integration
|
||
|
||
## Scope
|
||
|
||
- Integrate verified feature commit `1ee89da` from task `20260902-dashboard-mobile-share-4e91c7` into `main`.
|
||
- Reconcile the included prior card correction, mobile/portrait-tablet layout, focused leadership shell, and task-detail behavior against AUTH-001 and current dashboard rules.
|
||
- Promote only the durable user-confirmed category rule and integrated source references into canonical project memory.
|
||
- Run integration regression and project-document gates without deploying, restarting services, accessing ERP, or mutating runtime data.
|
||
|
||
## Intent And Constraints
|
||
|
||
- Keep `/operations-dashboard` authenticated and limited to administrators and team leads. A focused standalone route does not mean an anonymous public link.
|
||
- Preserve the aggregate-first, business-facing, read-only dashboard decision and all normal task ownership, mutation, artifact, audit, AgentBus, and ERP boundaries.
|
||
- Treat source task records as read-only. Integration notes belong only to this task record; canonical changes are limited to `current-state.md` and the relevant leadership-dashboard business rule.
|
||
- The previous card task's promotion candidate is semantically compatible with the consolidated feature commit and the user's explicit request: internal attention states remain intact but have no separate visible “待跟进” category.
|
||
|
||
## Outcome
|
||
|
||
- Cherry-picked feature commit `1ee89da` as main commit `8dddd21` with no conflict.
|
||
- Integrated the focused leadership shell, 320–920 px responsive behavior, mobile task cards, safe-area detail overlay, unified/accessible metric selected state, and regression coverage.
|
||
- Recorded the source and behavior in `current-state.md`.
|
||
- Updated the canonical dashboard business rule so internal attention/waiting states remain stored as before while the leadership view presents and filters them as “进行中”.
|
||
- AUTH-001, architecture, API, authorization, ERP, release, deployment, and runtime-service behavior remain unchanged.
|
||
|
||
## Verification
|
||
|
||
- Source task verification reviewed: focused dashboard 4/4, repository hygiene 10/10, control-plane 153/153, legacy/platform 264/264, TypeScript check/build, four responsive browser viewports, interaction checks, and zero browser console errors.
|
||
- Main repository hygiene: 10/10 passed.
|
||
- Main TypeScript no-emit check: passed.
|
||
- Main control-plane suite: 153/153 passed.
|
||
- Main legacy and platform suite: 264/264 passed.
|
||
- Main TypeScript build: passed.
|
||
- `git diff --check`: passed.
|
||
- `check_project_docs.py`: passed.
|
||
- `check_doc_drift.py --task-id 20260902-dashboard-mobile-integration-e28c`: passed after canonical reconciliation.
|
||
|
||
## Follow-ups
|
||
|
||
- A normal authenticated runtime check with live control-plane data may be performed under a later runtime/deployment task; this integration does not restart or deploy the service.
|
||
|
||
## Promotion Candidates
|
||
|
||
- None. The accepted user-facing category rule and integrated source reference are reconciled directly in this Integration task.
|