PR 0133 Vulkan attribute report queue lifecycle on current main

PR #133 — Vulkan: attribute report queue lifecycle on current main

State: Merged Reviewed head: 8f84df694cd5a2859023532127fc1ca9fef6342d Role: Supporting implementation/test history. The primary technical reference is Performance-Research-G03-Deferred-Report-Completion.

Why it mattered

Lifecycle telemetry should record interpretable aggregate state and do zero accounting when disabled. Wait attribution is not proof of legal deferral.

Processing difference

flowchart LR
    A["Before: Report waits lacked exact lifecycle attribution."] --> B["PR #133"]
    B --> C["After: Feature-tagged aggregate telemetry records age and routes without changing semantics."]

Loading

Durable lesson

Lifecycle telemetry should record interpretable aggregate state and do zero accounting when disabled. Wait attribution is not proof of legal deferral.

Avoid repeating

• Do not infer correctness or cost from labels such as clean, finish, same handle, or disabled.
• Preserve the ownership, range, publication, retry, identity, or progress contract exposed by the PR.
• Keep focused correctness evidence separate from broad throughput claims.
• Re-run the relevant negative control when moving the mechanism to another renderer or subsystem.

Evidence pointer

• PR #133
• Reviewed head: 8f84df694cd5a2859023532127fc1ca9fef6342d
• Primary technical reference: Performance-Research-G03-Deferred-Report-Completion

Architecture

This page records what the PR taught us. Current design, source status, future experiments, and acceptance rules belong on the linked technical reference page.