tadforce 0.2.0 → 0.3.0

package/.claude-plugin/marketplace.json

@@ -4,14 +4,14 @@
     "name": "Jihad AZAMI HASSANI"
   },
   "metadata": {
-    "description": "TADForce — technical architecture documents for Salesforce orgs, written by your agent from the org's own metadata."
+    "description": "TADForce — AI-Powered Salesforce Technical Documentation, written by your agent from the org's own metadata."
   },
   "plugins": [
     {
       "name": "tadforce",
       "source": "./",
-      "description": "Generate, review and validate the Technical Architecture Document of any Salesforce org (/tadforce, /tadforce-review).",
-      "version": "0.2.0",
+      "description": "AI-Powered Salesforce Technical Documentation: generate, review, validate and update the Technical Architecture Document of any Salesforce org (/tadforce, /tadforce-review, /tadforce-update).",
+      "version": "0.3.0",
       "author": { "name": "Jihad AZAMI HASSANI" },
       "license": "Apache-2.0",
       "category": "documentation"

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "tadforce",
-  "version": "0.2.0",
-  "description": "Point it at a Salesforce org, get the Technical Architecture Document a senior architect would write: evidence-based, reproducible, reviewable in the browser. All Salesforce products and industries.",
+  "version": "0.3.0",
+  "description": "AI-Powered Salesforce Technical Documentation — the Technical Architecture Document of any Salesforce org, written from the org's own metadata: evidence-based, reproducible, reviewable in the browser, kept up to date. All Salesforce products and industries.",
   "author": {
     "name": "Jihad AZAMI HASSANI",
     "url": "https://github.com/azamiji"

package/README.md

@@ -2,7 +2,7 @@
 
 <img src="assets/banner.svg" alt="TADForce — point it at a Salesforce org, get the architecture document a senior architect would write" width="100%">
 
-### The architect's scribe for Salesforce orgs.
+### AI-Powered Salesforce Technical Documentation
 
 **Four commands. One org. One Technical Architecture Document — evidence-based, reproducible, reviewable in the browser.**
 
@@ -20,7 +20,7 @@
 [![Copilot](https://img.shields.io/badge/GitHub%20Copilot-skill-6E40C9)](#-quick-start)
 [![Read-only](https://img.shields.io/badge/org%20access-read--only-16A34A)](#-read-only-by-design)
 
-[**Live demo**](https://azamiji.github.io/TADForce/) · [Quick start](#-quick-start) · [The four commands](#-four-commands) · [Every project type](#-every-kind-of-salesforce-project) · [Français](README.fr.md)
+[**Live demo**](https://azamiji.github.io/TADForce/) · [Quick start](#-quick-start) · [The four commands](#-four-commands) · [Every project type](#-every-kind-of-salesforce-project)
 
 </div>
 
@@ -140,7 +140,7 @@ The document carries **the client's logo and colours**: the logo is searched in
 | **No org access**, sources only | `--source local` documents the package directories of the project |
 | **Unlocked or managed packages** | Namespaces and installed packages are detected and documented with their evidence |
 | **Any cloud, any industry** | Sections switch on only when the product is detected, each with its writing guide (below) |
-| **French or English** | Document, skeletons and interface in both; Salesforce terms stay in English |
+| **Any language** | English and French built in. Any other language (Spanish, German, Italian, Portuguese, Arabic, Japanese…): pick it in `doctor`, your agent translates the headings and labels once, then writes in that language. Salesforce terms stay in English |
 
 ### Products and industries
 
@@ -219,7 +219,7 @@ The TADForce CLI sends nothing anywhere: no telemetry, no server, no account. It
 
 ## 🗺️ Roadmap
 
-- [ ] More languages for the skeletons (es, de, pt, it)
+- [ ] Built-in skeletons for more languages (es, de, pt, it) — any language already works through the agent; contributions welcome
 - [ ] Your own template: add, hide or rename chapters from `tadforce/templates/`
 - [ ] More examples: Service + Experience Cloud, an ISV package
 - [ ] Salesforce CLI plugin wrapper (`sf tad …`)
@@ -232,7 +232,17 @@ Issues and pull requests are welcome — new product modules, new extractors, ne
 
 ## 👥 Community
 
-TADForce was born in the **Salesforce Architect Community Group of Casablanca**. Share your generated documents (anonymised!), your module ideas and your war stories in the issues. Star the repo if TADForce saved you a week. ⭐
+TADForce was born for the **Salesforce ecosystem**: architects, consultants, integrators and in-house teams who need documentation they can trust.
+
+Your experience is what makes it better. Tell us, in the [issues](https://github.com/azamiji/TADForce/issues) and [discussions](https://github.com/azamiji/TADForce/discussions):
+
+- **How it went** — the kind of org and project, the time it took, what worked out of the box.
+- **How good the result was** — sections that read like a senior architect wrote them, and sections that did not.
+- **What to improve** — a product it should detect better, a section that misses the point, a question it should have asked.
+
+Please share your feedback, not your documents: they describe your clients' systems.
+
+If TADForce saved you a week, **star the repo** ⭐ — it is how other Salesforce teams find it.
 
 ## 👤 Author
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "tadforce",
-  "version": "0.2.0",
-  "description": "Point it at a Salesforce org. Get the technical architecture document a senior architect would write — evidence-based, reproducible, reviewable.",
+  "version": "0.3.0",
+  "description": "AI-Powered Salesforce Technical Documentation — the Technical Architecture Document of any Salesforce org, written from the org's own metadata: evidence-based, reproducible, reviewable in the browser, kept up to date.",
   "type": "module",
   "bin": {
     "tadforce": "bin/tadforce.js"

package/skills/tadforce/SKILL.md

@@ -19,7 +19,7 @@ The CLI (`npx tadforce …`) does everything deterministic: org access, retrieve
 6. **Numbers come from facts.** Write counts as `{{n:apex.classes}}`, links as `{{ref:section-id}}`. Never type a count by hand.
 7. **Client document ≠ internal review.** The TAD is factual and positive. Debt, risks and recommendations go to the Improvement Axes document.
 8. **Technical names in code font must exist** in the inventory (`tadforce validate` checks it).
-9. **Write in the document language** (`tadforce.config.json › language`). Keep Salesforce terms in English (Lead, Queue, Record Type, Named Credential…).
+9. **Write in the document language** (`tadforce.config.json › language` — any language; outside English and French, translate the headings and labels once, see `references/workflow.md › Other languages`). Keep Salesforce terms in English (Lead, Queue, Record Type, Named Credential…).
 10. **Ask in batches.** Group your questions; never ask what the facts already answer.
 
 ## The run

package/skills/tadforce/references/questions.md

@@ -6,7 +6,7 @@ Ask in **blocks**, each in one message, with your proposed answer for every item
 
 `npx tadforce doctor --json` returns these questions with a `recommended` answer each (from the org when connected). Ask them all in one message:
 
-1. Document language — recommended: the org default language.
+1. Document language — recommended: the org default language. English and French are built in; any other language works (the headings and labels are translated once, see `workflow.md › Other languages`).
 2. Client name and short code (file names) — recommended: `Organization.Name` / `<CODE>`.
 3. Integrator — **optional**. Blank: the document names the client only (no empty « Integrator » line, no badge).
 4. Author — **optional**. Blank: no author is shown anywhere. Never put your own name or the agent's.

package/skills/tadforce/references/workflow.md

@@ -25,6 +25,16 @@ What `doctor` does by itself, read-only:
 - metadata, as chosen (`source`): **org** (recommended — the org is the truth) retrieves every useful type with a `*` manifest into `tadforce/.snapshot` (`force-app` is never touched; large orgs take several minutes: tell the human); **local** reads the package directories; **both** combines them. Then `facts/facts.json`, `facts/org.json` (aggregates), `facts/questions.json`, the chapter skeletons in `tadforce/src/`;
 - branding from evidence: the client logo searched in the snapshot (static resources, content assets, site assets named *logo*), the colours from the org's Lightning theme (`BrandingSet`), else from the logo. Never fetch a logo from the web without the human's go-ahead; when they agree, pass its URL with `--logo`.
 
+### Other languages
+
+English and French are built in. Any other language (`--lang es`, `de`, `it`, `pt`, `nl`, `ar`, `ja`…) works too: the skeletons are scaffolded in English and `tadforce/i18n/<lang>.json` is created from the English labels. Once, before writing:
+
+1. Translate the headings of every `tadforce/src/*/*.md` file into the document language. Keep the `{#anchors}`, the `{-}` markers, the `<!-- tad:… -->` lines and the `@@…@@` directives exactly as they are.
+2. Translate every value of `tadforce/i18n/<lang>.json` (cover, tables, figures, buttons of the HTML). Keep the keys and the `{placeholders}`; set `meta.htmlLang`. Delete the `_translate` line.
+3. Write the sections in that language; Salesforce terms stay in English.
+
+`doctor` shows a reminder until step 2 is done. To ship the language for everyone, contribute it (issue template « New language »).
+
 ### Optional inputs
 
 - **Functional specifications** (`--specs`): copied into `knowledge/inputs/specs/`. Read them before chapters 3 and 5; they are evidence level P2/P3 (`evidence-rules.md`). They explain the *why*; the metadata still decides the *what*.

package/src/build/render.js

@@ -107,7 +107,7 @@ export async function buildDocument(wsCtx, doc, opts = {}) {
   const problems = [];
   const facts = loadFacts(wsCtx.ws);
   if (!facts) throw new Error('facts/facts.json not found: run `tadforce facts` first.');
-  const { lang, dict } = loadI18n(cfg.language);
+  const { lang, dict } = loadI18n(cfg.language, wsCtx.ws);
   const glossary = wsCtx.glossary() || {};
   const srcDir = wsCtx.p('src', doc);
   if (!exists(srcDir)) throw new Error(`No sources in ${srcDir}: run \`tadforce scaffold --doc ${doc}\`.`);

package/src/cli.js

@@ -38,7 +38,7 @@ const COMMANDS = { ...MAIN, ...ADVANCED };
 
 function help(all) {
   const v = readJson(path.join(PKG_ROOT, 'package.json')).version;
-  console.log(`${c.violet('▲')} ${c.bold('TADForce')} ${v} — technical architecture documents for Salesforce orgs. ${c.dim('No evidence, no sentence.')}\n`);
+  console.log(`${c.violet('▲')} ${c.bold('TADForce')} ${v} — AI-Powered Salesforce Technical Documentation. ${c.dim('No evidence, no sentence.')}\n`);
   console.log(`Usage: ${c.bold('npx tadforce <command> [options]')}\n`);
   for (const [k, [, d]] of Object.entries(MAIN)) console.log(`  ${c.cyan(k.padEnd(15))} ${d}`);
   if (all) {

package/src/commands/docs.js

@@ -4,6 +4,7 @@ import path from 'node:path';
 import { exists, writeJson, readText, copyDir, stableStringify } from '../util/fsx.js';
 import { loadWorkspace, sourceDirs } from '../util/config.js';
 import { TEMPLATES } from '../util/paths.js';
+import { LANGUAGES, normalizeLang, templateLang } from '../util/i18n.js';
 import { extractFacts, readCodeAnalyzer, loadFacts } from '../facts/index.js';
 import { collectOrgFacts } from '../facts/org.js';
 import { fingerprints } from '../facts/fingerprints.js';
@@ -70,7 +71,19 @@ export function buildQuestions(f, orgFacts) {
 
 export async function scaffold(args) {
   const ctx = loadWorkspace(args.cwd || process.cwd());
-  const lang = ctx.cfg.language === 'fr' ? 'fr' : 'en';
+  const lang = templateLang(ctx.cfg.language);
+  const target = normalizeLang(ctx.cfg.language);
+  // Any other language: English skeletons and labels, translated once by the agent in the workspace.
+  if (!LANGUAGES.includes(target)) {
+    const own = ctx.p('i18n', `${target}.json`);
+    if (!exists(own)) {
+      const en = JSON.parse(readText(path.join(TEMPLATES, 'i18n', 'en.json')));
+      en.meta.htmlLang = target;
+      en._translate = `Translate every value of this file into the document language (${target}); keep the keys and the {placeholders}. Then delete this line.`;
+      writeJson(own, en);
+    }
+    log.human(`document language "${target}": the skeletons are in English. Your agent translates the headings of src/*/*.md (keep the {#anchors}) and the labels of tadforce/i18n/${target}.json, once.`);
+  }
   for (const doc of docsOf(args)) {
     const src = path.join(TEMPLATES, doc, lang);
     const dst = ctx.p('src', doc);

package/src/commands/doctor.js

@@ -8,7 +8,7 @@ import YAML from 'yaml';
 import { exists, readJson, readText, writeText } from '../util/fsx.js';
 import { findWorkspace, defaultConfig, DEFAULT_BRAND, loadWorkspace, sourceDirs } from '../util/config.js';
 import { CONFIG_FILE } from '../util/paths.js';
-import { LANGUAGES } from '../util/i18n.js';
+import { LANGUAGES, normalizeLang } from '../util/i18n.js';
 import { sfVersion, sfJson, sfInteractive, soql } from '../sf/sf.js';
 import { findBrowser, closeBrowser } from '../build/browser.js';
 import { findLogoCandidates, orgThemeColors, imageColors, paletteFrom } from '../build/brand.js';
@@ -65,7 +65,7 @@ async function proposals(alias) {
   const out = {};
   try {
     const o = ((await soql('SELECT Name, IsSandbox, LanguageLocaleKey FROM Organization', alias)).records || [])[0] || {};
-    out.client = o.Name; out.language = /^fr/i.test(o.LanguageLocaleKey || '') ? 'fr' : 'en'; out.environment = o.IsSandbox ? 'Sandbox' : 'Production';
+    out.client = o.Name; out.language = normalizeLang(String(o.LanguageLocaleKey || 'en').split('_')[0]); out.environment = o.IsSandbox ? 'Sandbox' : 'Production';
   } catch { /* proposals stay empty */ }
   return out;
 }
@@ -76,7 +76,7 @@ const listArg = (v) => (typeof v !== 'string' ? undefined : v.split(',').map((x)
 async function applyAnswers(ctx, args) {
   const cfg = ctx.cfg;
   const set = (cond, fn) => { if (cond) fn(); };
-  set(args.lang, () => { cfg.language = LANGUAGES.includes(args.lang) ? args.lang : 'en'; });
+  set(args.lang, () => { cfg.language = normalizeLang(args.lang); });
   set(args.client, () => { cfg.client.name = String(args.client); if (!args.short && (cfg.client.short === 'CLIENT' || !cfg.client.short)) cfg.client.short = String(args.client).replace(/[^A-Za-z0-9]/g, '').slice(0, 8).toUpperCase(); });
   set(args.short, () => { cfg.client.short = String(args.short); });
   set(args.integrator !== undefined, () => { cfg.integrator.name = args.integrator === true || args.integrator === '' || args.integrator === 'none' ? null : String(args.integrator); });
@@ -164,7 +164,7 @@ function framingQuestions(cfg, prop, alias, hasLocal) {
   const q = [];
   const ask = (id, question, recommended, extra = {}) => q.push({ id, question, recommended, ...extra });
   if (!cfg.setup.confirmed) {
-    ask('lang', 'Document language', prop.language || cfg.language, { options: LANGUAGES });
+    ask('lang', `Document language — ${LANGUAGES.join(', ')} built in, or any language code (es, de, it, pt, nl, ar, ja…): the agent then translates the headings and labels once`, prop.language || cfg.language, { options: [...LANGUAGES, 'other'] });
     ask('client', 'Client name, as it must appear in the document', prop.client || cfg.client.name);
     ask('short', 'Client short name (file names, references)', cfg.client.short !== 'CLIENT' ? cfg.client.short : String(prop.client || cfg.client.name).replace(/[^A-Za-z0-9]/g, '').slice(0, 8).toUpperCase());
     ask('integrator', 'Integrator, if any (blank: the document only names the client)', cfg.integrator.name || '', { optional: true });
@@ -240,6 +240,9 @@ async function evaluate(project, args) {
     const ctx = loadWorkspace(project);
     snapshot = exists(ctx.p(ctx.cfg.source.dir));
     facts = exists(ctx.p('facts', 'facts.json'));
+    const lang = normalizeLang(ctx.cfg.language);
+    const own = ctx.p('i18n', `${lang}.json`);
+    if (!LANGUAGES.includes(lang) && exists(own) && readJson(own)._translate) add('language', true, `Document language "${lang}": headings and labels still to translate (once)`, `the agent translates the headings of src/*/*.md (keep the {#anchors}) and the values of tadforce/i18n/${lang}.json, then removes its "_translate" line`, false, 'warn');
     add('metadata', facts, facts ? `Metadata: ${snapshot ? 'retrieved from the org' : 'local sources'} → facts/facts.json` : 'Metadata not collected yet', facts ? null : 'doctor retrieves it once the questions are answered');
   }
   return { tools, ws, cfg, alias, status, list, facts, snapshot };
@@ -298,6 +301,7 @@ export async function run(args) {
         for (const q of framing) {
           const a = (await rl.question(`  ${q.question}${q.options ? ` (${q.options.join('/')})` : ''}${q.recommended ? ` [${q.recommended}]` : ''}: `)).trim();
           answers[q.id] = a || q.recommended || (q.optional ? '' : undefined);
+          if (q.id === 'lang' && /^(other|autre)$/i.test(a)) answers.lang = (await rl.question('  Language code (es, de, it, pt, nl, ar, ja…): ')).trim() || 'en';
         }
         const flags = { confirm: true, specs: answers.specs || false };
         for (const [k, v] of Object.entries(answers)) if (v !== undefined) flags[k === 'logo' ? 'logo' : k] = v === '' && ['integrator', 'author'].includes(k) ? 'none' : v === '' ? undefined : v;

package/src/commands/init.js

@@ -4,7 +4,7 @@ import readline from 'node:readline/promises';
 import { exists, writeText, writeJson, copyDir, readJson } from '../util/fsx.js';
 import { defaultConfig, findWorkspace } from '../util/config.js';
 import { WORKSPACE_DIR, CONFIG_FILE, SKILLS } from '../util/paths.js';
-import { LANGUAGES } from '../util/i18n.js';
+import { LANGUAGES, normalizeLang } from '../util/i18n.js';
 import { log } from '../util/log.js';
 import { run as doctor } from './doctor.js';
 
@@ -100,7 +100,7 @@ export async function run(args) {
     const prev = existing ? readJson(path.join(ws, CONFIG_FILE)) : {};
     const base = defaultConfig(prev);
     if (interactive) log.step('A few facts only you can confirm (Enter keeps the default):');
-    const language = args.lang || (await ask(rl, `Document language (${LANGUAGES.join('/')})`, base.language));
+    const language = args.lang || (await ask(rl, `Document language (${LANGUAGES.join('/')} built in, or any code: es, de, it, pt, ar…)`, base.language));
     const clientName = args.client || (await ask(rl, 'Client name', prev.client?.name || base.client.name));
     const short = args.short || (await ask(rl, 'Client short name (used in file names)', prev.client?.short || clientName.replace(/[^A-Za-z0-9]/g, '').slice(0, 8).toUpperCase()));
     const integrator = args.integrator || (await ask(rl, 'Integrator (blank if none)', base.integrator.name || ''));
@@ -109,7 +109,7 @@ export async function run(args) {
     const alias = args.org || (await ask(rl, 'Salesforce org alias (blank: decide later)', base.org.alias || ''));
     const cfg = defaultConfig({
       ...prev,
-      language: LANGUAGES.includes(language) ? language : 'en',
+      language: normalizeLang(language),
       client: { ...base.client, name: clientName, short },
       integrator: { ...base.integrator, name: integrator || null },
       document: { ...base.document, author: author || null, title, reference: prev.document?.reference || `TAD-${short}-CRM`, environment: args.environment || base.document.environment, status: language === 'fr' && !prev.document?.status ? 'Pour revue' : base.document.status, classification: language === 'fr' && !prev.document?.classification ? 'Confidentiel' : base.document.classification },

package/src/commands/update.js

@@ -7,6 +7,7 @@ import { AREAS, fingerprints } from '../facts/fingerprints.js';
 import { loadWorkspace, sourceDirs } from '../util/config.js';
 import { TEMPLATES } from '../util/paths.js';
 import { log, c } from '../util/log.js';
+import { templateLang } from '../util/i18n.js';
 import * as org from './org.js';
 import * as docs from './docs.js';
 
@@ -121,7 +122,7 @@ export async function run(args) {
   for (const m of modulesAfter.filter((x) => !modulesBefore.includes(x))) note('modules', `new product detected: ${m}`);
   for (const m of modulesBefore.filter((x) => !modulesAfter.includes(x))) note('modules', `product no longer detected: ${m}`);
   const specs = readYaml(path.join(TEMPLATES, 'specs', 'sections.yml'), {}).sections || {};
-  const sections = affectedSections(areas, specs, sectionLocations(ctx2.cfg.language === 'fr' ? 'fr' : 'en'));
+  const sections = affectedSections(areas, specs, sectionLocations(templateLang(ctx2.cfg.language)));
 
   // 4. New version in the document control.
   const cfg = ctx2.cfg;

package/src/util/i18n.js

@@ -2,15 +2,30 @@ import path from 'node:path';
 import { readJson, exists } from './fsx.js';
 import { TEMPLATES } from './paths.js';
 
+/** Languages shipped with skeletons and interface labels. Any other language works from the English ones. */
 export const LANGUAGES = ['en', 'fr'];
 
-export function loadI18n(lang) {
-  const l = LANGUAGES.includes(lang) ? lang : 'en';
-  const base = readJson(path.join(TEMPLATES, 'i18n', 'en.json'));
-  if (l === 'en') return { lang: 'en', dict: base };
-  const p = path.join(TEMPLATES, 'i18n', `${l}.json`);
-  const loc = exists(p) ? readJson(p) : {};
-  return { lang: l, dict: merge(base, loc) };
+/** A language code as written in the config: en, fr, es, de, pt-BR… (anything else falls back to en). */
+export function normalizeLang(lang) {
+  const m = /^([a-z]{2,3})(?:[-_]([a-z]{2}))?$/i.exec(String(lang || '').trim());
+  return m ? m[1].toLowerCase() + (m[2] ? '-' + m[2].toUpperCase() : '') : 'en';
+}
+
+/** Skeletons and specs come in the built-in languages; other languages start from English. */
+export const templateLang = (lang) => (LANGUAGES.includes(normalizeLang(lang)) ? normalizeLang(lang) : 'en');
+
+/**
+ * Interface and document labels: English, then the built-in translation, then the workspace's own
+ * file (tadforce/i18n/<lang>.json) — the translation the agent writes for any other language.
+ */
+export function loadI18n(lang, ws = null) {
+  const l = normalizeLang(lang);
+  let dict = readJson(path.join(TEMPLATES, 'i18n', 'en.json'));
+  const builtIn = path.join(TEMPLATES, 'i18n', `${l}.json`);
+  if (l !== 'en' && exists(builtIn)) dict = merge(dict, readJson(builtIn));
+  const own = ws && path.join(ws, 'i18n', `${l}.json`);
+  if (own && exists(own)) dict = merge(dict, readJson(own));
+  return { lang: l, dict };
 }
 
 function merge(a, b) {
@@ -29,5 +44,6 @@ export function t(dict, key, vars = {}) {
 export function formatNumber(n, lang) {
   if (typeof n !== 'number' || !Number.isFinite(n)) return String(n);
   // fr-FR uses a narrow no-break space as thousands separator, as in the reference document.
-  return new Intl.NumberFormat(lang === 'fr' ? 'fr-FR' : 'en-US').format(n);
+  const locale = lang === 'fr' ? 'fr-FR' : lang === 'en' || !lang ? 'en-US' : lang;
+  try { return new Intl.NumberFormat(locale).format(n); } catch { return new Intl.NumberFormat('en-US').format(n); }
 }

package/README.fr.md

@@ -1,125 +0,0 @@
-<div align="center">
-
-<img src="assets/banner.svg" alt="TADForce" width="100%">
-
-### Le scribe de l'architecte pour les orgs Salesforce.
-
-**Quatre commandes. Une org. Un document d'architecture technique fondé sur des preuves, reproductible, relu dans le navigateur.**
-
-[English](README.md) · [**Démo en ligne**](https://azamiji.github.io/TADForce/)
-
-</div>
-
-<img src="assets/divider.svg" width="100%" alt="">
-
-## Pourquoi TADForce
-
-Rédiger le document d'architecture technique d'une org Salesforce prend des semaines, et il est périmé à la release suivante. Un chat IA générique l'écrit en une heure, puis on passe des jours à vérifier ce qu'il a inventé.
-
-TADForce lit l'org comme le ferait un architecte Salesforce senior — chaque classe, Flow, objet, Permission Set Group, Named Credential et OmniScript — et votre agent IA rédige le document à partir de ces preuves. Une seule règle : **pas de preuve, pas de phrase.** Si les métadonnées ne le prouvent pas, l'agent vous pose la question ou écrit « à confirmer ». Il ne devine jamais le nom d'un système, ne documente jamais une fonction décommissionnée et ne tape jamais un chiffre à la main.
-
-<div align="center">
-<img src="assets/gifs/document.gif" alt="Navigation dans un document généré par TADForce" width="92%">
-</div>
-
-## ⚡ Démarrage
-
-**Prérequis** : Node.js 20+, Salesforce CLI (`sf`), Chrome ou Edge, un agent IA. `doctor` vérifie tout et installe ce qu'il peut.
-
-À la racine de votre projet Salesforce DX (ou dans un dossier vide) :
-
-```bash
-npx tadforce doctor
-```
-
-Puis, dans votre agent IA (Claude Code, Codex, Cursor, Copilot…) :
-
-```text
-/tadforce
-```
-
-| Chemin | Commandes |
-|---|---|
-| Plugin Claude Code | `/plugin marketplace add azamiji/TADForce` puis `/plugin install tadforce@tadforce` |
-| Tout agent (Agent Skills) | `npx tadforce doctor` installe les skills dans `.claude/`, `.agents/`, `.cursor/`, `.codex/`… |
-| Déterministe / CI | `npx tadforce prepare --org prod`, puis `npx tadforce build --pdf --docx`, puis `npx tadforce validate` |
-
-## 🧭 Quatre commandes
-
-| Commande | Ce qu'elle fait | Votre part |
-|---|---|---|
-| `npx tadforce doctor` | Tout ce qui précède la rédaction, en boucle jusqu'à ce que tout soit vert : outils, projet SFDX, connexion à l'org (réutilise la `target-org` du projet, n'ouvre le navigateur que si nécessaire), métadonnées (récupérées depuis l'org avec un manifest `*`, ou vos sources locales), logo et couleurs du client, puis les questions dont seul un humain connaît la réponse | Vous connecter une fois ; valider les réponses recommandées ; nommer les systèmes externes ; confirmer ce qui est inutilisé ou décommissionné |
-| `npx tadforce build` | Votre agent rédige chaque section à partir de sa fiche et des faits, puis le document est produit : **HTML** toujours, **PDF** et **Word** à la demande, et validé | — |
-| `npx tadforce review` | Ouvre le document pour le commenter. **Enregistrer écrit dans le même fichier** : un seul fichier par document, pas de copies, aucun commentaire perdu. Puis `/tadforce-review` transforme chaque commentaire en correction | Commenter un passage ou capturer une zone, Enregistrer |
-| `npx tadforce update` | Quelques mois plus tard : relit l'org, archive les faits précédents, liste les sections touchées par ce qui a changé (une classe Apex ajoutée, un Flow modifié, de nouveaux chiffres…), incrémente la version. `/tadforce-update` ne réécrit que ces sections | — |
-
-<div align="center">
-<img src="assets/gifs/doctor.gif" alt="tadforce doctor pose les questions dont seul un humain connaît la réponse" width="80%">
-</div>
-
-Les commandes fines (`manifest`, `retrieve`, `facts`, `next`, `validate`…) restent disponibles pour la CI et les experts : `npx tadforce help --all`.
-
-## 📦 Ce que vous obtenez
-
-- **Document d'architecture technique**, destiné au client :
-  - en HTML : navigable, modifiable en place, avec commentaire d'un passage ou capture d'une zone, enregistrement dans le même fichier et export PDF ou Word ;
-  - en PDF A4 et en DOCX, la version dans le nom du fichier.
-- **Axes d'amélioration**, document interne à l'intégrateur : signaux mesurés par pilier Well-Architected, registre `AX-nn` et feuille de route. Ils restent hors du document client.
-- **`facts.json`** : l'inventaire déterministe de l'org, identique octet pour octet d'une exécution à l'autre.
-
-Le document porte **le logo et les couleurs du client** : le logo est cherché dans l'org (static resources, content assets, assets des sites) ou fourni par vous ; les couleurs viennent du thème Lightning de l'org, sinon du logo, toujours lisibles (contraste WCAG vérifié). L'intégrateur et l'auteur sont facultatifs : laissés vides, le document ne nomme que le client.
-
-<div align="center">
-<img src="assets/gifs/review.gif" alt="Commenter un passage dans le HTML et l'enregistrer dans le même fichier" width="92%">
-</div>
-
-## 🧩 Tous les types de projets Salesforce
-
-| Votre situation | Comment TADForce s'y adapte |
-|---|---|
-| **Une org complète**, état existant | `doctor` récupère tout avec un manifest `*` maîtrisé (130 types, rapports et tableaux de bord dans leurs dossiers, objets standard) |
-| **Un projet dans une org partagée** (plusieurs BU, plusieurs intégrateurs) | Périmètre : `--scope "NWB_*,Loan*"` ou `--package-dirs`. Les composants hors périmètre sortent des faits, des chiffres et des tableaux ; les objets standard et les réglages globaux restent |
-| **Avant ou pendant le build** | Fournissez vos spécifications fonctionnelles (`--specs SFD.pdf,…`) : elles deviennent des preuves (niveau P2/P3) à côté des métadonnées |
-| **Sans accès à l'org**, sources seules | `--source local` documente les package directories du projet |
-| **Packages unlocked ou managés** | Namespaces et packages installés sont détectés et documentés avec leurs preuves |
-| **Tous les clouds, toutes les industries** | Une section ne s'active que si le produit est détecté, avec sa fiche de rédaction |
-
-- **Clouds** : Sales, Service, Field Service, Experience, Marketing, Commerce, CPQ et Revenue ;
-- **Industries** : Financial Services, Insurance, Health, Life Sciences, Manufacturing, Automotive, Consumer Goods, Communications, Public Sector, Education, Nonprofit, Loyalty, Net Zero ;
-- **Plateforme** : OmniStudio, Data Cloud, Agentforce, CRM Analytics, Platform Events, Shield, MuleSoft, Heroku et Slack.
-
-## 🔒 Lecture seule par construction
-
-- **Liste blanche des commandes `sf`** : pas de deploy, pas de suppression, pas d'exécution d'Apex.
-- **Garde-fou SOQL** : seuls les objets de configuration de l'org et les agrégats sont lus, jamais les données métier.
-- **`force-app` jamais modifié** : la récupération se fait dans `tadforce/.snapshot`.
-- **Aucun secret dans le texte** : la validation bloque les secrets et les identifiants d'org.
-
-**Ce qui sort de votre poste** : le CLI TADForce n'envoie rien nulle part — ni télémétrie, ni serveur, ni compte. Il parle à votre org via votre propre Salesforce CLI, et au web seulement quand **vous** lui donnez l'URL d'un logo. Votre agent IA lit les métadonnées, les faits et les spécifications que vous fournissez pour rédiger, exactement comme lorsque vous lui faites lire votre code. Utilisez l'agent et les réglages de confidentialité validés par votre entreprise pour les travaux client.
-
-## 🎯 Reproductible
-
-- **Les chiffres sont des placeholders**, par exemple `{{n:apex.classes}}`.
-- **Les tableaux, les ERD, la hiérarchie des rôles et les annexes sont générés.**
-- **84 fiches de section** cadrent la rédaction de n'importe quel agent.
-- **`npx tadforce validate`** bloque tout ce qui ne doit pas être livré.
-
-## 👤 Auteur
-
-<table>
-<tr>
-<td width="110"><img src="https://github.com/azamiji.png" width="96" alt="Jihad AZAMI HASSANI"></td>
-<td>
-
-**Jihad AZAMI HASSANI**<br>
-Salesforce Technical Architect, 10+ ans d'expérience · Claude Certified Architect · Leader du Salesforce Architect Community Group de Casablanca<br>
-[![Claude Certified Architect](https://img.shields.io/badge/Claude-Certified%20Architect-D97757?logo=claude&logoColor=white)](https://www.linkedin.com/in/jihadazami/)<br>
-[LinkedIn](https://www.linkedin.com/in/jihadazami/) · [GitHub](https://github.com/azamiji)
-
-</td>
-</tr>
-</table>
-
-## ⚖️ Licence
-
-[Apache-2.0](LICENSE). Salesforce et les noms de ses produits sont des marques de Salesforce, Inc. TADForce est un projet communautaire indépendant, ni affilié à Salesforce ni approuvé par elle. L'organisation de l'exemple (Northwind Bank, Acme Integrators) est fictive.