Ship and validate native Intel releases for the broad announcement

[lastobelus]

Outcome

Intel Mac users receive a native, provenance-backed Markover release only after the exact x64 artifact passes the dedicated physical Intel/Sonoma install, Gatekeeper, packaged-workflow, restoration, CLI, and rollback exercise. Apple Silicon releases do not wait for this work.

Acceptance criteria

• Release automation can build and publish the native Intel app and checksum without weakening the immutable-tag, protected-environment, exact-draft, provenance, or rollback controls.
• The exact x64 ZIP is natively built, hardened ad-hoc signed unless issue Sign, notarize, and add release provenance and rollback guidance #13 has activated Developer ID, checksummed, attested, and byte-verified before publication.
• Authenticated Safari on the dedicated physical 2019 Intel Mac running Sonoma downloads the exact draft artifacts; quarantine remains present.
• Gatekeeper behavior is observed honestly: hardened ad-hoc builds are rejected before the visible per-app override and are never described as Apple-verified or notarized.
• The shared packaged happy path covers launch, create/open, persistence before restart, restart/restoration, CLI open/get/edit, and reopen/edit against the installed x64 app.
• Version-pinned rollback reopens the preserved review successfully.
• Evidence records the tested version and commit, exact digests, model class, macOS version, native x86_64 state, Gatekeeper result, rollback target, and workflow/release links without serial numbers, usernames, or account details.
• Public compatibility and download guidance adds Intel support only after this evidence is accepted.

Scope boundaries

• Roadmap position: Broad announcement; this does not block downloadable Apple Silicon releases or the focused Apple Silicon preview.
• Reuse issue Authenticate the loopback review API #12 happy-path fixtures only; do not duplicate its adversarial authorization tests.
• Do not duplicate issue Guarantee bounded-loss autosave durability across crashes and restarts #39 bounded-loss or durability tests.
• Issue Sign, notarize, and add release provenance and rollback guidance #13 continues to own future Developer ID/notarization activation and the honest trust-language boundary.
• Existing immutable tags are never moved or reused.

Deferred checkpoint

The unpublished v0.1.2 attempt produced exact native arm64 and x64 artifacts in workflow run 31217557046, but publication stopped before the second release gate because clean Intel/Sonoma evidence could not be collected. That run is historical input, not clean-machine proof and not authorization to publish Intel artifacts.

[lastobelus]

Work intent

phase: completed
summary: "Completed the remote client host host-readiness tracer: exact current-main native x64 package, preflight, packaged smoke, sanitized evidence, and recoverable profile cleanup all passed without source changes"
touch-points:
  - "dedicated physical 2019 Intel Mac remote client host on Sonoma, connected through Tailscale with LastCode operational"
  - "a dedicated standalone clone outside ~/projects/markover, checked out at an exact current-main commit and using native x86_64 Node and macOS tooling; ~/projects/markover remains reserved for ordinary Markover development"
  - "native Markover packaging and Markover-darwin-x64.zip creation"
  - "x64 checksum generation and the existing hardened ad-hoc artifact preflight"
  - "the existing packaged happy-path smoke under remote client host’s current macOS account and sanitized toolchain/smoke evidence, run as an evidence-first tracer before adding build-host automation"
done-when:
  - "a clean current-main checkout on remote client host packages Markover-darwin-x64.zip with native x86_64 tooling"
  - "the generated checksum verifies and the existing hardened ad-hoc artifact preflight passes for x64"
  - "the existing packaged happy-path smoke passes against that exact archive"
  - "sanitized evidence records the exact commit, x86_64 architecture, macOS/toolchain versions, checksum, trust result, and smoke result"
  - "preflight proves the live Markover application-data directory was absent before the tracer; after the exact smoke process exits, only the tracer-created directory is moved to a uniquely named recoverable Trash location and the live path is verified absent"
excludes:
  - "release-workflow, release payload-contract, release-note, or publication changes"
  - "creating or moving a tag, assembling a GitHub draft, approving publication, or publishing a release"
  - "Safari download, quarantine-preservation, clean-machine Gatekeeper override, rollback, or public Intel-support claims"
  - "remote-client-to-canonical Markover review interoperability owned by LastCode thread 2ea00553-a8a2-46cc-a695-b8eba2a091f1"
  - "starting additional remote client host worker threads before this interview defines ownership and handoff boundaries"
  - "building or launching Markover from ~/projects/markover as part of the Intel-package tracer"
  - "a linked Git worktree that shares repository metadata or lifecycle with ~/projects/markover"
  - "a speculative bootstrap script, background build service, or general Intel build framework before the tracer proves a concrete need"
  - "Apple Silicon release selection and clean-machine evidence owned by #10 and #11"
  - "Developer ID and notarization activation owned by #13"
  - "adversarial authorization coverage owned by #12"
  - "bounded-loss durability coverage owned by #39"
  - "deleting, resetting, or moving any preexisting or concurrently modified Markover application data on remote client host"
blocked-by: []
may-block:
  - "a later #80 release-automation activation slice"
  - "#18 broad announcement operations"
branch: "t3code/setup-intel-builds (no tracked changes)"
authorized: true
evidence-comment: "https://github.com/lastobelus/markover/issues/80#issuecomment-5337011644"
worker-thread: "9b4f3fda-8c07-4c67-aa29-5b76dece7557"
validation:
  - "standalone clone pinned cleanly at 763f260277076c06551e5c288a05ddf060cc2aaa"
  - "npm ci passed under native x64 Node 22.13.0"
  - "npm run ci:local passed: 787/787 tests plus built-app smoke"
  - "native x64 hardened ad-hoc package and exact ZIP/checksum preflight passed"
  - "ZIP SHA-256 e4b24759383abb5429f4f80614cf14cd531db56a35df0329371979f897f1063c"
  - "packaged happy-path smoke passed with review mko_bc1e1adb"
  - "coordinator independently verified digest, sanitized JSON, clean checkout, absent live profile/process, and recoverable Trash copy"
  - "no repository source, tag, release, workflow, LastCode, Tailscale, credential, or visible UI change"
execution:
  - "canonical host thread retains the #80 claim, repository decisions, source fixes, GitHub evidence, and PR lifecycle"
  - "remote client host LastCode worker 9b4f3fda-8c07-4c67-aa29-5b76dece7557 owns host inventory, standalone clone setup, permitted prerequisites, and the native tracer"
  - "the remote client host worker reports blockers without source edits; canonical host patches and pushes, then remote client host retests the exact commit"
  - "LastCode thread 2ea00553-a8a2-46cc-a695-b8eba2a091f1 remains separate and owns remote-client-to-canonical Markover review interoperability"
  - "no additional remote client host workers start without a newly bounded independent need"

This run takes over the prior blocked claim with the user's confirmation. The former dedicated-host blocker is resolved by remote client host's availability. The user confirmed the initial host-readiness tracer boundary; #80 remains open afterward for dependent delivery and acceptance slices.

Interview update: LastCode is operational on remote client host, but Markover has not yet been built or run there. The user requires the Intel package build checkout to remain isolated from ~/projects/markover, which is reserved for ordinary Markover work.

Interview update: the user selected a standalone clone for the Intel build lane rather than a linked worktree.

Interview update: the user selected an evidence-first manual tracer using existing repository commands and native Node 22.13.0. Sanitized commands and results belong on #80; only a demonstrated blocker may justify the smallest repository change in this slice.

Interview update: the user authorized the local packaged smoke under remote client host’s current account but requires the live profile to be reset afterward. Cleanup is fail-closed and recoverable: proceed only from proven absence, retain sanitized evidence outside Application Support, quit the exact smoke process, move only the tracer-created Markover directory to a unique Trash target, and verify the live path is absent.

Authorization update: the user confirmed the complete interviewed boundary and authorized implementation with the recorded canonical-host/remote-client execution split.

Execution handoff: the user launched remote client host LastCode worker thread 9b4f3fda-8c07-4c67-aa29-5b76dece7557 with the approved tracer prompt.

Completion update: the local remote client host host-readiness tracer passed and its accepted, independently verified evidence is recorded in the linked #80 comment. This claim slice is complete; #80 remains open and In Progress for later release-automation and authoritative physical acceptance slices.