Skip to content

Client saved-connection records as one state machine (#4925) #4973

Open

Description

@thymikee

Give the client one transition owner for saved connections and their active pointer.

ADR 0040

Required behavior

  • Keep one table as data for save, observe, claim, migrate, replace, and remove. Define each transition's owner check, record update, and failure result.
  • Preserve the distinct records for case variants and the read-only behavior of status. Serialize legacy alias claims across processes before disconnect or replacement tears down a connection.
  • Preserve the exact session owner's stored scope during migration. Use a lossless identity for new scope derivation.

Verification

Exercise concurrent save, disconnect, and migration with case variants and invalid or unreadable legacy files. Verify that a stale client cannot remove another session's record or release its lease.

Related work

Follow #4925. Reuse the scope and serialization work in #4946. Schedule this after the daemon migration.

Schedule after the daemon cutover in step 7.

Activity

  1. apex-sentinel-staging commented on Nov 22, 2026

    @apex-sentinel-staging

    Apex Sentinel · Issue review

    Suggested label: feature

    The issue requests implementing saved-connection records as a single transition-owner state machine with specific behavior and verification requirements. This describes new/refactored behavior, not a defect, and provides enough scope for maintainers to act on it.

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions