docs(design-proposals): focus CLI proposal on cozyctl users

[myasnikovdaniil]

What this PR does

This proposal now covers one user CLI, cozyctl, for tenants and managed-service users. Previous operator CLI scope moved out, installation and upgrades need durable in-cluster API and controller, so cozystackctl will be designed separately as client of that API.

cozyctl keeps catalog discovery, generic application workflows, tenant selection and machine-readable output based on aggregated API, ApplicationDefinition, and OpenAPI.

Testing

• git diff --check
• Commit has valid GPG signature and DCO signoff

Downstream repositories

No downstream changes, this PR changes design only.

NONE

[coderabbitai]

📝 Walkthrough

Walkthrough

The proposal defines cozystackctl for operators and cozyctl for tenants. It specifies shared Kubernetes infrastructure, dynamic application discovery, tenant workflows, plugin behavior, compatibility contracts, security boundaries, testing, rollout, and open questions.

Changes

Unified CLI design

Layer / File(s)	Summary
CLI architecture and contracts design-proposals/cozystack-cli-interfaces/README.md	Defines operator and tenant command trees, shared client and discovery modules, generic application workflows, capability extensions, configuration and output contracts, plugin execution rules, compatibility behavior, security constraints, failure handling, testing, rollout phases, and alternatives.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly identifies the main documentation change: narrowing the CLI proposal to focus on cozyctl users. It is concise and specific.
Description check	✅ Passed	The description explains the scope, rationale, testing, downstream impact, and release-note status. It does not include the template's Before review section or explicitly state whether a decision reco…

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch proposal/cozystack-cli-interfaces

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}