Skip to content

perf(dev): queue the full Rust harness - #2

Open
fullofcaffeine wants to merge 1 commit into
hxhx/fresh-cargo-evidence-20260719from
hxhx/heavy-run-lease-20260719
Open

perf(dev): queue the full Rust harness#2
fullofcaffeine wants to merge 1 commit into
hxhx/fresh-cargo-evidence-20260719from
hxhx/heavy-run-lease-20260719

Conversation

@fullofcaffeine

@fullofcaffeine fullofcaffeine commented Jul 19, 2026

Copy link
Copy Markdown
Owner

Outcome

Adds an opt-in npm run test:all:queued command 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 ordinary npm run test:all behavior or CI job contents.

The adapter uses the shared haxe-family.heavy-run-lease.v1 wire 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) at 90e2e59a. 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.
  • hxhx cross-repository compatibility fixture: peer blocks hxhx, hxhx blocks peer, and nested handoff all passed.
  • 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.
  • Updating this stacked PR to d71fdc82 created exactly one pull-request run, 29692334651, and no duplicate feature-push run.
  • The scheduler diff against its base remains one commit and five owned files.
  • The canonical npm run test:all command and CI job behavior remain unchanged.
  • README Goals/North Star progress remains unchanged; this improves local scheduling but does not by itself raise production readiness.

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:check suite 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:

  • HEAD: c1c95fbe7debccac68975ac9b5d75c115894675f
  • index tree: 1dd5e6b49a64d649a289fa64f925fb6e7b9005aa
  • staged and unstaged digests: empty SHA-256
  • porcelain status digest: 8857eaa3ba52f8e7a900ed0f6b498fd314c63b6e167159d30f6a75fd101628db
  • untracked-state digest: 31608a8359ecb1f9832222b23ebaf414399148f9e6751414072d4116e03f9fe7

Origin/signature

Created by the hxhx agent for hxhx bead haxe_ocaml-850ii.20.2 because simultaneous Haxe-family suites were making the local hxhx and Reflaxe development loop unnecessarily slow. The stacked validation update also records haxe_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.

@fullofcaffeine
fullofcaffeine force-pushed the hxhx/fresh-cargo-evidence-20260719 branch from 4ab50a8 to baa6c40 Compare July 19, 2026 14:47
@fullofcaffeine
fullofcaffeine force-pushed the hxhx/heavy-run-lease-20260719 branch from c5f62e6 to 0f6ec36 Compare July 19, 2026 14:47
@fullofcaffeine

Copy link
Copy Markdown
Owner Author

Stack update: this scheduler branch was rebased after #1 moved onto the independent branch-safe release fixture in #3. The scheduler-only diff remains one commit against #1; new candidate: 0f6ec36cd97662c4adb872ee8adfdce2265aac57. The hxhx agent will not merge this owner-reviewed PR.

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
fullofcaffeine force-pushed the hxhx/heavy-run-lease-20260719 branch from 0f6ec36 to d71fdc8 Compare July 19, 2026 15:11
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