docs(app): replace oversized lane slices with one-behavior contract
This commit is contained in:
+19
@@ -514,3 +514,22 @@ Standing rules: keep the preview published with a rollback after each landing;
|
||||
never claim authenticated production mutations, OS sharing/notifications on
|
||||
mobile or device behaviour from web fixture evidence; keep mobile labelled
|
||||
unverified until the final build.
|
||||
## Lane contract (corrected after 30-60 minute overruns)
|
||||
|
||||
The oversized slice was mine, not the model's: prompts bundled 5-8 behaviours plus
|
||||
a two-host browser probe and a note file. A probe means two web builds plus
|
||||
Chrome/OCR, so Code alone exceeded the 30-minute stage budget and Review retries
|
||||
pushed runs past an hour.
|
||||
|
||||
Every new lane now gets ONE behaviour:
|
||||
- At most 2 source files (+1) and 1 focused test file.
|
||||
- No `flutter build`, no browser probe, no note file, no `flutter analyze` - the
|
||||
manager runs the probe once per area, writes the note and runs the integrated
|
||||
checks.
|
||||
- Exact web wording and request shape named in the prompt; native controls and
|
||||
theme roles only; no fixed sizes or palettes.
|
||||
- Target: Code under 10 minutes, run under 20.
|
||||
|
||||
Manager per wave: merge each branch, run the focused suite, one area probe, then
|
||||
the full suite/analyze and one preview publish. Probes and full checks are
|
||||
batched, not repeated per lane.
|
||||
|
||||
Reference in New Issue
Block a user