# Phase 5.10: Verify One Login Contract

Canonical Beads issue: `dirtydash-px3.10`

## Outcome

One login attempt crosses the public contract and returns observable success.

## Scope

Allowed:

- one login contract and its vertical adapters

Out of scope:

- account management, fleet rollout, and unrelated authentication flows

## Dependencies

- login contract

## Acceptance Evidence

- one contract test proves the login path

## Execution Boundary

- Acceptance boundary: one login contract succeeds or returns its defined failure
- Module surface: login API, UI form, database record, authentication adapter, and telemetry assertion
- Review boundary: login contract and adapter diff plus one vertical integration test

## Quality Gates

- vertical integration test and diff review

## Replanning Triggers

- the accepted login contract cannot express the required failure