Repository navigation
I-01C: add session RBAC idempotency transaction guards - #8
Merged
Merged
Conversation
Implement transaction-bound sessions, CSRF and epoch revocation, tenant-scoped RBAC, audit-safe idempotency leases with owner fencing, and last-admin protection. Add isolated MySQL and pure authorization tests plus I-01C acceptance documentation.
Owner
Author
|
@1605009600 审PR |
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.
I-01C scope
Implements transaction-bound session, RBAC, idempotency, audit, tenant-scope, and last-admin security primitives.
Changes
Validation
python -m ruff check apps packages tests tools/databasepython -m ruff format --check apps packages tests tools/databasebuild_specs.py --check: 16 artifacts;test_readiness_design.py: 148 checksReview / risks
tools/design/requirements.txtfor the final contract checkRollback
Revert this feature commit before enabling application routes; preserve session/audit history and do not delete database records.