refactor(types): consolidate shared task/tag/link models and normalize task status typing

[joshrotenberg]

Summary

Several response models that should be shared across the crate are currently duplicated across endpoint modules. The biggest example is TaskStateUpdate, which exists in multiple files with slightly different field shapes and typing. CloudTag/CloudTags are also duplicated, and task status is an enum in one place but a raw string elsewhere.

Why this matters

• increases drift risk when the API adds fields or semantics change
• makes docs and examples less consistent across handlers
• complicates Python bindings and future codegen/harmonization work
• makes it harder to reason about compatibility because similar names do not always mean the same type

Relevant code

Repeated TaskStateUpdate

• src/types.rs:16
• src/tasks.rs:71
• src/users.rs:113
• src/cloud_accounts.rs:200
• src/acl.rs:367
• src/fixed/subscriptions.rs:365
• src/fixed/databases.rs:478
• src/flexible/subscriptions.rs:801
• src/flexible/databases.rs:1241

Repeated tag/link models

• src/types.rs:111
• src/types.rs:118
• src/types.rs:146
• src/types.rs:159
• src/fixed/databases.rs:179
• src/fixed/databases.rs:310
• src/flexible/databases.rs:252
• src/flexible/databases.rs:1166

Suggested direction

• choose canonical shared models in src/types.rs
• migrate handlers to those shared types where the wire format is actually the same
• normalize task status typing so one representation is the source of truth
• use aliases or re-exports only where they preserve compatibility without reintroducing drift

Acceptance criteria

• one canonical shared representation exists for task state, tags, and links where the payload shape is the same
• task status typing is consistent across handlers, or any intentional exceptions are documented
• endpoint modules stop redefining structurally identical shared models
• tests and examples are updated to the canonical types

[joshrotenberg]

2026-05 review — confirms scope; one extension

Reviewed all 8 TaskStateUpdate definitions listed; each carries status: Option<String> instead of the canonical TaskStatus enum from src/types.rs:14-44. The dedup is the right move and worth doing as one PR.

Extension: private_link and connectivity deletes don't return TaskStateUpdate at all

Separate from the dedup, the entire src/connectivity/private_link.rs module returns Result<Value> on 14 methods where the spec promises TaskStateUpdate (lines 325-625). And vpc_peering / transit_gateway deletes return Value::Null (body discarded) when the spec returns a Task. Per-callsite issue filed — should be tackled either before or as part of the canonical-type migration so we don't migrate-then-migrate-again.

Also relevant: stale doctest

The example task.status == Some("completed".to_string()) in src/lib.rs:48 and src/tasks.rs:48 would never match either definition since OpenAPI uses kebab-case ("processing-completed"). Deduping under the typed enum lets the example use TaskStatus::ProcessingCompleted instead.