Skip to content

Provision release runner and validate main-workflow evidence - #103

Merged
perNyfelt merged 5 commits into
mainfrom
prepare-minimum-host-runner
Nov 16, 2026
Merged

perNyfelt merged 5 commits into
mainfrom
prepare-minimum-host-runner

Conversation

@perNyfelt

@perNyfelt perNyfelt commented Nov 16, 2026 •

Copy link
Copy Markdown
Member

The minimum-host gate needs a separate non-admin account because the existing ghrunner service also executes PR and Tier-B jobs. Following the owner's approval, provisioned jmlxrunner (UID 503, private 0700 home), registered runner ID 23 with jmlx-release-minimum, and tested the documented launchctl bootstrap/kickstart path. The listener connected as jmlxrunner and appeared online/idle, then was stopped and unloaded. The original local-m5-max runner is unchanged.

Retain setup/review evidence for the initial runner package, current listener, saved .path/.env hashes, resolved Python/Git paths and ownership, and the launchd definition. The saved PATH matches the deliberate clean configuration environment; .env is empty. Document runsvc.sh's PATH restoration and the owner-managed Homebrew trust dependency. Tightened the owner's Gradle properties file to 0600; the release account cannot read or write it. Public sharing evidence is limited to a guest-share boolean and scoped launchd/group observations. No owner credentials were copied; the generated account password was not retained and the temporary registration token was removed.

Treat ID 23 and installed package evidence as historical snapshots: persistent registrations expire after more than 14 offline days, and automatic updates remain enabled. Revalidate remote/local ID, environment, tool/listener versions and exposed queued jobs at each window. The queue command also lists approval-required runs even when their jobs/labels are not exposed; it makes no completeness claim for needs-blocked jobs. Compare the actual run's Set up job / Current runner version line with the pre-dispatch measurement and resolve updates before acceptance. Both release jobs are guarded to main, and minimum-host production/final verification require the reported manual main-workflow identity and SHA. Cut the candidate after these changes merge, with the updated producer in the tag.

Validation: the code changes committed as 407c7be passed all 84 release selftests in 70.196 seconds and actionlint; review.json now names their base commit and working tree. The documentation-only follow-up refreshed the live expanded queue check (no reported matching jobs or approval-required runs), verified synthetic approval-required responses with hidden jobs/labels in both status and conclusion forms, and checked local links/whitespace. Historical test evidence is not presented as a new test run. No candidate execution, signing or publication occurred.

Limits: Homebrew remains owner-managed. Main guards protect this workflow's dispatch path but do not stop repository writers from requesting the labels through another workflow. Queue inspection is a snapshot; no server-enforced workflow allowlist is installed. Sharing checks are not a network-access audit. Exact signed-candidate acceptance and legal/Portal gates remain open.

@perNyfelt perNyfelt changed the title Prepare dedicated minimum-host runner setup Provision dedicated minimum-host release runner Nov 16, 2026
@perNyfelt perNyfelt changed the title Provision dedicated minimum-host release runner Provision release runner and validate main-workflow evidence Nov 16, 2026
@perNyfelt
perNyfelt merged commit 88259fd into main Nov 16, 2026
3 checks passed
@perNyfelt
perNyfelt deleted the prepare-minimum-host-runner branch November 16, 2026 22:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant