chore: record the v0.5.0 security-and-consistency cycle - #166
Merged
Conversation
Promote itd-74 (name banlist) draft -> planned with spc-20, add the examples-use-reserved-identifiers principle, open the seven ledger entries from the privacy-leak investigation (iss-153..159), and land the v0.5.0 plan plus its DECISIONS lines. The scheduled cloud loop drains this plan one item per round; round 1 needs the record set on main. Assisted-by: Claude:claude-fable-5
record-lint links_resolve caught two references still targeting the drafts path. Assisted-by: Claude:claude-fable-5
REPPL
enabled auto-merge
July 29, 2026 10:30
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.
Lands the v0.5.0 "security & consistency" cycle records so the scheduled plan-drain loop finds its plan on main:
.abcd/development/plans/2026-07-29-v0.5.0-security-and-consistency.md— the cycle plan, including the run contract (auto-merge only through the strict gate: CI green + two adversarial MERGE verdicts).spc-20-name-banlist.md.examples-use-reserved-identifiers(illustrative machine identifiers come from RFC-reserved documentation ranges).Records only — no code changes.