Files
LWLT-AIBOT/.project-docs/30-worklog/tasks/20260901-integrate-account-system-7b2f4d.md
T

45 lines
2.0 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Task: Integrate account system and restart panel
## Identity
- Task ID: 20260901-integrate-account-system-7b2f4d
- Mode: Integration
- Branch: codex/20260901-integrate-account-system-5e8c1a-integrate-account-system-5e8c1a
- Worktree: /Users/inmanx/Documents/lwltAPI-integrate-account-system-5e8c1a
- Base commit: 191c1a1aad6f4bb1651143df3e0c1dc98dcd09e0
- Owner: codex
- Status: Planning
## Scope
- Integrate completed account-system source commit `375fda1` (cherry-picked as `191c1a1`) into the default branch without including unrelated ready-for-integration feature tasks.
- Promote the accepted fixed-scope account, role, dashboard, audit, archive, and task-route authorization model into canonical project memory.
- Run the full repository verification set against the integrated tree.
- Fast-forward local `main`, apply migrations 015–017 to the configured standard control-plane database, and restart only the authorized `127.0.0.1:8786` panel service.
- Verify health, schema readiness, existing administrator login, account management, task-type catalog, and leadership dashboard routing without performing ERP writes or external delivery.
## Intent And Constraints
- Preserve the existing dirty-state history: the prior main-sync task record was committed under its original owner before main was released and updated.
- Keep the roster-workbook feature and every other unrelated peer task outside this integration.
- Do not read or print `.env` or secrets. Reuse the existing supervisor and configured environment for migration/restart.
- Existing accounts migrate as administrators; do not create, reset, disable, or alter real account credentials during deployment verification.
- Do not access ERP, trigger business execution, reload the Chrome extension, or send external messages.
- The user explicitly authorized integration, database migration, and restart in this turn.
## Outcome
- Not completed.
## Verification
- Not run.
## Follow-ups
- None recorded.
## Promotion Candidates
- None recorded.