From de4e064885e6b23be9d8b96c7382209fc4647697 Mon Sep 17 00:00:00 2001 From: dctouch Date: Mon, 20 Apr 2026 11:46:25 +0300 Subject: [PATCH] =?UTF-8?q?DOCS:=20=D0=B4=D0=BE=D0=B1=D0=B0=D0=B2=D0=B8?= =?UTF-8?q?=D1=82=D1=8C=20=D0=BE=D1=82=D1=87=D0=B5=D1=82=20=D0=BF=D1=80?= =?UTF-8?q?=D0=BE=D0=B3=D1=80=D0=B5=D1=81=D1=81=D0=B0=20=D1=8D=D1=82=D0=B0?= =?UTF-8?q?=D0=BF=D0=B0?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- AGENTS.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 3562e74..9c23690 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -20,6 +20,13 @@ - `Необходимость жирного ручного прогона` must reflect how strongly the current change still needs a broad manual reality-check beyond unit tests, narrow replay, and build verification. - The percentages must be honest, architecture-aware, and useful for deciding whether the current pass is safe enough to trust without additional human validation. +## development_stage_progress_rule +- After every completed development stage, always report `Прогресс модуля: X%`. +- The percentage must describe progress inside the current large module or plan block, not the whole project. +- If the stage belongs to a named large block, include that block name next to the percentage. +- Use an integer `0%` to `100%` scale and keep the estimate architecture-aware, based on implemented runtime wiring, tests, replay coverage, and remaining integration risk. +- Do not inflate progress because unit tests are green; semantic replay and real runtime wiring still count as unfinished work when they are pending. + ## graphify This project has a graphify knowledge graph at graphify-out/.