fix(tally): require parent for ledger creates#52
Merged
Conversation
Owner
Author
|
@codex review |
|
Codex Review: Didn't find any major issues. Nice work! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
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.
Summary
Fixes #51: reject a controlled ledger create without an explicit parent before it can be previewed or authorized. This keeps the existing alter-state model intact and extends the synthetic XML-escaping test to cover the required parent.
Validation
cargo fmt --all --checkcargo test -p bridge-tally-writecargo clippy -p bridge-tally-write --all-targets -- -D warningscargo check --workspacegit diff --checkMigration and rollback
No database migration or sync-behavior migration. No live Tally request or write was made. Roll back with
git revert 0a671d2.Security impact
Tally write-qualification change: it narrows the accepted payload set and adds no endpoint, credential, raw-data, or logging path.
Review checklist