Skip to content

Honor saved runtime sources; release 0.76.1 - #1905

Merged
Brian Krabach (bkrabach) merged 1 commit into
mainfrom
fix/explicit-runtime-sources-20261111
Nov 11, 2026
Merged

Brian Krabach (bkrabach) merged 1 commit into
mainfrom
fix/explicit-runtime-sources-20261111

Conversation

@bkrabach

Copy link
Copy Markdown
Collaborator

A saved conversation could select a local component repair or an exact Git pin, then startup silently resolved the earlier bundle/default source instead. Strict loaded-plan verification correctly held the conversation, leaving it unable to continue.

Preserve the saved plan’s sources through dependency preparation and worker mounting, including distinct child and named-instance declarations. Required host components retain their installed source ownership. Credential binding, source-policy observation, history preservation and loaded-plan verification remain enforced. The configuration contract now states this precedence.

Includes patch release 0.76.1 and its authored What’s new entry. This repairs existing saved-source behavior; no new high-impact notice or dependency change. Canonical build matches all 316 committed static files (client 0.3.3, build 26ae62d8d25de029).

Validation: all six new cases failed on the predecessor and pass on this change. 393 distinct affected backend cases pass across preparation/mounting, component ownership, inherited sources, credential environment, source policy and targeted configuration recovery. The extended run initially found four outdated component test doubles; those were replaced with the actual component object and all four reran successfully without changing assertions. Canonical build and locked dependency dry-run pass. Independent source review found no remaining issues. Actual native Windows controller input qualification remains with its existing owner after live adoption; no claim of that acceptance is made here.

@bkrabach
Brian Krabach (bkrabach) merged commit d519e81 into main Nov 11, 2026
25 checks passed
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