docs(release): 0.5.0 notes cover the rubric-3b fixes landed on PR #28

CHANGELOG and releases/v0.5.0.md gain the four changes the owner's rubric
row 3b walkthrough (2026-09-20) put on feat/energy-demand-body-double:

- the item-5 entry no longer says "due recall is never deferred" as if it
  covered every due row — the due-review reader emits a struggling row as a
  hands-on guided repair, and that copy now carries the repair's demand and
  defers with it (the defect: a low-energy day showed the repair the learner
  was just spared as the primary, its own deferral printed beneath it);
- the micro teach-back door for a `learning` concept and its gentle-review
  wording;
- the teach-back protocol's low-energy guided-explanation fallback;
- the verification note records that every row-3b reading was re-emitted
  through both readers before its verdict was read as a verdict on shipped
  behaviour.

`just release-consistency-shipped` passes on this tree (pre-tag form).

Author: NetDevAutomate

CHANGELOG.md

@@ -77,12 +77,23 @@ experience may change before `1.0.0`.
   A live struggle (`struggling`, seen within 14 days) asks for 6/10, an older
   struggle or a weak teach-back for 4/10, a concept still `learning` for none;
   below the day's capability a repair is deferred like new work into
-  `energy_deferred_repairs` — never ranked — while due recall is never
-  deferred. When nothing plan-related fits the day and an active, ready plan
-  exists, one low-scoring proposal is synthesised: sit with the plan in a
-  body-double session (`studyloop study "<plan>" --mode co-study`), leading
-  with the progress the plan records and naming what is deferred. Every
-  offered command quotes learner-authored text as one shell word.
+  `energy_deferred_repairs` — never ranked — while due recall and teach-back
+  reviews are never deferred. The due-review reader emits every `struggling`
+  row as a hands-on "guided repair" as well, so that copy carries the same
+  demand and defers with the repair, named once — without it the repair the
+  learner had just been spared came back as the primary. When nothing
+  plan-related fits the day and an active, ready plan exists, one low-scoring
+  proposal is synthesised: sit with the plan in a body-double session
+  (`studyloop study "<plan>" --mode co-study`), leading with the progress the
+  plan records and naming what is deferred. Every offered command quotes
+  learner-authored text as one shell word.
+- **The low-energy teach-back is the one-sentence kind, with a way out.** A
+  concept still `learning` is offered as a *micro* teach-back
+  (`studyloop teachback … --type micro`) and its reason reads as the gentle
+  review it is, not "repair now"; the teach-back protocol gains a low-energy
+  fallback — when the sentence will not come, the mentor gives a short guided
+  explanation and asks for one phrase back, instead of walking the four-round
+  stuck ladder, and the blank is not scored.
 - **Plan with the architect from the Web UI.** *Plans → Plan with architect*
   launches the Study Plan Architect through the ordinary session machinery
   (one-session authority, reconnect, the same console) with a `planning`

releases/v0.5.0.md

@@ -43,10 +43,16 @@ does not advertise GitHub or PyPI binary distribution.
 - Repair has an energy demand of its own: a live struggle asks for 6/10, an
   older one or a weak teach-back for 4/10, a concept still `learning` for
   none. Below the day's capability a repair is deferred like new work
-  (`energy_deferred_repairs`), and due recall is never deferred. When nothing
-  plan-related fits and an active, ready plan exists, one low-scoring
-  proposal is synthesised — sit with the plan in a body-double session — that
-  leads with the progress the plan records and names what is deferred.
+  (`energy_deferred_repairs`); due recall and teach-back reviews are never
+  deferred. When nothing plan-related fits and an active, ready plan exists,
+  one low-scoring proposal is synthesised — sit with the plan in a body-double
+  session — that leads with the progress the plan records and names what is
+  deferred.
+- A concept still `learning` is offered as the one-sentence *micro*
+  teach-back and described as the gentle review it is; the teach-back
+  protocol gains a low-energy fallback (a short guided explanation and one
+  phrase back when the sentence will not come, instead of the four-round
+  stuck ladder; the blank is not scored).
 - A fully-checked active plan yields a completion action, not more study
   work: `studyloop plan close <id>` reviews the plan against its evidence and
   proposes *extend* or *close*; status never changes by itself, and a partial
@@ -78,6 +84,13 @@ does not advertise GitHub or PyPI binary distribution.
   shell word; a plan title carrying `$(…)` no longer executes when pasted.
 - A legacy `study_progress` row with no `last_seen` no longer crashes the
   struggle collector.
+- The due-review reader emits every `struggling` row as a hands-on "guided
+  repair" too — the same repair the struggle collector defers, collected a
+  second time. That copy now carries the repair's demand and defers with it
+  (named once), so a low-energy day no longer shows the repair the learner
+  was just spared as the primary with its own deferral printed beneath it.
+  Found by emitting the owner's rubric readings through both readers; the
+  earlier fixture had silenced one.
 - `anyio` 4.15.1 (two published advisories); both dependency audits clean.
 
 ### Release tooling
@@ -103,6 +116,9 @@ does not advertise GitHub or PyPI binary distribution.
   `docs/architecture/plan-integration/receipts/`).
 - Council records: `docs/architecture/plan-integration/council/` (reviews 1–7
   and the rubric-3b decision brief); owner rubric:
-  `docs/architecture/plan-integration/receipts/now-rubric-2026-09-16.md`.
+  `docs/architecture/plan-integration/receipts/now-rubric-2026-09-16.md` —
+  every row scored by the owner, row 3b (six readings) on 2026-09-20 with each
+  reading re-emitted through both real readers before its verdict was read as
+  a verdict on shipped behaviour.
 - `just release-check` (pre-tag) on the release commit; `just release-verify`
   after the tag.