# cli - Doramagic AI Context Pack > Purpose: pre-work context for the user's host AI. This pack does not prove that the project has been installed, run, or validated. ## Project - canonical_name: `larksuite/cli` - capability: The official CLI for Lark/Feishu open platform - expected_user_outcome: The official CLI for Lark/Feishu open platform ## Operating Boundaries - Do not claim that the project has been installed, run, called through an API, or used on local files unless separate evidence proves it. - Project facts must come from repo evidence, Claim Graph, or explicit source references. - When a capability is not verified, mark it as unverified instead of completing it as fact. - publish_status: `publishable` - blocking_gaps: none --- ## Doramagic Context Augmentation The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints. ## Human Manual Outline Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph. Host AI hard rules: - Do not treat page titles, section order, summaries, or importance values as factual project evidence. - When explaining the Human Manual outline, state that it is only a reading route or salience signal. - Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph. - **Overview, Installation & Quick Start**: importance `high` - source_paths: README.md, main.go, cmd/root.go, cmd/init.go, cmd/bootstrap.go - **Three-Layer Command System & Domain Shortcuts**: importance `high` - source_paths: cmd/api/api.go, cmd/schema/schema.go, cmd/service/service.go, shortcuts/register.go, shortcuts/apps/shortcuts.go - **Authentication, Identity Switching & Scope Management**: importance `high` - source_paths: cmd/auth/auth.go, cmd/auth/login.go, cmd/auth/login_interactive.go, cmd/auth/login_result.go, cmd/auth/login_scope_cache.go - **AI Agent Skills, Events & Platform Extensibility**: importance `high` - source_paths: cmd/skill/skill.go, cmd/event/event.go, cmd/event/subscribe.go, cmd/event/consume.go, cmd/event/list.go ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `1f2164c7c2abcdb159df0ac00ea5431667866ad5` - inspected_files: `README.md`, `package.json` Host AI hard rules: - Without repo_clone_verified=true, do not claim that the source code has been read. - Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts. - Without quick_start_verified=true, do not claim that the Quick Start path has run successfully. ## Doramagic Pitfall Constraints These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes. ### Constraint 1: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/larksuite/cli/issues/1497 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Installation risk requires verification - Trigger: Developers should check this installation risk before relying on the project: Feature request: Install skills into a dedicated subdirectory/category instead of root skills directory - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Feature request: Install skills into a dedicated subdirectory/category instead of root skills directory. Context: Observed during installation or first-run setup. - Why it matters: Developers may fail before the first successful local run: Feature request: Install skills into a dedicated subdirectory/category instead of root skills directory - Evidence: failure_mode_cluster:github_issue | https://github.com/larksuite/cli/issues/1497 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Installation risk requires verification - Trigger: Developers should check this installation risk before relying on the project: v1.0.52 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v1.0.52. Context: Observed when using python - Why it matters: Upgrade or migration may change expected behavior: v1.0.52 - Evidence: failure_mode_cluster:github_release | https://github.com/larksuite/cli/releases/tag/v1.0.52 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Configuration risk requires verification - Trigger: Developers should check this configuration risk before relying on the project: v1.0.47 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v1.0.47. Context: Source discussion did not expose a precise runtime context. - Why it matters: Upgrade or migration may change expected behavior: v1.0.47 - Evidence: failure_mode_cluster:github_release | https://github.com/larksuite/cli/releases/tag/v1.0.47 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Configuration risk requires verification - Trigger: Developers should check this configuration risk before relying on the project: v1.0.51 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v1.0.51. Context: Source discussion did not expose a precise runtime context. - Why it matters: Upgrade or migration may change expected behavior: v1.0.51 - Evidence: failure_mode_cluster:github_release | https://github.com/larksuite/cli/releases/tag/v1.0.51 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Configuration risk requires verification - Trigger: Developers should check this configuration risk before relying on the project: v1.0.53 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v1.0.53. Context: Source discussion did not expose a precise runtime context. - Why it matters: Upgrade or migration may change expected behavior: v1.0.53 - Evidence: failure_mode_cluster:github_release | https://github.com/larksuite/cli/releases/tag/v1.0.53 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: Capability evidence risk requires verification - Trigger: README/documentation is current enough for a first validation pass. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: capability.assumptions | https://www.npmjs.com/package/@larksuite/cli - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: Runtime risk requires verification - Trigger: Developers should check this runtime risk before relying on the project: v1.0.50 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v1.0.50. Context: Source discussion did not expose a precise runtime context. - Why it matters: Upgrade or migration may change expected behavior: v1.0.50 - Evidence: failure_mode_cluster:github_release | https://github.com/larksuite/cli/releases/tag/v1.0.50 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: Maintenance risk requires verification - Trigger: Project evidence flags a maintenance risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: evidence.maintainer_signals | https://www.npmjs.com/package/@larksuite/cli - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: Security or permission risk requires verification - Trigger: no_demo - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: downstream_validation.risk_items | https://www.npmjs.com/package/@larksuite/cli - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.