PR 0123 PGRAPH validate array packets before bulk selection

PR #123 — PGRAPH: validate array packets before bulk selection

State: Merged Reviewed head: fce724a16f819d7ef6cd0e918baf39f4d13bd1f9 Role: Supporting implementation/test history. The primary technical reference is Using-Hot-Path-Shortcuts.

Why it mattered

Correctness invariants belong before optimization/reference-route selection. A performance toggle must never disable packet bounds, atomicity, or rejection rules.

Processing difference

flowchart LR
    A["Before: Bulk-off scalar paths could bypass complete-packet capacity preflight."] --> B["PR #123"]
    B --> C["After: Validate the complete packet first, then choose bulk, trace, or scalar execution."]

Loading

Durable lesson

Correctness invariants belong before optimization/reference-route selection. A performance toggle must never disable packet bounds, atomicity, or rejection rules.

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 #123
• Reviewed head: fce724a16f819d7ef6cd0e918baf39f4d13bd1f9
• Primary technical reference: Using-Hot-Path-Shortcuts

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.