myco:extend-unifi-api

Create a manager class in unifi-core, define a Pydantic domain model with MUTABLE_FIELDS, add a tool module with preview/confirm flow, write manager and tool tests, then run make generate to update the manifest. The API layer also needs a Strawberry type, REST route, serializer, and dispatcher translator.

Implement get_{resource} via list-and-filter instead of a direct GET-by-ID call: fetch the full list, match on the _id field, and raise a not-found error if absent. This pattern applies to DNS records, AP groups, ACL rules, and filtering rules.

Silent drops happen when update tools skip the fetch-merge-put pattern or omit additionalProperties: false on the input schema. Always fetch current state, deepcopy it, merge the caller's partial dict, and PUT the fully merged object so omitted fields are preserved.

The V2 API _id is a controller-local ObjectID valid only within that controller's database, while the Integration UUID is used for cross-controller queries. Sending an ObjectID to a different controller fails silently with 404 or empty results.

The multi-surface Phase 8 gate requires all surfaces complete: GraphQL type and query field, REST route, action dispatcher entry, serializer registration, regenerated GraphQL docs, skill references artifact, and committed openapi.json. Incomplete PRs are merge-blocked.

Use kind=list with automatic _coerce_list_result normalization when the manager returns a consistent single-key envelope. Use a DETAIL wrapper with a normalizing from_manager_output classmethod when firmware versions return either a bare list or an {items, count} dict.