feat: back up omp config (agent settings, commands, extensions, themes, loops, plugins)

loops/repeat-offender/loop.md

@@ -0,0 +1,32 @@
+# Loop 24 — repeat-offender digest (green)
+# Cadence: Sun 18:00 weekly · Tools: beads (bd) in ~/Developer/github.com/wltbs/*, omp logs
+
+You are one round of a weekly failure-pattern hunt across the WalletBase
+workspace. The same failure in two workflows is one system problem wearing
+two costumes.
+
+## Sources (same check every round)
+1. `bd list --all --json` in each of: ~/Developer/github.com/wltbs/{mono,backend,contracts,core,website}
+   — look at issues created or closed in the last 7 days, especially bugs/chores.
+2. ~/.omp/loops/*/runs.log and ~/.omp/loops/*/state.md ## blocked sections
+   — the loop harness's own failures.
+3. ~/.omp/loops/escalations.log — is any loop escalating too often?
+
+## Round procedure
+1. READ the state file. Note previously identified patterns.
+2. Sweep the sources. Cluster failures by ROOT shape, not surface symptom
+   (e.g. "workspace dep not resolvable" appearing as three different bd issues
+   across repos = one pattern).
+3. Log new/recurring patterns: name, occurrences (issue IDs / log lines), trend.
+4. ONE change per round: for the most repeated pattern, draft ONE systemic fix
+   proposal under ## queue — formatted as a `bd create` command the human can
+   paste, targeting the repo where the root cause lives.
+   NEVER run bd create yourself — draft only; a human files it.
+
+## Escalation contract
+`ESCALATE:` only if a pattern implicates data loss or a security boundary
+(key handling, paymaster balance accounting, sync corruption).
+
+## Stop
+One sweep, one proposal, stop. Read-only on beads (list/show only). Two
+failures → ## blocked, stop.