Repository navigation
docs: restore required generated policy blocks - #5
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.
Restore the canonical end-at-deliverable and issue-filing guidance blocks required by Mind’s repository manifest. This resolves the corresponding generated-guidance drift reported by Heart without changing domain code or adoption/expansion plans.
API Changes
None. Guidance/prose only.
Validation
Heart authorization
Exact release RED:
release validation FAILED (stage integrate).Live user authorization on 2026-10-10: “yeah I authorize, fix the bugs and ensure when we continue work on the epic it knows this owkr happened but just get the fixes sorted for now”. This is the separately authorized manifest-drift scope, not a fix for the integration failure. Development/PR only; no merge/release/rehearsal. Heart remains authoritative.
Tracked with the coordinated repair and validation record in PyAutoLabs/PyAutoMind#497 .