docs: stack-close no longer records which model and effort ran each phase (#170)

Files changed:
- CHANGES.md
- VERSION
- docs/model-and-effort-selection.md
- instructions/dev/stack-close/SKILL.md
- instructions/dev/stack-mode.md

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.