@supersoniks/concorde 5.1.1 → 5.1.3-immutable.1

package/.agents/skills/concorde-docs/SKILL.md

@@ -0,0 +1,153 @@
+---
+name: concorde-docs
+description: >-
+  Writes, edits and trims Concorde documentation pages (*.md rendered by the
+  doc site): component pages, decorator pages, concept and misc guides. Short,
+  sober, generic English with live <sonic-code> examples and one API table.
+  Use when creating, rewriting, uniformizing, shortening or removing a doc page,
+  touching src/docs/navigation/navigation.ts, or when asked to make the docs
+  "cleaner", "shorter" or "less project-specific".
+---
+
+# Concorde docs
+
+Concorde is a **public, generic** web-component library. The docs explain the library, nothing else. Write as if the reader has never heard of the company or its products.
+
+## Principles
+
+1. **Short.** One idea per section, 0–4 sentences before an example. Cut anything the example already shows.
+2. **Example first.** A live `<sonic-code>` beats a paragraph. Prose states defaults, constraints and gotchas, not what the reader can see.
+3. **Generic.** No product, client, team or internal process. Demo data follows the aviation theme (see [Demo data](#demo-data)).
+4. **One source of truth.** Link to the page that owns a topic instead of re-explaining it.
+5. **Current API only.** Document the recommended way. Do not keep "legacy" tutorials; a removed or deprecated API gets one line + a link to its replacement, or nothing.
+
+## Stay generic — never write
+
+- Company or product names and history (ticketing, "La Billetterie", "nearly 100 sites", …). The only allowed brand is the npm scope `@supersoniks/concorde`.
+- Ticket / issue references (`REDMINE-12345`, Jira keys), branch names, MR links.
+- Paths or code from consumer apps (`la-billetterie/…`, `src/<app>/components/…`), lists of impacted files, migration audits.
+- Event-ticketing vocabulary in examples: events, shows, venues, orders, tickets, accreditations, counters. Use the aviation theme instead (see [Demo data](#demo-data)).
+- Internal hosts, tokens, real API keys, back-office URLs. Live demos call the local mock API (see below).
+- "We", "our team", "at X we usually…". Address the integrator in the imperative: "Set `announce` when…".
+
+Migration notes for one consumer app belong in that app's repo, not here. If such content exists on a page, delete it or move it out (ask before moving).
+
+## Page types
+
+| Type | Location | Template |
+|------|----------|----------|
+| UI / functional component | `src/core/components/<ui\|functional>/<name>/<name>.md` | [templates/component.md](templates/component.md) |
+| Decorator / directive | `src/docs/decorators/*.md` · `src/docs/directives/*.md` | [templates/decorator.md](templates/decorator.md) |
+| Getting started / misc | `src/docs/getting-started/` · `src/docs/misc/` | [templates/guide.md](templates/guide.md) |
+
+Before writing, read the source (`.ts`: props, slots, defaults, events) and **one sibling page** of the same type. Match the sibling over inventing a layout.
+
+Canonical siblings: `ui/alert/alert.md`, `ui/badge/badge.md`, `decorators/subscribe.md`, `getting-started/dataFlow.md`.
+
+## Writing rules
+
+- **English** only. Present tense. No marketing ("powerful", "seamless", "very useful").
+- **Title**: `# Alert`, `# @subscribe`, `# Data flow`. No "Legacy:" prefixes, no ticket numbers.
+- **Intro**: one paragraph, 1–3 sentences: what it does, when to choose it, the 1–2 key APIs.
+- **Headings**: sentence case, one concern each (`## Size`, `## Dynamic path`). `##` then `###`, never skip.
+- **Defaults first**: "With no `status`, the alert is `default`."
+- **Inline code**: tags, attributes, props, types in backticks. Never chain backtick spans with commas (they render glued): use `/`, ` · ` or "and".
+- **Bold** for behaviour that prevents misuse, not for every noun.
+- **Tables** for reference data (attributes, slots, options, routes). Not for narrative.
+- **Callouts**: `<sonic-alert status="info|warning">` only for something the reader will get wrong otherwise. Max one per page.
+- No emoji in headings or links.
+- **No "Next step(s)" section.** The pager already links the previous / next page; the sidebar order in `navigation.ts` is the reading order. Fix the order there instead.
+
+## Examples
+
+HTML demo (rendered live, editable):
+
+```html
+<sonic-code>
+  <template>
+    <div class="flex flex-wrap gap-2">
+      <sonic-badge>Default</sonic-badge>
+      <sonic-badge type="primary">Primary</sonic-badge>
+    </div>
+  </template>
+</sonic-code>
+```
+
+TypeScript snippet (not executed): `<sonic-code language="typescript">`, escape `<` `>` as `&lt;` `&gt;` inside the template.
+
+Lit component demo: put the component in `src/docs/example/<name>.ts`, register it in `DOCS_LIT_DEMO_REGISTRY` (`src/docs/components/docs-demo-sources.ts`), import it in `src/docs/docs.ts`, then embed `<docs-lit-demo for="<tag>"></docs-lit-demo>`. Source and live render then stay in sync.
+
+- Show all enum values in **one** grid, not one section per value.
+- Realistic copy from the aviation theme. Lorem ipsum only to demo truncation.
+- Network demos use the local mock: `serviceURL="/docs-mock-api"` + a route from `misc/docs-mock-api.md`. Add a route there (and in `src/docs/mock-api/`) rather than calling a third-party API.
+- Component pages get their `import "@supersoniks/concorde/<name>"` line added automatically under the intro: do not write one.
+- Imports use public entry points: `@supersoniks/concorde/decorators`, `@supersoniks/concorde/dataProviderKey`, … never `../../core/…`.
+- Demo `.ts` files under `src/docs/example/` go through the Vite alias (`@supersoniks/concorde` → `src/`), not the package exports: use `@supersoniks/concorde/decorators` · `directives` · `dataProviderKey` · `endpoint` or `@supersoniks/concorde/core/utils/<x>`. `@supersoniks/concorde/utils/<x>` breaks the dev server (fine in `.md` snippets).
+
+## Demo data
+
+The library is named after Concorde: every example tells a small aviation story. Pick the closest fit:
+
+| Need | Aviation equivalent |
+|------|---------------------|
+| User / profile | passenger, pilot, crew member (`Ada Lindqvist`, `Captain Leo Marchand`) |
+| List / table rows | flights (`CN 001` · `CDG → JFK` · `Boarding` / `Delayed` / `Landed`), aircraft, airports (`CDG` · `JFK` · `LHR`) |
+| Form | check-in, flight search (from / to / date / cabin), crew sign-up |
+| Status / alert | flight status, gate change, weather warning, turbulence |
+| Numbers / progress | altitude, speed (Mach 2.04), fuel, boarding progress |
+| Cart / selection | cabin class, meal choice, extra baggage |
+| Menu / navigation | Departures · Arrivals · Fleet · Crew |
+| Images | photos in `public/img/concorde/` (see below) — never picsum or any hotlinked URL |
+
+- Keep it light: one aviation word per example is enough; the example must still read as generic UI.
+- No real flight bookings or prices presented as genuine.
+- Lists and filters: reuse the `/flights` mock (departures / arrivals, `on-time` · `boarding` · `delayed` · `landed` · `cancelled`) and the `docs-flight-board` demo component (`src/docs/example/docs-flight-demos.ts`). Other mock routes (users, cats…) can stay: relabel them only when you touch the demo anyway.
+
+### Images
+
+Use `/img/concorde/plane_XX.jpg` (absolute from the site root, files in `public/img/`). Always set a meaningful `alt`.
+
+| File | Subject | Fits |
+|------|---------|------|
+| `plane_03.jpg` | Specifications board, black & white | square crops |
+| `plane_04.jpg` | Concorde on the apron, blue sky | square / card / rounded |
+| `plane_05.jpg` | Concorde behind a car park | wide |
+| `plane_06.jpg` | Ground crew and boarding stairs | wide |
+| `plane_07.jpg` | Crowd around Concorde at night | 3/2 · 16/9 |
+| `plane_09.jpg` | Person on the apron, Concorde behind | wide |
+| `plane_10.jpg` | Fleet parked in a star, aerial | cover / fullscreen |
+| `plane_11.jpg` | Concorde flying over a field | object-position demos |
+| `plane_12.jpg` | Concorde at the gate, black & white | 16/9 · modal |
+| `plane_13.jpg` | Technicians on a wing structure | wide |
+| `plane_01.jpg` | Spectators on a terrace watching Concorde | wide |
+| `plane_02.jpg` | Nose above the boarding stairs (~4 MB: avoid in grids) | portrait-ish |
+| `plane_08.jpg` | Concorde in front of a hangar, with a car | wide |
+
+## Links
+
+- Internal link format: `[Data flow](/docs/getting-started/dataFlow)` — same path as under `src/` without `.md`. Components drop the trailing duplicate: `/core/components/ui/button` (source `…/button/button.md`).
+- Same pathnames serve SPA (browser), static HTML (crawlers), and Markdown (`….md` or `Accept: text/markdown`). Do not link `/…/button/button`.
+- Link the first mention of a concept that has its own page, not every mention.
+- Never link to source files of consumer apps or internal tools.
+
+## Adding, renaming or removing a page
+
+1. Edit `src/docs/navigation/navigation.ts` (sidebar order; strings are section titles).
+2. `grep -rn "<file>.md" src docs ai` and fix or drop every link to it.
+3. Regenerate search: `node scripts/create-search.js` (also runs on `yarn dev`).
+4. Component pages: the Components index (`docs-components-index`) reads the nav, nothing else to do.
+
+## Shortening an existing page
+
+Cut, in this order: repeated explanations of a linked concept → prose restating the example → "why we built it" history → alternative ways to do the same thing → edge cases nobody hits. Keep working examples untouched unless they are wrong or project-specific.
+
+## Checklist
+
+- [ ] Nothing company-, product- or ticket-specific; demo data uses the aviation theme
+- [ ] Title + one-paragraph intro
+- [ ] Each `##` section has an example, or is a short note under one
+- [ ] Defaults and required attributes stated
+- [ ] Exactly one `## API reference`, last, matching the source
+- [ ] No comma-chained inline code
+- [ ] Links resolve; nav and search updated if pages moved
+- [ ] Page is shorter than before, or every added line earns its place

package/.agents/skills/{concorde-component-docs/template.md → concorde-docs/templates/component.md}

@@ -1,6 +1,6 @@
 # ComponentName
 
-One paragraph: what **`sonic-component`** does, when to use it instead of alternatives, and the most important `` `attributes` `` / slots. Mention defaults only if they prevent mistakes.
+One paragraph: what **`sonic-component`** does, when to use it instead of alternatives, and the key attributes / slots. Mention defaults only if they prevent mistakes.
 
 ## Basic example
 
@@ -25,7 +25,7 @@ Short explanation of default and allowed values.
 
 ## Accessibility
 
-When screen readers or keyboard users need special handling.
+Only when screen readers or keyboard users need special handling. Otherwise drop this section.
 
 <sonic-code>
   <template>
@@ -43,3 +43,7 @@ When screen readers or keyboard users need special handling.
 |------|-------------|
 | *(default)* | Primary content |
 | `named` | Optional slot purpose |
+
+If the component has no slots, replace the slots table with one line: "No slots."
+
+Values: list literals with ` · ` (`sm` · `md` · `lg`) or a range with `…` (`2xs` … `2xl`), never commas between backtick spans.

package/.agents/skills/concorde-docs/templates/decorator.md

@@ -0,0 +1,43 @@
+# @decoratorName
+
+One paragraph: what it keeps in sync or triggers, on which property/method, and the key argument (`DataProviderKey`, `Endpoint`, …). Link the owning concept once ([Data flow](#docs/getting-started/dataFlow.md/dataFlow)).
+
+## Import
+
+<sonic-code language="typescript">
+  <template>
+import { decoratorName } from "@supersoniks/concorde/decorators";
+
+@decoratorName(key)
+@state()
+value: Type | null = null;
+  </template>
+</sonic-code>
+
+## Basic usage
+
+One sentence on the default behaviour.
+
+<docs-lit-demo for="docs-decorator-name-demo"></docs-lit-demo>
+
+## Option or variant
+
+What changes, and the default.
+
+<sonic-code language="typescript">
+  <template>
+@decoratorName(key, { option: true })
+  </template>
+</sonic-code>
+
+## Notes
+
+- Lifecycle constraint (when it runs, when it stops)
+- Interaction with sibling decorators — link, don't re-explain
+
+## API reference
+
+| Argument | Type | Description |
+|----------|------|-------------|
+| `key` | `DataProviderKey<T>` | Path to read |
+| `options.option` | `boolean` (default `false`) | Behaviour in one line |

package/.agents/skills/concorde-docs/templates/guide.md

@@ -0,0 +1,25 @@
+# Topic
+
+One paragraph: the problem this page solves and the recommended approach. No history, no "why we built it".
+
+## Minimal example
+
+<sonic-code language="typescript">
+  <template>
+// smallest working code
+  </template>
+</sonic-code>
+
+## Step or concept
+
+Two to four sentences, then an example. Link pages that own sub-topics instead of repeating them.
+
+## Reference
+
+| Item | Role |
+|------|------|
+| `thing` | One line |
+
+## See also
+
+- [Related page](#docs/getting-started/dataFlow.md/dataFlow)

package/.claude/skills

@@ -0,0 +1 @@
+../.agents/skills

package/.github/workflows/ci.yml

@@ -0,0 +1,21 @@
+name: CI
+
+on:
+  push:
+    branches: [master, main]
+  pull_request:
+    branches: [master, main]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: "22"
+          cache: yarn
+
+      - run: yarn install --frozen-lockfile
+      - run: yarn test:ci

package/.github-export-ignore

@@ -0,0 +1,30 @@
+# Arborescence exclue du miroir public GitHub (GitLab reste complet).
+# Syntaxe : une entrée par ligne, # = commentaire.
+
+# Site doc
+index.html
+src/docs.ts
+src/docs/
+docs/
+img/
+scripts/create-search.js
+scripts/post-build-docs.js
+scripts/docs-mock-api-vite-plugin.ts
+scripts/docs-open-in-editor-plugin.ts
+public/docs-mock-api-sw.js
+public/docs-mock-api-sw.js.map
+
+# Captcha (dépend de altcha.supersoniks.org)
+src/core/components/ui/captcha/
+
+# Démos intégrées à la doc
+**/*.demo.ts
+
+# CI / infra interne
+gitlab/
+
+# Artefacts locaux
+dist/
+build-infos.json
+concorde-core.bundle.js
+concorde-core.es.js

package/CONTRIBUTING.md

@@ -0,0 +1,59 @@
+# Contribuer à Concorde
+
+Merci de votre intérêt pour `@supersoniks/concorde` !
+
+## Modèle de contribution (phase 1)
+
+Concorde utilise un dépôt **GitLab interne** comme source complète, avec un **export public filtré** sur GitHub (librairie uniquement — pas le site doc, pas le composant captcha lié à l’infra Supersoniks).
+
+| Qui | Où | Comment |
+|-----|-----|---------|
+| Équipe Supersoniks | GitLab | Branche + **Merge Request** vers `master` |
+| Contributeurs externes | GitHub | **Issues** pour signaler bugs ou proposer des améliorations |
+| Contributeurs externes (code) | GitHub / email | Décrire le changement dans une issue, ou proposer un patch que l'équipe intègre sur GitLab |
+
+> Les Pull Requests sur le dépôt GitHub public **ne sont pas mergées directement** : le miroir GitLab → GitHub écraserait ces changements. Ouvrez une issue pour discuter avant d'investir du temps.
+
+## Prérequis
+
+- Node.js 20+ (22 recommandé)
+- Yarn 1.22 (`packageManager` dans `package.json`)
+
+## Workflow développeur interne
+
+```bash
+git checkout -b ma-branche
+yarn install
+# … modifications …
+yarn test:ci
+# Ouvrir une Merge Request vers master sur GitLab
+```
+
+## Tests
+
+```bash
+yarn test       # watch (développement)
+yarn test:ci    # exécution unique (CI)
+```
+
+## Build
+
+```bash
+yarn build        # librairie → dist/
+yarn build-docs   # documentation statique → docs/
+yarn dev          # serveur de doc local (https://localhost:3000)
+```
+
+## Conventions
+
+- Suivre les patterns existants (Lit, décorateurs, DataProviderKey).
+- Pas de `console.log` oubliés (bloqué par `prepublishOnly`).
+- Documentation : fichiers `.md` colocalisés avec les composants dans `src/`.
+
+## Signaler un problème de sécurité
+
+Ne pas ouvrir d'issue publique. Contacter l'équipe Supersoniks directement.
+
+## Évolution prévue
+
+Si des contributions externes deviennent fréquentes, le dépôt GitHub pourra devenir la source canonique (modèle inversé). En attendant, GitLab reste le point d'entrée pour le code.

package/DEV.md

@@ -0,0 +1,54 @@
+# Développement local — consommer Concorde depuis un autre projet
+
+## Recommandé : `file:` (sans `yarn link`)
+
+Dans le projet consommateur (la-billetterie, etc.) :
+
+```bash
+yarn add @supersoniks/concorde@file:../../concorde
+```
+
+- Pas de `yarn link` / `yarn unlink` à gérer
+- Comportement proche d’un install registry
+- Après modification de Concorde : `yarn build` dans concorde (génère `dist/js/` + `dist/types/`), puis rebuild du consommateur
+
+## Alternative : `yarn link`
+
+Toujours supporté. Dans Concorde :
+
+```bash
+yarn link
+```
+
+Dans le consommateur :
+
+```bash
+yarn link @supersoniks/concorde
+```
+
+### Pourquoi `vite-config` exclut Concorde du pre-bundle
+
+Dans `vite/config.js`, quand un `tsconfig` est passé :
+
+```js
+optimizeDeps: {
+  exclude: ["@supersoniks/concorde"],
+  // ...
+}
+```
+
+**Toujours utile** avec `yarn link` ou `file:` : Vite ne met pas Concorde en cache dans `node_modules/.vite`, donc les changements dans `dist/js/` (après `yarn build` dans Concorde) sont pris en compte au prochain HMR / rebuild.
+
+Les exports npm pointent vers `dist/js/` (runtime) et `dist/types/` (types) — le source `src/` sert au développement de Concorde lui-même.
+
+## Types (`.d.ts`) et runtime (`.js`)
+
+`yarn build` exécute `prebuild` (exports) → bundle Vite → `postbuild` (génération de `dist/types/` + `dist/js/`).
+
+`yarn build:types` / `yarn build:js` restent disponibles pour régénérer uniquement les déclarations ou le JS.
+
+## Scripts la-billetterie
+
+`link:concorde` / `unlink:concorde` dans `la-billetterie/concorde/package.json` restent valides.
+
+`test:concorde-lib` pointe vers un fichier `resolvePublisher.spec.ts` **supprimé** — script obsolète à nettoyer côté billetterie.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) Supersoniks
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/OPEN_SOURCE_CHECKPOINT.md

@@ -0,0 +1,133 @@
+# Point d'étape — Open Source Concorde
+
+> Modèle retenu (phase 1) : **GitLab = source complète**, **GitHub = export filtré** (librairie seule).
+
+Dernière mise à jour : juin 2025.
+
+---
+
+## ✅ Fait (dans ce dépôt GitLab)
+
+| Élément | Fichier / action |
+|---------|------------------|
+| Licence MIT | `LICENSE` |
+| Retrait Typekit inutilisé | `index.html` |
+| Métadonnées npm (repo, homepage, bugs) | `package.json` |
+| README mis à jour | `README.md` |
+| Guide contributeurs | `CONTRIBUTING.md` |
+| CI GitHub Actions | `.github/workflows/ci.yml` |
+| **Liste d'exclusion GitHub** | `.github-export-ignore` |
+| **Script d'export filtré** | `scripts/github-export.mjs` |
+| **Job CI miroir GitHub** | `gitlab/job_github_mirror.sh` |
+
+### Ce qui reste sur GitLab uniquement (pas sur GitHub)
+
+| Exclu | Raison |
+|-------|--------|
+| `index.html`, `src/docs/`, `src/docs.ts` | Site doc → [concorde.supersoniks.org](https://concorde.supersoniks.org/) |
+| `src/core/components/ui/captcha/` | Dépend de `altcha.supersoniks.org` |
+| `**/*.demo.ts` | Démos intégrées à la doc |
+| `gitlab/` | CI / infra interne |
+
+Le script retire aussi l'import captcha dans `ui.ts` et filtre les `exports` npm liés à la doc/captcha.
+
+---
+
+## ⏳ À faire de votre côté
+
+### 1. Merger ces changements sur GitLab
+
+```bash
+git add LICENSE README.md CONTRIBUTING.md OPEN_SOURCE_CHECKPOINT.md \
+        .github-export-ignore scripts/github-export.mjs \
+        .github/workflows/ci.yml .gitlab-ci.yml \
+        gitlab/job_github_mirror.sh package.json index.html
+git commit -m "Open source : export GitHub filtré (sans doc ni captcha)"
+# MR vers master
+```
+
+### 2. Créer le dépôt GitHub public
+
+1. https://github.com/organizations/supersoniks → **New repository** → `concorde`
+2. **Public**, sans README initial
+
+### 3. Variables CI GitLab
+
+**Settings → CI/CD → Variables** (masquées) :
+
+| Variable | Exemple |
+|----------|---------|
+| `GITHUB_REPO_URL` | `https://github.com/supersoniks/concorde.git` |
+| `GITHUB_TOKEN` | PAT GitHub scope `repo` |
+
+### 4. Premier export (manuel ou CI)
+
+**En local :**
+
+```bash
+node scripts/github-export.mjs /tmp/concorde-github
+cd /tmp/concorde-github
+git init && git add -A && git commit -m "Initial export lib"
+git remote add origin git@github.com:supersoniks/concorde.git
+git push -u origin master
+```
+
+**Via GitLab CI** (après merge sur `master`) :
+
+- Lancer le job manuel **`github-mirror`** dans la pipeline
+
+> **Ne pas** utiliser le push mirror GitLab natif (il enverrait tout, doc + captcha inclus).
+
+### 5. Vérifier GitHub
+
+```bash
+git clone https://github.com/supersoniks/concorde.git
+cd concorde
+yarn install && yarn test:ci
+```
+
+- Pas de `index.html`, pas de `src/docs/`, pas de `captcha.ts`
+- Pas de référence à `cdn.supersoniks.com` ni `altcha.supersoniks.org` dans le tree
+
+### 6. npm
+
+```bash
+yarn build
+npm publish --access public
+```
+
+(idéalement depuis l'export filtré ou après avoir aligné `files` / `exports` npm)
+
+### 7. Documentation en ligne
+
+Doc hébergée sur **https://concorde.supersoniks.org/** (build depuis GitLab, pas depuis GitHub).
+
+---
+
+## Schéma
+
+```
+┌──────────────────────────────────────────┐
+│  GitLab (interne) — tout le dépôt         │
+│  doc + captcha + dev (yarn dev) + CI      │
+└──────────────────┬───────────────────────┘
+                   │ scripts/github-export.mjs
+                   │ (job github-mirror)
+                   ▼
+┌──────────────────────────────────────────┐
+│  GitHub (public) — librairie seule        │
+│  src/core, décorateurs, tests, CI Actions │
+└──────────────────────────────────────────┘
+
+Doc en ligne : concorde.supersoniks.org  (déployée depuis GitLab)
+```
+
+---
+
+## Checklist finale
+
+- [ ] Export GitHub sans `cdn.supersoniks` / `altcha.supersoniks`
+- [ ] `yarn test:ci` OK sur clone GitHub
+- [ ] Job `github-mirror` configuré
+- [ ] npm `@supersoniks/concorde` publié
+- [ ] Doc accessible sur concorde.supersoniks.org

package/README.md

@@ -23,7 +23,7 @@ yarn ai-init
 node node_modules/@supersoniks/concorde/scripts/ai-init.mjs
 ```
 
-Installe `.cursor/skills`, `.cursor/rules`, `.aiassistant/rules` et `AGENTS.md`. Voir [ai/README.md](ai/README.md).
+Installe la skill `concorde` dans `.agents/skills` (liée depuis `.claude/skills` et `.junie/skills`). `AGENTS.md` n’est jamais touché. Voir [ai/README.md](ai/README.md).
 
 ## 📁 Structure du projet
 
@@ -77,8 +77,8 @@ flowchart LR
 
 ### Les briques de données
 
-- **`DataProviderKey<T>`** — chemin **typé** en notation pointée vers une structure composite, ex. `new DataProviderKey<Data>("data").items[0]` → `"data.items.0"`. Navigation type-safe, chemins dynamiques via `${prop}`. Import : `@supersoniks/concorde/dataProviderKey`. Voir [la doc DataProviderKey](https://doc.concorde.test/#docs/_misc/dataProviderKey.md/dataProviderKey).
-- **`Endpoint<T, U>`** — un **unique chemin HTTP** (sans notation pointée) portant le type de réponse `T` ; segments dynamiques `${...}`. Consommé par `@get`. Import : `@supersoniks/concorde/utils/endpoint`. Voir [la doc Endpoint](https://doc.concorde.test/#docs/_misc/endpoint.md/endpoint).
+- **`DataProviderKey<T>`** — chemin **typé** en notation pointée vers une structure composite, ex. `new DataProviderKey<Data>("data").items[0]` → `"data.items.0"`. Navigation type-safe, chemins dynamiques via `${prop}`. Import : `@supersoniks/concorde/dataProviderKey`. Voir [la doc DataProviderKey](https://doc.concorde.test/#docs/misc/dataProviderKey.md/dataProviderKey).
+- **`Endpoint<T, U>`** — un **unique chemin HTTP** (sans notation pointée) portant le type de réponse `T` ; segments dynamiques `${...}`. Consommé par `@get`. Import : `@supersoniks/concorde/utils/endpoint`. Voir [la doc Endpoint](https://doc.concorde.test/#docs/misc/endpoint.md/endpoint).
 - **DataProvider** — le publisher observable qui notifie ses abonnés à chaque assignation.
 
 ### Les décorateurs (`src/core/decorators/subscriber/`)
@@ -91,7 +91,7 @@ flowchart LR
 | `@handle(...keys)` | Appelle une **méthode typée** à chaque assignation (effets de bord, calculs) | jusqu'à 3 `DataProviderKey<T>` |
 | `@get(endpoint)` | Charge des données via l'API ; la propriété devient `ApiResult<T> \| null` | `Endpoint<T>` |
 
-`DataProviderKey` est la pierre angulaire : c'est lui qui fournit les chemins **typés** utilisés par `@subscribe`, `@publish`, `@bind` et `@handle`, tandis que `Endpoint` fait le pont avec les données distantes via `@get`. Détails et exemples sur la [documentation des décorateurs](https://doc.concorde.test/#docs/_decorators/subscribe.md/subscribe).
+`DataProviderKey` est la pierre angulaire : c'est lui qui fournit les chemins **typés** utilisés par `@subscribe`, `@publish`, `@bind` et `@handle`, tandis que `Endpoint` fait le pont avec les données distantes via `@get`. Détails et exemples sur la [documentation des décorateurs](https://doc.concorde.test/#docs/decorators/subscribe.md/subscribe).
 
 ## 🛠️ Développement