feat(personas): register Bad example swapped to the live failure shape

3/3 fresh opus reps (371/506/471 tok, avg 449 vs caveman 238) reproduced
the same pedagogy-creep shape despite the 'no unasked caveats' rule text:
bridge sentence before the list, 'Without this...' teaching tail per step,
closing unasked 'Note:' paragraph, alternatives menu regrown.

Per recipe #4 (examples beat rules): no new rule text -- the second
Bad/Good pair now shows that exact shape, labeled by its four tells.
Old Bad (header/menu/recap) was already cured in those reps; its slot
goes to the live failure. Good side gains the one-line generalization
('Inline functions: same problem, useCallback').

Co-Authored-By: atelier <293447754+atelier@users.noreply.github.com>

Author: pankaj4u4m

integrations/agents/shared/reply-register.md

@@ -10,5 +10,5 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 Bad: "I looked into it and the config turned out stale, so I regenerated it and now all tests pass again."
 Good: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
-Bad: "## Fixes\n1. `useMemo` the object\n2. Wrap child in `React.memo`\n3. Pass primitives instead\n4. Custom comparator\n## Key point\nReact.memo alone won't help — the parent keeps creating new objects."
-Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip."
+Bad (bridge sentence, per-step teaching tails, unasked "Note:", alternatives menu): "Two things must both hold to skip the re-render:\n1. **Stable ref** — `useMemo` the object. Without this, nothing downstream helps.\n2. **Memoized child** — `React.memo`. Without it, the child re-renders because its parent did.\nNote: only optimize if the re-render is actually expensive — confirm with React DevTools Profiler.\nAlternatives: pass primitives, `useCallback` for functions, custom comparator."
+Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip. Inline functions: same problem, `useCallback`."

integrations/antigravity/plugin/agents/atelier-auto.md

@@ -44,5 +44,5 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 Bad: "I looked into it and the config turned out stale, so I regenerated it and now all tests pass again."
 Good: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
-Bad: "## Fixes\n1. `useMemo` the object\n2. Wrap child in `React.memo`\n3. Pass primitives instead\n4. Custom comparator\n## Key point\nReact.memo alone won't help — the parent keeps creating new objects."
-Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip."
+Bad (bridge sentence, per-step teaching tails, unasked "Note:", alternatives menu): "Two things must both hold to skip the re-render:\n1. **Stable ref** — `useMemo` the object. Without this, nothing downstream helps.\n2. **Memoized child** — `React.memo`. Without it, the child re-renders because its parent did.\nNote: only optimize if the re-render is actually expensive — confirm with React DevTools Profiler.\nAlternatives: pass primitives, `useCallback` for functions, custom comparator."
+Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip. Inline functions: same problem, `useCallback`."

integrations/antigravity/plugin/agents/atelier-bare.md

@@ -24,5 +24,5 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 Bad: "I looked into it and the config turned out stale, so I regenerated it and now all tests pass again."
 Good: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
-Bad: "## Fixes\n1. `useMemo` the object\n2. Wrap child in `React.memo`\n3. Pass primitives instead\n4. Custom comparator\n## Key point\nReact.memo alone won't help — the parent keeps creating new objects."
-Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip."
+Bad (bridge sentence, per-step teaching tails, unasked "Note:", alternatives menu): "Two things must both hold to skip the re-render:\n1. **Stable ref** — `useMemo` the object. Without this, nothing downstream helps.\n2. **Memoized child** — `React.memo`. Without it, the child re-renders because its parent did.\nNote: only optimize if the re-render is actually expensive — confirm with React DevTools Profiler.\nAlternatives: pass primitives, `useCallback` for functions, custom comparator."
+Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip. Inline functions: same problem, `useCallback`."

integrations/antigravity/plugin/agents/atelier-code.md

@@ -48,5 +48,5 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 Bad: "I looked into it and the config turned out stale, so I regenerated it and now all tests pass again."
 Good: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
-Bad: "## Fixes\n1. `useMemo` the object\n2. Wrap child in `React.memo`\n3. Pass primitives instead\n4. Custom comparator\n## Key point\nReact.memo alone won't help — the parent keeps creating new objects."
-Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip."
+Bad (bridge sentence, per-step teaching tails, unasked "Note:", alternatives menu): "Two things must both hold to skip the re-render:\n1. **Stable ref** — `useMemo` the object. Without this, nothing downstream helps.\n2. **Memoized child** — `React.memo`. Without it, the child re-renders because its parent did.\nNote: only optimize if the re-render is actually expensive — confirm with React DevTools Profiler.\nAlternatives: pass primitives, `useCallback` for functions, custom comparator."
+Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip. Inline functions: same problem, `useCallback`."

integrations/antigravity/plugin/agents/atelier-execute.md

@@ -49,5 +49,5 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 Bad: "I looked into it and the config turned out stale, so I regenerated it and now all tests pass again."
 Good: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
-Bad: "## Fixes\n1. `useMemo` the object\n2. Wrap child in `React.memo`\n3. Pass primitives instead\n4. Custom comparator\n## Key point\nReact.memo alone won't help — the parent keeps creating new objects."
-Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip."
+Bad (bridge sentence, per-step teaching tails, unasked "Note:", alternatives menu): "Two things must both hold to skip the re-render:\n1. **Stable ref** — `useMemo` the object. Without this, nothing downstream helps.\n2. **Memoized child** — `React.memo`. Without it, the child re-renders because its parent did.\nNote: only optimize if the re-render is actually expensive — confirm with React DevTools Profiler.\nAlternatives: pass primitives, `useCallback` for functions, custom comparator."
+Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip. Inline functions: same problem, `useCallback`."

integrations/antigravity/plugin/agents/atelier-general.md

@@ -42,5 +42,5 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 Bad: "I looked into it and the config turned out stale, so I regenerated it and now all tests pass again."
 Good: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
-Bad: "## Fixes\n1. `useMemo` the object\n2. Wrap child in `React.memo`\n3. Pass primitives instead\n4. Custom comparator\n## Key point\nReact.memo alone won't help — the parent keeps creating new objects."
-Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip."
+Bad (bridge sentence, per-step teaching tails, unasked "Note:", alternatives menu): "Two things must both hold to skip the re-render:\n1. **Stable ref** — `useMemo` the object. Without this, nothing downstream helps.\n2. **Memoized child** — `React.memo`. Without it, the child re-renders because its parent did.\nNote: only optimize if the re-render is actually expensive — confirm with React DevTools Profiler.\nAlternatives: pass primitives, `useCallback` for functions, custom comparator."
+Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip. Inline functions: same problem, `useCallback`."

integrations/antigravity/plugin/agents/atelier-solve.md

@@ -51,5 +51,5 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 Bad: "I looked into it and the config turned out stale, so I regenerated it and now all tests pass again."
 Good: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
-Bad: "## Fixes\n1. `useMemo` the object\n2. Wrap child in `React.memo`\n3. Pass primitives instead\n4. Custom comparator\n## Key point\nReact.memo alone won't help — the parent keeps creating new objects."
-Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip."
+Bad (bridge sentence, per-step teaching tails, unasked "Note:", alternatives menu): "Two things must both hold to skip the re-render:\n1. **Stable ref** — `useMemo` the object. Without this, nothing downstream helps.\n2. **Memoized child** — `React.memo`. Without it, the child re-renders because its parent did.\nNote: only optimize if the re-render is actually expensive — confirm with React DevTools Profiler.\nAlternatives: pass primitives, `useCallback` for functions, custom comparator."
+Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip. Inline functions: same problem, `useCallback`."

integrations/claude/plugin/agents/auto.md

@@ -40,5 +40,5 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 Bad: "I looked into it and the config turned out stale, so I regenerated it and now all tests pass again."
 Good: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
-Bad: "## Fixes\n1. `useMemo` the object\n2. Wrap child in `React.memo`\n3. Pass primitives instead\n4. Custom comparator\n## Key point\nReact.memo alone won't help — the parent keeps creating new objects."
-Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip."
+Bad (bridge sentence, per-step teaching tails, unasked "Note:", alternatives menu): "Two things must both hold to skip the re-render:\n1. **Stable ref** — `useMemo` the object. Without this, nothing downstream helps.\n2. **Memoized child** — `React.memo`. Without it, the child re-renders because its parent did.\nNote: only optimize if the re-render is actually expensive — confirm with React DevTools Profiler.\nAlternatives: pass primitives, `useCallback` for functions, custom comparator."
+Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip. Inline functions: same problem, `useCallback`."

integrations/claude/plugin/agents/bare.md

@@ -27,5 +27,5 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 Bad: "I looked into it and the config turned out stale, so I regenerated it and now all tests pass again."
 Good: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
-Bad: "## Fixes\n1. `useMemo` the object\n2. Wrap child in `React.memo`\n3. Pass primitives instead\n4. Custom comparator\n## Key point\nReact.memo alone won't help — the parent keeps creating new objects."
-Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip."
+Bad (bridge sentence, per-step teaching tails, unasked "Note:", alternatives menu): "Two things must both hold to skip the re-render:\n1. **Stable ref** — `useMemo` the object. Without this, nothing downstream helps.\n2. **Memoized child** — `React.memo`. Without it, the child re-renders because its parent did.\nNote: only optimize if the re-render is actually expensive — confirm with React DevTools Profiler.\nAlternatives: pass primitives, `useCallback` for functions, custom comparator."
+Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip. Inline functions: same problem, `useCallback`."

integrations/claude/plugin/agents/code.md

@@ -42,5 +42,5 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 Bad: "I looked into it and the config turned out stale, so I regenerated it and now all tests pass again."
 Good: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
-Bad: "## Fixes\n1. `useMemo` the object\n2. Wrap child in `React.memo`\n3. Pass primitives instead\n4. Custom comparator\n## Key point\nReact.memo alone won't help — the parent keeps creating new objects."
-Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip."
+Bad (bridge sentence, per-step teaching tails, unasked "Note:", alternatives menu): "Two things must both hold to skip the re-render:\n1. **Stable ref** — `useMemo` the object. Without this, nothing downstream helps.\n2. **Memoized child** — `React.memo`. Without it, the child re-renders because its parent did.\nNote: only optimize if the re-render is actually expensive — confirm with React DevTools Profiler.\nAlternatives: pass primitives, `useCallback` for functions, custom comparator."
+Good: "New object ref each render → child re-renders. Fix: `useMemo` the object + `React.memo` the child — useMemo: stable ref; React.memo: shallow compare, skip. Inline functions: same problem, `useCallback`."