feat: generate status-dependent action attempt properties as nullable

[razor-x]

What this means for SDK users

Every action attempt now deserializes to a subclass for its exact (action_type, status) pair, so Error and Result exist only where the API actually populates them:

var attempt = await seam.Locks.LockDoorAsync(new() { DeviceId = deviceId });

// attempt.Result — does not compile: Result is not on the base type.

switch (attempt)
{
    case ActionAttemptLockDoorSuccess success:
        var confirmed = success.Result.WasConfirmedByDevice; // Result is non-null here
        break;
    case ActionAttemptLockDoorError error:
        var message = error.Error.Message; // Error is non-null here
        break;
    case ActionAttemptLockDoorPending:
        // no Error or Result members at all
        break;
}

Unknown discriminator values still fall back safely with the raw payload preserved: an unknown action_type gives ActionAttemptUnrecognized, an unknown status gives e.g. ActionAttemptLockDoorUnrecognized. attempt.Status and attempt.ActionAttemptId stay on the base for polymorphic reads, and the waiter (waitForActionAttempt) behaves exactly as before. A failed attempt without an error object raises SeamActionAttemptFailedException with the message "Action attempt failed" instead of assuming one.

Runtime API behavior is unchanged — the API always sent null; the types just stopped lying about it. Code that read attempt.Error/attempt.Result off the base type must now pattern-match on the status subclass.

How

Bumps @seamapi/blueprint from ^1.8.0 to ^1.10.0, which annotates each action-attempt property with the statuses that populate it. The generator nests a second SeamUnion level under each action type — the existing converter composes for nested unions with no runtime changes. Property placement per status comes from the annotation alone; the status/error wire types remain the runtime-owned ActionAttemptStatus/ActionAttemptError the resolver depends on. @seamapi/types stays at 1.1034.0 (the annotations are complete against it; bumping would import unrelated API churn). The blueprint 1.9.x ordering change reorders request parameters in 7 Routes files — mechanical churn from the bump.

Generated sources are produced by this repo's Generate workflow on push (it runs npm run generate + csharpier and auto-commits), so this PR carries the codegen change, dependency bumps, runtime exception change, and tests.

Verification

Built and tested locally on net8.0: 175/175 tests pass, including new tests for pending/success/error subclass deserialization, unknown-status fallback with raw JSON, and the exception fallback without an error object. The wait-for-action-attempt integration tests exercise the failure path end to end. Codegen tsc + eslint + prettier clean; regeneration is deterministic. Not run locally: the net10.0 target and csharpier (CI covers both).

🤖 Generated with Claude Code

https://claude.ai/code/session_01EdWS7o3htQ9cNxhCWL5Frp