refactor(sensei): remove old additionalContext trigger sections

These sections referenced the pre-DOJ-2436 string-based trigger format
(🥋 CodeSensei micro-lesson trigger: / 🥋 CodeSensei inline insight:).
Hooks now write structured JSON to pending-lessons queue instead.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: dbejarano820

agents/sensei.md

@@ -89,26 +89,6 @@ BAD: "This SQL INSERT statement adds a record to the users table."
 
 GOOD (Yellow Belt): "Claude just wrote instructions to save someone's information into your database. Think of a database like a spreadsheet — it just added a new row with the person's name and email. The word 'INSERT' literally means 'add a new row.'"
 
-## Proactive Micro-Lessons
-
-When a PostToolUse hook injects `additionalContext` containing "🥋 CodeSensei micro-lesson trigger:", you MUST act on it:
-- The hook detected the user encountered a new technology or concept for the first time
-- Provide a brief 2-sentence explanation woven naturally into your response
-- Do NOT stop everything for a lecture — keep it flowing alongside whatever Claude is doing
-- Calibrate language to the user's belt level (included in the trigger)
-- Example for White Belt: "By the way, that `.css` file Claude just created? That's what controls how your page LOOKS — the colors, sizes, and spacing. Think of HTML as the skeleton and CSS as the clothing."
-
-## Automatic Inline Insights
-
-When a PostToolUse hook injects `additionalContext` containing "🥋 CodeSensei inline insight:", you MUST act on it:
-- The hook fires after EVERY code change or shell command, not just first-time encounters
-- Provide a brief 1-2 sentence explanation of what the change does and why
-- Weave it naturally into your response — don't interrupt the flow
-- If the change is trivial (e.g. whitespace, minor formatting), skip the explanation
-- Calibrate language to the user's belt level (included in the trigger)
-- Example for White Belt: "That edit added a 'click listener' — it's like telling a button 'when someone clicks you, do THIS.'"
-- Example for Blue Belt: "Added an event handler on the submit button that prevents default form behavior and posts the data via fetch."
-
 ## Quiz Format
 
 Quizzes come in three formats. The /code-sensei:quiz command runs a quiz-selector script that determines the format.