managed-portal/tasks/lessons.md

Lessons

2026-05-12

• Trigger: the user corrected the execution workflow for non-trivial tasks and required persistent task tracking.

• Rule: for any non-trivial task, create or update tasks/todo.md before substantive implementation, keep progress current, and do not mark done without review evidence.

• Preventive action: check for tasks/todo.md, tasks/lessons.md, and repository guidance files before editing code; if the user corrects process expectations, record the rule immediately.

• Trigger: the user required corrections to be persisted for future sessions.

• Rule: any user correction must be recorded in tasks/lessons.md as trigger -> rule -> preventive action.

• Preventive action: after any correction, update lessons before closing the task and mention the recorded rule in the final verification summary.

• Trigger: the user clarified that this repository is meant to run in mainland China environments.

• Rule: future code, build, deployment, and integration changes must consider mainland China network accessibility and should prefer China-friendly defaults where practical.

• Preventive action: when adding dependencies, mirrors, external endpoints, or download flows, explicitly check whether the default path works reliably in mainland China and add configuration or fallback when needed.

• Trigger: the user required deployment to use docker compose only and explicitly disallowed host environment changes.

• Rule: for remote rollout tasks in this repo, prefer repository-contained docker compose changes and do not install packages, edit host configs, or mutate global environment state unless the user explicitly approves it.

• Preventive action: when a deployment is blocked, first fix Dockerfiles, compose files, env files, and mounted paths inside the repo before considering any host-level workaround.