micro-models-agent 0.21.0 → 0.21.1

package/dist/main.js

@@ -2304,7 +2304,6 @@ Command: {command}`,
     "tool.friendly.process_log": "Process output",
     "tool.friendly.process_kill": "Stopping process",
     "plan.no_steps": "No plan steps specified. Provide concrete steps with files and commands.",
-    "plan.bad_steps": "Plan step quality unacceptable. Each step must describe concrete deliverables (files, packages, commands). Minimum 20 chars per step. Errors: {errors}",
     "plan.created": "Plan created: {title} ({steps} steps)",
     "plan.step_done": "Step {n}/{total}: {description} ✓",
     "plan.complete": "Task complete: {summary}",
@@ -2803,7 +2802,6 @@ var init_ru = __esm(() => {
     "tool.friendly.process_log": "Вывод процесса",
     "tool.friendly.process_kill": "Остановка процесса",
     "plan.no_steps": "Не указаны шаги плана. Укажите конкретные шаги с файлами и командами.",
-    "plan.bad_steps": "Качество шагов плана неприемлемо. Каждый шаг должен описывать конкретные deliverables (файлы, пакеты, команды). Минимум 20 символов на шаг. Ошибки: {errors}",
     "plan.created": "План создан: {title} ({steps} шагов)",
     "plan.step_done": "Шаг {n}/{total}: {description} ✓",
     "plan.complete": "Задача выполнена: {summary}",
@@ -12428,16 +12426,6 @@ class PlanCreator {
       baseDir
     };
   }
-  static validateSteps(steps) {
-    const errors = [];
-    for (let i = 0;i < steps.length; i++) {
-      const s = steps[i].trim();
-      if (s.length < MIN_STEP_DESC_LENGTH) {
-        errors.push(`Step ${i + 1} too short (${s.length} chars). Describe WHAT files to create, WHICH packages to install, WHICH commands to run. Minimum ${MIN_STEP_DESC_LENGTH} chars.`);
-      }
-    }
-    return { valid: errors.length === 0, errors };
-  }
   static toPromptBlock(plan, currentStepIndex) {
     const date = plan.createdAt.slice(0, 10);
     const lines = [
@@ -12455,7 +12443,6 @@ class PlanCreator {
 `);
   }
 }
-var MIN_STEP_DESC_LENGTH = 20;
 
 // src/modules/execution/tracker.ts
 class PlanTracker {
@@ -12863,13 +12850,13 @@ class ExecutionModule {
         name: "plan",
         description: `Create, update, show, or abort a multi-step plan. Use "create" at the start of complex tasks. Use "update" after completing each step to track progress. Use "show" to re-print the current plan checklist.
 
-IMPORTANT — each step MUST be detailed and concrete:
-- Specify WHICH files to create (filenames with paths, e.g. "create src/components/Header.tsx...")
-- Specify WHICH packages to install (e.g. "run npm install react react-dom")
-- Specify WHICH commands to run with exact arguments
-- Minimum 20 characters per step description
-- BAD: "Настройка проекта"
-- GOOD: "Создать package.json с зависимостями react@18, vite@5, установить их через npm install"`,
+IMPORTANT — each step MUST be detailed and concrete (≥50 chars):
+- Specify WHICH files to create with exact paths (e.g. "create src/components/Header.tsx with navigation and logo")
+- Specify WHICH packages to install with exact versions (e.g. "run npm install react@18.3 react-dom@18.3")
+- Specify WHICH CLI commands to run with exact arguments
+- Must contain at least one file extension (.ts, .tsx, .json, etc.) OR a command verb (install, create, build, run, add, init)
+- BAD: "Настройка проекта и установка зависимостей" (too vague, no files, no versions)
+- GOOD: "Создать package.json с зависимостями react@18.3 и vite@5.4, затем выполнить npm install в корне проекта"`,
         parameters: {
           type: "object",
           properties: {
@@ -12893,15 +12880,6 @@ IMPORTANT — each step MUST be detailed and concrete:
             if (steps.length === 0) {
               return { success: false, output: t("plan.no_steps") };
             }
-            const validation = PlanCreator.validateSteps(steps);
-            if (!validation.valid) {
-              return {
-                success: false,
-                output: t("plan.bad_steps", {
-                  errors: validation.errors.join("; ")
-                })
-              };
-            }
             const plan = PlanCreator.createPlan(title, steps, this.baseDir);
             this.setPlan(plan);
             const display = PlanCreator.toPromptBlock(plan, 0);
@@ -14647,7 +14625,7 @@ function buildSystemInfo(config, baseDir, profileCompressed) {
     lines.push(``, `Windows environment — use Windows-compatible commands:`, `- Use "dir" instead of "ls". Use "dir /b" for bare listing.`, `- Use "type" or "Get-Content" instead of "cat".`, `- Use "cd" instead of "pwd". Use "echo %cd%" to print working directory.`, `- Use "copy" instead of "cp", "move" instead of "mv", "del" instead of "rm".`, `- Do not use "mkdir -p" — Windows mkdir creates intermediate dirs by default. Use the create_dir tool instead.`, `- Use forward slashes (/) or escaped backslashes (\\\\) in file paths.`, `- Your working directory is: ${baseDir}`);
   }
   lines.push(``, `Bash tool rules:`, `- Use the "workdir" parameter to run commands in a specific directory. Do NOT chain "cd dir && cmd" — the security module blocks the "&&" operator.`, `- Run one command per tool call. Split multi-step shell operations into separate bash calls.`, `- Background processes (dev servers, watchers, long-running npm install): use the "background: true" parameter or the tool will auto-detect and background them. Check output with process_log.`);
-  lines.push(``, `=== DEVELOPMENT RULES — follow these strictly ===`, ``, `1. DEPENDENCIES FIRST: Before writing any source code, ALWAYS install project dependencies (e.g., "npm install", "pip install -r requirements.txt", "cargo build", "go mod tidy"). Verify the package manager's lock file or dependency directory exists. Never write code that imports/uses packages that aren't installed yet.`, `2. TOOLKIT/FWK FIRST: If the task specifies a framework or UI library, initialize and configure it BEFORE writing application code. Run its project init command first, then add components/modules. Never write your own version of what the framework already provides.`, `3. ONE STEP AT A TIME: Follow the plan sequentially. Complete step N before starting step N+1. When a step is done: verify the deliverables exist and have real content (not empty), then call "plan update step=N status=done". Do not redo completed work.`, `4. VERIFY YOUR WORK: After creating/modifying files, verify they exist on disk. After installing dependencies, verify the package manager completed successfully. After any command, check its output for errors. Don't assume operations succeeded.`, `5. NO PREMATURE WORK: Do not create files for future steps. Do not add imports/references to packages or modules that haven't been installed yet. Do not reference files or components that don't exist yet. Build incrementally — one layer at a time.`, `6. WHEN STUCK: If a command fails 2+ times, STOP and try a different approach. Write files directly instead of using commands. Ask the user for help. Never repeat the same failing command more than twice.`, ``, `=== PLAN QUALITY RULES — your plan MUST follow these ===`, ``, `- Each step must describe CONCRETE deliverables: exact filenames with paths, exact packages to install, exact CLI commands to run.`, `- A step like "Настройка проекта" or "Setup the project" is USELESS and will be REJECTED.`, `- A step like "Создать src/components/Header.tsx с хедером навигации, подключить в App.tsx" is GOOD.`, `- Include file extensions (.tsx, .css, .json) and directory paths. Never write vague steps.`, `- The plan must cover EVERYTHING needed: init → deps → framework setup → code → verification.`, `- Number of steps: 5-8 for a typical task. Too few means you're being vague. Too many means you're over-splitting.`);
+  lines.push(``, `=== DEVELOPMENT RULES — follow these strictly ===`, ``, `1. DEPENDENCIES FIRST: Before writing any source code, ALWAYS install project dependencies (e.g., "npm install", "pip install -r requirements.txt", "cargo build", "go mod tidy"). Verify the package manager's lock file or dependency directory exists. Never write code that imports/uses packages that aren't installed yet.`, `2. TOOLKIT/FWK FIRST: If the task specifies a framework or UI library, initialize and configure it BEFORE writing application code. Run its project init command first, then add components/modules. Never write your own version of what the framework already provides.`, `3. ONE STEP AT A TIME: Follow the plan sequentially. Complete step N before starting step N+1. When a step is done: verify the deliverables exist and have real content (not empty), then call "plan update step=N status=done". Do not redo completed work.`, `4. VERIFY YOUR WORK: After creating/modifying files, verify they exist on disk. After installing dependencies, verify the package manager completed successfully. After any command, check its output for errors. Don't assume operations succeeded.`, `5. NO PREMATURE WORK: Do not create files for future steps. Do not add imports/references to packages or modules that haven't been installed yet. Do not reference files or components that don't exist yet. Build incrementally — one layer at a time.`, `6. WHEN STUCK: If a command fails 2+ times, STOP and try a different approach. Write files directly instead of using commands. Ask the user for help. Never repeat the same failing command more than twice.`, ``, `=== PLAN QUALITY RULES — your plan MUST follow these ===`, ``, `- Each step must describe CONCRETE deliverables: exact filenames with paths, exact packages to install, exact CLI commands to run. Steps shorter than 50 characters or without file paths/commands are REJECTED.`, `- A step like "Настройка проекта" or "Setup the project" is USELESS and will be REJECTED.`, `- A step like "Создать src/components/Header.tsx с навигацией и логотипом, добавить в src/App.tsx импорт <Header />" is GOOD.`, `- Include file extensions (.tsx, .css, .json) and directory paths. Every step must mention at least one file or command.`, `- The plan must cover EVERYTHING needed: init → deps → framework setup → code → verification.`, `- Number of steps: 5-8 for a typical task. Too few means you're being vague. Too many means you're over-splitting.`);
   if (config.autoPlan) {
     lines.push(``, `Plan rule (MANDATORY): For ANY task that requires creating files, installing packages, or multiple actions — you MUST create a plan using the "plan" tool BEFORE starting work. Each step must describe a concrete deliverable (specific files to create, packages to install, commands to run). Do not combine unrelated work into one step.`);
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "micro-models-agent",
-  "version": "0.21.0",
+  "version": "0.21.1",
   "description": "Micro Models Agent (MMA) — LLM agent harness for small models (Qwen3.5-9B, 32K-64K context)",
   "type": "module",
   "bin": {