kodu 1.2.0 → 2.0.0

package/src/core/config/config.schema.ts

@@ -1,43 +1,4 @@
 import { z } from 'zod';
-import {
-  DEFAULT_COMMIT_TOKENS,
-  DEFAULT_LLM_MODEL,
-  DEFAULT_REVIEW_TOKENS,
-} from '../../shared/constants';
-
-// Model ID format: provider/model-name (e.g., "openai/gpt-4o", "anthropic/claude-4-5-sonnet")
-const modelIdSchema = z.string().regex(/^[a-zA-Z0-9-_]+\/[a-zA-Z0-9-_.]+$/, {
-  message:
-    "Model must be in format 'provider/model-name' (e.g., 'openai/gpt-4o')",
-});
-
-const llmCommandSettingsSchema = z
-  .object({
-    maxOutputTokens: z.number().int().positive().optional(),
-  })
-  .passthrough();
-
-const llmCommandSchema = z.object({
-  modelSettings: llmCommandSettingsSchema.optional(),
-});
-
-const createDefaultCommandSettings = () => ({
-  commit: { modelSettings: { maxOutputTokens: DEFAULT_COMMIT_TOKENS } },
-  review: { modelSettings: { maxOutputTokens: DEFAULT_REVIEW_TOKENS } },
-});
-
-const llmCommandsSchema = z
-  .object({
-    commit: llmCommandSchema.optional(),
-    review: llmCommandSchema.optional(),
-  })
-  .default(() => createDefaultCommandSettings());
-
-const llmSchema = z.object({
-  model: modelIdSchema.default(`openai/${DEFAULT_LLM_MODEL}`),
-  apiKeyEnv: z.string().default('OPENAI_API_KEY'),
-  commands: llmCommandsSchema.optional(),
-});
 
 const cleanerSchema = z.object({
   whitelist: z.array(z.string()).default(['//!']),
@@ -63,40 +24,14 @@ const packerSchema = z.object({
   contentBasedBinaryDetection: z.boolean().default(false),
 });
 
-const promptSourceSchema = z.string();
-
 const promptsSchema = z
   .object({
-    review: z.record(z.string(), promptSourceSchema).optional(),
-    commit: promptSourceSchema.optional(),
-    pack: promptSourceSchema.optional(),
+    pack: z.string().optional(),
   })
   .optional();
 
-const serverPathsSchema = z
-  .object({
-    apps: z.string().default('/var/agent-apps'),
-    caddy: z.string().optional(),
-  })
-  .optional();
-
-const serverConfigSchema = z.object({
-  host: z.string(),
-  port: z.number().default(22),
-  user: z.string(),
-  sshKeyPath: z.string(),
-  description: z.string().optional(),
-  paths: serverPathsSchema,
-  env: z.record(z.string(), z.string()).optional(),
-});
-
-const opsSchema = z.object({
-  servers: z.record(z.string(), serverConfigSchema),
-});
-
 export const configSchema = z.object({
   $schema: z.string().optional(),
-  llm: llmSchema.optional(),
   cleaner: cleanerSchema.default({
     whitelist: ['//!'],
     keepJSDoc: true,
@@ -118,8 +53,6 @@ export const configSchema = z.object({
     contentBasedBinaryDetection: false,
   }),
   prompts: promptsSchema,
-  ops: opsSchema.optional(),
 });
 
 export type KoduConfig = z.infer<typeof configSchema>;
-export type ServerConfig = z.infer<typeof serverConfigSchema>;

package/src/core/config/config.service.ts

@@ -21,14 +21,14 @@ export class ConfigService {
 
     if (!result || result.isEmpty || !result.config) {
       this.terminate(
-        'kodu.json config not found. Run `kodu init` to create the file.',
+        'kodu.json not found. Create it in the project root to configure kodu.',
       );
     }
 
     const parsed = configSchema.safeParse(result.config);
 
     if (!parsed.success) {
-      console.error(pc.red('kodu.json config is invalid:'));
+      console.error(pc.red('kodu.json is invalid:'));
       parsed.error.issues.forEach((issue) => {
         const path = issue.path.join('.') || '(root)';
         console.error(pc.red(`- ${path}: ${issue.message}`));

package/src/core/config/prompt.service.ts

@@ -1,19 +1,13 @@
 import { promises as fs } from 'node:fs';
 import path from 'node:path';
 import { Injectable } from '@nestjs/common';
-import { replacePromptVariables } from './default-prompts';
-
-type Variables = Record<string, string | number>;
 
 @Injectable()
 export class PromptService {
   private readonly cache = new Map<string, string>();
 
-  async load(source: string, variables?: Variables): Promise<string> {
-    const raw = await this.readSource(source);
-    return variables
-      ? replacePromptVariables(raw, this.normalize(variables))
-      : raw;
+  async load(source: string): Promise<string> {
+    return this.readSource(source);
   }
 
   async loadFromPromptsDir(name: string): Promise<string> {
@@ -66,29 +60,13 @@ export class PromptService {
     }
     const hasPathSegments = value.includes('/') || value.includes('\\');
     const hasExtension = path.extname(value) !== '';
-
     return value.trim().length > 0 && !hasPathSegments && !hasExtension;
   }
 
   private buildCandidates(name: string): string[] {
     const names = path.extname(name) ? [name] : [`${name}.md`, `${name}.txt`];
-
-    const roots = [path.join(process.cwd(), '.kodu', 'prompts')];
-
-    const candidates: string[] = [];
-    for (const root of roots) {
-      for (const variant of names) {
-        candidates.push(path.join(root, variant));
-      }
-    }
-
-    return candidates;
-  }
-
-  private normalize(variables: Variables): Record<string, string> {
-    return Object.fromEntries(
-      Object.entries(variables).map(([key, value]) => [key, value.toString()]),
-    );
+    const root = path.join(process.cwd(), '.kodu', 'prompts');
+    return names.map((variant) => path.join(root, variant));
   }
 
   private async exists(target: string): Promise<boolean> {

package/src/shared/constants.ts

@@ -1,8 +1,4 @@
 export const MAX_FILE_SIZE_BYTES = 1024 * 1024; // 1 MB
-export const WARNING_TOKEN_THRESHOLD = 12_000;
-export const DEFAULT_COMMIT_TOKENS = 1_500;
-export const DEFAULT_REVIEW_TOKENS = 5_000;
-export const DEFAULT_LLM_MODEL = 'gpt-4o';
 export const DEFAULT_PRICE_PER_MILLION = 5;
 
 const BINARY_EXTENSION_LIST = [

package/src/shared/git/git.module.ts

@@ -1,9 +1,7 @@
 import { Module } from '@nestjs/common';
-import { ConfigModule } from '../../core/config/config.module';
 import { GitService } from './git.service';
 
 @Module({
-  imports: [ConfigModule],
   providers: [GitService],
   exports: [GitService],
 })

package/src/shared/git/git.service.ts

@@ -1,38 +1,20 @@
 import { Injectable } from '@nestjs/common';
 import { execa } from 'execa';
-import { ConfigService } from '../../core/config/config.service';
-
-const EXCLUDE_PREFIX = ':(exclude)';
 
 @Injectable()
 export class GitService {
-  constructor(private readonly configService: ConfigService) {}
-
   async ensureRepo(): Promise<void> {
     try {
       await execa('git', ['rev-parse', '--is-inside-work-tree']);
     } catch (error) {
       const message =
-        error instanceof Error && 'stdout' in error
+        error instanceof Error && 'stderr' in error
           ? String((error as { stderr?: string }).stderr ?? error.message)
           : 'Git repository not found. Initialize git before running the command.';
       throw new Error(message);
     }
   }
 
-  async hasStagedChanges(): Promise<boolean> {
-    const { stdout } = await execa('git', ['diff', '--staged', '--name-only']);
-    return stdout.trim().length > 0;
-  }
-
-  async getStagedDiff(): Promise<string> {
-    await this.ensureRepo();
-    const excludeArgs = this.buildExcludeArgs();
-    const args = ['diff', '--staged', '--unified=3', '--', '.', ...excludeArgs];
-    const { stdout } = await execa('git', args);
-    return stdout;
-  }
-
   async getChangedFiles(): Promise<string[]> {
     await this.ensureRepo();
     const changed = new Set<string>();
@@ -52,18 +34,4 @@ export class GitService {
     await load(['ls-files', '--others', '--exclude-standard']);
     return [...changed].sort();
   }
-
-  async getStatusShort(): Promise<string> {
-    const { stdout } = await execa('git', ['status', '--short']);
-    return stdout.trim();
-  }
-
-  async commit(message: string): Promise<void> {
-    await execa('git', ['commit', '-m', message]);
-  }
-
-  private buildExcludeArgs(): string[] {
-    const ignore = this.configService.getConfig().packer.ignore ?? [];
-    return ignore.map((pattern) => `${EXCLUDE_PREFIX}${pattern}`);
-  }
 }

package/src/shared/tokenizer/tokenizer.module.ts

@@ -1,9 +1,7 @@
 import { Module } from '@nestjs/common';
-import { ConfigModule } from '../../core/config/config.module';
 import { TokenizerService } from './tokenizer.service';
 
 @Module({
-  imports: [ConfigModule],
   providers: [TokenizerService],
   exports: [TokenizerService],
 })

package/src/shared/tokenizer/tokenizer.service.ts

@@ -1,60 +1,30 @@
 import { Injectable } from '@nestjs/common';
-import { encodingForModel, getEncoding, type TiktokenModel } from 'js-tiktoken';
-import { ConfigService } from '../../core/config/config.service';
-import { DEFAULT_LLM_MODEL, DEFAULT_PRICE_PER_MILLION } from '../constants';
+import { encodingForModel, getEncoding } from 'js-tiktoken';
+import { DEFAULT_PRICE_PER_MILLION } from '../constants';
 
 type TokenEstimate = {
   tokens: number;
   usdEstimate: number;
 };
 
-const PRICE_PER_MILLION: Record<string, number> = {
-  'gpt-4o': 10,
-  'gpt-5-mini': 2.5,
-};
-
 @Injectable()
 export class TokenizerService {
-  private encoder?: ReturnType<typeof encodingForModel>;
-
-  constructor(private readonly configService: ConfigService) {}
+  private encoder?: ReturnType<typeof getEncoding>;
 
   count(text: string): TokenEstimate {
     const tokens = this.getEncoder().encode(text).length;
-    const price = this.getPricePerMillion();
-    const usdEstimate = price > 0 ? (tokens / 1_000_000) * price : 0;
-
+    const usdEstimate = (tokens / 1_000_000) * DEFAULT_PRICE_PER_MILLION;
     return { tokens, usdEstimate };
   }
 
-  private getPricePerMillion(): number {
-    const config = this.configService.getConfig();
-    const model = config.llm?.model ?? `openai/${DEFAULT_LLM_MODEL}`;
-    const key = this.normalizeModelKey(model);
-    return PRICE_PER_MILLION[key] ?? DEFAULT_PRICE_PER_MILLION;
-  }
-
-  private createEncoder() {
-    try {
-      return encodingForModel(DEFAULT_LLM_MODEL as TiktokenModel);
-    } catch {
-      return getEncoding('o200k_base');
-    }
-  }
-
   private getEncoder() {
     if (!this.encoder) {
-      this.encoder = this.createEncoder();
+      try {
+        this.encoder = encodingForModel('gpt-4o');
+      } catch {
+        this.encoder = getEncoding('o200k_base');
+      }
     }
-
     return this.encoder;
   }
-
-  private normalizeModelKey(model: string): string {
-    const lower = model.toLowerCase();
-    if (lower.includes('/')) {
-      return lower.split('/').pop() ?? lower;
-    }
-    return lower;
-  }
 }

package/.kodu/prompts/commit.md

@@ -1,9 +0,0 @@
-You generate Conventional Commit messages.
-Rules:
-- Format: <type>(<optional scope>): <subject>
-- Lowercase subject, no trailing period.
-- Keep under 70 characters.
-- Summarize the diff accurately.
-
-Diff:
-{diff}

package/.kodu/prompts/pack.md

@@ -1,7 +0,0 @@
-Project context below. Keep instructions concise.
-
-Files packed ({{tokenCount}} tokens, ~{{usdEstimate}}):
-{{fileList}}
-
-Context:
-{{context}}

package/.kodu/prompts/review-bug.md

@@ -1,6 +0,0 @@
-You are a strict code reviewer. Response format: concise markdown with bullet points.
-Mode: {mode}. Find potential bugs, logical errors, and regressions.
-Provide a concise list of issues and recommendations. If no critical issues found, state that.
-
-Diff:
-{diff}

package/.kodu/prompts/review-security.md

@@ -1,6 +0,0 @@
-You are a strict code reviewer. Response format: concise markdown with bullet points.
-Mode: {mode}. Find vulnerabilities, secret leaks, improper permission checks.
-Provide a concise list of issues and recommendations. If no critical issues found, state that.
-
-Diff:
-{diff}

package/.kodu/prompts/review-style.md

@@ -1,6 +0,0 @@
-You are a strict code reviewer. Response format: concise markdown with bullet points.
-Mode: {mode}. Check readability, consistency, formatting, and naming.
-Provide a concise list of issues and recommendations. If no critical issues found, state that.
-
-Diff:
-{diff}

package/.opencode/command/openspec-apply.md

@@ -1,24 +0,0 @@
----
-description: Implement an approved OpenSpec change and keep tasks in sync.
----
-The user has requested to implement the following change proposal. Find the change proposal and follow the instructions below. If you're not sure or if ambiguous, ask for clarification from the user.
-<UserRequest>
-  $ARGUMENTS
-</UserRequest>
-<!-- OPENSPEC:START -->
-**Guardrails**
-- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
-- Keep changes tightly scoped to the requested outcome.
-- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
-
-**Steps**
-Track these steps as TODOs and complete them one by one.
-1. Read `changes/<id>/proposal.md`, `design.md` (if present), and `tasks.md` to confirm scope and acceptance criteria.
-2. Work through tasks sequentially, keeping edits minimal and focused on the requested change.
-3. Confirm completion before updating statuses—make sure every item in `tasks.md` is finished.
-4. Update the checklist after all work is done so each task is marked `- [x]` and reflects reality.
-5. Reference `openspec list` or `openspec show <item>` when additional context is required.
-
-**Reference**
-- Use `openspec show <id> --json --deltas-only` if you need additional context from the proposal while implementing.
-<!-- OPENSPEC:END -->

package/.opencode/command/openspec-archive.md

@@ -1,27 +0,0 @@
----
-description: Archive a deployed OpenSpec change and update specs.
----
-<ChangeId>
-  $ARGUMENTS
-</ChangeId>
-<!-- OPENSPEC:START -->
-**Guardrails**
-- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
-- Keep changes tightly scoped to the requested outcome.
-- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
-
-**Steps**
-1. Determine the change ID to archive:
-   - If this prompt already includes a specific change ID (for example inside a `<ChangeId>` block populated by slash-command arguments), use that value after trimming whitespace.
-   - If the conversation references a change loosely (for example by title or summary), run `openspec list` to surface likely IDs, share the relevant candidates, and confirm which one the user intends.
-   - Otherwise, review the conversation, run `openspec list`, and ask the user which change to archive; wait for a confirmed change ID before proceeding.
-   - If you still cannot identify a single change ID, stop and tell the user you cannot archive anything yet.
-2. Validate the change ID by running `openspec list` (or `openspec show <id>`) and stop if the change is missing, already archived, or otherwise not ready to archive.
-3. Run `openspec archive <id> --yes` so the CLI moves the change and applies spec updates without prompts (use `--skip-specs` only for tooling-only work).
-4. Review the command output to confirm the target specs were updated and the change landed in `changes/archive/`.
-5. Validate with `openspec validate --strict --no-interactive` and inspect with `openspec show <id>` if anything looks off.
-
-**Reference**
-- Use `openspec list` to confirm change IDs before archiving.
-- Inspect refreshed specs with `openspec list --specs` and address any validation issues before handing off.
-<!-- OPENSPEC:END -->

package/.opencode/command/openspec-proposal.md

@@ -1,29 +0,0 @@
----
-description: Scaffold a new OpenSpec change and validate strictly.
----
-The user has requested the following change proposal. Use the openspec instructions to create their change proposal.
-<UserRequest>
-  $ARGUMENTS
-</UserRequest>
-<!-- OPENSPEC:START -->
-**Guardrails**
-- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
-- Keep changes tightly scoped to the requested outcome.
-- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
-- Identify any vague or ambiguous details and ask the necessary follow-up questions before editing files.
-- Do not write any code during the proposal stage. Only create design documents (proposal.md, tasks.md, design.md, and spec deltas). Implementation happens in the apply stage after approval.
-
-**Steps**
-1. Review `openspec/project.md`, run `openspec list` and `openspec list --specs`, and inspect related code or docs (e.g., via `rg`/`ls`) to ground the proposal in current behaviour; note any gaps that require clarification.
-2. Choose a unique verb-led `change-id` and scaffold `proposal.md`, `tasks.md`, and `design.md` (when needed) under `openspec/changes/<id>/`.
-3. Map the change into concrete capabilities or requirements, breaking multi-scope efforts into distinct spec deltas with clear relationships and sequencing.
-4. Capture architectural reasoning in `design.md` when the solution spans multiple systems, introduces new patterns, or demands trade-off discussion before committing to specs.
-5. Draft spec deltas in `changes/<id>/specs/<capability>/spec.md` (one folder per capability) using `## ADDED|MODIFIED|REMOVED Requirements` with at least one `#### Scenario:` per requirement and cross-reference related capabilities when relevant.
-6. Draft `tasks.md` as an ordered list of small, verifiable work items that deliver user-visible progress, include validation (tests, tooling), and highlight dependencies or parallelizable work.
-7. Validate with `openspec validate <id> --strict --no-interactive` and resolve every issue before sharing the proposal.
-
-**Reference**
-- Use `openspec show <id> --json --deltas-only` or `openspec show <spec> --type spec` to inspect details when validation fails.
-- Search existing requirements with `rg -n "Requirement:|Scenario:" openspec/specs` before writing new ones.
-- Explore the codebase with `rg <keyword>`, `ls`, or direct file reads so proposals align with current implementation realities.
-<!-- OPENSPEC:END -->

package/.opencode/skills/kodu-ops/SKILL.md

@@ -1,184 +0,0 @@
----
-name: kodu-ops
-description: Use when a user asks in plain language to deploy, update environment variables, add/remove domains, or inspect server/app status on dev/prod, and these intents should be translated into `kodu ops` commands.
----
-
-# Kodu Ops
-
-## Overview
-
-Справочник для `kodu ops`: как переводить пользовательские запросы в корректные команды `sysinfo`, `env`, `routes`, `service`.
-
-Ключевой принцип: `kodu ops` должен возвращать JSON-ответы без интерактивщины; агент выбирает подкоманды и флаги точно по контракту.
-
-## When To Use
-
-Используйте этот скилл, когда нужно:
-
-- Перевести бытовой/джуновский запрос на инфраструктуру в `kodu ops` (без ожидания, что пользователь знает CLI).
-- Получить диагностику удаленного сервера (`sysinfo`).
-- Прочитать или изменить `.env` проекта (`env`).
-- Посмотреть или изменить маршруты Caddy (`routes`).
-- Управлять lifecycle сервиса через Docker Compose (`service`).
-- Выполнить несколько ops-действий в одном запросе в строгой последовательности.
-
-Не используйте, если задача не про `kodu ops` (например, локальная сборка/линт/git без удаленных операций).
-
-## Core Rules
-
-- Всегда используйте именованные флаги; positional arguments не поддерживаются.
-- Не ожидайте, что пользователь назовет `kodu ops` или `--action`; извлекайте intent из обычной речи.
-- Для каждого шага проверяйте обязательные флаги до запуска следующего.
-- В цепочке "сначала ... потом ..." выполняйте команды последовательно.
-- В ошибках ориентируйтесь на JSON-поля `status`, `code` и `error`/`stderr`.
-- Если пользователь дал неполные данные, запрашивайте только отсутствующие обязательные параметры.
-
-## Quick Reference
-
-| Подкоманда | Назначение | Действия | Обязательные флаги |
-| --- | --- | --- | --- |
-| `sysinfo` | Диагностика сервера | - | `--server` |
-| `env` | Работа с `.env` проекта | `get`, `set`, `unset` | `--server --action --project` (+ `--key` для `set/unset`, + `--val` для `set`) |
-| `routes` | Работа с Caddy маршрутами | `list`, `add`, `remove`, `update` | `--server --action` (+ `--domain` для `add/remove/update`, + `--upstream` для `add/update`) |
-| `service` | Управление сервисом | `clone`, `pull`, `up`, `down`, `logs`, `status` | `--server --action --project` (+ `--repo` для `clone`) |
-
-## Command Details
-
-### `sysinfo`
-
-Назначение: собрать `uptime`, загрузку диска `/` и свободную память.
-
-Флаги:
-
-- `-s, --server <name>` - алиас сервера из `kodu.json`.
-
-Пример:
-
-```bash
-kodu ops sysinfo --server dev
-```
-
-### `env`
-
-Назначение: читать и изменять `.env` файла проекта в `ops.servers.<alias>.paths.apps/<project>/.env`.
-
-Флаги:
-
-- `-s, --server <name>`
-- `-a, --action <get|set|unset>`
-- `-p, --project <name>`
-- `--key <key>` - обязателен для `set` и `unset`
-- `--val <value>` - обязателен только для `set`
-
-Примеры:
-
-```bash
-kodu ops env --server dev --action get --project my-app
-kodu ops env --server dev --action set --project my-app --key PORT --val 3123
-kodu ops env --server dev --action unset --project my-app --key PORT
-```
-
-Ограничения:
-
-- Ключ проходит валидацию: `[A-Za-z_][A-Za-z0-9_]*`.
-
-### `routes`
-
-Назначение: читать и редактировать блоки доменов в `Caddyfile` (reverse proxy).
-
-Флаги:
-
-- `-s, --server <name>`
-- `-a, --action <list|add|remove|update>`
-- `--domain <domain>` - обязателен для `add`, `remove`, `update`
-- `--upstream <host:port>` - обязателен для `add`, `update`
-
-Примеры:
-
-```bash
-kodu ops routes --server dev --action list
-kodu ops routes --server dev --action add --domain api.example.com --upstream 127.0.0.1:3000
-kodu ops routes --server dev --action update --domain api.example.com --upstream 127.0.0.1:4000
-kodu ops routes --server dev --action remove --domain api.example.com
-```
-
-Поведение:
-
-- После `add/remove/update` автоматически применяется `./caddy.sh`.
-- Если маршрут не найден при `remove/update`, ожидайте ошибку с кодом `NOT_FOUND`.
-
-### `service`
-
-Назначение: управлять проектом в директории apps через `git` и `docker compose`.
-
-Флаги:
-
-- `-s, --server <name>`
-- `-a, --action <clone|pull|up|down|logs|status>`
-- `-p, --project <name>`
-- `--repo <url>` - обязателен только для `clone`
-
-Примеры:
-
-```bash
-kodu ops service --server dev --action clone --project temp --repo https://github.com/org/repo.git
-kodu ops service --server dev --action up --project temp
-kodu ops service --server dev --action status --project temp
-kodu ops service --server dev --action logs --project temp
-kodu ops service --server dev --action pull --project temp
-kodu ops service --server dev --action down --project temp
-```
-
-Фактические действия:
-
-- `clone` -> `git clone <repo> <projectPath>` (ошибка, если директория уже существует)
-- `pull` -> `git pull`
-- `up` -> `docker compose up -d`
-- `down` -> `docker compose down`
-- `logs` -> `docker compose logs --no-color --tail=200`
-- `status` -> `docker compose ps --format json` (fallback на обычный `docker compose ps`)
-
-## JSON Output Contract
-
-Успех:
-
-- Всегда есть `status: "ok"`.
-- Полезная нагрузка приходит в `data` или `message` в зависимости от подкоманды.
-
-Ошибка:
-
-- Всегда есть `status: "error"`.
-- Поле `code` может быть строкой (например, `VALIDATION_ERROR`, `NOT_FOUND`) или числовым exit-code SSH.
-- Текст ошибки приходит как `error` (CLI-валидация) или `stderr` (SSH/remote ошибки).
-
-## Multi-Step Intent Mapping
-
-Если пользователь описывает цепочку действий, раскладывайте ее на команды в указанном порядке.
-
-Частые разговорные формулировки:
-
-- "залей на прод/дев" -> обычно `service pull` + `service up` (или `service clone` + `service up`, если проекта еще нет).
-- "добавь домен" -> `routes --action add --domain ... --upstream ...`.
-- "поменяй домен на новый порт" -> `routes --action update --domain ... --upstream ...`.
-- "посмотри что с сервисом" -> `service --action status` (+ при необходимости `service --action logs`).
-- "поставь переменную" -> `env --action set --key ... --val ...`.
-
-Пример:
-
-```text
-"Покажи sysinfo на dev, поставь PORT=3123 в temp и добавь маршрут api.example.com -> 127.0.0.1:3000"
-```
-
-Порядок команд:
-
-1. `kodu ops sysinfo --server dev`
-2. `kodu ops env --server dev --action set --project temp --key PORT --val 3123`
-3. `kodu ops routes --server dev --action add --domain api.example.com --upstream 127.0.0.1:3000`
-
-## Common Mistakes
-
-- Пропуск `--project` для `service`/`env` (он обязателен даже для `clone`).
-- Использование `pull` как обновления docker-образов: здесь `pull` делает `git pull` в проекте.
-- Ожидание единого формата ошибки `error` во всех случаях: для SSH-ошибок обычно поле `stderr`.
-- Передача key в неверном формате (например, `my.key`), что ломает валидацию.
-- Попытка передать positional args вместо `--flags`.

package/dist/src/commands/commit/commit.command.d.ts

@@ -1,18 +0,0 @@
-import { CommandRunner } from 'nest-commander';
-import { UiService } from '../../core/ui/ui.service';
-import { AiService } from '../../shared/ai/ai.service';
-import { GitService } from '../../shared/git/git.service';
-type CommitOptions = {
-    ci?: boolean;
-    output?: string;
-};
-export declare class CommitCommand extends CommandRunner {
-    private readonly ui;
-    private readonly git;
-    private readonly ai;
-    constructor(ui: UiService, git: GitService, ai: AiService);
-    parseCi(): boolean;
-    parseOutput(value: string): string;
-    run(_inputs: string[], options?: CommitOptions): Promise<void>;
-}
-export {};