[KAVentures]

Product gap

Observed ownership transition alone cannot prove a cross-person handoff actually progressed. Jira's authorized changelog sometimes supplies a second independent audit event: the newly assigned account later changes the issue status.

Change

• HMAC-pseudonymize the Jira changelog's optional author.accountId on valid status transitions using the existing per-install secret; never emit user IDs, display names, comments, issue keys, or status labels.
• For each exact-issue assignee transition, look for a strictly later, independently audited valid status ID transition authored by the new assignee; annotate subsequent_status_action_by_assignee_observed, the corroborating opaque source audit reference and observed count.
• Keep accepted_by_new_assignee=false, work_completed_by_new_assignee=false, verified_human_handoffs=0, verified_business_outcome=false, and document that no evidence of later status change does not mean no work. Bounds, authorization, and default-OFF behavior unchanged.
• Synthetic tests cover matching and nonmatching actor actions, missing author data, strict ordering, output redaction, and persistent refusal to declare acceptance.

This is source-corroborated later activity, not a verified human handshake, cross-system confirmation, customer outcome or real provider account test. Changes only Jira source code + existing Jira tests/docs, with no overlap with PR #240's local Stripe setup or #241's trial runner. Draft pending CI and customer-authorized Jira test; does not alone close #226.