docs: stack-close no longer records which model and effort ran each phase (#170)
CI / verify (push) Successful in 5m10s
CI / pwsh (push) Successful in 2m0s
Release / release (push) Successful in 34s

Files changed:
- CHANGES.md
- VERSION
- docs/model-and-effort-selection.md
- instructions/dev/stack-close/SKILL.md
- instructions/dev/stack-mode.md
This commit is contained in:
torben committed 2026-10-03 10:49:12 +02:00
1 parent 100ace846e
commit b3022b8ffb
5 files changed
+19 -32

No files matched your search

+1 -7
View File
@@ -48,11 +48,6 @@ tokens are, which makes it the tempting one to run cheaper. It is also the row w
settled answer: a build phase of this stack reads a lot of the tree, and a smaller context window
does not hold it - it runs into compaction, which costs more than the cheaper model saves. Sonnet
at high effort remains possible, but only as a session of its own (below).
<!-- dist:strip-start -->
Which default the middle row should have is left to the record: every closed work package in this
repo names the model, effort and session shape of each phase, and the table follows that evidence
rather than the other way round.
<!-- dist:strip-end -->
**Effort is the cheaper lever than the model.** A reduced effort level is what gives up
multi-file consistency first, so `high` is a reasonable floor for anything touching more than one
@@ -115,8 +110,7 @@ choice a session *can* make on its own:
once, an unchecked Sonnet phase can ship something nobody looks at again.
- The phase changed and the session runs on a model or effort the table would not pick: keep
working, and cut the session at the next handover rather than switching mid-flow - never block a
publish or an issue close on a choice the session cannot make itself. Naming which model and
effort ran which phase in the handover keeps the gap visible instead of silent.
publish or an issue close on a choice the session cannot make itself.
## Scope