[houlianpi]

Requirement

Closes #76

User-visible result

One authenticated Candidate artifact contains exact macOS arm64 / CPython 3.11 and Windows x64 / CPython 3.12 dependency wheelhouses and can install without an acceptance-host package index.

Scope

• Same-run Candidate base, target-wheelhouse, final-artifact, and offline-install workflow jobs.
• Canonical target manifests, provenance, fixed-source acquisition, checksum closure, and final artifact verification.
• Candidate-only offline installation prompt, focused contract tests, eval input, and technical documentation.

Non-goals

• No public Release wheelhouse or normal PyPI installation change.
• No Linux/WSL or additional Python/platform support.
• No package publication, protected-branch/settings change, Runtime behavior change, or release.

Interface changes

Candidate artifact schema 3 gains wheelhouse/darwin-arm64-py311/ and wheelhouse/win32-amd64-py312/, one canonical manifest per target, exact file inventories, and complete checksum coverage. Public Release interfaces remain unchanged.

Acceptance scenarios

Given one clean commit and same-run strict-hash dependency lock
When the Candidate workflow assembles and verifies both target wheelhouses
Then one final artifact contains exact target inventories and installs offline on each declared native target
And missing, extra, substituted, incompatible, stale, or cross-run content fails closed without an index fallback

Verification evidence

Check	Result	Evidence
Targeted tests	Pass	94 passed in 7.33s: test_candidate_wheelhouse.py and test_skills.py
Build/type checks	Pass	Python compilation; workflow YAML parse; git diff --check
Clean-environment smoke test	Pending CI	Native macOS 3.11 and Windows 3.12 final-artifact jobs added; local host lacks those exact environments
Acceptance scenarios	Partial pending CI	Builder/verifier, substitution, provenance, credential isolation, tag boundary, network-denial and prompt contracts pass locally

Agent roles and review gate

• Implementer: OMP coding assistant, directed by @houlianpi
• Independent reviewer: Issue76SecurityReview security-reviewer
• Security coverage: same qualified independent reviewer; final decision APPROVED after two remediation rounds
• Separate acceptor: required after merge
• Acceptance-gate reason, if required: issue [Release]: Bundle exact dependency wheelhouses in Candidate artifacts #76 requires exact native built-artifact jobs and post-merge exact-main native-macOS acceptance

Security review

• Secrets and sensitive inputs are not written to logs, generated code, or tracked configuration.
• File writes are scoped and atomic.
• Command/process inputs are not shell-interpolated.
• Package downloads and remote instructions are pinned or verified.
• Not security-sensitive; explanation: security-sensitive packaging and process-execution change; independent review approved.

Fixed unauthenticated PyPI acquisition uses a transaction-private empty home, null netrc/config, disabled keyring, no ambient proxy/source/cache overrides, wheel-only strict hashes, and bounded/suppressed untrusted diagnostics. Candidate installation verifies the external GitHub artifact service digest before internal closure and denies network access during pip execution.

Compatibility impact

Candidate support is intentionally restricted to native macOS arm64 / CPython 3.11 and native Windows x64 / CPython 3.12. Unsupported or ambiguous hosts fail closed. Public package coordinates and release behavior do not change.

Rollback

Revert commit 8030072; return #28/#70 to blocked and do not accept a wheelhouse Candidate. No public identity or migration is introduced.

Known limitations

• Native CI evidence is required before merge.
• Wheelhouse availability alone does not qualify Windows journeys, Skill discovery, MCP readiness, Calculator/Notepad behavior, or recording safety.
• Post-merge exact-main Candidate and separate native-macOS acceptance remain required.

Definition of Done

• The issue met Definition of Ready before implementation began.
• Scope and non-goals were preserved.
• All acceptance scenarios pass in their required environments; clean-environment evidence is present when the issue or release gate requires it.
• Required CI checks pass.
• One independent reviewer approved the change.
• A separate acceptor posted clean-environment evidence when the issue or release gate requires it; otherwise marked not required with a reason.
• Security coverage passed or is explicitly not applicable; correctness and security may be covered by the same qualified independent reviewer.
• Prompt changes include an eval comparison.
• Documentation and machine-readable configuration agree.

[houlianpi]

Implementation commit: 8030072. Independent combined correctness/security review: APPROVED after remediation. Auto-merge to feature/agent-integration-v3 is enabled and remains gated by required CI, including native macOS arm64 / CPython 3.11 and Windows x64 / CPython 3.12 final-artifact offline-install jobs. Direct merge to main is intentionally not attempted: repository governance requires capability PRs to enter the integration branch, followed by epic-level black-box acceptance before integration targets main. Post-merge exact-main Candidate and separate native-macOS acceptance remain required by #76.