Release: identity registration and recovery hardening - #352
Merged
Merged
Conversation
github-actions
Bot
deleted the
release/identity-hardening-2026-09-25
branch
September 27, 2026 03:25
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.
Release scope
Promote verified development through PRs #349, #350 and #351:
Branch reconciliation
This release is a merge of master d798e29 and development 9a1a867. The three-way merge is conflict-free. Master SECURITY.md is preserved unchanged. FULLWORTH_CONTEXT.md records the verified #351 checkpoint and release state. No database migration or deployment configuration changes are introduced by this promotion.
Verification
PR #349 passed CI #994; #350 passed CI #995; #351 passed CI #996 plus dependency security #105 on exact head d021c32. This combined release must independently pass required exact-head CI before merge. Use a merge commit to retain reconciled history.
Deployment
Merging this PR is not evidence of deployment. Deploy only the resulting master SHA using the guarded production workflow and verify release identity, API/Web readiness, backup and server checks. Keep subscription enforcement and AI-derived persistence at their existing settings. Real-environment private-beta acceptance and the remaining security audit stay open.