[agliznetsov]

Description of your changes

Adds two write tools, create_community and create_domain (DEV-217560).

• create_community: name, optional parentCommunity (UUID or name), optional description, confirm.
• create_domain: name, community (UUID or name), domainType (UUID or name), optional description, confirm.
• Both follow the confirm checkpoint in docs/TOOL_CONTRIBUTION_STANDARDS.md section 5: confirm=false (default) returns a preview of every field to be written and sends no write; confirm=true creates.
• Names are resolved to UUIDs server-side through a new shared resolve.Community / resolve.DomainType. An unknown or ambiguous name returns a validation_error listing the valid options.
• Inputs are validated before any request, including the 255-character name limit from the dgc-core AddCommunityRequest / AddDomainRequest.
• Clients call POST /rest/2.0/communities and POST /rest/2.0/domains through executeCollibraRequest, so Collibra's error message reaches the caller.
• Both tools are registered ungated, like create_asset.

Tested against a local Collibra instance: preview writes nothing, confirm creates, nested communities, name and UUID resolution, invalid domain type, and duplicate community name.

---

Impact Analysis

Additive change: two new tools in the default tool surface, one new shared resolver file, and two new client files. Existing tools are unchanged. Both tools need Collibra permission to create communities or domains; without it the write returns an error status.

---

Checklist

• I have performed a self-review of my code
• My code follows the contribution guidelines of this project
• My changes generate no new warnings

🤖 Generated with Claude Code