docs(funding): record verified production recovery deployment - #32
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
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.
What
Record the exact PR31 source and Vercel artifact now serving production, verified login and funding-history reload, anonymous deposit boundaries, and patched rollback constraints. Refresh the DOX deployment index and distinguish historical consent deployment records.
Why
Deployment evidence must follow the actual promoted artifact without implying that global charging or payouts were activated.
Tested
Prettier checks on all three documents, git diff --check, and staged gitleaks passed. Runtime PR31 passed all required CI before merge; the clean merged source built remotely, reached Ready, was promoted, and was checked through the live Console.
Risk
Documentation only. No environment, database, balance, payment or payout changes. No runtime deployment required for this documentation follow-up.