Same grammar as Clarté TDAH (clarte kit: ProgressHeader, QuestionCard,
OptionPills, useDigitKeys), linear 25-item flow: consent-gated home with
optional gender, intro, auto-advancing questions, recap with jump,
results with total band + percentiles vs autistic and non-autistic
norms, five interpretation caveats, copyable consult sentence, jspdf
report. FR at /tsa, EN at /asd, mirroring /tdah + /adhd.

25 items Likert 1-7 (verbatim Hull 2019 in EN, our translation in FR,
flagged non-validated), items 3/12/19/22/24 reversed, subscales
compensation/masking/assimilation. Percentiles via normal CDF on the
Hull 2020 gender-matched norms; Baker 2024 descriptor bands on the
total score. Storage contract catq:v1, same discipline as clarte:v1.

Adds remark-gfm/directive/parse/rehype, rehype-pretty-code, shiki,
unified, unist-util-visit; retires remark/remark-html. Under PnP there
are no real node_modules dirs — cache zips live under paths *containing*
/node_modules/, so jest's transformIgnorePatterns now only excludes the
css module mocks, keeping the ESM-only unified chain transformable.

The site ships as flat files (out/) served by self-hosted nginx; every
route prerenders at build. next/image ships originals (unoptimized) —
optimization needs a server. The two parvagues revalidate = 60 exports
go with ISR; rebuild-on-push replaces it.

The one render chain: remark-gfm, remark-directive (mapped-tag escape
hatch for future embed islands), rehype-figure, rehype-pretty-code with
vesper highlighting at build time. Shipped pages are flat HTML with
inline token colors and zero client JS.

- lib/markdown.ts mints all /blog HTML; lib/blog.js binds the section
- app/blog + app/blog/[slug] on the App Router (SSG, generateMetadata);
  app/post/[id] and lib/posts.js removed with the route
- content/posts moved to content/blog; the 2021 entries are draft:true,
  hello-world-again is the one published post (engine fixture: figure
  captioning, shiki, GFM table) with its edge.png image
- yarn post / yarn post:image scaffold posts and stage images
- e2e smoke routes follow the rename

Aurora-glass cosmos, frosted-glass cards with iridescent foil edges,
Fraunces + Space Mono. Hybrid DRAW/BROWSE: chilled 3D tarot flip (spring
42/22/1.3), semantic swipes (left discard, right favorite, up stash),
haptics, kept-spread; realtime typotolerant search with incremental
16-card rendering. Date-seeded daily card. State in localStorage + URL
hash only.

Each card face carries a unique deterministic sacred-geometry figure:
mulberry32 seeded on card id + hexagram codepoint drives ring count,
packing, rotation, polygon overlays, and dash patterns — 187/187 distinct,
with a radial-mask quiet zone keeping the central text zone clear.

App Router native: server pages export metadata, interactive bodies are
'use client' leaves (ObliqueClient / DesignClient), per cosmicfest
conventions. Data: 187 deduped strategies (ceejbot cross-edition superset)
tagged with I Ching hexagrams.

Validated on the production build: routes 200, no console errors, no
horizontal overflow, tap targets >=44px, browse incremental 16->48 on
scroll, geometry uniqueness 48/48 sampled distinct, daily card deals,
Fraunces 25px legible on mobile.

Two gaps between the live page and the canonical invite text.

1. The lineup named the three acts but linked nowhere. PLN's invite carries a
   destination for each, so the page now sends people to the work:
     ParVagues  -> soundcloud.com/parvagues
     Nesta Flex -> soundcloud.com/antoine-renaudet
     shipow     -> instagram.com/shipow
   The anchor takes `color: inherit` so the existing odd/even cyan/magenta
   :hover rules on .lineupName stay in charge; the underline is a 30% mix that
   solidifies on hover/focus-visible rather than a permanent blue link.

2. The RSVP paragraph read "une réponse avant le 1er août, ce serait top."
   True when written, silently wrong since 2 August, and actively confusing
   today — 15 August, with arrivals open and jour J six days out. A page whose
   copy expires is the same failure as a countdown to a date that has passed.

   So it reads the clock instead of a frozen sentence. Four phases off the
   existing JOUR_J plus three new date constants: before the deadline, after it
   but pre-arrivals, during the 15-23 August window, and after — which hands
   over to the v3.42Hz teaser from the invite.

   Rendered null on the server and filled in an effect, because the phase
   depends on the viewer's clock and a server/client disagreement is a
   hydration mismatch. The invariant "pas de billetterie / Riders, come to the
   storm" line stays outside the component, so the paragraph still reads
   correctly if JS never arrives.

Every other fact on the page was checked against the canonical invite and
already matched: 20-23 August, arrivals from the 15th, Labenne-Océan, jour J
the 22nd, 10 indoor places, tents, van, 16 capacity, +1 welcome, both stations,
the 15-minute Bayonne->Labenne train, the taxis, and the packing list.

Verified: clean build, all three hrefs present in the prerendered HTML, and
zero occurrences of "1er août" in the server output.

origin/main carried PR #7 — the entanglement-themed CosmicFest rebuild, merged
2026-06-29 and LIVE on me.nech.pl/cosmicfest ever since. Meanwhile this branch
hoisted the whole app out of next/ and deleted the Pages Router. The two sides
had zero overlapping paths, so a naive `git diff --name-only` check reported no
conflict — and was wrong in the most expensive way available: one side had
deleted the entire tree the other side was editing.

Resolving "ours" would have silently deleted the invite from a page guests are
reading right now, six days before the festival. Resolving "theirs" would have
resurrected the Pages Router. Both merge without complaint. So: a port.

Git's rename detection did most of it — Countdown, the stylesheet and
EntanglementField all landed at their App Router homes automatically. Five
content hunks in the page body needed hand-resolution, all "theirs, adapted":

- next/pages/cosmicfest/index.js  ->  app/cosmicfest/CosmicFestClient.js
- <Head> block                    ->  page.js `metadata` + `viewport` exports
  (App Router has no <Head>; theme-color moves to `viewport` per Next 15)
- kept 'use client' and the @/ path aliases over the ../../ relatives
- dropped the v0 June-21st countdown; JOUR_J is now 2026-08-22T18:00:00+02:00

Also fixes a build break that predates this merge and had nothing to do with it:
#161 regenerated the OPAL tracks.json from the parsers, renaming `ingredients`
to `samples` AND changing its shape — rich {type,code,description} objects
became bare name strings. LiveEvent.js still called track.ingredients.map(),
so /parvagues/live/opal-festival-2026 threw at prerender and failed the whole
build. Now renders whichever generation is present, guarded with Array.isArray
so a third shape can't crash the build either.

Verified: yarn build clean, 86/86 static pages. /cosmicfest 6.04 kB vs the
6.3 kB the original PR measured. Built HTML carries intrication, v2.67Hz,
Labenne, the full lineup, <title>cosmicfest_v2.67Hz</title>, theme-color
#1a1330, and zero occurrences of "juin". The 2026-08-22 target is present in
the shipped chunk. next/ stays deleted — 0 files.

These timecodes were generated before #148 — back when track boundaries came
from Pulsar tab-focus events rather than from the audio. Tab focus records when
PLN LOOKED at a file, not when the music changed, so every cut was wrong by
however long he sat on a tab before evaluating it.

Regenerated from the measured boundaries (segments_v3.json) via
Tidal/tools/gig-metadata.py, which now reads that shape directly and matches
segments to the setlist by title rather than by position.

  #  track                        was        now      drift
  5  You My Sunshine              0:25:41    0:25:58    +18s
  7  Piment Bresilien             0:36:51    0:37:07    +17s
  9  Perfect                      0:48:24    0:49:14    +50s
 10  Gimme Acid                   0:53:39    0:54:12    +33s
 11  Ghosts in the Toilets        0:58:48    0:59:20    +32s
 13  Vague de CRIME               1:04:33    1:04:49    +16s
 14  Desire                       1:09:12    1:09:40    +28s

totalDuration_s 4809 -> 4769.1. Tracks 1, 12 and 15 were already correct.

Only timing changed: names, order, bpmRange, styleDistribution and all 60
samplePacks diff byte-identical against the previous file, and venue/stage are
carried through verbatim. This matters beyond the website — Slopmotion reads
this file to cut visuals to the set, so shipping it stale would have put the
cuts half a minute off the music on a third of the album.

Third Opal in a row and the first on the main stage. Saturday 8 Aug 2026,
sunset slot, 1h20, 15 tracks of live-coded TidalCycles.

tracks.json is GENERATED, not typed — Sound/Tidal/tools/gig-metadata.py reads
membership/order/name/bpm/section from backlog.md via the setlist parser, the
sample packs from each .tidal via setlist_samples, and the timecodes from the
Ardour take. Nothing here was copied by hand, which is the point: the last time
gig strings were hand-carried between files they were wrong.

The per-track timecodes are new for a lives entry and deliberate — they let
Shipow cut Slopmotion visuals to the set without re-deriving boundaries by ear.
They were measured by aligning the 1 Hz gig log to the audio via
cross-correlation (r>=0.99 over 20 probes, 0.00 ms spread).

Note for whoever touches lives content next: the live tree is content/lives/,
NOT content/parvagues/lives/ (legacy, last moved by the June hoist) and not
next/content/lives/ (the path Sound/Tidal/CLAUDE.md still documents — stale
since the app moved out of next/).

Full redesign of the standalone invite page for the 2026 edition (20-23 August,
Labenne-Ocean, jour J samedi 22). Concept: intrication (entanglement) - two
states, one system, communicating across distance. Dark OKLCH design system with
a paired cyan/magenta accent language, an EntanglementField canvas (starfield +
mirrored particle pairs + 67Hz interference waveform), Archivo (wdth) + Martian
Mono, replacing the v0 light theme.

- new EntanglementField signature canvas (DPR-capped, mobile-scaled, full
  prefers-reduced-motion static path)
- sections: hero, concept, jour-J lineup, sejour, hebergement, transport,
  packing, v0 souvenirs (lifted audio embeds + accessible photo lightbox), RSVP
- countdown retargeted to 2026-08-22, hydration-safe placeholder
- lightbox renders full-size via plain img with managed focus
- add PRODUCT.md / DESIGN.md design context at repo root

Verified: clean SSG build (6.3 kB), WCAG AA contrast, zero console errors,
correct SSR + reduced-motion paths.

The canonical tracklist carried the old track name "Aria Sans Serif" and, worse,
a `file` pointing at live/collab/raph/aria_sans_serif.tidal — a path that no
longer exists. The track was renamed to Mafia Sans Serif in the score long ago
(real file: mafia_sans_serif.tidal); only the published metadata lagged. Since
the track identity in the armada catalog pipeline IS its .tidal path, the
dangling ref meant the catalog keyed this track on a non-existent score.

Fixed both the display name and the file ref to the real score. This is the
canonical root: the armada catalog regenerates from here (tide.py build).

Reflect Step 5: single lib/content/index.ts (two collection shapes),
wrappers re-export from @/lib/content, plain string[] ids +
.map((id) => ({ id })), and the parvagues-presence.ts seam.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Phase 1 Step 5. Fold lib/utils.js (flat Markdown collections) and
lib/livesData.js (year-foldered ParVagues gigs) into one module,
lib/content/index.ts — two collection shapes in one entry, not one
forced shape. Thin section wrappers (posts/hydras/poems/talks) now
re-export from @/lib/content; the two ParVagues pages import the lives
API from there too. Old lib/utils.js and lib/livesData.js deleted.

- strip the per-file console.log noise that was in lib/utils.js;
- getAllContentIds now returns plain string[]; the three dynamic pages
  drop the vestigial Pages-Router `.map(({params}) => params)` adapter
  for `.map((id) => ({ id }))`;
- add lib/content/parvagues-presence.ts: a single thin seam holding the
  already-in-repo platform links, so a future tooling-emitted
  presence.json swaps in without touching components. No schema, no
  invented links, components not yet rewired (deliberate).

Verified: prod build green (14 routes, all dynamic params intact);
fresh-dev smoke 14/14.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Phase 1 Step 4. Move the palette out of globals.css :root into a new
styles/tokens.css: a neutral/professional default on :root (landing +
content) and the ParVagues neon/dark palette scoped to
[data-theme="parvagues"], set on the app/parvagues/layout.tsx wrapper.
The ~90 var(--…) consumers resolve against that ancestor scope, so
theming is one attribute — no per-component edits.

- globals.css: drop the :root palette + hardcoded dark html/body bg;
  body now reads var(--surface)/var(--text-primary).
- parvagues.module.css: remove the dead duplicate .colorRoot/.colorContainer.
- main.css: replace the body:not(:has(.parvagues-root)) element-style hack
  with a positive .site-shell scope on the content Layout container; links
  use the new --link token.
- delete dead styles/dunbar.module.css.

Verified: prod build green (14 routes, ParVagues ISR intact); fresh-dev
smoke all 200; data-theme scoping confirmed (landing neutral, parvagues neon).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>