docs: introduce mandatory AI logging system

- add AI worklog and prompt logs
- enforce logging rules in instructions-agent.md
- require AI agents to record plan and build tasks
- establish traceable AI-assisted development workflow

instructions-agent.md

@@ -83,3 +83,48 @@ Rules:
 4. Do not store private chain-of-thought or internal reasoning.
 5. Store only concise, user-facing summaries of what was done.
 6. Keep entries chronological and easy to scan.
+
+## Mandatory AI Logging
+
+Every significant AI interaction in this repository must be logged.
+
+This applies to:
+- `plan` tasks
+- `build` tasks
+- debugging tasks
+- documentation tasks
+- architectural discussions that affect the project
+
+Required files:
+- `docs/ai-worklog.md`
+- `docs/ai-prompts.md`
+
+Mandatory rules:
+1. After every significant `plan` task, append a concise entry to `docs/ai-worklog.md`.
+2. After every significant `build` task, append a concise entry to `docs/ai-worklog.md`.
+3. If the task was driven by a meaningful prompt, also append an entry to `docs/ai-prompts.md`.
+4. Logging is part of the task itself and must not be skipped.
+5. The task is not complete until the logs are updated.
+
+Each worklog entry must include:
+- date
+- task type (`plan` or `build`)
+- short objective
+- files inspected or modified
+- key decisions
+- validation commands run, if any
+- result
+- unresolved issues, if any
+
+Each prompt log entry must include:
+- date
+- task type (`plan` or `build`)
+- short prompt summary
+- scope
+- result summary
+
+Rules:
+- Do not store chain-of-thought or private reasoning.
+- Store only concise user-facing summaries.
+- Keep entries chronological.
+- Even small but meaningful tasks must be logged.