Publish v0.11.0: canonical onboarding and read-only project entry - #34
Merged
Conversation
Owner
Author
|
Publication complete.
Existing projects do not inherit an upstream governance upgrade. Begin with |
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.
Publish Writwall 0.11.0 with one documented onboarding lifecycle and explicit
read-only entry for existing projects.
writwall inspect --project-root <repo> --role architectemits a fresh Architect handoff without changing projectfiles; normal new-project start also reaches the Architect before adoption.
Inspecting the Writwall distribution itself now identifies it as a
distribution and asks for the target project instead of inheriting the source
repository's adoption records. Active-work and malformed-state checks remain
in force. The complete-tree ledger has one documented, executable calculation.
Preserved naming examples are validated at their recorded decision times.
Their evidence and dates are unchanged. New naming decisions still require
current evidence; the ordinary name-clearance command retains that default.
Closes #31
Closes #32
Closes #33
Validation on the post-closeout candidate bytes:
ba9ae864efbfd350267af4c40283b0d4da55c7bcefc1086215ecacba15df541c.Merge remains gated by the live
CI requiredrule. Tag/release publicationfollows the merged public commit and requires verified immutable metadata.