task-record-contractlisted

# Task record contract A task record is the durable contract for one implementation task. The engineer must be able to work from the task record without guessing. If the current role is orchestrator, route task-record creation or refinement through [[role-delegation]] instead of writing the task record directly. Task records are stored in the configured backend: - **Files projection**: one Markdown file at `.agenticloop/tasks/<TASK-ID>.md`. See `agenticloop/backends/files.md`. - **GitHub projection**: one GitHub issue per task when the project explicitly uses `task_backend: github`. See `agenticloop/backends/github.md`. ## Event Logging Event logging is optional and off by default. When enabled, follow [[event-logging]]: emit `task.created` for a new record and `task.updated` after material scope, criteria, check, or backend-linkage changes. Use the task id and a concise gate fact; never copy the task body or chat into the log. ## Required sections Use `agenticloop/memory/task-record.md` as the canonical task-record shape. It defines the ordered required sections and the optional `Proof Pressure`, `Concurrency Plan`, `Parallel Safety`, `Grouping`, `Source Reference`, `Applicable Project Skills`, and `Outcome` sections. New records also include the `## Verification Attempts` section with the canonical empty state from [[verification-evidence]]. Historical records without that optional learning section remain readable. The `## Outcome` section is optional for routine c