Agnir v1.0.1: harden Project activation - #50
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
1 participant
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
Implements the Agnir v1.0.1 activation/packaging hardening discussed after the real commit-boundary miss.
AGNIR.mdas the canonical Executor-facing Project activation and operation surface;AGENTS.mdlocator-only and point it directly toAGNIR.md;README.md#Agnir-Project-Instructionsas a backward-compatible v1.0.0 locator only;AGENTS.md -> READMEactivation so an existing v1.0.0 Project can activate safely before upgrade;commit/提交/提交代码an explicit repository-context dispatch to checkpoint evaluation before commit;.agnir/mutation is not;Core
1.0andrepository-filesystem/1.0remain unchanged. This PR does not publishv1.0.1; stable publication remains a separate authoritative-main operation.The branch is intentionally opened as draft while release/version/conformance surfaces are being reconciled and CI is used as the next gate.