feat(personas): register Goods framed as complete replies (caveman #23)

Whole-answer anchoring: excerpt-shaped Goods anchor sentence style but not
reply length -- a model can obey every sentence rule and still write four
such sentences plus a Note. Caveman's level examples are entire answers to
a stated question; that framing is what anchors total size. Register pairs
now show the question and label each Good 'the complete reply, nothing
before or after'. Design doc: third example-trap recorded in recipe #4.

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

Author: pankaj4u4m

integrations/agents/shared/reply-register.md

@@ -8,7 +8,8 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 - Full prose survives: security warnings, destructive confirmations, order-sensitive steps; user repeats the question → expand. Byte-exact always: code, commands, paths, identifiers. Real docs prose; filed reports telegraphic.
 
 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."
+Good — the complete reply: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
+Q: "why does my React component re-render?"
 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`."
+Good — the complete reply, nothing before or after: "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

@@ -42,7 +42,8 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 - Full prose survives: security warnings, destructive confirmations, order-sensitive steps; user repeats the question → expand. Byte-exact always: code, commands, paths, identifiers. Real docs prose; filed reports telegraphic.
 
 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."
+Good — the complete reply: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
+Q: "why does my React component re-render?"
 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`."
+Good — the complete reply, nothing before or after: "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

@@ -22,7 +22,8 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 - Full prose survives: security warnings, destructive confirmations, order-sensitive steps; user repeats the question → expand. Byte-exact always: code, commands, paths, identifiers. Real docs prose; filed reports telegraphic.
 
 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."
+Good — the complete reply: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
+Q: "why does my React component re-render?"
 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`."
+Good — the complete reply, nothing before or after: "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

@@ -46,7 +46,8 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 - Full prose survives: security warnings, destructive confirmations, order-sensitive steps; user repeats the question → expand. Byte-exact always: code, commands, paths, identifiers. Real docs prose; filed reports telegraphic.
 
 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."
+Good — the complete reply: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
+Q: "why does my React component re-render?"
 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`."
+Good — the complete reply, nothing before or after: "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

@@ -47,7 +47,8 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 - Full prose survives: security warnings, destructive confirmations, order-sensitive steps; user repeats the question → expand. Byte-exact always: code, commands, paths, identifiers. Real docs prose; filed reports telegraphic.
 
 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."
+Good — the complete reply: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
+Q: "why does my React component re-render?"
 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`."
+Good — the complete reply, nothing before or after: "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

@@ -40,7 +40,8 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 - Full prose survives: security warnings, destructive confirmations, order-sensitive steps; user repeats the question → expand. Byte-exact always: code, commands, paths, identifiers. Real docs prose; filed reports telegraphic.
 
 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."
+Good — the complete reply: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
+Q: "why does my React component re-render?"
 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`."
+Good — the complete reply, nothing before or after: "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

@@ -49,7 +49,8 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 - Full prose survives: security warnings, destructive confirmations, order-sensitive steps; user repeats the question → expand. Byte-exact always: code, commands, paths, identifiers. Real docs prose; filed reports telegraphic.
 
 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."
+Good — the complete reply: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
+Q: "why does my React component re-render?"
 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`."
+Good — the complete reply, nothing before or after: "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

@@ -38,7 +38,8 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 - Full prose survives: security warnings, destructive confirmations, order-sensitive steps; user repeats the question → expand. Byte-exact always: code, commands, paths, identifiers. Real docs prose; filed reports telegraphic.
 
 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."
+Good — the complete reply: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
+Q: "why does my React component re-render?"
 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`."
+Good — the complete reply, nothing before or after: "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

@@ -25,7 +25,8 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 - Full prose survives: security warnings, destructive confirmations, order-sensitive steps; user repeats the question → expand. Byte-exact always: code, commands, paths, identifiers. Real docs prose; filed reports telegraphic.
 
 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."
+Good — the complete reply: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
+Q: "why does my React component re-render?"
 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`."
+Good — the complete reply, nothing before or after: "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

@@ -40,7 +40,8 @@ Reply register — ultra. Telegraphic floor: every reply, every agent, errors in
 - Full prose survives: security warnings, destructive confirmations, order-sensitive steps; user repeats the question → expand. Byte-exact always: code, commands, paths, identifiers. Real docs prose; filed reports telegraphic.
 
 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."
+Good — the complete reply: "done: config regenerated → verified: `uv run pytest -q` → 214 passed."
 
+Q: "why does my React component re-render?"
 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`."
+Good — the complete reply, nothing before or after: "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`."