SILVER
/
NODEDC_1C
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

DOCS: добавить отчет прогресса этапа

This commit is contained in:
dctouch 2026-04-20 11:46:25 +03:00
parent 75e665e836
commit de4e064885
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
AGENTS.md
View File

@ -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/.