Skip to content

Release audit ledger: track audit ranges, heads, artifacts, and follow-up status #4010

Description

@justin808

Problem

Release and post-merge audits are currently discoverable only by reading a mix of release-gate comments, tracking issues, and chat summaries. That makes "what has already been audited?" ambiguous.

Current examples:

Those are all useful, but none is a canonical audit ledger that records coverage by range/head SHA and points to follow-up status.

Proposal

Use the release gate issue as the canonical audit coverage ledger for a release train, with finding details staying in dedicated audit parent issues.

Add an Audit ledger section or append-only Audit Ledger Update: comments with:

Field Meaning
Audit ID Stable ID, e.g. 2026-06-14-rc3-catchup
Purpose release gate, process audit, skill audit, continuous eval
Base tag or SHA
Head SHA audited through
Range exact git range
PR count included PR count
Report link issue/comment/artifact
Follow-up parent parent issue if findings exist
Status planned / running / clean / follow-ups-open / superseded
Next range where the next audit should start

The detailed findings should still live in audit-specific parent issues, but the release gate should answer the coverage question immediately: "last audited through SHA X; next audit starts at X."

Acceptance criteria

Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    TRACKINGParent tracking issue for multi-task initiativesrelease

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions