TODO — Institut de beauté "Si j'étais moi" - à Lutry

Per-project status doc for everything a script can't derive: facts from the client, human

approvals, and owner-executed actions. Pipeline progress itself is computed from artifacts —

run node <skill-dir>/scripts/project-status.mjs --project <this project> for the full picture.

Conventions: 🔲 open · ✅ done · owner in brackets · every item keeps a stable [Tn] ID (new items take the next free number, IDs are never reused) — the dossier shows them so anyone can reply "T4 done, T2: …" from a phone. Keep items one-line and checkable.

Client items are questions a non-technical person can answer from their phone: plain words, a concrete example, no trade terms — a real client answered "display name ???" to jargon here. Translate them into the client's language when the dossier goes out.

Facts needed — [client]

• ☐T1Your exact opening hours, day by day (e.g. "Mon–Fri 9:00–18:30, Sat 9:00–16:00, closed Sun" — including lunch breaks and holiday habits)
• ☐T2Your trainings, diplomas or certifications, with their exact official names (we only publish what you can show a certificate for)
• ☐T3How can clients pay (cash, TWINT, card…)? And can a person in a wheelchair get into your premises?
• ☐T4The official registered name of your business, exactly as on your company registration, + your business ID number (UID/IDE, looks like CHE-123.456.789) if you have one. This can differ from the name on your sign — Swiss law requires the official one on the site's legal page
• ☐T5Your own photos we may publish (from the shot list in deploy/gbp-setup.md §3) — and for any photo showing a person, their OK in writing
• ☐T6Which languages do you serve clients in — and in which language(s) should the website be?

Visibility actions — [client executes, kits prepared]

• ☐T7Google Business Profile: create/claim per deploy/gbp-setup.md — then [agent] record place_id + run the dossier export
• ☐T8localsearch (local.ch + search.ch) / Apple / Bing per deploy/listings-kit.md

Decisions — [operator]

• ☐T9Styleguide approval (review at the preview /_styleguide/)
• ☐T10Final domain + email tier (references/domain-email.md)
• ☐T11Category-spec deviations confirmed (build/category-mapping.md)

Phase 2 — [agent, after styleguide approval]

• ☐T12Copy deck (all locales, incl. impressum + privacy) → operator reviews the markdown
• ☐T13Site build (tokens-driven) → distinctiveness + preflight gates → preview update
• ☐T14Publish: GitHub · Cloudflare · custom domain · deploy/go-live.md · registry entry

Later

• ☐T15Testimonials (real, consented, never invented) + reviews kickoff
• ☐T16Maintenance agreement decision → deploy/maintenance.md + registry flag