Repository navigation
fix: fence native project inputs before legacy operations - #155
Merged
Merged
Conversation
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.
Native
hack.project.jsoninput could be ignored by legacy discovery, allowing an ancestor Compose project or a constructed legacy context to be selected and changed. This adds a shared input selector and refuses native or mixed authored inputs before legacy project operations.Discovery stops at native markers even when malformed, future-version, nonregular or dangling, while preserving legacy
.hack/.devprecedence. Registered name/ID lookup checks the exact stored root. Init, config, registration, env repair and domain migration/rollback check before effects and again at mutation boundaries; refused rollback preserves its recovery journal. Doctor now checks before global/runtime probes. Listing reports blocked registrations as unavailable, skips their legacy metadata, and continues with healthy peers.The common legacy guard performs one strict marker check. Native input has stable human/JSON refusal codes;
env getkeeps empty stdout and its redacted error. Global config and explicit offline compilation remain available. This does not enable native execution or provide atomic admission against concurrent external edits; NC03 execution and NC04 locked adoption remain separate.Validation:
Release intent: a safety correction for native-input recognition in the v5 candidate. Base:
next. HACK-1220 remains in progress for full frozen-contract coverage and local configuration merge; this PR is a bounded integration slice.