perf(dev): queue the full Rust harness - #2
Open
fullofcaffeine wants to merge 1 commit into
Open
Conversation
fullofcaffeine
force-pushed
the
hxhx/fresh-cargo-evidence-20260719
branch
from
July 19, 2026 14:47
4ab50a8 to
baa6c40
Compare
fullofcaffeine
force-pushed
the
hxhx/heavy-run-lease-20260719
branch
from
July 19, 2026 14:47
c5f62e6 to
0f6ec36
Compare
Owner
Author
Add an opt-in local command that waits for the shared Haxe-family heavy-run lease before starting the unchanged full Rust harness. This prevents concurrent compiler suites from exhausting one workstation, while ordinary local commands and CI behavior stay unchanged. The lease has a bounded 15-minute wait, recovers stale owners without signalling processes, and supports nested wrappers across repositories. Its fixture covers acquisition, contention, timeout, process identity reuse, signal cleanup, CI bypass, nesting, and incompatible future schemas. Verified with npm run hooks:check, the hxhx cross-repository compatibility fixture in both ownership directions, and the full harness through the queued entry point. The semantic and structural harness stages passed; fresh Cargo evidence drift is intentionally handled by prerequisite PR #1. The shared primary checkout fingerprint remained unchanged. The repository hook was bypassed for this commit because linked worktrees share hook and Beads paths; equivalent checks were run explicitly in this worktree.
fullofcaffeine
force-pushed
the
hxhx/heavy-run-lease-20260719
branch
from
July 19, 2026 15:11
0f6ec36 to
d71fdc8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Outcome
Adds an opt-in
npm run test:all:queuedcommand that waits for the shared Haxe-family heavy-run lease before invoking the unchanged Rust full harness. This prevents simultaneous compiler suites from exhausting a developer workstation without changing ordinarynpm run test:allbehavior or CI job contents.The adapter uses the shared
haxe-family.heavy-run-lease.v1wire contract, a bounded 15-minute wait, exit status 75 on temporary capacity exhaustion, PID plus process-start ownership, heartbeat recovery, nested-wrapper handoff, and no signalling of another process.Stacked prerequisite
This PR is intentionally based on #1 (
hxhx/fresh-cargo-evidence-20260719) at90e2e59a. The first queued full-harness run found that the live Cargo registry now resolves newer semver-compatible crates than the checked-in fresh-resolution evidence. That independent evidence refresh remains in #1 so this PR stays a reviewable scheduler-only diff against its base.#1 also repairs branch-safe release validation and prevents duplicate feature-push plus pull-request runs. After rebasing the single scheduler commit, this stacked PR now receives one pull-request-context run even though its base is a feature branch.
Verification
npm run test:heavy-run-lease: passed after the rebase.npm run hooks:check: passed before the scheduler commit and again for the updated prerequisite workflow.npm run test:all:queued: acquired and released the shared lease correctly. All structural, snapshot, native-lock, lifecycle, portable semantic, upstream-stdlib, and API-probe stages passed. The run stopped only at the stale fresh-Cargo evidence that is refreshed and independently validated in fix(ci): restore pull-request validation #1.d71fdc82created exactly one pull-request run, 29692334651, and no duplicate feature-push run.npm run test:allcommand and CI job behavior remain unchanged.Final pull-request run
Run 29692334651 completed with every executable compiler, Rust, packaging, snapshot, conformance, policy, benchmark, and security-audit job green, including the aggregate Snapshots + Examples job. The long conformance + policy shard passed in 32 minutes 3 seconds. Release publication was skipped as expected for a pull request. The only failed job was Dependency review, for the repository setting described below.
Known independent repository setting
GitHub dependency review remains red until the repository dependency graph is enabled in repository settings. This PR does not weaken or skip that check; npm audit, cargo-audit, and all-history gitleaks remain independent required jobs.
Shared-checkout safety
The owning repository hook was bypassed only for the isolated task commit because linked worktrees share hook and Beads paths. Its equivalent
npm run hooks:checksuite was run explicitly inside the task worktree first.The primary checkout remained exactly unchanged before and after commit, rebase, and push. The originally recorded fingerprints remain:
c1c95fbe7debccac68975ac9b5d75c115894675f1dd5e6b49a64d649a289fa64f925fb6e7b9005aa8857eaa3ba52f8e7a900ed0f6b498fd314c63b6e167159d30f6a75fd101628db31608a8359ecb1f9832222b23ebaf414399148f9e6751414072d4116e03f9fe7Origin/signature
Created by the hxhx agent for hxhx bead
haxe_ocaml-850ii.20.2because simultaneous Haxe-family suites were making the local hxhx and Reflaxe development loop unnecessarily slow. The stacked validation update also recordshaxe_ocaml-wu4d4, which was opened after live duplicate GitHub Actions runs made the remote feedback cost measurable. This PR follows the durable cross-repository worktree, signed-PR, hook-locality, and primary-fingerprint rule added after the earlier shared-checkout coordination incident. The hxhx agent will not merge this owner-reviewed PR.