neuvikon 0.2.28 → 0.2.30

package/dist/index.mjs

@@ -733,6 +733,27 @@ function parsePayload(raw) {
 	}
 }
 /**
+* What actually gets the model/effort switch to happen, versus the
+* AGENTS.md wording alone: tested against real tickets, an agent reading
+* "judge difficulty and switch model" in its rules file consistently read
+* past it and started working at whatever model/effort it already had —
+* the instruction competed with everything else in that file and lost.
+*
+* `UserPromptSubmit` can inject `additionalContext`, which Claude Code
+* surfaces as a system-level reminder on the *same turn* the ticket lands,
+* not as background file content the agent may or may not re-read. It's
+* still just text — this can't force a `/model`/`/effort` call, only put it
+* in front of the model at the one moment it's actually relevant instead of
+* buried in a rules file next to a dozen other instructions.
+*/
+const MODEL_TRIAGE_CONTEXT = "A Neuvikon ticket just landed in this prompt. Before reading any file or running `start`: judge how difficult it actually is. If it's a small, mechanical change (button placement, a copy/label edit, a trivial styling tweak, a one-line config change), send `/model haiku` and `/effort low` now, as their own messages, before touching the ticket — there's no reason to spend a frontier model thinking hard about something this small. If it needs real design judgment, touches multiple systems, or you're unsure, stay on the current model and effort level instead.";
+function hookResponse(additionalContext) {
+	return JSON.stringify({ hookSpecificOutput: {
+		hookEventName: "UserPromptSubmit",
+		additionalContext
+	} });
+}
+/**
 * The `UserPromptSubmit` counterpart to `start`. Unlike `start`, this runs on
 * *every* prompt regardless of whether it mentions a ticket, so it must never
 * fail the hook and block the user's message — no credentials, no ticket ref,
@@ -745,6 +766,7 @@ async function hookStart() {
 		const { prompt, transcriptPath } = parsePayload(await readStdin());
 		const [ref] = extractTicketRefs(prompt ?? "");
 		if (!ref) return;
+		process.stdout.write(hookResponse(MODEL_TRIAGE_CONTEXT));
 		const existing = readSession();
 		if (existing?.ticket === ref) return;
 		const transcript = transcriptPath ?? claudeTranscriptPath();
@@ -851,27 +873,30 @@ const START_MARKER = "<!-- neuvikon:start -->";
 const END_MARKER = "<!-- neuvikon:end -->";
 const INSTRUCTION_BODY = `## Neuvikon ticket tracking
 
-When the user hands you a Neuvikon ticket — text beginning with a reference like
-\`EWWQ-1:\` — run this before you start working on it:
-
-    npx neuvikon start --ticket EWWQ-1
-
-Before doing anything else, judge how difficult the ticket actually is, and
-match both your model and your reasoning effort to it instead of defaulting
-to maximum for everything:
+**The moment you receive a Neuvikon ticket — text beginning with a reference
+like \`EWWQ-1:\` — before reading any file, before running \`start\`, before
+anything else: judge its difficulty and act on it.** This is a real step, not
+background bookkeeping — if your CLI supports switching model or reasoning
+effort mid-session (Claude Code: \`/model\`, \`/effort\`; Codex: \`/model\`,
+\`/reasoning\`), the command to do that is the literal first thing you send,
+on its own, before you touch the ticket:
 
 - Small, mechanical change — swapping button placement, a copy/label edit, a
-  trivial styling tweak, a one-line config change: switch to a cheaper/faster
-  model if your CLI supports doing so mid-session (e.g. \`/model haiku\`), and
-  drop reasoning effort to its lowest setting (e.g. \`/effort low\` in Claude
-  Code, \`/reasoning low\` in Codex). There's no reason to spend a frontier
-  model thinking hard about something this small.
+  trivial styling tweak, a one-line config change: send \`/model haiku\` (or
+  your CLI's equivalent cheap/fast model) and \`/effort low\` (or
+  \`/reasoning low\`) right now, as their own messages, before doing anything
+  else. There's no reason to spend a frontier model thinking hard about
+  something this small, and downgrading after you've already started reading
+  code is too late to save anything.
 - Needs real design judgment, touches multiple systems, or you're unsure:
   stay on your current model and effort level — don't downgrade either just
   to save cost on something that actually needs it.
+- Your CLI doesn't expose a way to change model or effort mid-session: skip
+  this and go straight to the ticket.
 
-If your CLI doesn't expose a way to change model or effort mid-session,
-skip this and just work the ticket.
+Only after that's decided, run this before you start working on the ticket:
+
+    npx neuvikon start --ticket EWWQ-1
 
 Before you start, and any time you need more context, read the ticket's
 project pages — this is the project's accumulated knowledge, not just this

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "neuvikon",
-  "version": "0.2.28",
+  "version": "0.2.30",
   "description": "Tell Neuvikon which ticket your coding agent is working on.",
   "keywords": [
     "neuvikon",