feat: add behavior-preserving performance reference - #114
Conversation
uditgoenka
left a comment
There was a problem hiding this comment.
Thanks for the thoughtful behavior-preservation direction. This is intentionally out of scope for the v2.2.2 stabilization release, and the current generated Codex artifacts are not merge-ready: and contain , while the plugin mirrors contain ; those resource paths do not exist. The change also needs a path-existence/parity assertion so transformed references cannot pass byte-comparison checks while remaining unresolvable. Please regenerate from the canonical source with valid package-relative paths and add a test that every routed resource exists. Keeping this PR open for a post-v2.2.2 release.
|
Exact path correction for the review above: (1) |
Summary
latency, throughput, runtime, CPU, memory, allocation, binary-size, power,
energy, bandwidth, and compute-cost goals.
keepmeans abetter exploratory incumbent, not proof that useful behavior survived.
confirmation, comparable provenance, resource boundaries, and rollback.
distribute it to Claude, Codex/Agents, and OpenCode mirrors.
This is the optimization counterpart of the ownership split in
pawpaw-dev-skillsPR #39.Flow change
Changed files
Verification
bash scripts/transform.shbash tests/test-orchestrator.shbash tests/test-regression.shbash tests/test-hooks.shcmpacross the four behavior reference copiesgit diff --checkRisks / follow-ups
green metric or guard still cannot prove that the chosen observations reflect
real user behavior.
real acceptance remains based on inspectable evidence.