feat: introduce Wiggum Break as named circuit breaker

Replaces generic "circuit breaker" with "Wiggum Break" — policy enforcement
halt condition named after Chief Wiggum (policy + Ralph Loop's dad).
Hard breaks (immediate halt) and soft breaks (finish then halt) with
wiggum.break event type. Updated both papers and shadow-detection skill.

paper/archeflow.tex

@@ -395,17 +395,28 @@ Beyond individual archetype dysfunction, ArcheFlow monitors for
   proposal's file list.
 \end{description}
 
-\subsection{Policy Boundaries}
+\subsection{Policy Boundaries and the Wiggum Break}
 
-The third layer enforces operational limits:
-\begin{itemize}
-  \item \textbf{Budget enforcement}: per-run token limits with per-agent
-  tracking.
-  \item \textbf{Cycle limits}: maximum PDCA iterations (1/2/3 for
-  fast/standard/thorough).
-  \item \textbf{Checkpoint frequency}: mandatory progress saves to prevent
-  lost work on interruption.
-\end{itemize}
+The third layer enforces operational limits through budget gates, cycle
+limits, and checkpoint policies. When limits are exceeded, the system
+triggers a \emph{Wiggum Break}\footnote{Named after Chief Wiggum from
+\emph{The Simpsons}---a nod to both ``policy enforcement'' and the
+Ralph Loop plugin for Claude Code.}---a circuit breaker that halts
+execution, saves state, and reports to the user.
+
+Wiggum Breaks are classified as \emph{hard} (halt immediately) or
+\emph{soft} (finish current task, then halt):
+
+\begin{description}
+  \item[Hard breaks]: 3 consecutive agent failures, 3 consecutive shadow
+  detections in one run, test suite broken after merge, 2+ oscillating
+  findings.
+  \item[Soft breaks]: convergence score $< 0.5$ for 2 consecutive cycles,
+  findings unchanged between cycles, budget $> 95\%$ spent.
+\end{description}
+
+Each Wiggum Break emits a \texttt{wiggum.break} event capturing the
+trigger, run state, and unresolved findings for post-run analysis.
 
 \subsection{Connection to the Assistant Axis}