fix(acceptance): retain tracer performance evidence (#104)

[Niko4417]

Scope

• Accepted issue: Integrated packaged macOS acceptance for the Codex tracer #104
• Accepted planning-contract version: v6
• Automated readiness record: Integrated packaged macOS acceptance for the Codex tracer #104 (comment)
• Actual source branch: codex/104-picker-budget-v6
• Accepted target branch: epic/98-codex-tracer
• Parent epic and Quality Envelope rows: Epic: Governed Codex lifecycle tracer — one workspace, one no-effect turn #98 v5; all parent rows, with direct ownership of production-composition CORE, machine-enforced acceptance CORE, desktop blackbox, integrated accessibility/design, security/privacy, and resource evidence
• Change classification: parity-replacement
• Product decision, finding, or incident: Product-owner-approved coding-tracer-first sequence and the 2026-08-08 correction separating platform-owned native picker dismissal from unchanged Keiko-controlled projection latency
• In scope: Repository-owned packaged-macOS acceptance harness and tests; separate picker metric/distribution; closed reference-Mac evidence; monotonic action-inclusive AX timing; exact semantic checkpoints
• Out of scope: Product/application behavior, issue Epic: Contract-as-Code migration and lifecycle activation cutover (ADR-0003/ADR-0004) #49, Knowledge Capsules/RAG, signing/notarization, Windows/Linux qualification, performance optimization, credentials, effects, Git, or delivery
• Native targets, contracts, or trust boundaries affected: macOS arm64 acceptance/evidence only; acceptance schema advances from acceptance/v1 to acceptance/v2; no product or privileged-effect trust boundary changes

Product and architecture alignment

• The implemented contract version and fingerprint match the automated readiness record; no
  semantic planning change was absorbed during implementation.
• The change follows the Decision Addendum, CONTEXT.md, accepted ADRs, and the issue Quality
  Plan.
• Existing Keiko material was used only after a recorded Reuse Assessment, or the issue records
  why Existing Keiko evidence is not applicable.
• This greenfield change creates no mandatory build-time or runtime dependency on Existing
  Keiko.
• Product authority, policy, evidence, and privileged effects remain in their owning Native
  layer.
• Any durable architecture change is recorded in an ADR.

Acceptance criteria and evidence

Acceptance criterion	Evidence	Exact head or artifact	Result
AC1	npm run acceptance:codex-tracer:macos; 16/16 packaged checkpoints, fixed no-effect turn, cancellation and cleanup	e36094423fd0a9909e2c34b73bf8cb6206967b81	Complete
AC2	acceptance/v2 validator retains ordered 20-launch distribution; Keiko p95 67 ms; picker p95 638 ms; turn cancellation 51 ms; zero effects/context/residuals	e36094423fd0a9909e2c34b73bf8cb6206967b81	Complete
AC3	npm run acceptance:macos plus digest-bound physical observation of AX semantics, keyboard focus, Unicode, Light/Dark, Increase Contrast, picker cancellation, and process cleanup	e36094423fd0a9909e2c34b73bf8cb6206967b81	Complete

Acceptance journey evidence

• Applicability: Required

Journey and checkpoint	Automated evidence and command	Manual or platform evidence	Result
J1.1 exact package/runtime identity	npm run acceptance:codex-tracer:macos; source/package/runtime/schema identity checks	Physical packaged macOS arm64 app, digest bound	Complete
J1.2 select, submit, stream, deny, cancel, recover, quit	Canonical acceptance, 16/16 checkpoints; 0 accepted effects; 0 repository bytes/context; 0 residual processes	Folder picker cancellation and process observation on the authoritative Mac	Complete
J1.3 evidence and accessibility	Closed acceptance/v2 validation; 20 ordered fresh-launch samples; exact p95 consistency	AX semantics, keyboard/focus, Unicode, Light/Dark, Increase Contrast, streaming readability and cancellation observed	Complete

• Automated checks exercise user-visible outcomes rather than incidental implementation
  details.
• Required failure, recovery, accessibility, visual, and platform observations are settled.

Quality Plan settlement

• Applicable positive, negative, boundary, failure, cancellation, and recovery behavior is
  covered.
• The actually wired production composition was tested where this change crosses layers.
• Applicable security, accessibility, performance, resource, visual, and platform evidence is
  attached or linked.
• Excluded quality areas retain the rationale accepted in the issue.
• Secrets, credentials, raw customer content, private endpoints, and PII are absent from source,
  tests, logs, evidence, artifacts, issues, and this pull request.

Verification

• npm ci --ignore-scripts
• npm run quality
• npm audit --audit-level=high
• Every declared native target-specific gate passed on its authoritative platform.
• I reviewed the complete diff against requirements, contracts, trust boundaries, and failure
  modes.

Additional affected checks and concise results:

Exact-head verify receipt: full quality and npm audit green at e36094423fd0a9909e2c34b73bf8cb6206967b81
Focused acceptance suites: 49/49
npm run acceptance:macos: green; acknowledgement/workspace 1686 ms; shutdown 383 ms; descendants 0
npm run acceptance:codex-tracer:macos: green; 16/16 checkpoints; local projection p95 67 ms; native picker p95 638 ms/20 fresh launches; turn cancellation 51 ms; effects/context/residuals 0
git diff --check: green

Independent audit and findings

• Audit scope and dimensions: Full Integrated packaged macOS acceptance for the Codex tracer #104 v6 diff, acceptance criteria, Quality Plan, composition, evidence schema, timing, containment/redaction, package exclusion, process cleanup, scope and trust boundaries
• Audited commit: e36094423fd0a9909e2c34b73bf8cb6206967b81

Confirmed finding	Evidence	Disposition	Settlement evidence or follow-up
None	Independent exact-head re-audit; stable patch identity and byte-identical eight-file delta	Settled	Findings 0; full verify and both macOS acceptance commands green

• Findings are evidence-cited; speculative observations are advisory rather than blockers.
• Every confirmed finding is resolved, explicitly accepted by an authorized human, or linked to
  a scoped follow-up that does not invalidate current acceptance.
• Verification and audit were repeated after the latest implementation or audit fix.

Integrated epic acceptance

• Applicability: Required
• Production-composition result: Exact packaged app and @openai/codex@0.145.0 runtime exercised through production modules; complete
• Machine-enforced acceptance result: 16/16 checkpoints; closed schema; exact source/package/runtime binding; no product test hook
• macOS evidence: Packaged arm64 shell and canonical tracer acceptance green on the declared reference Mac
• Windows evidence: Not applicable under ADR-0006 and issue Integrated packaged macOS acceptance for the Codex tracer #104 v6
• Manual usability, accessibility, visual, signing, or packaging evidence: Digest-bound physical AX semantics, keyboard/focus, Unicode, Light/Dark, Increase Contrast, folder-picker cancellation, streaming readability, crash/cancellation recovery, package inspection, and zero residual processes complete

Delivery

• Target path: child issue -> epic branch
• The target branch matches the delivery path accepted in the issue; no direct push, force
  push, gate bypass, finding dismissal, or authority widening occurred.
• Commits are signed and every required check is bound to the exact current head and expected
  producer.
• Advisory tools are not treated as required merge authority under the current quality-gate
  policy.
• Documentation, ADRs, contracts, known limitations, and follow-ups are current.
• A draft pull request was not promoted to Ready for Human Review before every required
  Acceptance Journey result and exact-head gate was complete.

For a child-issue pull request targeting its designated epic branch:

• The accepted issue authorizes this epic-branch target.
• Acceptance and audit evidence is complete, every applicable exact-head gate is green, and no
  blocking finding or review conversation remains.

This authority exists only for a fully eligible child-issue pull request targeting its exact
accepted epic/** branch. Epic and standalone pull requests remain human-only deliveries to dev.

Residual risks and follow-ups

• Remote exact-head CI and Codex review are pending while this PR remains draft. No implementation residual risk is currently confirmed.