[BASELINE-01] Pin unstable and run the baseline capability audit

[krisoshea-eth]

Why

The plan describes required capabilities, while Lodestar and the related specifications continue to change.

Tasks

• Pin one exact Lodestar unstable SHA for implementation and record its relationship to the newest immutable release-candidate audit target.
• Record consensus-specs, builder-specs, Beacon API, fixture, and image versions.
• Run install, build, lint, type-check, targeted tests, and known baseline checks.
• Record pre-existing failures separately.
• Audit every Confirm or add capability against the pin.
• Recheck merged upstream work, including PR 9725, PR 9726, PR 9739, PR 9749, PR 9750, PR 9751, PR 9756, PR 9757, PR 9758, and PR 9770.
• Recheck additional landed baseline capabilities in PR 9486, PR 9598, PR 9689, PR 9710, Builder CI follow-up PR 9766, plus merged consensus tests PR 5504 and post-alpha.13 PR 5514.
• Recheck the current prepareNextSlot flow in PR 9762, local-versus-peer fault ownership in PR 9755, and the Heze scaffold in PR 9505.
• Advance the immutable audit target to Lodestar v1.46.0-rc.1 at e2b315e; stable remains v1.45.0 and rc.1 is not the final project pin.
• Audit rc.1 shutdown and resource changes PR 9790 and PR 9792. Record that PR 9793 closed without merge because its self-signal/force-exit approach did not generalize, especially for default container PID 1. Test state persistence, database close, process-manager timeout, and Builder restart/cache/reveal recovery without treating the underlying hung worker as solved or prescribing the rejected approach.
• Audit open or moving direct inputs: PR 9736, PR 9761, and Builder PR 9781, plus builder-specs PR 165 and beacon-APIs PR 630.
• Record that Lodestar PR 9594 closed without merge. Re-audit the replacement Lodestar Builder API implementation when the specifications settle; do not depend on the abandoned draft.
• Record the latest execution fixtures as tests-glamsterdam-devnet@v8.1.0, while keeping fixture publication separate from a verified devnet-8 launch.
• Record the delayed correction that Prysm PR 17268 merged on 2026-08-07, moving epoch-boundary duty fetching off the proposal hot path.
• Keep Lodestar PR 9723 and broader monitor-only FCR, range-sync, and epoch-transition research watches outside the Builder dependency graph unless the pinned audit proves a direct requirement.
• Record the live Builder PR #9781 state at the audit pin. On 10 August it was open, review-required, and not draft with 30 commits, four unresolved threads, and head 7386db08081ce635662d6898c925036cd2015b71. The two latest commits replace the manual Builder-response check with the API client's standard .value() path and fix the asynchronous API-error response mocks.
• Track draft release PR #9788 at the rc.1 commit and open circuit-breaker follow-up PR #9780 as baseline watches. Do not treat Lodestar PR 9788 as a shipped stable release or Lodestar PR 9780 as settled policy.
• Record the four devnet-7 Tysm/Prysm host removals in 1ca063f and Dora image override in df1dfc7 as configuration evidence only; do not infer devnet runtime health.
• Record that the August 10 monitor run was partial. Preserve unavailable source cursors, use direct primary-source checks for current claims, and do not infer a devnet-8 launch or runtime health.
• Narrow or close already-satisfied issue work with evidence.
• Update only affected dependencies, estimates, and target weeks.
• Create or confirm the shared feature branch.

Done when

The project has one reproducible baseline pin and every implementation issue reflects what is actually missing on that pin.

Evidence

• Newest immutable audit target: Lodestar v1.46.0-rc.1 at e2b315e
• Release watch: Lodestar PR 9788 remains an open draft at the rc.1 commit; stable remains v1.45.0
• Circuit-breaker watch: Lodestar PR 9780 remains open outside rc.1; policy is unsettled
• August 10 monitor status: partial; live claims require direct verification
• Stable reference: Lodestar v1.45.0
• Historical observed unstable head on 2026-08-05: c65aaefd91a602df1ffb82d929ec479fba8578ac (not the project pin)
• Exact project unstable pin:
• Spec/API versions:
• Fixture/image versions:
• Test commands/results:
• Capability audit:
• Feature branch:

[linear-code]

LOD-6