@jcode.labs/ragmir 4.2.1 → 5.0.0

package/skills/ragmir-audio-summary/forge-voice.sh

@@ -1,150 +0,0 @@
-#!/usr/bin/env bash
-# Render a Ragmir audio-summary text file to MP3. The text is a throwaway intermediate written
-# outside the repository by the skill. The final audio should normally be written under .ragmir/audio.
-#
-# Engine via TTS_ENGINE (auto|edge|xtts|say|piper); default "auto" matches the global Voice Forge
-# quality path:
-#   edge  - edge-tts neural voices, single request (online). Default; clean on normal text.
-#           Set TTS_SEGMENT=1 to render sentence-by-sentence for long-text truncation.
-#   xtts  - local Coqui XTTS-v2 when installed.
-#   say   - macOS built-in, offline, clean but robotic.
-#   piper - local neural TTS.
-#
-# Usage:  forge-voice.sh <text-file> [voice]
-# Env:    OUT_MP3                 explicit mp3 output path
-#         TTS_ENGINE              force an engine (default: auto)
-#         TTS_VOICE               voice/speaker (engine-specific); the [voice] arg overrides it
-#         TTS_RATE                edge-tts speed delta, default +0%
-#         TTS_SEGMENT=1           edge: render sentence-by-sentence
-#         XTTS_SPEAKER            xtts preset speaker (default Ana Florence)
-#         PIPER_MODEL             piper onnx model path
-#         KEEP_TEXT=1             keep the source text file after a successful render
-set -euo pipefail
-
-TXT="${1:?usage: forge-voice.sh <text-file> [voice]}"
-[ -f "$TXT" ] || { echo "error: file not found: $TXT" >&2; exit 1; }
-VOICE="${2:-${TTS_VOICE:-}}"
-ENGINE="${TTS_ENGINE:-auto}"
-OUT_FINAL="${OUT_MP3:-${TXT%.txt}.mp3}"
-OUTBASE="${OUT_FINAL%.mp3}"
-
-cleanup() {
-  [ "${KEEP_TEXT:-0}" = "1" ] || rm -f "$TXT"
-  rm -f "${OUTBASE}.wav" "${OUTBASE}.aiff"
-}
-trap cleanup EXIT
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-XTTS_PY="${XTTS_PY:-$HOME/.local/share/voice-forge/xtts/bin/python}"
-XTTS_HELPER="$SCRIPT_DIR/xtts-voice.py"
-
-xtts_ready() { [ -x "$XTTS_PY" ] && [ -f "$XTTS_HELPER" ]; }
-
-finish() {
-  echo "$1"
-  exit 0
-}
-
-to_mp3() {
-  local src="$1" out="${OUTBASE}.mp3"
-  if ! command -v ffmpeg >/dev/null 2>&1; then
-    rm -f "$src"
-    echo "error: ffmpeg is required to convert local TTS output to mp3" >&2
-    exit 1
-  fi
-  if ffmpeg -y -loglevel error -i "$src" -ac 1 -c:a libmp3lame -q:a 4 "$out"; then
-    rm -f "$src"
-    finish "$out"
-  fi
-  rm -f "$src" "$out"
-  echo "error: failed to convert local TTS output to mp3" >&2
-  exit 1
-}
-
-if [ "$ENGINE" = "edge" ] || [ "$ENGINE" = "auto" ]; then
-  if command -v edge-tts >/dev/null 2>&1; then
-    OUT="${OUTBASE}.mp3"
-    SPLIT="$SCRIPT_DIR/split-lines.py"
-    voice="${VOICE:-fr-FR-DeniseNeural}"
-    rate="${TTS_RATE:-+0%}"
-    if [ "${TTS_SEGMENT:-0}" = "1" ] && [ -f "$SPLIT" ] \
-       && command -v ffmpeg >/dev/null 2>&1 && command -v python3 >/dev/null 2>&1; then
-      TMP="$(mktemp -d)"
-      ffmpeg -y -loglevel error -f lavfi -i anullsrc=r=24000:cl=mono -t 0.28 \
-        -c:a libmp3lame -q:a 4 "$TMP/sil.mp3"
-      i=0
-      : > "$TMP/list.txt"
-      while IFS= read -r line; do
-        [ -z "$line" ] && continue
-        i=$((i + 1))
-        if edge-tts --text "$line" --voice "$voice" --rate="$rate" \
-          --write-media "$TMP/seg_$i.mp3" >/dev/null 2>&1; then
-          printf "file '%s'\n" "$TMP/seg_$i.mp3" >> "$TMP/list.txt"
-          printf "file '%s'\n" "$TMP/sil.mp3" >> "$TMP/list.txt"
-        else
-          echo "warn: edge-tts failed on a sentence, skipping it" >&2
-        fi
-      done < <(python3 "$SPLIT" "$TXT")
-      ffmpeg -y -loglevel error -f concat -safe 0 -i "$TMP/list.txt" \
-        -ac 1 -c:a libmp3lame -q:a 4 "$OUT"
-      rm -rf "$TMP"
-      finish "$OUT"
-    fi
-    edge-tts --file "$TXT" --voice "$voice" --rate="$rate" --write-media "$OUT" >/dev/null
-    finish "$OUT"
-  fi
-  if [ "$ENGINE" = "edge" ]; then
-    echo "error: TTS_ENGINE=edge but edge-tts not installed (pipx install edge-tts)" >&2
-    exit 1
-  fi
-fi
-
-if [ "$ENGINE" = "xtts" ] || { [ "$ENGINE" = "auto" ] && xtts_ready; }; then
-  if ! xtts_ready; then
-    echo "error: TTS_ENGINE=xtts but venv/helper missing ($XTTS_PY)" >&2
-    exit 1
-  fi
-  WAV="${OUTBASE}.wav"
-  if [ -n "$VOICE" ]; then
-    COQUI_TOS_AGREED=1 "$XTTS_PY" "$XTTS_HELPER" "$TXT" "$WAV" "$VOICE" >&2
-  else
-    COQUI_TOS_AGREED=1 "$XTTS_PY" "$XTTS_HELPER" "$TXT" "$WAV" >&2
-  fi
-  to_mp3 "$WAV"
-fi
-
-if [ "$ENGINE" = "say" ] || [ "$ENGINE" = "auto" ]; then
-  if command -v say >/dev/null 2>&1; then
-    AIFF="${OUTBASE}.aiff"
-    say -v "${VOICE:-Jacques}" -f "$TXT" -o "$AIFF" 2>/dev/null || say -f "$TXT" -o "$AIFF"
-    to_mp3 "$AIFF"
-  fi
-  if [ "$ENGINE" = "say" ]; then
-    echo "error: TTS_ENGINE=say but 'say' not available" >&2
-    exit 1
-  fi
-fi
-
-if [ "$ENGINE" = "piper" ] || [ "$ENGINE" = "auto" ]; then
-  if command -v piper >/dev/null 2>&1; then
-    WAV="${OUTBASE}.wav"
-    piper -m "${PIPER_MODEL:-fr_FR-siwis-medium.onnx}" -f "$WAV" < "$TXT"
-    to_mp3 "$WAV"
-  fi
-  if [ "$ENGINE" = "piper" ]; then
-    echo "error: TTS_ENGINE=piper but piper not installed (pip install piper-tts)" >&2
-    exit 1
-  fi
-fi
-
-cat >&2 <<'EOF'
-error: no TTS engine available. Install one:
-  edge-tts (cleanest, online): pipx install edge-tts
-  XTTS-v2 (local):
-    uv venv --python 3.11 ~/.local/share/voice-forge/xtts
-    uv pip install --python ~/.local/share/voice-forge/xtts/bin/python \
-       coqui-tts 'transformers>=4.57,<5' 'torch==2.8.*' 'torchaudio==2.8.*'
-  piper (local): pip install piper-tts
-  ffmpeg: required for local engine MP3 conversion
-EOF
-exit 127

package/skills/ragmir-audio-summary/listening-style.md

@@ -1,92 +0,0 @@
-# Listening Style Guide
-
-Reference for the narration-writing step of `ragmir-audio-summary`. This file defines how to turn
-retrieved evidence into spoken text that a TTS engine can pronounce and a listener can follow and
-remember in one pass. There is no second chance to re-read audio.
-
-## Pacing And Duration
-
-- Conversational narration lands around **130-150 words per minute**. Plan on **140 words/minute**
-  as the working estimate.
-- Estimated duration = `word count / 140`. Keep a short narration under the target; never pad to
-  reach a target.
-- Per-format word budgets (use them as ceilings, not goals):
-
-| Format | Target duration | Word budget |
-| --- | --- | --- |
-| Micro-brief | ~60-90 s | 150-220 words |
-| Brief standard | ~3-5 min | 450-750 words |
-| Dossier long | ~10-20 min | 1500-3000 words |
-
-If the relevant material does not fill the budget, stop earlier. Padding makes audio undrinkable.
-
-## Sentence Shape
-
-- One idea per sentence. If you need "and" twice, split the sentence.
-- Aim for **20 words or fewer** per sentence. A few longer sentences are fine for rhythm; never chain
-  three long ones in a row.
-- Prefer subject-verb-object order. TTS engines and the human ear both handle it best.
-- Avoid stacked subordinate clauses and parentheticals. They trip the reader and the listener.
-
-  Before: "Le contrat, qui avait été signé, malgré des réserves émises tardivement, par les deux
-  parties, prévoit une rupture."
-
-  After: "Les deux parties ont signé le contrat, avec des réserves de dernière minute. Il prévoit
-  une rupture."
-
-## Punctuation For TTS
-
-Punctuation is the only cue a TTS engine has for pausing. Use it deliberately.
-
-- **Comma** `,`: short micro-pause. Use it to separate clauses and ease breathing points.
-- **Period** `.`: full pause. End sentences here. Favour periods over commas when in doubt.
-- **Ellipsis** `…`: deliberate longer pause. Use it before the answer in an active-recall question,
-  so the listener gets a beat to think (about three seconds).
-- **Colon** `:`: read as a mild pause; acceptable when introducing a short enumeration spoken as
-  prose, but prefer rephrasing into a plain sentence.
-- **Semicolon** `;`: avoid. Engines hesitate inconsistently. Split into two sentences.
-- **Exclamation** `!`: avoid for TTS. It can trigger an unnatural spike in pitch.
-- **Question mark** `?`: use it for the active-recall questions; the engine raises intonation
-  naturally.
-
-## Pronounceability
-
-Anything the engine might misread must be rewritten for the ear.
-
-- **Acronyms**: expand on first use, then use the short form if it is pronounceable. "Le RGPD, le
-  Règlement Général sur la Protection des Données, ..."
-- **Numbers**: write them the way they should be read. "1500" can read as "mille cinq cents" or
-  "quinze cents". Write the intended form. For money, spell the currency: "douze mille euros".
-- **Symbols**: rewrite in words. `&` becomes "et", `%` becomes "pour cent", `->` becomes "mène à".
-- **Dates and times**: write them fully. "Le quinze mars deux mille vingt-cinq", not "2025-03-15".
-- **URLs, paths, code**: never read them aloud. Paraphrase: "le fichier de configuration du
-  projet" instead of `ragmir/config.json`.
-- **Foreign terms**: if the term has no clean translation, introduce it once and keep it.
-
-## Anti-Patterns
-
-Avoid these. They are the main causes of "imbuvable" audio.
-
-- **Jargon without setup.** If a technical term is needed, define it in one short clause first.
-- **Spoken bullet lists.** Enumerations read aloud are exhausting. Convert lists into flowing
-  sentences with signposting ("D'abord…, Ensuite…, Pour finir…"). See `narration-templates.md`.
-- **Meta-commentary.** Drop "Dans ce résumé, nous allons parler de…". Open on the substance.
-- **Padding to reach a duration.** Restating the same idea in more words lowers density and respect
-  for the listener. Shorter is better than watered down.
-- **Reading raw source passages.** The audio is a synthesis, not a quote dump. Reformulate in plain
-  speech and keep the citation in your working notes, not in the narration.
-- **Overload.** More than ~4 new ideas in a brief is too many to retain. Group, merge, or defer.
-
-## Language
-
-- Write the narration in the same language passed to `--lang` (`fr` by default; `en`, `es`, `ja`,
-  `th`, and `zh` are also supported).
-- Match the working language the user used when asking for the summary when it is one of the
-  supported languages.
-- Keep numerals, units, and proper nouns pronounceable in the target language.
-
-## Self-Check Before Rendering
-
-Read the draft aloud once at a normal pace. If you stumble or run out of breath on a sentence, it is
-too long or too dense. Fix it, then estimate the duration with `word count / 140` and confirm it
-matches the chosen format's budget.

package/skills/ragmir-audio-summary/narration-templates.md

@@ -1,162 +0,0 @@
-# Narration Templates
-
-Reference for the drafting step of `ragmir-audio-summary`. These are **thinking skeletons**, not
-output formatting. The final narration is plain flowing prose with no markdown, headings, bullets,
-tables, SSML, or XML tags. The skeletons below only shape how you order and connect ideas before you
-write the spoken text.
-
-Pick the format chosen in the skill, then fill the skeleton with the evidence that serves the user's
-intent. Drop anything that does not serve the intent. That is how you avoid superfluous data.
-
-## Format Selection Recap
-
-| Format | When to use | Word budget |
-| --- | --- | --- |
-| Micro-brief | Little relevant material, or one clear question | 150-220 words |
-| Brief standard | Moderate material, a few angles worth keeping | 450-750 words |
-| Dossier long | Dense, multi-faceted material needing chapters | 1500-3000 words |
-
-Length follows relevant material. Never pad.
-
----
-
-## Micro-Brief Skeleton
-
-Spoken-prose shape (write it as one flowing passage, not as headings):
-
-1. **Hook + intent**: one sentence naming the subject and why the listener asked.
-2. **Key idea**: the single thing to remember, stated up front (primacy).
-3. **Evidence**: one short, plain-language reason or fact that supports it.
-4. **Uncertainty / caveat**: one sentence if the evidence is partial or stale; omit only if solid.
-5. **Recap + recall**: restate the key idea in other words, then ask one active-recall question,
-   pause with `…`, and give the answer.
-
-Abstract example (do not copy the words, follow the shape):
-
-> "Vous vouliez savoir si la clause de rupture est applicable. Oui, elle l'est, mais seulement après
-> un préavis de trente jours. Le contrat le prévoit explicitement à la section terminaison. En
-> revanche, la date de départ du préavis reste ambiguë, aucun courrier ne la fixe clairement.
-> Retenez donc une chose: rupture possible, préavis de trente jours, point de départ à confirmer.
-> Question: quelle est la durée du préavis prévu? … Trente jours."
-
----
-
-## Brief Standard Skeleton (Pyramid + SCQA)
-
-The standard brief follows Barbara Minto's pyramid: answer first, then supporting points, then
-recap. Wrap it in a short Situation-Complication-Question-Answer opening.
-
-1. **Situation**: one or two sentences framing the context the listener already shares.
-2. **Complication**: the tension, change, or question that prompted the summary.
-3. **Question**: the explicit question the summary answers.
-4. **Answer (the key message)**: the one-to-three points to retain, stated first (primacy).
-5. **Developed points**: each of the two-to-four points expanded in plain speech, grouped with
-   signposting ("D'abord…, Ensuite…, Enfin…"). Proven facts only; separate from inference.
-6. **Uncertainty, risks, decisions, missing documents**: a short passage on what is not yet
-   settled or needs action.
-7. **Recap**: restate the two-to-four key points in compressed form (recency).
-8. **Active recall**: two or three recall questions, each followed by a `…` pause and the answer.
-
-Abstract example (shape only):
-
-> "Le projet a atteint sa phase de test. Le souci, c'est que deux blocages apparaissent en
-> parallèle. Faut-il continuer ou mettre en pause? La réponse tient en deux points: continuez sur
-> le module A, mais mettez en pause le module B. D'abord, le module A passe ses tests sans
-> régression. Ensuite, le module B dépend d'un composant externe encore instable. Ce qu'on ne sait
-> pas encore, c'est la date de livraison du composant externe. Donc retenez: module A en avant,
-> module B en attente, dépendance externe à confirmer. Première question: quel module peut
-> continuer sans risque? … Le module A. Deuxième question: pourquoi mettre en pause le module B? … À cause d'un
-> composant externe instable."
-
----
-
-## Dossier Long Skeleton (Chaptered)
-
-Use only when the material genuinely has several distinct facets. Each chapter is a self-contained
-mini-brief with its own mini-recap, so a listener can step away and come back.
-
-1. **Promise**: what the whole audio covers and the three-to-five landmarks to listen for. State
-   the key message of the whole dossier up front.
-2. **Chapter 1**: signpost the chapter ("Premier point: …"). Give its mini pyramid
-   (answer → evidence → caveat), then a one-sentence mini-recap.
-3. **Chapter 2**: same shape, explicit transition ("Deuxième point: …").
-4. **Continue** for each facet. Keep chapters balanced in length; merge thin ones.
-5. **Global recap**: compress the key message of every chapter into one flowing passage (recency).
-6. **Active recall**: three to five recall questions across the chapters, each with a `…` pause
-   and the answer. Spread the questions across chapters, not only the last one.
-
-Transitions between chapters are essential in long audio. See the signposting catalogue below.
-
-Abstract shape:
-
-> "Ce dossier couvre les trois enjeux du contrat: la durée, la rupture, et les pénalités. En une
-> ligne: la durée est ferme, la rupture est conditionnée, les pénalités sont plafonnées. Premier
-> point: la durée. Le contrat court sur trois ans, fermes. … [chapitre] … Donc, durée ferme de
-> trois ans. Deuxième point: la rupture. … [chapitre] … Donc, rupture possible sous préavis.
-> Troisième point: les pénalités. … [chapitre] … Donc, pénalités plafonnées à dix pour cent. Pour
-> récapituler l'ensemble: trois ans fermes, rupture sous préavis, pénalités plafonnées. Première
-> question: quelle est la durée ferme du contrat? … Trois ans. …"
-
----
-
-## Signposting Catalogue
-
-Signposting is the connective tissue that makes audio followable without visuals. Use these spoken
-transitions instead of lists or headings.
-
-| Move | Spoken cue (FR examples) |
-| --- | --- |
-| Open | "Voici l'essentiel sur…" / "Vous vouliez savoir si… La réponse courte est…" |
-| Enumerate | "D'abord…, Ensuite…, Enfin…" / "Il y a trois points…" (then speak each) |
-| Contrast | "En revanche…" / "Mais attention…" / "À l'inverse…" |
-| Cause / effect | "Parce que…" / "C'est pourquoi…" / "La conséquence est…" |
-| Emphasize | "Retenez ceci…" / "Le point clé, c'est…" |
-| Transition chapter | "Deuxième point…" / "Passons à…" / "Cela nous amène à…" |
-| Mini-recap | "En un mot…" / "Donc, pour ce point…" |
-| Close | "Pour récapituler…" / "En résumé…" |
-| Recall question | "Question: …? … [answer]" |
-
-When enumerating, say the count first ("trois points") then speak each one with "D'abord / Ensuite /
-Enfin". Never read a literal list.
-
----
-
-## Active-Recall Question Catalogue
-
-Active recall forces the listener to retrieve from memory, which anchors retention far better than
-passive re-exposure. Phrase questions so they require **recall**, not recognition (no multiple
-choice, no "est-ce que c'est X?" with the answer embedded).
-
-### By intent
-
-| Intent | What to drill | Question shape (FR examples) |
-| --- | --- | --- |
-| Decide | The decision and its one main driver | "Quelle option recommande-t-on, et pourquoi?" |
-| Learn | The definitions and the one mechanism to remember | "Comment définit-on X, et qu'est-ce qui le déclenche?" |
-| Monitor | The thresholds and the alert condition | "À partir de quel seuil déclenche-t-on l'alerte?" |
-| Compare | The decisive differentiator | "Quelle est la principale différence entre A et B?" |
-| Plan | The next concrete action and its owner | "Quelle est la première action à mener, et par qui?" |
-
-### Rules
-
-- Two to three questions for a brief, three to five for a dossier. One is enough for a micro-brief.
-- Each question targets a key point from the recap, not a peripheral detail.
-- After the question mark, insert `…` so the TTS pause gives the listener a beat to answer silently,
-  then state the answer in the fewest words possible.
-- Do not reveal the answer inside the question. "Le préavis est-il de trente jours?" leaks the
-  answer. Prefer "Quelle est la durée du préavis?".
-
----
-
-## Evidence Separation In Spoken Form
-
-Spoken audio can still respect the Ragmir separation of evidence and inference. Use language cues,
-not formatting:
-
-- Proven fact: state plainly. "Le contrat fixe le préavis à trente jours."
-- Inference: mark it. "Cela suggère que…" / "On peut en déduire que…"
-- Uncertainty: mark it. "Ce qu'on ne sait pas encore, c'est…" / "Reste à confirmer…"
-- Missing document: name it. "Il manque le courrier de notification, donc…"
-- Decision / action: mark it. "La décision à prendre est…"
-
-This keeps the narration honest without leaning on tables or footnotes that audio cannot carry.

package/skills/ragmir-audio-summary/split-lines.py

@@ -1,14 +0,0 @@
-"""Print one sentence per line from a text file.
-
-Used to render long narrations sentence-by-sentence when an engine benefits from segmentation.
-"""
-import re
-import sys
-
-with open(sys.argv[1], encoding="utf-8") as source:
-    raw = source.read()
-text = re.sub(r"\s+", " ", raw).strip()
-for part in re.split(r"(?<=[.!?…])\s+", text):
-    part = part.strip()
-    if part:
-        print(part)

package/skills/ragmir-audio-summary/xtts-voice.py

@@ -1,46 +0,0 @@
-#!/usr/bin/env python3
-"""Render a text file to WAV with Coqui XTTS-v2.
-
-Run with the dedicated venv interpreter:
-  ~/.local/share/voice-forge/xtts/bin/python xtts-voice.py <text.txt> <out.wav> [speaker]
-
-Env: XTTS_SPEAKER (preset name), XTTS_LANG (default "fr").
-"""
-import os
-import sys
-
-os.environ.setdefault("COQUI_TOS_AGREED", "1")
-
-
-def main() -> None:
-    if len(sys.argv) < 3:
-        sys.exit("usage: xtts-voice.py <text.txt> <out.wav> [speaker]")
-    text_file, out_wav = sys.argv[1], sys.argv[2]
-    speaker = sys.argv[3] if len(sys.argv) > 3 else os.environ.get("XTTS_SPEAKER", "Ana Florence")
-    language = os.environ.get("XTTS_LANG", "fr")
-
-    with open(text_file, encoding="utf-8") as handle:
-        text = handle.read().strip()
-    if not text:
-        sys.exit("error: empty text file")
-
-    from TTS.api import TTS
-
-    tts = TTS("tts_models/multilingual/multi-dataset/xtts_v2")
-    speakers = list(getattr(tts, "speakers", None) or [])
-    if speakers and speaker not in speakers:
-        sys.stderr.write(f"speaker '{speaker}' not found; falling back to '{speakers[0]}'\n")
-        speaker = speakers[0]
-
-    tts.tts_to_file(
-        text=text,
-        speaker=speaker,
-        language=language,
-        file_path=out_wav,
-        split_sentences=True,
-    )
-    print(out_wav)
-
-
-if __name__ == "__main__":
-    main()

package/skills/ragmir-legal-dossier/SKILL.md

@@ -1,143 +0,0 @@
----
-name: ragmir-legal-dossier
-description: >-
-  Prepare cited legal-dossier work products from a local Ragmir knowledge base. Use when the user asks
-  for a legal chronology, clause search, dossier summary, evidence table, redaction review, or
-  professional-review handoff grounded in confidential local documents.
----
-
-# Ragmir Legal Dossier
-
-Use this skill for legal or quasi-legal dossiers where confidentiality, evidence separation, and
-professional review matter. This skill does not provide final legal advice. It prepares structured,
-cited work products for review by the user or a qualified professional.
-
-## Safety Rules
-
-- Treat source documents, retrieved passages, party names, dates, amounts, identifiers, and draft
-  outputs as confidential.
-- Keep generated work under `.ragmir/reports/` unless the user explicitly asks for a sanitized
-  tracked artifact.
-- Do not upload documents, snippets, queries, vector stores, or generated drafts to hosted services.
-- Do not present conclusions as legal advice. Separate evidence, inference, uncertainty, and review
-  items.
-- Prefer short cited summaries over long raw extracts.
-- Flag missing documents, unsupported files, stale indexes, and ambiguous source passages.
-
-## Recommended Redaction Patterns
-
-If a legal dossier includes professional secrecy, case identifiers, or French personal identifiers,
-add project-local redaction patterns in `.ragmir/config.json` before indexing. Keep patterns scoped to the
-dossier and test them on non-sensitive samples first.
-
-```json
-{
-  "redaction": {
-    "enabled": true,
-    "builtIn": true,
-    "patterns": [
-      {
-        "name": "case_reference",
-        "pattern": "\\b(?:RG|N°\\s*RG|No\\s*RG)\\s*[:\\-]?\\s*[0-9A-Z/\\-]{4,}\\b",
-        "replacement": "[CASE_REFERENCE]"
-      },
-      {
-        "name": "french_nir",
-        "pattern": "\\b[12]\\s?\\d{2}\\s?\\d{2}\\s?\\d{2}\\s?\\d{3}\\s?\\d{3}\\s?\\d{2}\\b",
-        "replacement": "[FRENCH_NIR]"
-      },
-      {
-        "name": "iban",
-        "pattern": "\\b[A-Z]{2}\\d{2}(?:\\s?[A-Z0-9]){11,30}\\b",
-        "replacement": "[IBAN]"
-      }
-    ]
-  }
-}
-```
-
-After changing redaction rules, rebuild the index:
-
-```bash
-pnpm exec rgr ingest --rebuild
-pnpm exec rgr security-audit --strict
-```
-
-## Retrieval Workflow
-
-Start from readiness checks:
-
-```bash
-pnpm exec rgr doctor
-pnpm exec rgr audit
-pnpm exec rgr audit --unsupported
-pnpm exec rgr security-audit --strict
-```
-
-Then run targeted retrieval passes:
-
-```bash
-pnpm exec rgr search "parties obligations dates amounts" --top-k 8
-pnpm exec rgr search "termination clause liability indemnity notice" --top-k 8
-pnpm exec rgr search "timeline meeting decision approval refusal" --top-k 8
-pnpm exec rgr ask "Which documents support the chronology of events?" --top-k 8
-```
-
-When MCP is available, prefer `ragmir_status`, `ragmir_search`, `ragmir_ask`, `ragmir_audit`, and
-`ragmir_security_audit` so the agent can keep retrieval bounded and cited.
-
-## Output Formats
-
-### Dossier Summary
-
-```markdown
-# Legal Dossier Summary
-
-## Scope
-
-## Evidence Inventory
-
-## Key Facts
-
-## Main Legal Or Contractual Questions
-
-## Risks And Unknowns
-
-## Professional Review Items
-
-## Sources
-```
-
-### Chronology
-
-```markdown
-| Date | Event | Evidence | Confidence | Review item |
-| --- | --- | --- | --- | --- |
-| YYYY-MM-DD |  | source.md chunk=0 | High/Medium/Low |  |
-```
-
-### Clause Review
-
-```markdown
-| Clause topic | Source | Extract summary | Risk | Follow-up |
-| --- | --- | --- | --- | --- |
-| Termination | contract.docx chunk=3 |  |  |  |
-```
-
-### Evidence Gap List
-
-```markdown
-| Missing or weak evidence | Why it matters | Suggested next document |
-| --- | --- | --- |
-|  |  |  |
-```
-
-## Final Response Checklist
-
-Before handing back the work:
-
-- state where the report was saved;
-- list source paths used, not private full passages;
-- mention unsupported, stale, or missing files;
-- include a professional-review section;
-- state whether the artifact is safe to commit or must remain local.