eklavya 1.61.1 → 1.62.1

package/dist/assets/tutor/references/writing-mcq.md

@@ -115,11 +115,16 @@ The reasoning behind each option goes in `option_notes` when you record the
 attempt (the card path) and in the panel's `explanation` (the panel path), both
 shown only after the answer.
 
-**5. Placement.** The plan gives each question an `answer_position`, 1 to 4. Put
-the correct option in that slot. Left to your own judgement you will put the
-right answer first nearly every time, and a learner needs only a handful of
-questions to notice that and start picking A without reading; the quiz keeps
-looking fine and stops measuring anything.
+**5. Placement.** The plan gives each question an `answer_position`, 1 to 4.
+**Put the correct option in exactly that slot** — slot 4 means the fourth option
+in the list, not the first. Do this mechanically: write the three distractors,
+then insert the key at index `answer_position`. Before sending, re-read the list
+and check the key is in that slot and that `correct` matches it. Left to your
+own judgement you will put the right answer first nearly every time, and a
+learner needs only a handful of questions to notice that and start picking A
+without reading; the quiz keeps looking fine and stops measuring anything. A
+question whose key is in the wrong slot is a failed question however good the
+rest is.
 
 **6. `header`.** Set it to `Eklavya`, and then **do what the plan's
 `ask_attribution` says** — it is the rule for the host you are actually running
@@ -168,7 +173,7 @@ telling you which part to rebuild.
   no description says why an option is right, wrong or tempting.
 - Each of the three wrong options came from a different row of the table above.
 - Only the correct option answers the stem; no expert could argue for another.
-- The correct option sits at `answer_position`.
+- The correct option sits at `answer_position`, and `correct` names it.
 - The tool renders the labels, so the stem does not number them.
 - The stem is the question and nothing else — the dials are in the developer's
   status bar.

package/dist/plugin/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "eklavya",
   "displayName": "Eklavya",
-  "version": "1.61.1",
+  "version": "1.62.1",
   "description": "Learn while your agent works. Turns coding-agent generation time into adaptive, Socratic learning grounded in the code being written.",
   "author": {
     "name": "Ajay Kumar"

package/dist/plugin/hooks/panel/model.ts

@@ -148,6 +148,10 @@ export const STR = {
   nothingTyped: 'Write your answer first, or pick one of the options.',
   graderFailed: "We couldn't check that answer. Your text is saved here — Retry.",
   explainer: 'A page explaining this is being written.',
+  /** What the transcript draws for the mod's own queued prompts; the model still reads the full text. */
+  askedNext: 'Eklavya: next quiz question',
+  askedExplainer: 'Eklavya: write an explainer page for the missed question',
+  askedOther: 'Eklavya: a note for Claude',
   focus: 'Ctrl+X then Tab moves the keys here.',
   keys: '1–4 pick · o other · s submit · k skip · Esc back to prompt',
   keysApp: '1–4 pick · o other · s submit · k skip',

package/dist/plugin/hooks/panel/register.tsx

@@ -345,6 +345,17 @@ export const register: Register = on => {
     }
   })
 
+  // The mod's queued prompts are instructions for the model, not words for the
+  // learner: their transcript row shows one short line, as a tool call does.
+  // Only the drawing changes; the model still reads the whole message.
+  on('ui.render', { component: 'UserMessage' }, async ($, e, next) => {
+    const from = e.props.origin
+    if (from.kind !== 'plugin' || from.name !== 'eklavya') return next(e)
+    const said = e.props.text
+    const text = said === NEXT_PROMPT ? STR.askedNext : said.includes('eklavya-explainer') ? STR.askedExplainer : STR.askedOther
+    return next({ ...e, props: { ...e.props, text } })
+  })
+
   on('ui.render', { component: 'Pane', requestId: 'eklavya-quiz' }, async ($, e, next) => {
     // Only our pane: every other pane, and everything else, is the host's.
     if (e.requestId !== PANE) return next(e)

package/dist/plugin/skills/tutor/references/writing-mcq.md

@@ -115,11 +115,16 @@ The reasoning behind each option goes in `option_notes` when you record the
 attempt (the card path) and in the panel's `explanation` (the panel path), both
 shown only after the answer.
 
-**5. Placement.** The plan gives each question an `answer_position`, 1 to 4. Put
-the correct option in that slot. Left to your own judgement you will put the
-right answer first nearly every time, and a learner needs only a handful of
-questions to notice that and start picking A without reading; the quiz keeps
-looking fine and stops measuring anything.
+**5. Placement.** The plan gives each question an `answer_position`, 1 to 4.
+**Put the correct option in exactly that slot** — slot 4 means the fourth option
+in the list, not the first. Do this mechanically: write the three distractors,
+then insert the key at index `answer_position`. Before sending, re-read the list
+and check the key is in that slot and that `correct` matches it. Left to your
+own judgement you will put the right answer first nearly every time, and a
+learner needs only a handful of questions to notice that and start picking A
+without reading; the quiz keeps looking fine and stops measuring anything. A
+question whose key is in the wrong slot is a failed question however good the
+rest is.
 
 **6. `header`.** Set it to `Eklavya`, and then **do what the plan's
 `ask_attribution` says** — it is the rule for the host you are actually running
@@ -168,7 +173,7 @@ telling you which part to rebuild.
   no description says why an option is right, wrong or tempting.
 - Each of the three wrong options came from a different row of the table above.
 - Only the correct option answers the stem; no expert could argue for another.
-- The correct option sits at `answer_position`.
+- The correct option sits at `answer_position`, and `correct` names it.
 - The tool renders the labels, so the stem does not number them.
 - The stem is the question and nothing else — the dials are in the developer's
   status bar.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eklavya",
-  "version": "1.61.1",
+  "version": "1.62.1",
   "description": "Learn while your agent works — local knowledge graph, spaced repetition, and quiz gating for agent-assisted development.",
   "license": "MIT",
   "repository": {