WIP: Combined Backups for 6 branches

.agents/skills/handover/SKILL.md

@@ -7,7 +7,7 @@ description: Prepare a concise evidence-backed Database handover without automat
 
 1. Inspect branch, upstream, worktrees, status, relevant diffs, and recent commits.
 2. Run `npm run workflow:lifecycle -- --phase handoff --write-evidence`.
-3. Run the smallest proportionate offline verification; prefer `npm run verify:pr-local` for non-trivial ready work.
+3. Run the smallest proportionate offline verification; prefer `npm run verify:pr-local` for non-trivial ready work. Mandate running `verification-router` (or the specific applicable gate) before claiming a PR is green, and never report exit 0 alone (paste the decisive proof line).
 4. Separate intended changes from unrelated dirty work and list generated artifacts.
 5. Summarize files, checks, failures, skipped gates, risks, and the exact next action.
 6. Do not commit, push, open a PR, merge, or call providers unless explicitly requested and authorized.

.agents/skills/ledger/SKILL.md

@@ -5,7 +5,7 @@ description: Sweep the current session, repo/task context, local task files, and
 
 # Ledger
 
-1. Target `docs/outstanding-issues.md` only — never `docs/branch-review-ledger.md` or the `ledger:*` npm scripts, which belong to the review ledger.
+1. Target `docs/outstanding-issues.md` only — never `docs/branch-review-ledger.md` or the `ledger:*` npm scripts, which belong to the review ledger. Agents must revalidate against `origin/main:docs/outstanding-issues.md` (or fast-forward first) before answering `/issues` prompts to avoid proposing stale work.
 2. Sweep the full chat context, git state, files touched this session, and local task notes for deferred work, unresolved TODO/"should"/"follow up" statements, blockers, and unmet acceptance criteria. Remote task stores (GitHub, MCP) stay approval-gated.
 3. Report before writing, in order: confirmed outstanding tasks, risky/blocked areas, then up to three `/ledger` improvement suggestions.
 4. Keep only useful high-confidence items; dedupe against existing open rows by intent and reference duplicates as `#NNN`.

.claude/skills/issues/SKILL.md

@@ -44,7 +44,7 @@ Parse the intent from natural language too — the exact syntax is a convenience
  with today's date and a one-line outcome. In the recommended queue, remove only that ID from any
  composite source and rewrite the row for the remaining open work; remove the whole row only when
  no referenced open ID remains, then close the order gap. Archive, never delete.
-- **`/issues update <id> <text>`** — edit an open row's summary or next action in place.
+- **`/issues update <id> <text>`** — edit any open planning or evidence field in place.
 - **`/issues capture`** — scan the current session for recommendations, follow-ups, deferrals, and
  unfixed problems that surfaced but were not recorded. Propose them as a numbered list and add the
  confirmed ones (dedupe against existing rows first — do not re-add something already tracked).
@@ -54,7 +54,9 @@ Parse the intent from natural language too — the exact syntax is a convenience
 When a task in _any_ session ends with unresolved follow-ups — a deferred fix, a "revisit when X"
 recommendation, a known risk, a TODO you had to leave — offer to record them here before the context
 is lost. That is what makes this a memory rather than a static list. Prefer one crisp row over a
-paragraph; put the smallest next action in **Detail / next action**.
+paragraph. Put the buildable problem in **Group / main issue**, the prerequisite in **Before
+starting**, the acceptance result in **Done when**, and retain supporting proof, source, and added
+date in the collapsed **Evidence** details cell.
 
 ## Writing rules
 
@@ -67,6 +69,12 @@ npm run issues:done -- '#151' --outcome "Resolved 2026-07-31 by PR #1494. …"
 npm run issues:update -- '#151' --detail "…"
 ```
 
+Planning fields are optional on the CLI but should be supplied when known: `--status`, `--group`,
+`--before`, `--codex`, `--checks`, `--external`, and `--done`. `--summary` writes the main issue and
+the backwards-compatible `--detail` flag writes the collapsed evidence context. The writer safely
+combines priority/status and group/main issue, and bundles context/source/date behind the expandable
+control. Missing estimates are recorded explicitly for later triage; they are never invented.
+
 It allocates the id from the marker and bumps it, appends into the **open** table (never the
 archive), moves rather than copies on `done`, reshapes to each table's width, escapes `|`, and
 re-runs the gate against its own output — refusing to write anything CI would reject. Hand-editing

.claude/skills/ledger/SKILL.md

@@ -76,14 +76,20 @@ hand-edit** (hand edits are what the gate exists to reject):
 npm run issues:add -- --pri P2 --type issue --summary "<title>" --detail "<detail>" --source "session YYYY-MM-DD /ledger sweep"
 ```
 
-Field mapping into the row (the repo ledger has fixed columns; the extra fields ride in Detail):
+Field mapping into the expanded open-item row:
 
-- `importance` → **Pri**: P0 and P1 → `P1` (note "was P0" in Detail), P2 → `P2`, P3 → `P3`.
+- `importance` → **Pri**: P0 and P1 → `P1` (note "was P0" in Context), P2 → `P2`, P3 → `P3`.
 - `category` → **Type**: bug/risk → `issue`; follow-up/refactor/infrastructure/hygiene → `task`;
  idea → `rec`.
-- **Detail** = `next_step`, then `Why:`, `Context:`, `Owner:`, `Confidence:`, and
- `Depends on:` as short clauses. Escape `|` as `\|`. Keep it one crisp cell, not a paragraph.
+- `status` is paired with priority in **Priority / status**; the owning subsystem and `title` are
+ paired in **Group / main issue**.
+- `dependencies` and approvals → **Before starting**; estimates → **Codex**, **Checks / CI**, and
+ **External input / time**; acceptance criteria → **Done when**.
+- The collapsed **Evidence** cell contains `Why:`, triggering context, owner, confidence,
+ constraints, supporting proof, source, and added date. The backwards-compatible CLI flag for its
+ context field is `--detail`.
 - **Source** = `session YYYY-MM-DD /ledger sweep` plus the doc/PR/file:line when one exists.
+- Escape `|` as `\|` in every value. Never invent an estimate; use `Estimate before start`.
 
 If **no** new items survive the filter, append one dated line to the notes block above the Open
 items table: `> Ledger sweep YYYY-MM-DD: no new outstanding items found.`

.cursor/settings.json

@@ -5,6 +5,9 @@
  },
  "figma": {
  "enabled": true
+ },
+ "mem0": {
+ "enabled": false
  }
  }
 }