feat: add ziti management proto

[casey-brooks]

Summary

• add ziti management proto definition for ZitiManagementService
• keep proto comments ASCII to match existing files

Testing

• buf lint
• buf build
• $(npm config get prefix)/bin/redocly bundle openapi/team/v1/openapi.yaml -o dist/team-v1.yaml
• $(npm config get prefix)/bin/redocly bundle openapi/files/v1/openapi.yaml -o dist/files-v1.yaml
• $(npm config get prefix)/bin/redocly bundle openapi/llm/v1/openapi.yaml -o dist/llm-v1.yaml
• $(npm config get prefix)/bin/spectral lint dist/team-v1.yaml (warnings from existing specs)
• $(npm config get prefix)/bin/spectral lint dist/files-v1.yaml (warnings from existing specs)
• $(npm config get prefix)/bin/spectral lint dist/llm-v1.yaml (warnings from existing specs)

Refs #30

[github-actions]

The latest Buf updates on your PR. Results from workflow buf-pr / buf (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	✅ passed	Mar 17, 2026, 11:58 PM

[casey-brooks]

Summary

• add ziti management proto definition for the ZitiManagementService
• keep proto comments ASCII to match existing files

Test & Lint Summary

Commands:

• buf lint
• buf build
• $(npm config get prefix)/bin/redocly bundle openapi/team/v1/openapi.yaml -o dist/team-v1.yaml
• $(npm config get prefix)/bin/redocly bundle openapi/files/v1/openapi.yaml -o dist/files-v1.yaml
• $(npm config get prefix)/bin/redocly bundle openapi/llm/v1/openapi.yaml -o dist/llm-v1.yaml
• $(npm config get prefix)/bin/spectral lint dist/team-v1.yaml (warnings from existing specs)
• $(npm config get prefix)/bin/spectral lint dist/files-v1.yaml (warnings from existing specs)
• $(npm config get prefix)/bin/spectral lint dist/llm-v1.yaml (warnings from existing specs)

Tests: 0 passed, 0 failed, 0 skipped.
Lint: no errors; spectral warnings remain from existing OpenAPI specs.

[noa-lucent]

Proto definition matches the issue #30 specification exactly. Verified against existing codebase conventions:

• Package naming, go_package format, file location all consistent with existing protos.
• snake_case fields, UPPER_SNAKE enum values, _UNSPECIFIED = 0 sentinel — all correct.
• ASCII-only comments (-> instead of →) as noted in the PR description.
• Service RPCs, messages, and enum values match the spec one-to-one.
• Field numbering is sequential and correct.

Clean addition. LGTM.