diff --git a/CHANGES.md b/CHANGES.md index 80f3903..975d8eb 100644 --- a/CHANGES.md +++ b/CHANGES.md @@ -59,7 +59,7 @@ concern - readable here, never shipped as something to parse. --- -## 8.0.0-beta.28 - 2026-10-03 - raw fetch --html record and kb/CONTRACT.md path budget follow the folder accept +## 8.0.0-beta.29 - 2026-10-03 - stack-close no longer records which model and effort ran each phase **Author:** Torben Nehmer @@ -139,8 +139,18 @@ concern - readable here, never shipped as something to parse. - preflight.ps1: the asset-mode error helper is Exit-Asset, so PSScriptAnalyzer passes - kb/CONTRACT.md: an external article's raw_files point under raw/, a raw fetch capture names both files - raw fetch --html record and kb/CONTRACT.md path budget follow the folder accept +- stack-close no longer records which model and effort ran each phase +### stack-close no longer records which model and effort ran each phase + +`stack-close`'s closing comment no longer carries a per-phase table of model, effort, session +shape and compaction, nor the `size/` label beside it; the comment is the changelog line, then +the issue closes. The operator decided the models used need not be documented (Gitea #170), so +the record is dropped without a replacement, together with the sentences that leaned on it: `stack-mode.md` § Sessions +and models, and two in `docs/model-and-effort-selection.md`. Which model suits which phase is +unchanged. Dev-only apart from one `docs/` sentence; no behaviour change. + ### raw fetch --html record and kb/CONTRACT.md path budget follow the folder accept Two sentences the previous change left behind, found in its closing check. `raw fetch --html`'s diff --git a/VERSION b/VERSION index a6af12a..268c2ea 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -8.0.0-beta.28 +8.0.0-beta.29 diff --git a/docs/model-and-effort-selection.md b/docs/model-and-effort-selection.md index b52f33b..5cc4cd6 100644 --- a/docs/model-and-effort-selection.md +++ b/docs/model-and-effort-selection.md @@ -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). - -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. - **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 diff --git a/instructions/dev/stack-close/SKILL.md b/instructions/dev/stack-close/SKILL.md index 1349c48..9defb6c 100644 --- a/instructions/dev/stack-close/SKILL.md +++ b/instructions/dev/stack-close/SKILL.md @@ -1,6 +1,6 @@ --- name: stack-close -description: Closes out a stack work package once its publish has a green CI run - checks the issue body's final state, checks for docs/ and contract staleness, and records which model and effort ran each phase in the closing comment. Started only by the operator as /stack-close, after stack-build has ended its phase. +description: Closes out a stack work package once its publish has a green CI run - checks the issue body's final state, checks for docs/ and contract staleness, and closes the issue. Started only by the operator as /stack-close, after stack-build has ended its phase. disable-model-invocation: true --- @@ -49,7 +49,7 @@ always will. This phase is meant to run on Opus at high effort - a lower effort gives up multi-file consistency first, which is exactly what the staleness check in step 3 needs. If this session runs on something else, say so once and carry on; offer no `/model` or `/effort` switch (see - `instructions/dev/stack-mode.md` § Sessions and models), and record it in step 4. + `instructions/dev/stack-mode.md` § Sessions and models). 2. **Check that the body is in its final state.** `stack-build` kept it current at three fixed points, so this is a check, not a rewrite - but the test is still what a reader who opens the @@ -100,24 +100,8 @@ always will. it only advances the running candidate's counter - then publish and wait per `instructions/dev/publish-and-ci.md`, and name that run in the body too. -4. **Record the handover, then close.** The closing comment carries the one changelog line - `instructions/dev/issue-tracking.md` step 3 asks for, and the handover for **every phase**, - not only this one: - - | Phase | Model | Effort | Own session? | Context overflowed or compacted? | - |---|---|---|---|---| - | 1 Design (`stack-dev`) | | | | | - | 2 Build (`stack-build`) | | | | | - | 3 Closing (`stack-close`) | | | | | - - plus the issue's `size/` label. Fill every cell, even when all three phases ran the same - model in one session - a handover that only flags the unusual case stays silent exactly when - an equally unchecked phase also ran cheap. Phases from an earlier session are named from the - record (the issue's comments, `CHANGES.md`), not from memory, and marked unknown where the - record does not say. These rows are the evidence `docs/model-and-effort-selection.md`'s - phase guide is checked against. - - Then close the issue. +4. **Comment, then close.** The closing comment carries the one changelog line + `instructions/dev/issue-tracking.md` step 3 asks for. Then close the issue. ## Decision points @@ -125,7 +109,7 @@ always will. actually finished and its last publish has a green run - not after every individual publish. - **Resuming a package whose publish landed in an earlier, already-ended session?** Run this skill now, on whatever model the current session is - do not reopen the earlier session to run - it "correctly." Step 4 names the earlier phases from the record. + it "correctly." - **Nothing to close - the session's own exploration, no publish happened?** This skill does not apply; there is no package to close. diff --git a/instructions/dev/stack-mode.md b/instructions/dev/stack-mode.md index ea6d4f6..0b7640c 100644 --- a/instructions/dev/stack-mode.md +++ b/instructions/dev/stack-mode.md @@ -118,5 +118,4 @@ next phase's slash command in a session started on the right model - and the tra what carries the work across it. Which model suits which phase, and the reasoning, is -`docs/model-and-effort-selection.md`. What every phase records, so that reasoning can be checked -against practice, is `stack-close`'s handover (its own step 4). +`docs/model-and-effort-selection.md`.