Append exact qualification and deployment receipts to issue timelines #69

Outcome

Show the exact job, commit, qualification, release, and deployment receipt chain on the issue that requested the work.

Current behavior

Issue #10 names this linkage, and /status can show deployment history, but an issue does not yet provide one bounded timeline from execution through the environment that accepted the revision.

Source: docs/episode-triage.md, the receipt station and assessment track E.

Contract

• Link work jobs and commits through stable identifiers, not free-form commit messages alone.
• Attach test and qualification receipts to the exact commit they evaluated.
• Attach release and deployment receipts to the exact candidate and environment.
• Preserve failed, canceled, superseded, and rolled-back attempts.
• Make every append idempotent and actor-attributed.
• Apply artifact visibility independently so a public issue can show that evidence exists without disclosing private evidence.
• Never treat a push receipt as a deployment receipt.

Acceptance criteria

• One issue can show several execution and deployment attempts without losing history.
• A deployment receipt for another commit or environment cannot satisfy the issue.
• Reloading or replaying an event does not duplicate timeline entries.
• Public, member-only, and private viewers see the correct bounded projection.
• The final accepted outcome links back to the exact evidence that qualified it.

Verification

Add schema, idempotency, authorization, stale-revision, rollback, and LiveView tests. Qualify one issue-to-production path on staging and run mix precommit.

Dependencies

This is a delivery slice of #10. Coordinate #33 for the status projection.