Ship and validate native Intel releases for the broad announcement

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.

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.

Native Intel host tracer evidence — local setup proof only

The dedicated physical Intel/Sonoma host can build and exercise a native x64 Markover package from a clean, exact origin/main checkout.

Source commit: 763f260277076c06551e5c288a05ddf060cc2aaa
Package version: 0.1.3
Host: 2019 Intel MacBook Pro (MacBookPro15,3), macOS Sonoma 14.8.9, native x86_64, Rosetta translation false
Toolchain: Xcode 16.2 / CLT 16.2, native x64 Node 22.13.0, npm 10.9.2, Git 2.55.0, GNU Bash 5.3.15
Checkout: standalone clone, detached at the exact commit, with clean tracked files before and after
Dependencies: npm ci passed; 243 packages and zero reported vulnerabilities
Deterministic gate: npm run ci:local passed with 787/787 tests plus built-app smoke. An initial run selected Apple Bash 3.2 because of PATH ordering and failed 14 environment-sensitive tests; correcting PATH to the already-installed Bash 5.3.15 made the complete unchanged gate pass. No source fix was required.
Packaging: npm run package:mac passed with Electron 43.2.0; the main executable, frameworks, and helpers were verified native x86_64
Exact artifact: Markover-darwin-x64.zip
SHA-256: e4b24759383abb5429f4f80614cf14cd531db56a35df0329371979f897f1063c
Artifact preflight: passed for architecture x64, hardened ad-hoc trust; not Apple-verified or notarized; Gatekeeper rejected as expected
Packaged smoke: passed against the exact ZIP/checksum with evidence kind local; review mko_bc1e1adb; launch, create/open, persistence before restart, restart/restoration, CLI get, CLI edit/reopen, and reopened on-disk state all passed
Profile cleanup: live Markover application data was absent before the tracer; the smoke-created directory was proven by birth time and exact review contents, moved recoverably to Trash with inode continuity, and the live path was absent afterward; no Markover process or service remained
Worker thread: 9b4f3fda-8c07-4c67-aa29-5b76dece7557

Independent coordinator verification recomputed the ZIP digest, matched it to the sidecar and evidence JSON, read the sanitized evidence fields, confirmed the clean pinned checkout, and confirmed the final process/profile/Trash state.

This completes only the scoped local host-readiness tracer. It is not clean-machine evidence and does not satisfy the later Safari/quarantine, visible Gatekeeper override, rollback, release-workflow activation, publication, or public Intel-support acceptance criteria. No release, tag, draft, workflow, repository source, LastCode, Tailscale, credential, or visible-UI change occurred.

Work intent

phase: completed
summary: "Merged PR #184 as 3b7dfb0: native x64 release activation and finite first-Intel draft qualification pass local, GitHub, review, and isolated native Intel gates"
touch-points:
  - ".github/workflows/release.yml"
  - "scripts/release-operations.ts"
  - "packages/cli/src/bootstrap.ts"
  - "test/release-operations.test.ts"
  - "test/release.test.ts"
  - "test/bootstrap.test.ts"
  - "docs/developer/releasing.md"
  - "generated release-note trust, provenance, architecture, and rollback language"
  - "separate exact-commit validation in the isolated /Users/lasto/builds/markover-intel clone"
done-when:
  - "the tag-triggered native job runs independently on macos-15 arm64 and macos-15-intel x64, packages and smokes each exact native ZIP, and retains collision-free payload, toolchain, and smoke artifacts"
  - "staging and publication require exactly both native ZIPs, both checksum sidecars, and the portable CLI plus sidecar; both native ZIPs are attested and byte-verified without weakening immutable-tag, protected-environment, exact-draft, provenance, or rollback revalidation controls"
  - "the release payload/type/toolchain contract reports arm64, x64, and portable entries, and the portable CLI selects and validates the matching arm64 or x64 release asset"
  - "generated notes list both native payloads and resolved build contexts, preserve hardened ad-hoc/not-Apple-verified/not-notarized language, scope the current rollback command to Apple Silicon, and keep first-Intel publication gated until #80 records a real validated x64 rollback target"
  - "targeted release/bootstrap tests and the complete local CI gate pass"
  - "the pushed candidate commit is independently validated from the isolated Intel clone with native x64 install, CI, packaging, checksum/preflight, packaged smoke evidence, and recoverable cleanup"
excludes:
  - "Developer ID signing or notarization activation owned by #13"
  - "creating or moving a tag, approving publication, or publishing a release"
  - "physical Intel clean-machine Safari, quarantine, visible Gatekeeper override, rollback execution, or final public Intel-support acceptance"
  - "coordinator mutation of /Users/lasto/builds/markover-intel"
  - "Apple Silicon release selection or validation regressions"
  - "public compatibility/download-guide changes before clean Intel evidence is accepted"
blocked-by: []
may-block:
  - "a later #80 physical Intel release-acceptance slice"
  - "#18 broad announcement operations"
branch: "t3code/activate-native-x64-release"
base: "97098cb1e59161e1a3bb31e2403365fa3442648b"
candidate: "6983f08ec0fdc343d2fd774527b486d9ca5d9db8"
pull-request: "https://github.com/lastobelus/markover/pull/184"
merge-commit: "3b7dfb0edaa9d47bb7121e7dd2f2ae2b64691313"
authorized: true
validation:
  - "focused release/bootstrap suites passed: 28/28"
  - "exact head 6983f08 npm run ci:local passed locally and in the isolated Intel clone: lint, typecheck, notices, 787/787 tests, and bundled Electron smoke"
  - "GitHub CI passed and exact-head automated review found no major issues; all review threads resolved"
  - "separate physical Intel/Sonoma validation used checksum-verified official temporary native x64 Node 22.13.0 and left no persistent install"
  - "final detached HEAD/source/index clean; all 15 packaged Mach-O files independently verified thin x86_64"
  - "x64 v0.1.3 hardened ad-hoc preflight passed with expected Gatekeeper rejection; not Apple-verified and not notarized"
  - "exact x64 ZIP SHA-256 34d67cee3bff8750cef58aa8e08c6567da9808b2636c4235e08dcaf70d7c500d"
  - "exact-bytes local packaged smoke passed with review mko_aca0acf5 and 0600 digest/commit-bound evidence"
  - "smoke-created profile and validation-owned temporary state moved recoverably to unique Trash paths; final live profile, Markover processes/services, and temporary toolchain source absent"
  - "evidenceKind local and cleanMachine false; no Safari/quarantine, visible override, rollback, publication, notarization, Apple verification, or public-support claim"
  - "squash merge 3b7dfb0 is live on origin/main and tree-equivalent to candidate 6983f08 across every claimed touchpoint"
  - "post-merge Markover done could not cold-start because canonical-descriptor-missing; no review was created in this thread and the verified GitHub merge is unaffected"

The completed remote client host tracer and its evidence comment remain inputs, not publication authorization. This slice preserves issue #13's signing/notarization boundary.

Interview decisions: use the current supported GitHub native matrix labels macos-15 and macos-15-intel; restore x64 across the exact staged/published payload, attestation, toolchain, and portable bootstrap contracts; keep both architectures hardened ad-hoc; and make the generated first-Intel note truthful about the missing published x64 rollback target. The user confirmed this boundary and authorized implementation.

Review round 2: narrow the runbook so this slice qualifies the first Intel draft without claiming the unavailable x64 rollback/publication acceptance; a later #80 slice owns that finite gate. Review round 1: fixed the supported canonical-runbook regression by documenting the six-asset dual-native workflow and required Intel gate. Deferred dynamic discovery of a future x64 rollback release to the later #80 rollback-acceptance slice: this first-Intel slice has no valid published x64 target and explicitly keeps publication gated, so adding a GitHub API compatibility path is outside its finite boundary.

Completion: PR #184 was squash-merged as 3b7dfb0 and verified live on origin/main with tree-equivalent claimed touchpoints. This slice is complete; issue #80 remains open for the separately bounded clean-machine, Gatekeeper override, x64 rollback, publication, and public-support acceptance work.

Activate native Intel release payloads (#184)

Work intent

phase: completed
summary: "Merged PR #186 as af3bc58: v0.1.4 version agreement is live on main with local CI, GitHub CI, and exact-head automated review green"
touch-points:
  - "package.json"
  - "package-lock.json"
  - "packages/cli/package.json"
  - "PR #186 review, CI, and merge lifecycle"
done-when:
  - "the root application, lockfile root package, and portable CLI versions agree on 0.1.4"
  - "the version agreement lands on protected main with required CI passing"
  - "the exact PR head receives completed automated review with every finding dispositioned"
excludes:
  - "creating or moving the immutable v0.1.4 tag"
  - "approving either protected release-environment gate"
  - "assembling, qualifying, or publishing a release draft"
  - "physical Intel/Sonoma Safari, quarantine, Gatekeeper, packaged-smoke, or rollback operations"
  - "public Intel compatibility or download-guidance claims"
blocked-by: []
may-block:
  - "the next #80 v0.1.4 draft-qualification slice"
  - "#18 broad-announcement operations"
branch: "t3code/work-on-issue-80-slice"
candidate: "v0.1.4"
candidate-commit: "4c8e87301a78714cd640e180b6c7b0d427dc73ff"
pull-request: "https://github.com/lastobelus/markover/pull/186"
merge-commit: "af3bc585e8ffee6da761828e0cb9e89247cfce8f"
authorized: true
validation:
  - "version agreement 0.1.4 passed"
  - "git diff --check passed"
  - "npm run ci:local passed: build, lint, typecheck, notices, 787/787 tests, and Electron smoke on native x64 Sonoma"
  - "GitHub Verify (Node 24) passed on exact head 4c8e873"
  - "automated exact-head review completed with thumbs-up and no findings; zero review rounds required changes"
  - "GitHub reported clean mergeability and zero unresolved review threads"
  - "squash merge af3bc58 is live on origin/main and tree-equivalent across all three touched files"
  - "post-merge Markover done could not cold-start because canonical-descriptor-missing; the verified GitHub merge is unaffected"
prepared-follow-on:
  - "v0.1.4 remains the nominated immutable tag for the first dual-architecture draft"
  - "this thread runs on remote-client-host.local: MacBookPro15,3, native x86_64, macOS 14.8.9"
  - "Safari was verified authenticated to GitHub and focus stealing is authorized"
  - "the clean standalone /Users/lasto/builds/markover-intel checkout remains the exact-tag validation lane"
  - "the live Markover profile was absent before work; the future clean smoke profile and review are to remain live for rollback"

Boundary correction — narrow: this claim initially combined the reversible version PR with later irreversible release and host operations. The one-PR/one-slice rule and the user’s explicit instruction to stop before immutable tag creation end this claim at the merged source-preparation checkpoint; the recorded host, Safari, isolation, and profile-retention decisions remain prepared context for the next separately claimed #80 operational slice.

Completion: PR #186 was squash-merged as af3bc58. Issue #80 remains open and tracked in the Broad announcement milestone.

Work intent

phase: completed
summary: "Create and qualify the first dual-architecture v0.1.4 draft on remote client host, stopping at the second protected gate with publication blocked"
touch-points:
  - "exact merged origin/main commit af3bc585e8ffee6da761828e0cb9e89247cfce8f"
  - "immutable v0.1.4 tag creation and tag-triggered GitHub release workflow"
  - "first protected release-environment approval and exact six-asset draft assembly"
  - "GitHub draft metadata, assets, checksums, attestations, toolchain reports, and automated native smoke evidence"
  - "authenticated Safari on remote client host and dedicated quarantined x64 installation"
  - "visible hardened ad-hoc Gatekeeper rejection and per-app Open Anyway override"
  - "isolated /Users/lasto/builds/markover-intel exact-tag checkout and clean Intel packaged smoke"
  - "sanitized issue #80 draft-qualification evidence"
done-when:
  - "preflight proves GitHub release safeguards ready, Developer ID intentionally blocked, v0.1.4 absent, af3bc58 is current protected main with successful required CI, and all version fields agree on 0.1.4"
  - "one immutable v0.1.4 tag points exactly to af3bc58 and starts one authoritative release workflow"
  - "the oldest eligible run receives only the first protected-environment approval and creates one complete exact six-asset draft"
  - "draft metadata, all payload bytes and digests, attestations, build contexts, automated arm64/x64 packaged smoke, and honest hardened-ad-hoc trust and rollback-blocked notes verify"
  - "authenticated Safari downloads the exact draft artifacts on native Intel/Sonoma with quarantine preserved"
  - "Gatekeeper rejection is observed before the visible per-app override, then the separately installed app opens"
  - "the exact-tag isolated checkout passes clean-intel-sonoma packaged smoke against the installed x64 app through saved-state restart, CLI get, and edit/reopen"
  - "one sanitized #80 evidence comment records the exact candidate, artifacts, host, trust result, smoke review, rollback pending, and overall result draft qualified; publication blocked"
  - "the smoke-created test-only live profile and exact review remain present for the later rollback slice, with no Markover process left running"
excludes:
  - "approving publish-release or publishing v0.1.4"
  - "executing or claiming x64 rollback before a real published x64 target exists"
  - "editing draft assets or metadata after authoritative staging"
  - "public Intel compatibility or download-guidance claims"
  - "Developer ID signing, Apple verification, or notarization owned by #13"
  - "adversarial authorization coverage owned by #12"
  - "bounded-loss durability coverage owned by #39"
  - "building or validating from ~/projects/markover or this linked LastCode worktree"
  - "cleaning, moving, or deleting the smoke-created live profile before later rollback disposition"
blocked-by: []
may-block:
  - "a later #80 x64 rollback and publication-acceptance slice"
  - "#18 broad-announcement operations"
branch: "operations only; exact candidate origin/main af3bc585e8ffee6da761828e0cb9e89247cfce8f"
candidate: "v0.1.4"
tag-object: "ad281025f4c765c44b217d642ebf25f0a6d526e7"
workflow-run: "https://github.com/lastobelus/markover/actions/runs/32225200993"
host: "remote-client-host.local; MacBookPro15,3; x86_64; macOS 14.8.9"
authorized: true

Prepared inputs from completed PR #186: v0.1.4 version agreement is live on main; Safari authentication, focus authorization, standalone-clone isolation, and future profile retention were already confirmed. This claim owns only first-draft qualification and stops before the publication gate.

Authorization update: the user instructed this thread to continue with the next separately claimed slice. The prepared v0.1.4 candidate, exact merged commit, remote client host execution, Safari/focus authorization, isolated validation lane, profile retention, evidence shape, and stop-before-publication boundary make the zero-question implementation path complete.

Execution update: annotated immutable tag v0.1.4 was created with subject Markover v0.1.4 and pushed once. Remote peeling resolves exactly to af3bc58; authoritative workflow run 32225200993 started from that exact head.

Execution update: prerequisite, CLI, macos-15 arm64, and macos-15-intel x64 jobs passed. The sole pending release environment deployment for run 32225200993 was approved with a staging-only comment; stage-release started and no publication approval was issued.

Execution update: draft release 372851837 was independently verified as unpublished, exact-tagged, and complete with six exact assets; primary digests are arm64 80fa75ee73a860264b290bae8008d2ba6c32722c7ff18af4d5cb58fcb3495e19, x64 2713a9203fcdc7c7ea0c2886cbfb4e94d818890a69ff46851a81cd694d003566, and CLI d4960f9f72f3e33e7ea833527a4de22cc30d23ce330ee3cf9a07bfa8597169c6. Checksums, GitHub attestations, build contexts, draft notes, and automated arm64/x64 packaged smoke all verified.

Completion update: authenticated Safari download and quarantine preservation were verified on physical native Intel/Sonoma; Gatekeeper visibly rejected the hardened ad-hoc app before the per-app Open Anyway override. Exact-tag physical packaged smoke passed with evidence review mko_6b7879f0, all finite happy-path steps true, and no Markover process left; the qualification record is #80 (comment).

Boundary disposition: the first physical attempt hit the five-second save-and-quit retry dialog; defer that bounded-loss durability behavior to #39 under this slice exclusion. Its test-only review mko_8d62fcee remains preserved alongside the successful review; publication and x64 rollback remain unclaimed and blocked at the second release-environment approval.

First post-policy clean Intel evidence — v0.1.4

Source/tag: v0.1.4 annotated tag object ad281025f4c765c44b217d642ebf25f0a6d526e7, peeling exactly to protected-main commit af3bc585e8ffee6da761828e0cb9e89247cfce8f.
Draft/workflow: unchanged unpublished draft assembled by release run 32225200993; stage-release passed and publish-release remains waiting behind the unapproved second release environment gate.
Exact candidate payloads: arm64 80fa75ee73a860264b290bae8008d2ba6c32722c7ff18af4d5cb58fcb3495e19; x64 2713a9203fcdc7c7ea0c2886cbfb4e94d818890a69ff46851a81cd694d003566; CLI d4960f9f72f3e33e7ea833527a4de22cc30d23ce330ee3cf9a07bfa8597169c6.
Exact candidate sidecars: arm64 a43732ea6f1d2d8839860b851a01ed0060423ffbd34008aeac9572a381502635; x64 9c149f6bd6852a7fa0ba6df14d608fa2e370f944b61bdef39623a21b1d73cd82; CLI fa276406f1c581f9b2452ab29c3a4f4e51d3fcf291e3f19fc6ee8fb5d4b20745.
Independent candidate checks: all six draft assets still match their original GitHub digests; all three primary sidecars and build-provenance attestations verified for this repository, workflow, source commit, tag ref, and GitHub-hosted builders. Draft metadata and assets were not modified.
Automated native smoke: Intel job 95983609964 and Apple Silicon job 95983609998 passed the packaged happy path from the exact tag.
Clean host: physical 2019 Intel MacBook Pro class, macOS Sonoma 14.8.9, native x86_64, Rosetta translation false.
Candidate trust result: Safari-authenticated draft download preserved quarantine. Gatekeeper visibly rejected the hardened ad-hoc v0.1.4 app before the per-app Open Anyway override; Apple verification false; notarization false.
Physical candidate smoke: status passed, evidence kind clean-intel-sonoma, cleanMachine: true, source af3bc585e8ffee6da761828e0cb9e89247cfce8f, x64 digest 2713a9203fcdc7c7ea0c2886cbfb4e94d818890a69ff46851a81cd694d003566, preserved review mko_6b7879f0.
Covered candidate path: exact artifact verification; packaged launch; CLI open; saved-state confirmation; restart/restoration; CLI get; CLI edit/reopen; reopened-state disk confirmation; clean shutdown.
Rollback selection: every live published stable release was inspected. v0.1.3 is newer but arm64-only; v0.1.2 and v0.1.4 are drafts. v0.1.1 is therefore the newest published complete Intel target.
Rollback source/workflow: v0.1.1 annotated tag object 1d30c20eec862b3317d51bc82c0ba3ed6c72f596, peeling to commit 2760d01bd2ce1ba53973e7d34d7f295ecf75017a; release workflow 30780129789 passed for that exact commit.
Exact rollback payloads: x64 ZIP ccf6e1a3c7645f292f5d078fe97aa01dde088bc0fa0b767efec48705f0a91506; x64 sidecar 2e3fed0b5437d3e677f8082ce8ae7fbe8b1569482f18b68bf01f9c5229627cbf; CLI 7a3953febedb0c6dc070911897223e5c5a735a38c7eddbf8028b8b1806dc0530; CLI sidecar 9e3d7b2d28dbef5e49ba5adcb70151bb8ef1305d16f7f20b85f530dfbbc3777f. Downloaded bytes matched both sidecars and GitHub asset digests.
Rollback package inspection: version 0.1.1; all 15 Mach-O files are thin x86_64; the ad-hoc code signature verifies; Gatekeeper rejects it; minimum macOS is 12.0. This historical release predates hardened-runtime and GitHub-attestation policy and is not described as hardened, Apple-verified, notarized, or attested. Both candidate and rollback use portable markover-review version 1.
Profile backup: Markover was stopped before rollback. A recoverable complete-profile copy contained all 53 files and both review directories; relative-path SHA-256 manifests and recursive content comparison matched. The backup manifest digest is c8dca0268aeec4cc2667c67699145aa9be8f7c5a6da0a5e95490db98a11dfa6e.
Exact rollback command: npx --yes --package=https://github.com/lastobelus/markover/releases/download/v0.1.1/markover-cli.tgz markover edit mko_6b7879f0, run with fresh isolated npm and app caches.
Rollback result: passed. The first call reached v0.1.1's historical ten-second startup deadline while the exact app was still starting; its v1 service then became healthy, and one identical idempotent retry returned {"reviewId":"mko_6b7879f0","status":"editing"}. Deterministic v0.1.1 startup selected that newest preserved review. Both complete review directories remained byte-for-byte identical before and after reopen, and Markover stopped cleanly.
Automation correction: PR #189, exact reviewed head 02c9da152052089e1c1d892fb5eee065af569730, merged as a318f7eacb50bacd86af3595f057a6ff9348ed5d. Future staging selects arm64 and x64 rollback targets independently, freezes fingerprints over each target's app, sidecar, CLI, and CLI sidecar, emits architecture-appropriate version-pinned commands, and revalidates the live tags and fingerprints immediately before publication. CI passed; exact-head automated review found no major issues; the one first-round note-prose finding was fixed and resolved.
Excluded: adversarial authorization (Authenticate the loopback review API #12), bounded-loss durability (Guarantee bounded-loss autosave durability across crashes and restarts #39), Developer ID/Apple verification/notarization (Sign, notarize, and add release provenance and rollback guidance #13), and public Intel compatibility/download claims.
Overall: rollback accepted; publication still blocked. The immutable v0.1.4 workflow and draft remain unchanged and unpublished, and its publication approval remains untouched. Because that tagged workflow predates the merged architecture-aware fix, a later separately authorized slice must nominate a new version; this slice created no additional tag and issued no publication approval.

Boundary disposition: the first physical v0.1.4 smoke attempt's five-second save-and-quit retry dialog remains deferred to #39. The v0.1.1 first-start timeout is narrowly documented as one observable idempotent recovery retry; a second failure rejects rollback rather than extending the retry surface.

Work intent

phase: completed
summary: "Rollback acceptance completed: v0.1.1 was proven as the newest published Intel recovery release, the preserved review reopened on remote client host, and PR #189 merged the smallest automation/runbook correction"
touch-points:
  - ".github/workflows/release.yml"
  - "scripts/release-operations.ts and scripts/release-preflight.ts"
  - "test/release-operations.test.ts and test/release.test.ts"
  - "docs/developer/releasing.md"
  - "complete Markover profile backup and preserved reviews on remote client host"
  - "sanitized rollback evidence on issue #80"
done-when:
  - "live GitHub release state determines v0.1.1 is the newest published native Intel recovery target"
  - "the complete remote client host profile is backed up with matching integrity manifests and all reviews preserved"
  - "the exact version-pinned v0.1.1 rollback reopens mko_6b7879f0 on native x86_64 Sonoma"
  - "automation selects/fingerprints/revalidates architecture-specific targets and emits pinned commands"
  - "PR #189 passes exact-head review and CI, merges, and the runbook matches the verified operation"
  - "sanitized evidence is recorded on #80"
  - "v0.1.4 remains unchanged and unpublished, with no new tag or publication approval"
excludes:
  - "creating or moving any tag"
  - "approving publication or publishing v0.1.4"
  - "editing staged v0.1.4 draft assets or metadata"
  - "deleting or moving preserved reviews"
  - "public Intel compatibility or download-guidance claims"
  - "Developer ID, notarization, authorization, or bounded-loss durability work owned elsewhere"
blocked-by: []
may-block:
  - "the later #80 publication-acceptance slice"
  - "#18 broad-announcement operations"
branch: "t3code/issue-80-rollback-acceptance"
pull-request: "https://github.com/lastobelus/markover/pull/189"
reviewed-head: "02c9da152052089e1c1d892fb5eee065af569730"
merge-commit: "a318f7eacb50bacd86af3595f057a6ff9348ed5d"
authorized: true
validation:
  - "npm run ci:local passed: lint, typecheck, notices, 796/796 tests, and Electron smoke"
  - "live selection returned arm64 v0.1.3 and x64 v0.1.1"
  - "complete 53-file profile backup and two-review manifests matched before rollback"
  - "exact version-pinned v0.1.1 edit mko_6b7879f0 succeeded after one documented idempotent startup retry"
  - "both preserved review directories remained byte-identical and the rollback app stopped cleanly"
  - "v0.1.4 draft/tag/assets and its unapproved publication gate remained unchanged"
evidence: "https://github.com/lastobelus/markover/issues/80#issuecomment-5339869398"

The slice is complete. #80 remains open and in progress because publication and public compatibility guidance were explicitly outside this slice. Post-merge Markover completion reporting could not run because this Mac has no canonical Markover descriptor; that did not affect the merged PR or the persisted issue evidence.

Work intent

phase: completed
summary: "Merged PR #192 as e04174c: v0.1.5 version agreement is live on protected main, with all release operations deliberately untouched"
touch-points:
  - "package.json application version"
  - "package-lock.json root package version"
  - "packages/cli/package.json portable CLI version"
  - "PR #192 review, CI, and merge lifecycle"
done-when:
  - "the root application, lockfile root package, and portable CLI versions agree on 0.1.5"
  - "the version-only change passes proportionate local validation"
  - "the exact PR head passes required GitHub CI and automated review with every finding dispositioned"
  - "the PR merges to protected main and the merged tree is verified"
  - "v0.1.4 remains unchanged and unpublished, its waiting publication deployment is untouched, and no tag or release gate is created, rejected, cancelled, or approved"
excludes:
  - "creating, moving, or deleting any tag"
  - "rejecting, cancelling, or approving the v0.1.4 workflow or protected deployment"
  - "assembling, changing, approving, or publishing any release draft"
  - "physical Intel/Sonoma qualification or rollback"
  - "public Intel compatibility or download-guidance changes"
  - "release automation or runbook changes beyond the already-merged PR #189"
blocked-by: []
may-block:
  - "the later #80 v0.1.5 draft-qualification slice"
  - "#18 broad-announcement operations"
branch: "t3code/issue-80-v0.1.5-version"
candidate: "v0.1.5"
pull-request: "https://github.com/lastobelus/markover/pull/192"
reviewed-head: "4b79c7a73938feceed2f167ef9550f037e9491c4"
merge-commit: "e04174c4b6a317530349993a8f6dd5bca5e13f6d"
authorized: true
validation:
  - "version agreement: package.json, package-lock.json, and packages/cli/package.json all report 0.1.5"
  - "git diff --check passed"
  - "npm run ci:local passed: build, lint, strict typecheck, notices, 823/823 tests, and Electron smoke at 0.1.5"
  - "required Verify (Node 24) GitHub CI passed on exact head"
  - "automated exact-head review completed with thumbs-up, no findings, and zero unresolved threads"
  - "squash merge e04174c is live on origin/main and tree-equivalent across all three claimed files"
  - "post-merge Markover done succeeded with zero matching reviews"
  - "v0.1.4 remains the unchanged unpublished af3bc58 draft and run 32225200993 remains waiting at publish-release"
  - "no v0.1.5 tag or release exists"

This version-preparation slice is complete. #80 remains open and In Progress for the separately bounded v0.1.5 tag, draft qualification, physical Intel acceptance, publication decision, and post-publication guidance.

Work intent

phase: completed
summary: "Closed v0.1.5 as a terminal failed staging attempt: immutable candidate jobs passed, staging failed before draft creation, publication was skipped, and PR #193 repaired the defect for a strictly newer candidate"
touch-points:
  - "unchanged unpublished v0.1.4 draft and terminal workflow run 32225200993"
  - "exact protected-main v0.1.5 candidate e04174c4b6a317530349993a8f6dd5bca5e13f6d"
  - "immutable annotated v0.1.5 tag object 68d9ebf764fe7c3d863fb35477319419ba1fb2b5"
  - "v0.1.5 Release workflow run 32317811360"
  - "first protected release-environment staging approval"
  - "repair PR #193 merged as b43f08d81edb9255b0c3022425ff032407c1d031"
done-when:
  - "the v0.1.4 waiting publication deployment is explicitly rejected as superseded while its unchanged draft, tag, metadata, and six assets remain preserved"
  - "v0.1.5 preflight, exact tag, candidate, CLI, arm64, x64, and automated smoke jobs pass"
  - "the deterministic staging failure is diagnosed and recorded without a v0.1.5 GitHub release or publication attempt"
  - "the smallest automation repair passes review and CI, merges to main, and the runbook requires a strictly newer candidate"
excludes:
  - "approving or publishing any release"
  - "changing, deleting, rerunning, or replacing preserved v0.1.4 or v0.1.5 tags, drafts, assets, reviews, workflow attempts, or profile backups"
  - "claiming or implying that v0.1.5 produced a draft"
  - "physical Intel acceptance, rollback execution, and public guidance"
  - "creating v0.1.6 or performing its version, tag, staging, or publication operations inside this claim"
blocked-by: []
may-block:
  - "the later #80 v0.1.6 version and staging claims"
  - "the later #80 physical acceptance and publication-decision slice"
  - "#18 broad-announcement operations"
branch: "operations only; immutable v0.1.5 tag object 68d9ebf764fe7c3d863fb35477319419ba1fb2b5"
candidate: "v0.1.5 terminal failed staging attempt"
authorized: true
validation:
  - "live v0.1.4 release 372851837 remains an unpublished draft with the same six asset names and digests recorded before this attempt"
  - "v0.1.4 run 32225200993 is terminal failure after the superseded publication deployment was rejected; no publication occurred"
  - "v0.1.5 tag object 68d9ebf764fe7c3d863fb35477319419ba1fb2b5 still peels exactly to e04174c4b6a317530349993a8f6dd5bca5e13f6d"
  - "v0.1.5 run 32317811360 passed candidate, CLI, arm64, x64, and packaged-smoke work"
  - "stage-release failed before draft creation after prepare-release rejected --rollback-arm64-tag=v0.1.3; the non-pipefail tee pipeline masked that upstream failure until release-notes.md was absent"
  - "live release inventory contains no v0.1.5 release; publish-release was skipped"
  - "PR #193 fixed digit-bearing rollback option parsing and added pipefail to the finite five release verification pipelines; exact required CI passed and merge b43f08d is live on origin/main"

Terminal disposition: this claim completed with a failed staging outcome, not its original successful-draft target. Immutable v0.1.5 produced no GitHub release; recovery requires a separately claimed, strictly newer candidate and no v0.1.5 rerun or tag mutation.

Work intent

phase: completed
summary: "Merged PR #193 as b43f08d: numeric rollback flags now parse and all five release verification pipelines fail closed"
touch-points:
  - "scripts/release-preflight.ts strict flag-name parser"
  - ".github/workflows/release.yml finite five pipe-to-tee verification pipelines across staging and publication"
  - "test/release.test.ts focused release CLI/workflow regressions"
  - "docs/developer/releasing.md failed v0.1.5 checkpoint and recovery boundary"
  - "PR #193 review, CI, and merge lifecycle"
done-when:
  - "strict release CLI parsing accepts declared option names containing digits while continuing to reject malformed or unknown options"
  - "all five release verification pipelines propagate upstream failures before later staging or publication steps"
  - "focused regressions prove the numeric flag and finite pipeline requirements"
  - "the runbook records v0.1.5 as an immutable failed staging attempt and requires a strictly newer repaired candidate"
  - "full local CI, required GitHub CI, exact-head automated review, and protected-main merge pass"
excludes:
  - "changing the immutable v0.1.5 tag or rerunning its broken tagged workflow"
  - "version bumping to 0.1.6 or creating another tag"
  - "creating, changing, approving, or publishing any release draft"
  - "physical Intel qualification, rollback execution, or public guidance"
  - "additional parser refactoring, compatibility paths, retry machinery, or shell hardening outside the finite release verification pipelines"
blocked-by: []
may-block:
  - "the later #80 v0.1.6 version and draft slice"
  - "the paused #80 v0.1.5 operational claim"
  - "#18 broad-announcement operations"
branch: "t3code/issue-80-release-flag-repair"
pull-request: "https://github.com/lastobelus/markover/pull/193"
reviewed-head: "5b21785fb049ac6d5e2a6fb1c3f0315942124daf"
merge-commit: "b43f08d81edb9255b0c3022425ff032407c1d031"
authorized: true
validation:
  - "focused release suites passed: 20/20"
  - "git diff --check passed"
  - "npm run ci:local passed: build, lint, strict typecheck, notices, 824/824 tests, and Electron smoke"
  - "required GitHub CI passed on retry after an unrelated concurrent-order assertion transient"
  - "automated exact-head review completed with thumbs-up, no findings, and zero unresolved threads"
  - "squash merge b43f08d is live on origin/main and tree-equivalent across every claimed file"
  - "post-merge Markover done succeeded with zero matching reviews"

Fix: numeric rollback options are supported staging inputs, and the five current release verification pipelines are a finite completion list; the merged correction restores fail-closed staging/publication without retries or compatibility machinery. Immutable v0.1.5 remains failed before draft creation, so the next candidate must use a separately authorized strictly greater version.

Work intent

phase: completed
summary: "Merged PR #194 as fc43f8e: the version-only v0.1.6 checkpoint is live on protected main"
touch-points:
  - "package.json application version"
  - "package-lock.json root package version"
  - "packages/cli/package.json portable CLI version"
  - "PR #194 review, CI, and merge lifecycle"
done-when:
  - "only the intended version fields in package.json, package-lock.json, and packages/cli/package.json change from 0.1.5 to 0.1.6"
  - "the complete relevant local validation passes"
  - "the draft PR is made ready and its exact head passes required GitHub CI and completed automated review with every finding dispositioned"
  - "the PR merges to protected main and the exact merged tree is verified"
  - "the Markover pending-review soft gate reports every pending review without resolving or deleting any of them"
excludes:
  - "creating, moving, deleting, or pushing any tag"
  - "starting, approving, rerunning, cancelling, or publishing any release workflow"
  - "assembling, editing, approving, or publishing any release draft"
  - "changing release automation, the runbook, or files outside the three version manifests"
  - "changing or deleting v0.1.4 or v0.1.5 tags, drafts, assets, attempts, reviews, or the preserved Markover profile backup"
  - "resolving or deleting mko_6b7879f0 or any other Markover review"
  - "physical Intel/Sonoma QA, Safari, Markover UI launch/focus, rollback execution, or public guidance"
blocked-by: []
may-block:
  - "the separately claimed #80 v0.1.6 staging operation"
  - "the later #80 physical acceptance and publication-decision slice"
  - "#18 broad-announcement operations"
branch: "t3code/continue-issue-80"
candidate: "v0.1.6 version checkpoint"
pull-request: "https://github.com/lastobelus/markover/pull/194"
reviewed-head: "aae47ed3f691ec7c2e2da4d6f21201ed3afb5e25"
merge-commit: "fc43f8e09e15de552bfd1bd90cf679ed1072e7b6"
authorized: true
validation:
  - "npm ci passed with zero reported vulnerabilities"
  - "git diff --check and exact three-file scope assertions passed"
  - "npm run ci:local passed: build, lint, strict typecheck, notices, 824/824 tests, and Electron smoke at 0.1.6"
  - "required Verify (Node 24) passed on the unchanged exact head after one retry of the known unrelated concurrent digest ordering assertion"
  - "automated exact-head review completed with thumbs-up, no findings, and zero unresolved threads"
  - "squash merge fc43f8e is live on origin/main and the merged diff contains only the four intended version replacements"
  - "all four intended merged version fields report 0.1.6"
  - "pre-merge Markover pending returned zero reviews for this exact thread; post-merge done returned zero matching PR reviews"
  - "mko_6b7879f0 and mko_8d62fcee hashes remained unchanged"

This version checkpoint slice is complete. Tagging and staging are owned by a new operational claim and remain conditional on the exact merged-main pre-tag checks.

Work intent

phase: completed
summary: "Staged and independently verified the complete unpublished v0.1.6 draft; publication remains waiting at the unapproved second gate"
touch-points:
  - "exact protected-main commit fc43f8e09e15de552bfd1bd90cf679ed1072e7b6"
  - "Verify (Node 24) on the exact merged-main commit"
  - "GitHub release readiness and expected intentional Developer ID blocked readiness"
  - "live stable releases and architecture-specific rollback selection"
  - "one annotated v0.1.6 tag with subject Markover v0.1.6"
  - "one authoritative v0.1.6 Release workflow run"
  - "the first release-environment gate for staging only"
  - "unpublished v0.1.6 draft metadata, notes, six assets, attestations, digests, toolchains, and smoke evidence"
  - "sanitized operational evidence on issue #80"
done-when:
  - "all intended merged version fields are 0.1.6 and the exact merged-main Node 24 check is green"
  - "GitHub release readiness is ready and Developer ID readiness returns the expected intentional blocked result"
  - "no local or remote v0.1.6 tag and no v0.1.6 release exists before tagging; v0.1.6 is strictly newer than v0.1.5"
  - "live release preflight independently selects the newest safe published rollback target for arm64 and x64"
  - "one annotated v0.1.6 tag with subject Markover v0.1.6 is created on and explicitly pushed from the exact merged-main commit"
  - "one authoritative Release workflow run is selected and its candidate, CLI, arm64, and x64 jobs complete successfully"
  - "only the first release-environment gate is approved"
  - "one unpublished v0.1.6 draft is staged with exactly the expected six verified assets, correct attestations, digests, toolchains, smoke evidence, release notes, and architecture-specific rollback targets"
  - "sanitized evidence is recorded on #80 and the publish-release job remains waiting for approval"
excludes:
  - "approving the publication gate or publishing v0.1.4 or v0.1.6"
  - "creating another version or tag after v0.1.6"
  - "moving, deleting, mutating, replacing, or rerunning any immutable tag or failed tagged workflow"
  - "changing the preserved v0.1.4 draft, v0.1.5 failed attempt, reviews, or Markover profile backup"
  - "resolving or deleting mko_6b7879f0 or any other review"
  - "launching or focusing Markover or Safari for physical Intel QA"
  - "physical Intel acceptance, rollback execution, public compatibility guidance, or announcement completion"
  - "source changes inside this operational claim; a deterministic small in-scope automation defect requires a separate repair claim and PR, then stops further version/tag operations"
blocked-by:
  - "exact merged-main Verify (Node 24) and finite pre-tag readiness checks"
may-block:
  - "the later #80 physical acceptance and publication-decision slice"
  - "#18 broad-announcement operations"
branch: "operations only; exact candidate commit fc43f8e09e15de552bfd1bd90cf679ed1072e7b6"
candidate: "v0.1.6 staging"
tag-object: "8bfe6f46da7a4de553ed518f2a044735470976e2"
workflow-run: "https://github.com/lastobelus/markover/actions/runs/32320752810"
draft: "https://github.com/lastobelus/markover/releases/tag/untagged-5f1509082df66682d9f5"
evidence: "https://github.com/lastobelus/markover/issues/80#issuecomment-5350099608"
authorized: true
validation:
  - "version checkpoint PR #194 merged as fc43f8e with its exact head reviewed and CI-green"
  - "origin/main and the four intended version fields were verified immediately after merge"
  - "preserved review hashes remained unchanged"
  - "exact merged-main CI run 32320468996 passed Verify (Node 24) and bundled smoke"
  - "GitHub release readiness reported ready; Developer ID readiness reported the expected intentional blocked result"
  - "v0.1.6 version/tag/release absence and strict ordering over v0.1.5 passed immediately before tagging"
  - "live rollback preflight selected Apple Silicon v0.1.3 and Intel v0.1.1"
  - "annotated tag object 8bfe6f46 has subject Markover v0.1.6 and peels exactly to fc43f8e"
  - "authoritative run 32320752810 passed candidate, CLI, arm64, x64, packaged-smoke, attestation, and stage-release jobs"
  - "only the first release gate was approved; publish-release job 96283310269 remains waiting at the unapproved second gate"
  - "draft 373438819 is unpublished, targets fc43f8e, and contains exactly the six expected assets"
  - "independent downloads verified all six GitHub digests, all three sidecars, producing-job byte identity, and all three build-provenance attestations"
  - "arm64 mko_9472427d and x64 mko_bff24c15 automated packaged-smoke evidence passed the complete retained happy path"
  - "retained notes exactly match the draft and record the source, run, digests, toolchains, trust boundary, and architecture-specific rollback targets"
  - "final pending-review soft gate returned zero entries; preserved reviews remained byte-unchanged"
  - "v0.1.4 remained unchanged and unpublished; v0.1.5 remained without a GitHub release"
  - "sanitized staging evidence was posted to issue #80"

The user authorizes the annotated tag and first staging approval only after every listed pre-tag check passes. Publication approval remains explicitly unauthorized.

v0.1.6 staging evidence — draft qualified; publication blocked

Prior attempt closed truthfully: immutable v0.1.5 remains a terminal failed staging attempt with no GitHub release. Its tag object is 68d9ebf764fe7c3d863fb35477319419ba1fb2b5, peeling to e04174c4b6a317530349993a8f6dd5bca5e13f6d; failed run 32317811360 was not rerun.
Version checkpoint: PR #194 merged the four intended version-field changes only as fc43f8e09e15de552bfd1bd90cf679ed1072e7b6. Local CI passed 824/824 tests plus Electron smoke; exact merged-main Verify (Node 24) passed.
Pre-tag readiness: all four intended fields reported 0.1.6; GitHub release readiness was ready; Developer ID readiness returned the expected intentional blocked ad-hoc state; v0.1.6 was strictly newer than v0.1.5; no local/remote v0.1.6 tag or release existed.
Rollback selection from live releases: Apple Silicon v0.1.3; Intel v0.1.1. The newer published v0.1.3 lacks x64, so selection was architecture-specific.
Immutable candidate: annotated tag object 8bfe6f46da7a4de553ed518f2a044735470976e2, subject “Markover v0.1.6”, peeling exactly to fc43f8e09e15de552bfd1bd90cf679ed1072e7b6.
Authoritative workflow: Release run 32320752810. Candidate, portable CLI, native arm64, native x64, and stage-release jobs passed. Only the first release environment gate was approved.
Draft: unchanged unpublished v0.1.6 draft, release ID 373438819, target fc43f8e09e15de552bfd1bd90cf679ed1072e7b6, exactly six assets.
Primary payload SHA-256: arm64 3f7c63f3585516b771e4bcf821717ba2d5ec873760e5abc7108302fecd1fa2e0; x64 d779565bd6103da7e26b68af305ab23a78c4287f9d4fae5ae3339bbd81b3baaa; CLI 3a7540446bdea04e5d5709220f7780fae00ea5bd3005509b9ef96072bf879957.
Sidecar asset SHA-256: arm64 8db62992364920a51d1b5088ab3c44b0dea1822a4ada069e11cc84173d728cc3; x64 19115c171b64f61787e22ac67dabac7d7d268110fef525a29756c86679868864; CLI 2e82f658d96355866d6a3d8f66c1b114be66517c8aab447c02e29fdf1f5faa5f.
Independent payload verification: downloaded asset digests matched GitHub, all three sidecars verified, and every draft asset was byte-identical to the retained producing-job artifact.
Attestations: GitHub build-provenance verification passed for both native ZIPs and the CLI with signer workflow .github/workflows/release.yml, source digest fc43f8e09e15de552bfd1bd90cf679ed1072e7b6, source ref refs/tags/v0.1.6, and self-hosted runners denied.
Resolved toolchains: arm64 GitHub Actions 1000003155 / macOS 15.7.7 arm64 / Node 22.13.0 / npm 10.9.2 / Electron 43.2.0 / Xcode 16.4; x64 GitHub Actions 1000003156 / macOS 15.7.7 x86_64 with the same tool versions; portable GitHub Actions 1000003154 / Linux 6.17.0-1022-azure.
Automated packaged smoke: arm64 review mko_9472427d and x64 review mko_bff24c15 both passed exact-artifact verification, launch, CLI open, saved state before restart, restart/restoration, CLI get, CLI edit/reopen, and reopened on-disk state. Both report hardened ad-hoc trust, expected Gatekeeper rejection, not Apple-verified, not notarized, and explicitly exclude adversarial authorization and bounded-loss durability.
Release notes: retained staging notes exactly matched the draft body and name the exact source, workflow, three payload digests, resolved toolchains, ad-hoc trust boundary, arm64 rollback v0.1.3, and Intel rollback v0.1.1.
Preservation: v0.1.4 remains the same unpublished six-asset draft; v0.1.5 still has no release; preserved reviews mko_6b7879f0 and mko_8d62fcee remained byte-unchanged. No review was resolved or deleted, and the final exact-thread pending-review soft gate returned no entries.
Publication boundary: publish-release job 96283310269 is waiting at the unapproved second release environment gate. No publication approval was issued.
Excluded and still pending: authenticated Safari download, physical Intel/Sonoma quarantine and visible Gatekeeper override, clean-machine smoke, rollback execution, public Intel guidance, and publication.

Overall: v0.1.6 draft staging is accepted as complete automation evidence; publication remains blocked and unapproved. Issue #80 stays open and the announcement-readiness project stays In Progress.

Work intent

phase: completed
summary: "Rejected the physical v0.1.6 qualification before smoke: visible Gatekeeper override was unavailable to automation and both protected review JSON files changed during the initial quarantined Finder launch"
touch-points:
  - "live GitHub v0.1.6 tag, release run 32320752810, unpublished six-asset draft 373438819, attestations, digests, and waiting publication job"
  - "dedicated physical 2019 Intel Mac on Sonoma, native x86_64 and no Rosetta translation"
  - "authenticated Safari downloads of the exact x64 ZIP, checksum sidecar, and portable CLI with quarantine preserved"
  - "visible hardened ad-hoc Gatekeeper rejection and per-app Open Anyway override"
  - "exact installed v0.1.6 app and shared packaged smoke with evidence-kind clean-intel-sonoma"
  - "complete Markover Application Support profile, preserved reviews, distinct pre-rollback backup, restart/restoration, CLI open/get/edit, and on-disk state"
  - "exact version-pinned v0.1.1 Intel rollback and reopen of mko_6b7879f0"
  - "sanitized physical qualification evidence on issue #80"
done-when:
  - "live state re-verifies candidate fc43f8e09e15de552bfd1bd90cf679ed1072e7b6, annotated tag object 8bfe6f46da7a4de553ed518f2a044735470976e2, authoritative workflow, unchanged unpublished six-asset draft, exact digests and attestations, waiting publish job, and rollback targets arm64 v0.1.3/x64 v0.1.1"
  - "authenticated Safari downloads the exact x64 ZIP, x64 sidecar, and portable CLI and the installed app retains quarantine"
  - "Gatekeeper rejects the hardened ad-hoc app before the visible per-app override; evidence says not Apple-verified and not notarized"
  - "shared packaged smoke passes against the exact installed v0.1.6 x64 app with evidence-kind clean-intel-sonoma, native x86_64, no Rosetta, exact artifact bytes, saved state before restart, restoration, CLI open/get/edit, and reopened on-disk state"
  - "every existing review including mko_6b7879f0 and mko_8d62fcee is preserved; a new distinct complete-profile backup is made before rollback without altering any existing backup"
  - "the exact version-pinned v0.1.1 CLI/app reopens mko_6b7879f0; only one identical retry is permitted for its documented historical first-start timeout and a second failure rejects rollback"
  - "all preserved review directories remain byte-identical and Markover stops cleanly"
  - "one sanitized #80 evidence comment records pass or the first terminal failure without usernames, serial numbers, credentials, or account-specific paths"
excludes:
  - "approving the publication gate or publishing any release"
  - "modifying the v0.1.4 or v0.1.6 draft, creating another version, or creating, moving, deleting, or mutating any tag"
  - "changing repository source or release automation"
  - "altering, replacing, or deleting any existing backup"
  - "deleting or resolving mko_6b7879f0, mko_8d62fcee, or any other review"
  - "blind reruns after qualification failure or creating v0.1.7"
  - "Developer ID signing, notarization, or Apple-verification claims owned by #13"
  - "adversarial authorization coverage owned by #12 and bounded-loss durability coverage owned by #39"
blocked-by: []
may-block:
  - "a later explicit #80 publication-decision slice"
  - "#18 broad-announcement operations"
branch: "t3code/qualify-intel-sonoma-v016 (operations only; no source changes)"
candidate: "fc43f8e09e15de552bfd1bd90cf679ed1072e7b6"
tag-object: "8bfe6f46da7a4de553ed518f2a044735470976e2"
workflow-run: "https://github.com/lastobelus/markover/actions/runs/32320752810"
draft: "https://github.com/lastobelus/markover/releases/tag/untagged-5f1509082df66682d9f5"
staging-evidence: "https://github.com/lastobelus/markover/issues/80#issuecomment-5350099608"
authorized: true
validation-policy:
  - "fail closed at the first discrepancy and record it once"
  - "the v0.1.1 historical first-start timeout permits exactly one identical retry; a second failure rejects rollback"
  - "sanitized evidence omits usernames, serial numbers, credentials, and account-specific paths"

The opening request fully fixes the acceptance evidence, preservation boundary, retry limit, and prohibited mutations, and explicitly authorizes this operations-only qualification slice.

Terminal disposition: live GitHub state, Safari downloads, exact bytes, quarantine, x64 architecture, and candidate attestations passed. The visible per-app override could not be exercised under the deferred-human-QA policy, and the initial quarantined Finder launch changed both protected review JSON byte digests; the run stopped without smoke, backup, rollback, publication, source/tag/draft changes, or review deletion/resolution. Evidence: #80 (comment)

Correction: the preservation-failure attribution above was overturned by follow-up forensics. The files changed during the deliberate shutdown of the already-running v0.1.4 app, before v0.1.6 was extracted; only review.updatedAt changed. See #80 (comment). The qualification remains rejected because the visible Gatekeeper override was not completed.

Physical Intel/Sonoma v0.1.6 qualification — rejected before smoke

Live GitHub state passed: annotated v0.1.6 tag object 8bfe6f46da7a4de553ed518f2a044735470976e2 peels exactly to fc43f8e09e15de552bfd1bd90cf679ed1072e7b6; Release run 32320752810 is still waiting; publish-release job 96283310269 remains unapproved; the unpublished draft is unchanged, targets the exact commit, and contains exactly six assets.
Draft provenance passed: all six live GitHub asset digests match the staging record. GitHub's SLSA statement covers the exact arm64 ZIP, x64 ZIP, and portable CLI from .github/workflows/release.yml at refs/tags/v0.1.6, source commit fc43f8e09e15de552bfd1bd90cf679ed1072e7b6, run 32320752810, on GitHub-hosted runners. Live published rollback selection remains Apple Silicon v0.1.3 and Intel v0.1.1.
Authenticated Safari download passed: Safari downloaded the exact x64 ZIP, x64 checksum sidecar, and portable CLI from the private draft. All retained quarantine attributes identify Safari. The x64 sidecar verifies, and the downloaded payload digests are x64 d779565bd6103da7e26b68af305ab23a78c4287f9d4fae5ae3339bbd81b3baaa and CLI 3a7540446bdea04e5d5709220f7780fae00ea5bd3005509b9ef96072bf879957. GitHub attestation verification passed for both downloaded payloads.
Physical host passed: 2019 Intel MacBook Pro class; macOS 14.8.9 Sonoma; native x86_64. The extracted installed app retained Safari quarantine, reported v0.1.6, and its main executable was native x86_64.
Trust boundary observed honestly: command-line Gatekeeper assessment rejected the hardened ad-hoc app. Finder then produced the visible Gatekeeper dialog. This build is not Apple-verified and not notarized.
Terminal failure: the agent host is not authorized for Accessibility UI automation, and machine policy defers human QA, so the visible per-app Open Anyway control could not be exercised or verified. The required trust workflow therefore did not pass.
Preservation failure: the initial quarantined Finder launch rewrote both existing v1 review.json files. mko_6b7879f0 changed from SHA-256 7a3e4bf1fa29b782d0dc3a643e4e0573789e311b092519c3f47b0a578119d2f7 to 312322c8472857bf447ef4c1ab12eb15c7ee59482a353c198204d60732e55a57; mko_8d62fcee changed from f48cedeb58ac42388c901371fa33ac68b28ad15badd9b0b815d6259fe0fae75d to b32bd88137530968153b8b2ba10194f861fdc79fe2086c4700e19813a44890e5. Both directories still exist, both JSON files parse as v1, and neither review was deleted or resolved. No speculative restore was attempted.
Stopped before expansion: no clean packaged smoke ran, no new complete-profile backup was created, and no v0.1.1 rollback was attempted. No source, tag, draft, release, publication approval, existing backup, or review resolution/deletion was changed. No Markover process remains.
Overall result: rejected; publication remains blocked. Per the fail-closed boundary, this run stopped at the first unresolvable visible-override failure and did not rerun or create another version.

Correction: the preservation-failure attribution above was overturned by follow-up forensics. The files changed during the deliberate shutdown of the already-running v0.1.4 app, before v0.1.6 was extracted; only review.updatedAt changed. See #80 (comment). The qualification remains rejected because the visible Gatekeeper override was not completed.

Work intent

phase: completed
summary: "Corrected the apparent v0.1.6 review rewrite as a pre-candidate v0.1.4 shutdown timestamp update; no restoration or source fix is warranted"
touch-points:
  - "existing physical-host evidence and preserved profile copies from the completed v0.1.6 qualification claim"
  - "pre-launch and post-launch review.json artifacts for mko_6b7879f0 and mko_8d62fcee"
  - "the exact v0.1.6 persistence/startup code path, read-only, only as needed to explain the rewrite"
  - "sanitized forensic evidence on issue #80"
done-when:
  - "every available pre-launch, post-launch, and backup artifact is identified and hash-verified without mutation"
  - "a structural and semantic diff names every changed field in both protected reviews"
  - "the evidence distinguishes user content, feedback, source, attachment, and lifecycle changes from reconstructible metadata changes"
  - "the responsible code path is identified from finite evidence, or the remaining uncertainty is stated precisely"
  - "one smallest safe disposition is recorded: restore then retry manual QA, implement a separate source fix, or reject the candidate"
  - "sanitized evidence is recorded on #80"
excludes:
  - "restoring, replacing, deleting, moving, or otherwise mutating any review, Markover profile, or existing backup"
  - "launching or focusing Markover or Safari, rerunning physical QA, or exercising the Gatekeeper override"
  - "source edits, commits, pull requests, tags, drafts, releases, publication approval, publication, or another version"
  - "resolving or deleting mko_6b7879f0, mko_8d62fcee, or any other review"
  - "broad bounded-loss durability work owned by #39"
blocked-by: []
may-block:
  - "the next physical Intel qualification slice"
  - "any later v0.1.6 publication-decision slice"
  - "#18 broad-announcement operations"
branch: "read-only forensics; detached checkout"
candidate: "v0.1.6 at fc43f8e09e15de552bfd1bd90cf679ed1072e7b6"
authorized: true

The user authorized proceeding with the narrow forensic follow-up. The completed physical qualification remains terminally rejected; this claim diagnoses its preservation failure without changing the protected artifacts or release state.

Completion: the apparent candidate rewrite was a baseline-ordering error. Installed v0.1.4 graceful shutdown updated only review.updatedAt at 03:08:08.543 UTC, before v0.1.6 extraction; the exact reconstructed bytes match both archived aggregate after-digests. The protected 53-file backup verified 53/53, focused tests passed 61/61, no artifact was restored or changed, and sanitized evidence is recorded at #80 (comment). Next disposition: retry physical QA only in a later authorized human-QA window, taking byte baselines after the installed app has fully stopped; publication remains blocked.

v0.1.6 physical-QA review preservation forensics - earlier attribution corrected

This evidence supersedes only the preservation-failure attribution in the earlier physical-QA report. The physical qualification remains rejected because the required visible Gatekeeper override was not completed.

Measurement correction: the four values previously reported as review JSON SHA-256 values were aggregate review-directory digests. Each review directory contained one review.json, but the aggregate also hashes the file path and therefore is not the raw file digest.
Preserved reference: the existing complete-profile backup remains untouched. Its 53-entry manifest reverified 53/53 files, and the manifest SHA-256 remains c8dca0268aeec4cc2667c67699145aa9be8f7c5a6da0a5e95490db98a11dfa6e.
Causal chronology: the baseline was recorded at 03:07:55 UTC while installed Markover v0.1.4 was still running. The next operation quit that app. Both protected JSON files have the resulting 03:08:08 UTC modification time. The v0.1.6 candidate was not extracted until 03:11:03 UTC, minutes after the files changed.
Exact reconstructed post-quit state: both files differ from the protected backup only at review.updatedAt, set to 2026-08-20T03:08:08.543Z. Reconstructing those exact bytes yields raw SHA-256 822305173def70914a9aaaf69119264f2eed51219d73b735ec674beb72722eed for mko_6b7879f0 and 2d94c8d7aeffd8684c34742af72f410459fa809ff882b53aad2370c237567764 for mko_8d62fcee; recomputing the original aggregate command exactly matches both archived "after" digests.
Semantic preservation: no source snapshot, document tree, feedback, source edit, attachment, lifecycle status, resolution, agent metadata, or other JSON field changed in either review. Neither review was deleted or resolved.
Cause: v0.1.4 graceful shutdown captured each editable renderer snapshot. The persisted updateTree operation intentionally advances review.updatedAt, even when the snapshot's content is otherwise unchanged. The previous baseline was therefore taken too early; the evidence does not show that v0.1.6 rewrote either review.
Focused verification: at exact candidate commit fc43f8e09e15de552bfd1bd90cf679ed1072e7b6, the review-store, durability-shutdown, and durability-integration suites passed 61/61.
Disposition: no restoration and no source repair are justified. A later authorized physical-QA attempt should first stop the installed app, wait for all Markover processes to exit, and only then record the protected byte baseline. Human QA is currently deferred, so no Gatekeeper retry was started.
Release boundary unchanged: the unpublished six-asset v0.1.6 draft remains unchanged and the publication job remains waiting at the unapproved gate. No tag, draft, release, review, backup, or publication state was changed.

Overall: candidate-caused review corruption is retracted. v0.1.6 is still not qualified for publication because the visible Gatekeeper override and the remaining physical smoke/rollback sequence have not passed.

Work intent

phase: completed
summary: "Retry the unchanged v0.1.6 physical Intel qualification with a post-shutdown preservation baseline, visible Gatekeeper override, exact packaged smoke, distinct profile backup, and v0.1.1 rollback"
touch-points:
  - "live v0.1.6 tag, authoritative release run 32320752810, unpublished six-asset draft 373438819, attestations, digests, and waiting publication job"
  - "dedicated physical 2019 Intel Mac on Sonoma, native x86_64 with no Rosetta translation"
  - "existing authenticated Safari downloads and the exact quarantined v0.1.6 x64 app"
  - "visible hardened ad-hoc Gatekeeper rejection and per-app Open Anyway override"
  - "exact installed v0.1.6 app and shared packaged smoke with evidence-kind clean-intel-sonoma"
  - "complete Markover Application Support profile, every existing review, and the preserved rollback backup"
  - "new distinct complete-profile backup created only after v0.1.6 smoke and before rollback"
  - "exact version-pinned v0.1.1 Intel rollback and reopen of mko_6b7879f0"
  - "sanitized physical qualification evidence on issue #80"
done-when:
  - "live state re-verifies candidate fc43f8e09e15de552bfd1bd90cf679ed1072e7b6, annotated tag object 8bfe6f46da7a4de553ed518f2a044735470976e2, authoritative workflow, unchanged unpublished six-asset draft, exact digests and attestations, waiting publish job, and rollback targets arm64 v0.1.3/x64 v0.1.1"
  - "the currently installed Markover is stopped through its managed quit path, every process exits, and only then are review byte baselines recorded"
  - "the exact downloaded x64 ZIP, sidecar, CLI, extracted v0.1.6 app, and quarantine attributes reverify"
  - "Gatekeeper rejects the hardened ad-hoc app before the visible per-app override; the user confirms the override during the authorized QA window"
  - "shared packaged smoke passes against the exact installed v0.1.6 x64 app with evidence-kind clean-intel-sonoma, native x86_64, no Rosetta, exact artifact bytes, saved state before restart, restoration, CLI open/get/edit, and reopened on-disk state"
  - "every preexisting review remains semantically intact; expected updatedAt-only managed saves are recorded separately from content changes"
  - "a new distinct complete-profile backup is made before rollback and the existing 53-file backup remains 53/53 valid and untouched"
  - "the exact version-pinned v0.1.1 CLI/app reopens mko_6b7879f0; only one identical retry is permitted for its documented historical first-start timeout and a second failure rejects rollback"
  - "all preserved reviews remain present and semantically intact, Markover stops cleanly, and sanitized evidence is recorded on #80"
excludes:
  - "approving the publication gate or publishing any release"
  - "modifying the v0.1.4 or v0.1.6 draft, creating another version, or creating, moving, deleting, or mutating any tag"
  - "changing repository source or release automation"
  - "altering, replacing, deleting, or resolving any preexisting review or existing backup"
  - "blind reruns after qualification failure or creating v0.1.7"
  - "Developer ID signing, notarization, or Apple-verification claims owned by #13"
  - "adversarial authorization coverage owned by #12 and bounded-loss durability coverage owned by #39"
blocked-by: []
may-block:
  - "a later explicit #80 publication-decision slice"
  - "#18 broad-announcement operations"
branch: "operations only; detached exact candidate commit fc43f8e09e15de552bfd1bd90cf679ed1072e7b6"
candidate: "v0.1.6"
tag-object: "8bfe6f46da7a4de553ed518f2a044735470976e2"
workflow-run: "https://github.com/lastobelus/markover/actions/runs/32320752810"
draft: "https://github.com/lastobelus/markover/releases/tag/untagged-5f1509082df66682d9f5"
authorized: true
validation-policy:
  - "fail closed at the first discrepancy and record it once"
  - "the v0.1.1 historical first-start timeout permits exactly one identical retry; a second failure rejects rollback"
  - "sanitized evidence omits usernames, serial numbers, credentials, and account-specific paths"

The user opened the human-QA window. This retry incorporates the completed forensic correction: stop the installed app before recording preservation baselines, and do not treat expected updatedAt-only managed shutdown saves as candidate corruption. Publication remains explicitly unauthorized.

First post-policy clean Intel evidence — v0.1.6

Source/tag: v0.1.6 annotated tag object 8bfe6f46da7a4de553ed518f2a044735470976e2 peels exactly to fc43f8e09e15de552bfd1bd90cf679ed1072e7b6.
Draft/workflow: unchanged unpublished six-asset draft / Release run 32320752810. Candidate, CLI, arm64, x64, and staging jobs passed; publication job 96283310269 remains waiting and unapproved.
Exact candidate assets: x64 d779565bd6103da7e26b68af305ab23a78c4287f9d4fae5ae3339bbd81b3baaa; CLI 3a7540446bdea04e5d5709220f7780fae00ea5bd3005509b9ef96072bf879957. Sidecars matched, and GitHub attestations verified both payloads against the release workflow, exact source commit, and refs/tags/v0.1.6 with self-hosted runners denied.
Automated native smoke: the workflow x64 job passed. Physical packaged-smoke evidence 51c4f3671fe4fac13f97d1f73d598dac7ba2814d85950a9380631978898f6644 passed for review mko_9860f735.
Clean host: 2019 Intel MacBook Pro class; macOS 14.8.9 Sonoma; native x86_64; not Rosetta-translated.
Trust result: hardened ad-hoc; not Apple-verified; not notarized. Gatekeeper rejected the quarantined Safari download before the visible per-app Open Anyway override, which the user exercised in the authorized QA window.
Covered: exact artifact bytes and installed app; native launch; CLI create/open; saved state before restart; restart/restoration; CLI get; CLI edit/reopen; reopened state on disk. Every pre-existing review remained semantically identical; managed saves changed only expected updatedAt values.
Excluded: adversarial authorization (Authenticate the loopback review API #12); bounded-loss durability (Guarantee bounded-loss autosave durability across crashes and restarts #39).
Rollback selection: live preflight independently selected Apple Silicon v0.1.3 and Intel v0.1.1.
Rollback target/command: Intel v0.1.1 / npx --yes --package=https://github.com/lastobelus/markover/releases/download/v0.1.1/markover-cli.tgz markover edit mko_6b7879f0.
Rollback provenance: v0.1.1 tag object 1d30c20eec862b3317d51bc82c0ba3ed6c72f596 peels to 2760d01bd2ce1ba53973e7d34d7f295ecf75017a; release workflow 30780129789 passed. Published x64 digest ccf6e1a3c7645f292f5d078fe97aa01dde088bc0fa0b767efec48705f0a91506 and CLI digest 7a3953febedb0c6dc070911897223e5c5a735a38c7eddbf8028b8b1806dc0530 matched; the app was native x86_64 version 0.1.1 with a v1 review reader.
Rollback result: passed. A new distinct 69-file complete-profile backup matched the live profile byte-for-byte and its manifest digest is df2bfba1065ec7e794a5ac0c676320d0c80f1eb8e5347660d8a9ea015e4f1d27; the older protected 53-file backup still verifies 53/53 unchanged. The documented first-start timeout occurred once; the exact v0.1.1 app then owned the live v1 service, all five reviews remained semantically unchanged, and the one permitted identical retry reopened preserved review mko_6b7879f0. The app then stopped and every review reverified.
Overall result: accepted; publication remains blocked pending separate explicit approval. No release, tag, draft, repository source, backup, or review was modified beyond the authorized managed review timestamps and this evidence update.

Completion checks

Pending-review soft gate: the exact current T3 Code/Codex thread returned no unresolved reviews. No review was resolved or deleted; all five profile reviews, including preserved mko_6b7879f0, remain present in editing state with unchanged normalized content.
Exit state: both backup manifests reverified (53/53 protected historical backup; 69/69 new rollback backup), the repository worktree remains clean, no Markover process remains, issue Ship and validate native Intel releases for the broad announcement #80 remains open, and Markover Announcement Readiness remains In Progress.

Navigation Menu

Repository navigation

Ship and validate native Intel releases for the broad announcement #80

Outcome

Acceptance criteria

Scope boundaries

Deferred checkpoint

Work intent

Native Intel host tracer evidence — local setup proof only

Work intent

Work intent

Work intent

First post-policy clean Intel evidence — v0.1.4

Work intent

Work intent

Work intent

Work intent

Work intent

Work intent

v0.1.6 staging evidence — draft qualified; publication blocked

Work intent

Physical Intel/Sonoma v0.1.6 qualification — rejected before smoke

Work intent

v0.1.6 physical-QA review preservation forensics - earlier attribution corrected

Work intent

First post-policy clean Intel evidence — v0.1.6

Completion checks

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Ship and validate native Intel releases for the broad announcement #80

Description

Outcome

Acceptance criteria

Scope boundaries

Deferred checkpoint

Activity

lastobelus commented on Aug 7, 2026

Work intent

lastobelus commented on Aug 19, 2026

Native Intel host tracer evidence — local setup proof only

lastobelus commented on Aug 19, 2026

Work intent

lastobelus commented on Aug 19, 2026

Work intent

lastobelus commented on Aug 19, 2026

Work intent

lastobelus commented on Aug 19, 2026

First post-policy clean Intel evidence — v0.1.4

lastobelus commented on Aug 19, 2026

Work intent

lastobelus commented on Aug 19, 2026

Work intent

lastobelus commented on Aug 20, 2026

Work intent

lastobelus commented on Aug 20, 2026

Work intent

lastobelus commented on Aug 20, 2026

Work intent

lastobelus commented on Aug 20, 2026

Work intent

lastobelus commented on Aug 20, 2026

v0.1.6 staging evidence — draft qualified; publication blocked

lastobelus commented on Aug 20, 2026

Work intent

lastobelus commented on Aug 20, 2026

Physical Intel/Sonoma v0.1.6 qualification — rejected before smoke

lastobelus commented on Aug 21, 2026

Work intent

lastobelus commented on Aug 21, 2026

v0.1.6 physical-QA review preservation forensics - earlier attribution corrected

lastobelus commented on Aug 25, 2026

Work intent

First post-policy clean Intel evidence — v0.1.6

Completion checks

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions