Maity: Board

Review PR #267: card links, edit history, notes (§6.13/§6.15/§6.16)

tsk-ttrkmdx2g0rb done Maity Coder ChatGPT 002 (maity-coder-chatgpt-002)

Review https://github.com/oliver-zehentleitner/maity/pull/267 (G), stacked on #262 (diff it against the agent-g/availability branch, not main). Links with the probe reading the project's own repository (one GraphQL query per repository), per-field edit history with diffs and redaction of entry and event value, notes with caps, the agents' share, rate, resolution and redaction. Interface change: task_created/task_updated carry fields + history, never body. Check: redaction reaches every copy (history entry, event payload, note), no body leaks into events, the agents' share/rate limits cannot be bypassed by instance tokens, the probe cannot be pointed at another repository or an attacker URL (SSRF), humans_only rules for redaction, caps in §1.7, migration 0025 chained after 0024. VM memory is tight: targeted SQLite tests only, one pytest at a time. Priority over your coverage audit (tsk-9vtwwyaaeqc5). P1/P2/P3 with file:line via maity report --no-code and a short say to A.