Test fail-closed macOS runtime boundaries (#193)

[Niko4417]

Scope

• Accepted issue: Test: Harden fail-closed macOS runtime boundary paths #193
• Accepted planning-contract version: v2
• Automated readiness record: Test: Harden fail-closed macOS runtime boundary paths #193 (comment)
• Actual source branch: codex/193-runtime-boundary-tests
• 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; Contract and unit behavior; Failure and recovery envelope; Security and privacy; Performance and resource use for zero-residue evidence
• Change classification: hardening
• Product decision, finding, or incident: exact cf870ab baseline report add40f2938fb397d351d293ba1ac3c295879d9cdb21ba335e573cb5457787774 left the fixed 33 runtime directions uncovered; the audited Defect: Make Codex cleanup coverage proof deterministic #101 composition report f99a8327a81d48c302613923a589aca0564aa58de90a0024fd8a9387fcd26272 proved insufficient portfolio margin.
• In scope: deterministic hermetic tests for the accepted 33 existing runtime-boundary outcomes in native/crates/keiko-host-macos/src/runtime.rs
• Out of scope: product behavior, runtime seams, new types or monomorphs, gates, workflows, dependencies, UI, documentation, Defect: Make Codex cleanup coverage proof deterministic #101, Integrated packaged macOS acceptance for the Codex tracer #104, and Epic: Contract-as-Code migration and lifecycle activation cutover (ADR-0003/ADR-0004) #49
• Native targets, contracts, or trust boundaries affected: macOS host test evidence for bounded protocol input, verified runtime identity, private runtime paths, exact process identity and authenticated signaling, and retained retirement refusal

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	Focused schema, framing, projection, and verified-artifact tests; all fixed selected directions changed from zero to positive coverage	5160de5dcd3b04924217c893d4e612a0dd3b93eb; report SHA 0cd2665bc4969fa8d5cdb3a6b800eb32de5517ac7176c7696a7560ba55824596	Complete
AC2	authenticated_signal_refuses_another_owned_process_group; exact-current ownership, live/unmutated refusal snapshot, authenticated bounded teardown, zero residue	5160de5dcd3b04924217c893d4e612a0dd3b93eb	Complete
AC3	Private-directory, startup, cancellation, request dispatch, and live-owned/live-descendant retirement-refusal focused tests	5160de5dcd3b04924217c893d4e612a0dd3b93eb	Complete
AC4	Same-base workspace branches 1072/1250 = 85.76% to 1104/1258 = 87.7583%; +32 covered outcomes, +8 denominator, 24 fewer uncovered; every fixed33 direction positive	report SHA 0cd2665bc4969fa8d5cdb3a6b800eb32de5517ac7176c7696a7560ba55824596	Complete
AC5	One-file test-only diff; focused tests; host 172/172 x3; native coverage x3; full quality/audit/macOS acceptance; independent audits findings 0; remote macOS 14/26 and review settlement pending	5160de5dcd3b04924217c893d4e612a0dd3b93eb	Pending remote exact-head evidence

Acceptance journey evidence

• Applicability: Not applicable — this issue changes only repository-owned test evidence for existing non-user-facing runtime behavior; no product or UI state changes

• Automated checks exercise user-visible outcomes rather than incidental implementation details. Not applicable and settled by the accepted issue rationale; automated checks directly exercise the non-user-facing runtime contracts.

• Required failure, recovery, accessibility, visual, and platform observations are settled. Local failure/recovery and macOS evidence are green; fresh remote macOS 14/26 evidence is pending.

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. Local security/resource/zero-residue evidence is green; remote macOS 14/26 evidence is pending.
• 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. Local macOS acceptance is green; remote macOS 14/26 jobs are pending.
• I reviewed the complete diff against requirements, contracts, trust boundaries, and failure modes.

Additional affected checks and concise results:

Focused accepted tests: 11/11 green
Host suite: 172/172, three sequential passes
npm run native:coverage: three sequential passes
npm run quality: exit 0
npm audit --audit-level=high: 0 vulnerabilities
npm run acceptance:macos: exit 0
Workspace branch coverage: 1104/1258 = 87.7583%
Net newly covered same-base outcomes: +32
Persisted report SHA-256: 0cd2665bc4969fa8d5cdb3a6b800eb32de5517ac7176c7696a7560ba55824596
SHA-bound verify receipt: green at 5160de5
SHA-bound audit receipt: findings=0, user_facing=false at 5160de5

Independent audit and findings

• Audit scope and dimensions: accepted fixed33 mapping, one-file test-only scope, semantic assertions, existing reader monomorph, private-state construction, exact process identity/authenticated effects, failure-safe bounded teardown, helper branch deficit, same-base report, signatures, receipts, and all local exact-head gates
• Audited commit: 5160de5dcd3b04924217c893d4e612a0dd3b93eb

Confirmed finding	Evidence	Disposition	Settlement evidence or follow-up
Initial test-harness identity, teardown, helper-branch, digest-construction, and schema-completeness findings	Independent pre-report audit against the uncommitted candidate	Resolved before the sole report	Corrected diff 88aa6584a7dbd70daf24c0078dd6f78f6064223ff753a2b8e65bbff3ea4b5d16; repeated focused checks; post-report and exact-head audits findings 0
None remaining	Final local-gate audit	Findings 0	Signed exact head, clean worktree, green receipts

• 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: Not applicable — this child adds test evidence and does not itself deliver or change the epic integrated production acceptance surface
• Production-composition result: unchanged; no production bytes were modified
• Machine-enforced acceptance result: local exact-head quality and macOS acceptance green; child remote CI pending
• macOS evidence: local host 172/172 x3, coverage x3, full acceptance green; remote macOS 14/26 pending
• Windows evidence: not applicable to the macOS host test-only issue; cross-platform smoke CI is tracked separately
• Manual usability, accessibility, visual, signing, or packaging evidence: user-facing/manual/visual/accessibility not applicable; local signing/package gates green

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. Commit and local receipts are bound; remote exact-head checks are pending.
• 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. Remote CI and review settlement are pending.

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.

Sequencing disclosure: the exact audited source branch at 5160de5 was pushed immediately before a later runner instruction required SHA-bound receipts as the final pre-PR action. No pull request existed and no code changed. The verify and audit receipts were completed successfully and bound to the same unchanged 5160de5 before this pull request was created.

Residual risks and follow-ups

• Fresh exact-head macOS 14 and macOS 26 CI, required review settlement, zero unresolved conversations, and guarded child integration remain pending.
• The branch-before-receipt sequencing disclosure above is retained for auditability; the immutable commit and PR creation boundary were not crossed by different code.

[Niko4417]

@codex review

[Niko4417]

Superseded by readiness-accepted atomic bridge #195 after exact-head run 31366872754 proved the sequential #193/#101 delivery cycle. This PR is closed without merge or retry; commit 5160de5 and its audited report remain immutable component provenance. Standalone #193 acceptance is not claimed as passed.