docs: finalize AI logging format system

- align ai-worklog and ai-prompts with the current logging framework
- require timestamped structured log entries
- finalize logging rules in instructions-agent.md

instructions-agent.md

@@ -143,10 +143,16 @@ Agents must write log entries using the following structure.
 Example for build tasks:
 
 ### AI BUILD ENTRY
-Date: YYYY-MM-DD HH:MM  
-Task: build  
+Date: YYYY-MM-DD HH:MM
+Task ID: BUILD-YYYYMMDD-XXX
+Agent: OpenCode
+Task: build
 Objective: short description of the task
 
+Scope:
+- src/app/module.py
+- tests/test_module.py
+
 Files Modified:
 - file/path/example.py
 - another/file.md
@@ -167,10 +173,16 @@ Open Issues:
 Example for plan tasks:
 
 ### AI PLAN ENTRY
-Date: YYYY-MM-DD HH:MM  
-Task: plan  
+Date: YYYY-MM-DD HH:MM
+Task ID: PLAN-YYYYMMDD-XXX
+Agent: OpenCode
+Task: plan
 Objective: short description of planning objective
 
+Scope:
+- src/app/module.py
+- specs/module_spec.md
+
 Files Inspected:
 - src/app/example.py
 - specs/example_spec.md
@@ -188,3 +200,8 @@ Rules:
 - Use bullet points when possible.
 - This format must be used when updating `docs/ai-worklog.md`.
 - The Date field must include both date and time using the format YYYY-MM-DD HH:MM.
+- Every log entry must include a `Task ID`.
+- `Task ID` format must be `BUILD-YYYYMMDD-XXX` or `PLAN-YYYYMMDD-XXX`.
+- `Agent` must identify the tool or AI system performing the task (e.g., OpenCode).
+- `Scope` must describe the main files or project areas affected.
+- These fields make the AI worklog suitable for long-term traceability and large histories.