docs: integrate leadership dashboard definition

.project-docs/30-worklog/current-state.md

@@ -11,10 +11,12 @@ This file is the integrated default-branch snapshot. Feature tasks record progre
 - Commit `b08f2960fa4db09c807b6fb61dfba33dc524a274` for the read-only list-attachment behavior inspection record; no product behavior changed.
 - Commit `191c1a1aad6f4bb1651143df3e0c1dc98dcd09e0` for the fixed-scope account system, three-role authorization, owner isolation, operations dashboard, audit/archive behavior, and per-account task-route grants.
 - Integration task `20260901-integrate-account-system-7b2f4d` for canonical authorization reconciliation, migrations 015–017, and the authorized standard-panel restart.
+- Commit `823d1cb6305077e1743f8783176d2cae3b5aec39` for the aggregate-first leadership platform-operations dashboard and business-safe input/result projections.
+- Integration task `20260901-integrate-leadership-dashboard-9e2b6c` for the leadership-dashboard product-definition correction.
 
 ## Current Focus
 
-Operate the current `0.5.163` extension baseline and the deployed fixed-scope account model safely, provision roles and task grants through administrator workflows, and preserve Program/AI plus ERP execution boundaries.
+Operate the current `0.5.163` extension baseline and the deployed fixed-scope account model safely, provision roles and task grants through administrator workflows, use the aggregate-first leadership dashboard for business oversight, and preserve Program/AI plus ERP execution boundaries.
 
 ## Recently Completed
 
@@ -26,6 +28,7 @@ Operate the current `0.5.163` extension baseline and the deployed fixed-scope ac
 - 2026-08-31: Integrated structured privacy-safe diagnostics across service, HTTP, task/audit, parser, AgentBus, attachment, database, and cleanup stages, with bounded Docker stdout retention and a read-only server diagnostic command.
 - 2026-08-31: Confirmed from the supplied production log that attachment correlation succeeded and the failure was private/reserved DNS rejection; removed that rejection for the trusted internal deployment while retaining credential-free HTTPS, DNS pinning, redirect validation, size, timeout, and SHA-256 controls.
 - 2026-09-01: Integrated and started the three-role account system on the standard 8786 control plane. Migrations 015–017 added owner/audit/archive state, team-lead dashboard support, and administrator-managed task-route allowlists; the existing account migrated as administrator.
+- 2026-09-01: Reframed the leadership dashboard from instruction-history/audit presentation to a platform-running view across tasks, people, input, output, time, type, and completion, with clickable drill-through and no visible technical payload language.
 
 ## In Progress
 

.project-docs/30-worklog/tasks/20260901-integrate-leadership-dashboard-9e2b6c.md

@@ -0,0 +1,50 @@
+# Task: Integrate leadership dashboard product definition
+
+## Identity
+
+- Task ID: 20260901-integrate-leadership-dashboard-9e2b6c
+- Mode: Integration
+- Branch: main
+- Worktree: /Users/inmanx/Documents/lwltAPI
+- Base commit: 823d1cb6305077e1743f8783176d2cae3b5aec39
+- Owner: codex
+- Status: Ready for integration
+
+## Scope
+
+- Integrate feature commit `823d1cb6305077e1743f8783176d2cae3b5aec39` and its accepted leadership-dashboard product correction into canonical project memory.
+- Reconcile `AUTH-001`, architecture/data-flow, domain rules, current state, evidence, and reflection indexes.
+- Do not change runtime behavior, restart services, access ERP, mutate tasks, or send data externally.
+
+## Intent And Constraints
+
+- Preserve the accepted three-role authorization and read-only manual-task dashboard boundary.
+- Record the user-confirmed distinction between an aggregate-first leadership operations view and an audit/debug history surface.
+- Canonicalize the rule that technical payloads and machine-shaped historical input are not rendered in the leadership dashboard while underlying audit evidence remains unchanged.
+
+## Outcome
+
+- Accepted the feature task's promotion candidates without semantic conflict: the correction narrows presentation and product framing but does not widen access or change task mutation authority.
+- Updated `AUTH-001`, decision index, system overview, data flow, business rules, current state, evidence index, and reflection index.
+- Recorded feature commit `823d1cb6305077e1743f8783176d2cae3b5aec39` and this integration task under `Integrated Through`.
+- No runtime, database, ERP, external-system, or service-process state was changed.
+
+## Verification
+
+- Source feature verification: repository check 10/10, control-plane 153/153, legacy 256/256, TypeScript check/build, JavaScript syntax, focused 8/8, diff check, and authenticated browser drill-through all passed.
+- `check_project_docs.py`: passed.
+- `check_doc_drift.py --task-id 20260901-integrate-leadership-dashboard-9e2b6c`: passed for all canonical writes.
+- `node --run check:repo`: 10/10 passed after canonical integration.
+- `node --run check`: passed after canonical integration.
+- `node --run test:control-plane`: 153/153 passed after canonical integration.
+- `node --run test:legacy`: 256/256 passed after canonical integration.
+- `node --run build`: passed after canonical integration.
+
+## Follow-ups
+
+- Create representative team-lead and ordinary-user accounts through the existing administrator workflow so the people-comparison dimension contains more than the migrated administrator.
+- Apply the control-plane projection on the next separately authorized service restart; the running static page already enforces the same leadership-safe presentation.
+
+## Promotion Candidates
+
+- None. The accepted feature candidates were promoted in this integration task.