Repository navigation
docs: reconcile audited design and implementation drift - #2629
Open
codeforester wants to merge 2 commits into
Open
codeforester wants to merge 2 commits into
codeforester wants to merge 2 commits into
Conversation
This was referenced Oct 21, 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.
Summary
Several maintained guides describe older behavior even though the corresponding runtime changes are implemented and tested. Reconcile the audited contracts across design, user/reference docs, contributor guidance, and AI context without changing runtime code.
test.requirementsin the project-runtime decision table and make IDE mutation consent explicit.Issue
Fixes #2628
Refs #1611 and #1613 for broader runtime separation and the future input schema; neither is implemented or closed by this PR.
Validation
git diff --checkpassed. No real install, release publication, or uninstall was performed.Design Impact
Reconciles descriptions of implemented behavior. Release recovery follows the accepted #2551 contract. Uninstall explicitly retains the existing removal/retention behavior and describes its verification limits. No new runtime behavior or documentation-governance gate is introduced.
Docs Impact
Canonical runtime, IDE, release, workspace, ownership, and review documents now agree with the implementation. A dedicated uninstall guide is linked from the index, command reference, stability contract, cache layout, and adopter guide. Contributor guidance distinguishes Base-owned Python packages from the external framework and the legacy CI search-path entry. The contract registry maps reconciled behavior to implementation/tests and states the remaining semantic-coverage limits.
AI Context Impact
Update ARCHITECTURE, COMMANDS, and STATUS for runtime triggers, isolated wrapper execution, and static versus explicitly executing requirements inspection.
Release Notes
Unreleased now records the activation discovery repair from #2611. Documentation corrections do not change published release contents. The two missing upgrade notes belong to #2597's PR.
Demo Impact
None. This PR changes documentation only and preserves existing runtime/demo behavior.