P0: pin and verify secure-network installer metadata for pristine Macs

[100yenadmin]

Problem

The pristine-Mac guided-action draft can open Tailscale's official macOS download page, but Workbench does not yet own a pinned, verified installer candidate. That browser handoff is useful guidance, not the zero-touch release contract in #662.

Without release-owned version, digest, signing identity, and license metadata, Workbench must not silently download or run a mutable package and must not call the installation complete.

Required contract

• Extend the evaOS Workbench release manifest with an approved macOS secure-network client artifact:
  • vendor and supported variant;
  • exact version and immutable URL;
  • SHA-256 digest;
  • expected package/app signing identity;
  • license/source notice;
  • target architecture and supported macOS versions.
• Download only after an explicit customer click into a private temporary location.
• Verify digest and signing identity before opening the normal macOS Installer.
• Never bypass Installer, administrator, Touch ID, VPN, system-extension, or System Settings consent.
• Detect an existing supported Standalone or App Store variant and never install both variants.
• Delete temporary material after completion or cancellation and re-probe state.
• No Terminal, Python, pip, Homebrew, CLI integration, or customer-entered commands.

Acceptance proof

• unit tests for missing/mutated digest, wrong signer, wrong architecture/version, duplicate variant, cancellation, and cleanup;
• release-script checks bind the installer metadata to the exact signed Workbench candidate;
• clean-host Functional Smoke opens only the verified installer;
• exact pristine-Mac proof remains owned by P0: Workbench fresh-Mac onboarding depends on unbundled Python and manual private-network setup #662/P0: Mac & iPhone readiness can appear ready before end-to-end broker runtime control works #655.

Dependencies

• Parent P0: P0: Workbench fresh-Mac onboarding depends on unbundled Python and manual private-network setup #662
• Typed prerequisite consumer: P0: add typed Mac onboarding prerequisites #664
• Guided actions: forthcoming stacked PR from codex/662-guided-actions
• End-to-end readiness: P0: Mac & iPhone readiness can appear ready before end-to-end broker runtime control works #655

Proof boundary

Opening the official vendor page is not a pinned installer, installation, enrollment, release, or customer-ready proof.

[coderabbitai]

🔗 Related PRs

#399 - Register local signed DMG manifest workflow [merged]
#403 - fix: recover Mac control installed app states [merged]
#449 - Fix legacy app stale owner proof path [merged]
#462 - [codex] Document Workbench release proof lanes [merged]
#476 - Harden installed Mac-control proof scope [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #665 - P0: pin and verify secure-network installer metadata for pristine Macs
State: open; milestone: Workbench Runtime Reliability Release Train

Related issues/PRs: #662, #664, #655.
Existing labels: evaos, public-beta, ready-for-agent, area:native-companion, area:release, risk:security, kind:integration, blocked, release-train:runtime-reliability, priority:P0.
Suggested labels: tests, support.
Suggested owners: none.

Related context

• P0: Workbench fresh-Mac onboarding depends on unbundled Python and manual private-network setup #662 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• P0: add typed Mac onboarding prerequisites #664 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• P0: Mac & iPhone readiness can appear ready before end-to-end broker runtime control works #655 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.

Agent-start packet

Problem shape: P0: pin and verify secure-network installer metadata for pristine Macs - ## Problem The pristine-Mac guided-action draft can open Tailscale's official macOS download page, but Workbench does not yet own a pinned, verified installer candidate. That browser handoff is useful guidance, not the
Product fit: Product/market issue; check vision fit, customer value, and whether external precedent can reduce time-to-market.
Implementation wedge: Start with a bounded adapter/contract or dry-run packet before changing live runtime behavior.

Build / borrow / buy scan:

• Build: identify the smallest implementation wedge that proves the issue without broad rollout.
• Borrow: inspect same-repo prior art, repo memory, GitNexus context, and allowlisted cross-repo examples first.
• Buy/use: run capped external OSS/library/API/current-market research with citations, observed dates, and why each source matters.
• Library choice: compare maintenance, API fit, license, bundle/runtime cost, and integration proof.

Candidate sources:

• VISION.md / repo policy / repo-memory.md / GitNexus packet.
• Same-repo issues and PRs referenced by issue metadata.
• Allowlisted cross-repo GitHub examples with direct issue/PR/repo URLs.
• External OSS repositories or library/API docs with freshness dates.
• Current market/product examples, capped and cited, only when they change implementation direction.

Acceptance criteria:

• Preserve and execute the issue's stated acceptance criteria.
• Include source citations for any external OSS/library/current-market claims.
• Keep issue-enrichment comments sticky and idempotent.
• Keep labels, owners, reviewers, and roadmap fields suggestion-only.

Proof plan:

• Focused unit/fixture test for the changed planner behavior.
• Dry-run issue-enrichment evidence packet before live comment posting.
• Redaction check for issue body, citations, and generated markdown.
• Contract or degraded-mode proof before runtime promotion.
• Dependency/license/API-fit note before adding or relying on a package.

Known traps:

• Do not treat related links as proof by themselves; each source needs a reason why it matters.
• Do not scan old issue backlogs or exceed repo-level enrichment throttles.
• External research must stay capped, cited, fresh-dated, and redacted.
• Technical severity alone can miss product/UX regressions; include product-manager review framing.

Non-goals:

• Do not auto-apply labels, owners, reviewers, roadmap fields, or milestones.
• Do not bulk-enrich old backlog issues from this planner output.
• Do not claim external market or OSS research was performed unless cited sources are present.

Context-source taxonomy:

• [enabled] vision_repo_policy_memory_gitnexus: Use repo vision, policy, memory, and GitNexus first before external research.
• [enabled] same_repo_issues_prs: Issue metadata contains same-repo references.
• [enabled] allowlisted_cross_repo_github: Triggered by issue class; keep to configured allowlist and source caps.
• [enabled] external_oss_examples: Use for build/borrow/buy precedent with citations and observed dates.
• [enabled] library_api_docs: Use when implementation may depend on a module, SDK, API, or framework choice.
• [enabled] current_market_examples: Use for product/UX/market positioning issues with freshness dates.
• [enabled] internal_mcp_docs: Use internal docs/MCP context when available; missing context is degraded, not blocking.

Validation suggestions

• Confirm owner, acceptance criteria, and validation evidence before implementation.

Triage gaps

• Owner or reviewer signal not detected in issue body.

No labels, owners, reviewers, or roadmap fields were changed by this bot.