feat: make init.jsonc canonical and nudge config drift#966
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.
Summary
src/lingtai/init.jsoncthe single canonical config-shape source, with explicit canonical/current shapes plus read-only compatibility shapesFULLY_EFFECTIVE,READ_OK_WITH_IGNORED_FIELDS, andREAD_FAILEDoutcomes, including safe effective/failure detailsinit.jsonagainst the canonical/compatibility layers and emit a typedinit_config_shapeNudge; never rewrite or migrate the file automaticallyLINGTAI_NUDGE_ENABLEDandLINGTAI_NUDGE_REPEAT_INTERVALto all Nudge kindsANATOMY.mdBehavior contract
init.jsonValidation
ffda3739d457df4b5a43c425ac4299364acb4593Native Windows / PowerShell 7: successa3f172ff571c39792ae219b76611e38feb673de4py_compile: PASSgit diff --check: PASSScope
This PR owns the kernel reader, canonical shape source, Nudge semantics/policy, prompt/manual guidance, Contracts, Anatomies, and regression gates. The TUI's byte-identical projection and retirement of TUI/Portal runtime migration callers remain in the separate TUI PR.
It does not automatically modify user config, release, deploy, publish, or delete user data.