fix: auto-approve phase 3 rewrite

harness/.pi/skills/tht-sessione/SKILL.md

@@ -243,15 +243,12 @@ Phase 3 (CLI exit 5).
    terms, each condition as a separate numbered clause, ambiguous terms replaced with
    the concepts clarified in Phase 1 citing the defining evidence, expected output
    made explicit).
-2. Present in **a single** `reviewer_decide(advance:false, allow_other:true)`. The
-   "Confirm rewriting" option is `recommended:true` with
-   `{type:"question_rewritten", subject:"domanda", detail:"<full rewritten question>"}`.
-3. **Order matters:** (a) the `reviewer_decide` records `question_rewritten` → (b) call the
-   gate's `rewrite_question` tool, which runs `tht session set-question` to write
-   `question.md` (regenerates question + an "## Assunzioni" section; never edit it by hand)
-   → (c) close the phase with `reviewer_confirm kind:"phase"`. F3 does NOT auto-advance:
-   the `question_rewritten` decision alone does not move the phase.
-4. "Altro" iterates (re-propose a new `reviewer_decide`). "Torna indietro" reopens F1.
+2. Call `rewrite_question` once with the completed rewritten question and assumptions. The
+   gate writes `question.md` (including `## Assunzioni`), records `question_rewritten`, and
+   closes F3 automatically.
+3. Do **not** call `reviewer_decide` or `reviewer_confirm` in F3: the rewrite is assumed
+   approved. Continue at F4 only after `rewrite_question` reports success. To revise the
+   rewrite, use "Torna indietro" to reopen F1.
 
 ## Phase 4 — Schema linking