Skip to content

Enforce exact concurrency for active account mutations #104

Description

@adrianwebb

The SDK catalog marks profile, username, email primary/removal, preferences, notification preferences, personal-theme update/deletion, and account deletion as concurrency-required. The shared HTTP adapter currently proves only that If-Match is present for several of these handlers; it does not prove that the supplied revision is the one the user inspected.\n\nAcceptance:\n- account reads expose an exact authoritative revision;\n- each concurrency-required account mutation rejects a stale revision with 412 before mutation;\n- Admin carries the inspected value from its UI form;\n- focused and full control-plane tests cover stale revisions;\n- no credential or token values are added to outputs or logs.\n\nParent integration: treeseed-ai/platform#152

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions