| 2026-10-21 | Developing → Developing | paper #10 Q12: 3/5 (chat answer after close), loss=technique — 'store in a variable called advice, output once' not followed; no print(advice) after the selection | session 127 |
| 2026-10-15 | Developing → Developing | 15 Oct, cold, no reminder: int(input()) on the price line of the pseudo-code translation, 2 days after 13 Oct. 2/2 across two days unprompted. str() and real conversion still untouched. | session 108 |
| 2026-10-13 | Developing → Developing | Session 102, 13 Oct, typed, no reminder: int(input()) written in the Code Lab program (passed run 1) and again in the fresh two-line price item. 2/2 unprompted. str() and real conversion still untouched. | standalone |
| 2026-09-29 | Developing → Developing | 29 Sep starter, no notes, 4 days on: "4"+"5" → 45 and with int() → 9, unaided. Third cold success on the text-join item. | session 58 |
| 2026-09-28 | Developing → Developing | Placement Q6: "4"+"5" → 45 and int("4")+int("5") → 9, both correct cold two days after the misconception, 2/2, 27 Sep. | session 52 |
| 2026-09-25 | Gap → Developing | 25 Sep: taught int(input()) from zero — say-back in own words, worked example 3/3 lines first time, predictions 2/3 unaided ('4'+'5' → '9' before teaching, '45' after; '10'+'20' → '1020'). Then int() written unprompted on all four inputs across two handwritten programs. Taught, checked, applied: gap → developing, single level. | session 48 |
| 2026-09-24 | Gap → Gap | 24 Sep exit ticket (handwritten while loop comparing input with 100): no int() on either input, so the comparison would fail at runtime. Task needed P17 while it is still a gap — set too early by the tutor; not evidence against the topic. She did write money = int(input()) unprompted on 22 Sep. | session 45 |
| 2026-09-15 | Gap → Gap | 15 Sep warm-up after a 4-day gap: 10 / 5 prints 2.0, unaided, second session running. No float-producing expression arose later, so int() unprompted (watch #10) not observed. Proposed developing; not moved here. | session 27 |
| 2026-09-11 | Developing → Gap | audit: session 22's promotion to developing jumped two levels (notstarted→developing) in one session, breaching the single-level-per-session rule. Reverted to gap; the cited retention evidence (float rule retained unaided after a 3-day gap) stands as a proposed developing, not a confirmed move. | standalone |
| 2026-09-11 | Not started → Developing | 11 Sep retrieval after a 3-day gap: said 10 / 5 prints 2.0, unprompted. This was the 8 Sep misconception (predicted 60 for a float expression), so the rule has survived a gap | session 22 |