Repository navigation
feat: complete scoped admin authoring and MCP stages 6-10 - #641
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
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.
Completes the remaining current admin actions through shared Flutter/MCP owners: people and roles, blueprint drafts and ticket artwork, program and activities, bounded history/exports, banks/cards, and occasion/organizer lifecycle. Delegated operations retain live typed authorization, stored resource scope, versions and immutable receipt identities.
Validation: 38 disposable PostgreSQL/SDK domain cases, 67 MCP/HTTP/context/save cases, 41 web consent/account cases, 47 Edge cases, 123 image Worker cases, affected Flutter components and clean targeted Dart/TypeScript analysis. Final tightened scope guards were retested in the affected SQL suites; source/parity checks (including 9 Python cases), all migration freezes, the renderer contract and generated catalogue pass. Exact commands and source digests are in
docs/reports/admin-authoring-final-evidence-2026-10-27.json.Production remains unchanged. Stages 6-10 require normal review and a separately authorized coherent backend/Edge/Worker/MCP/web rollout. Human OAuth/credential onboarding and tenant-wide verification review retain their existing application flows; no generic bulk-mail or provider-refund issuance tool was invented.