Feature request: support commenting on Objectives/Key Results in the OKR domain

What

Add the ability to create comments on Objectives / Key Results in the okr domain — e.g.:

lark-cli okr +comment-create --target-type objective --target-id <id> --content "..."

plus +comment-list, and ideally reply support.

Why / use case

I run cross-team OKR reviews with AI agents driving lark-cli. The natural workflow: an agent reads a teammate's OKRs (okr +list, cycle detail), then leaves review feedback on the OKR itself, so the owner sees it in context in the OKR product.

Today that last step can't be done programmatically:

• The OKR product UI does have a comment/discussion feature, but as far as I can tell it isn't exposed in the open API, so the CLI has nothing to wrap.
• The current OKR v1 open API surface — period (create/patch/list), period_rule/list, okr/list, okr/batch_get, progress_record (create/update/delete/get/upload), review/query (read-only) — has no comment capability.
• The only write channel, progress_record/create, is effectively owner-only: it works on my own OKRs, but an identical payload targeting another user's O/KR fails with 1009999 internal server error (not a clean permission error). And semantically progress records aren't review comments anyway — they land on the progress timeline.

Current workaround: mirror the OKRs into a docx/wiki page and comment there with drive +add-comment. It works, but it splits the review discussion away from the OKR system where the owner actually looks.

Ask

1. Expose OKR comment create/list (reply would be great) via the open API and wrap it in lark-cli. I understand this likely needs the OpenAPI platform team rather than the CLI repo alone — filing here because lark-cli is the developer/agent-facing surface; hoping the team can route it internally.
2. Minor, related: a documented, permission-style error instead of 1009999 when progress_record/create targets someone else's OKR would save integrators real debugging time.

Environment

• lark-cli 1.0.65, macOS (darwin), Feishu tenant

Sent by Jerry's Claw

Begin with the existing lark-cli OKR commands and the documented OKR v1 API surface described in the issue. Confirm whether comment create/list or replies are available, then define completion as supported API operations, CLI wrappers, and a documented permission-style error for progress_record/create on another user's OKR.