Skip to content

Connect desktop console actions to owner-scoped backend services #4

Description

@Conner512

Goal

Implement the currently presentation-only console operations while preserving existing OAuth/MCP read-only and account isolation contracts. Requested by the repository owner after merging the Layout A UI.

Scope

  • Own-memory create/correct/retract, classification and organizer scheduling/status.
  • Personal model settings with explicit egress/budget controls, no secret echo.
  • Owner-scoped connections/session revocation, account security and configured recovery flows.
  • Personal export/import (not downloading a shared database).
  • Registration-code administration and account metadata/state management restricted to explicitly provisioned operator roles.
  • Real forms and result/error handling in the existing Layout A UI; no mock-success fallbacks.

Compatibility and release boundary

Additive schema/API changes; preserve old account IDs, data, handoff and existing read-only credentials. Privileged operations require explicit deployment capability/role provisioning, not frontend flags. Shared-database restore remains a separate controlled operator procedure rather than an ordinary personal-data action. No production data, credentials or deployment access is part of this work.

Implementation will be submitted on a separate branch with regression tests and explicit coverage/remaining limitations.

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions