specs/openspec/changes/establish-audit-remediation-workflow/tasks.md

1. Durable remediation registry

• 1.1 Create docs/development/audit-remediation.md with the registry contract, allowed statuses, required terminal evidence fields and a link to the immutable audit-20-08-2026.md.
• 1.2 Add one planned record for each of the 5 P1, 13 P2 and 8 P3 confirmed findings; preserve Audit IDs, priorities, affected repositories and concise remediation goals without duplicating the full audit text.
• 1.3 Record that no audit remediation change is active and mark stabilize-frontend-query-and-strict-contracts as the sole next recommended change for WL-P1-01 and WL-P1-02.
• 1.4 Add the registry to docs/development/README.md and state that this bootstrap change does not by itself close WL-P2-13 or any other audit finding.

2. Agent discovery

• 2.1 Add a concise audit-work link and canonical OpenSpec continuation rule to frontend/AGENTS.md, backend/AGENTS.md, specs/AGENTS.md and docs/AGENTS.md; do not copy the backlog into those files.
• 2.2 From each of the four Git roots, verify that the documented relative path resolves to the same registry and that a linked Audit ID leads to the canonical OpenSpec workflow.

3. Evidence and review

• 3.1 Review the registry against audit-remediation-workflow scenarios: dated audit remains unmodified, statuses are valid, there is at most one active record, the next task is unique, and no done record lacks terminal evidence.
• 3.2 Run non-mutating checks: openspec validate establish-audit-remediation-workflow --type change --store wealth-ledger-specs, git diff --check in each affected repository, and a read-only link/record structure check.
• 3.3 Perform an independent review of registry-to-audit mapping, OpenSpec links, instruction discoverability and unintended scope expansion; resolve every confirmed issue before completion.

4. Completion

• 4.1 Add this bootstrap change to the registry history with its exact commands and observed results, without marking any audit finding done.
• 4.2 Run opsx-verify for the change and resolve every blocking result before archive.
• 4.3 Archive the change only after all tasks and required evidence are complete; sync resulting delta specs into main specs.
• 4.4 Commit the change separately in each affected Git repository with no unrelated files.