feat: Generate a status-discriminated action attempt union

[razor-x]

What this means for SDK users

Every action attempt now parses to a class for its exact (action_type, status) pair, so mypy knows when error and result are real and when they are None:

attempt = seam.locks.lock_door(device_id=device_id, wait_for_action_attempt=False)

# Before: this typechecked and crashed at runtime (result is None while pending).
# Now: mypy rejects it.
attempt.result.was_confirmed_by_device

# Narrow on status — no None checks needed:
if attempt.status == "success":
    attempt.result.was_confirmed_by_device  # ok: result is not Optional here
if attempt.status == "error":
    attempt.error.message  # ok: error is not Optional here
if attempt.status == "pending":
    attempt.error   # typed None
    attempt.result  # typed None

# isinstance works too:
if isinstance(attempt, LockDoorSuccessActionAttempt):
    attempt.result.was_confirmed_by_device

Waiting for completion is typed as the success union, no cast needed:

resolved = seam.locks.lock_door(device_id=device_id)  # waits by default
# poll_until_ready returns SuccessActionAttempt: result is not Optional

Runtime behavior is unchanged — the API always sent null; the types just stopped lying about it.

How

Bumps @seamapi/blueprint to ^1.10.0, which annotates each action-attempt property with the statuses that populate it. The existing generated-union mechanism (per-variant dataclasses, Literal discriminators, dispatch dict) gains a second axis: 21 action types × 3 statuses = 63 classes, dispatched on the (action_type, status) tuple, with the same DeepAttrDict fallback for unknown values. Union aliases keep old names importable (LockDoorActionAttempt) and add PendingActionAttempt / SuccessActionAttempt / ErrorActionAttempt. Nothing is keyed off the names error/result.

Verification

mypy-checked tests cover every snippet above; pytest covers parsing pending/success/error payloads and unknown-status fallback. 185 tests passed, mypy clean (120 files), pylint 10/10. Regeneration from a clean install reproduces the diff exactly; only seam/resources/action_attempt.py and seam/resources/__init__.py changed among generated files.

🤖 Generated with Claude Code

https://claude.ai/code/session_01EdWS7o3htQ9cNxhCWL5Frp