Repository navigation
fix: preserve image resources and stable planning inputs (2026.10.21.1) - #827
Merged
Sunrisepeak merged 10 commits intoOct 20, 2026
Merged
Conversation
This was referenced Oct 20, 2026
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.
Dependency-owned executables and shared libraries currently lose their Windows resources when built through a consumer. Repeated planning also rewrites unchanged lockfiles, and build-database output reports synthesized host files as watch inputs, creating a watcher feedback loop.
This change binds resources to the image's package, preserves unchanged lockfiles and reports I/O errors, and excludes generated host inputs while retaining editable build dependencies. It updates the specifications and both user-documentation trees and prepares release 2026.10.21.1 without advancing the bootstrap pin.
Closes #826
Closes #807
#816 is resolved as a design-boundary decision: the default text scanner does not expand includes. Visible imports already receive transitive mappings. This PR documents that boundary and adds a supported-path control test; it adds no workaround or compatibility mode. After merge, #816 will be closed explicitly as
not planned, without an issue comment.Implementation checkpoints and dependency order are recorded in
.agents/docs/2026-10-21-resource-ownership-module-scan-and-lock-write-design.md. The branch contains checkpoint commits; final merge uses squash as requested.Validation: