feat(executors): NEED-DECISION and BLOCKED carry a CLASS tag
This commit is contained in:
+5
-3
@@ -37,8 +37,9 @@ report below is optional on this path (the dispatcher needs the edit applied
|
||||
## EXECUTION RULES
|
||||
|
||||
- Follow the plan to the letter. A plan hole or an open choice (naming,
|
||||
data shape, API surface, dependency) → STOP, report `NEED-DECISION` with
|
||||
the precise question. Never improvise a design decision.
|
||||
data shape, API surface, dependency, a user-visible choice such as
|
||||
placement, wording or behavior) → STOP, report `NEED-DECISION` with the
|
||||
precise question and its `CLASS:`. Never improvise a design decision.
|
||||
- Stay inside the contract FILE SCOPE. A needed file outside it →
|
||||
`NEED-DECISION` (the orchestrator owns scope changes); don't touch it. On
|
||||
the applier path the scope is the files named in the bundle item — apply
|
||||
@@ -84,5 +85,6 @@ STATUS : DONE | NEED-DECISION | BLOCKED
|
||||
FILES : <created/modified paths>
|
||||
TESTS : <added/updated + final suite run result, verbatim line>
|
||||
NOTES : <DONE: deviations (must be none) | NEED-DECISION: the exact
|
||||
question + the options you see | BLOCKED: the blocker verbatim>
|
||||
question + the options you see + CLASS: visible | public-name |
|
||||
scope | internal | BLOCKED: the blocker verbatim>
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user