remove dated examples

soleprint/atlas2/docgen/docs/index.html

@@ -759,7 +759,7 @@ python3 -m docgen view ir.json --shape          <span class="c"># what will this
   <a href="viewer.html?src=img/erd.svg">
     <img src="img/erd.svg" alt="an entity-relationship diagram">
   </a>
-  <figcaption>A schema from the sample room. Same emitter, same style file as
+  <figcaption>An invoicing schema. Same emitter, same style file as
     every other diagram here.</figcaption>
 </figure>
 

soleprint/atlas2/docgen/extractors/db.py

@@ -9,7 +9,7 @@ reading it means this extractor works for every source modelgen supports
 (Django, SQLAlchemy, OpenAPI, CSV/ODS, a live database) without knowing about
 any of them.
 
-    python3 -m docgen extract db --schema cfg/sample/.../graphgen/schema.json
+    python3 -m docgen extract db --schema path/to/schema.json
 
 Connecting to a live database is **not here**. `modelgen from-db --url ...`
 reflects via SQLAlchemy's Inspector across dialects and writes the schema.json

soleprint/common/theme/bake.py

@@ -11,7 +11,7 @@ so the background goes transparent and the text goes initial-black on a design
 that assumed dark. Unstyled, not merely unbranded.
 
 That matters because `/theme.css` is an absolute path and soleprint is not
-always at the root. In the sample room's nginx, soleprint sits under `/spr/`
+always at the root. In a wrapped site's nginx, soleprint sits under `/spr/`
 while `location /` proxies to the frontend, so `/theme.css` reaches the wrong
 service. Same story for a page opened over file://.
 

soleprint/station/cabinets/README.md

@@ -35,12 +35,12 @@ Then build. `python build.py --cfg <room>` merges each cabinet's `service.yml`
 into the room's `docker-compose.yml` and appends its settings to `.env.example`:
 
 ```bash
-python build.py --cfg sample
-cd gen/sample && docker compose up -d
+python build.py --cfg <room>
+cd gen/<room> && docker compose up -d
 ```
 
-**A service the room already declares wins.** `cfg/amar/docker-compose.yml`
-ships its own `db`; switching on the postgres cabinet will not overwrite it.
+**A service the room already declares wins.** A room whose `docker-compose.yml`
+ships its own `db`: switching on the postgres cabinet will not overwrite it.
 Build says so when it skips one.
 
 ## On a cluster

soleprint/station/tools/datagen/README.md

@@ -26,8 +26,7 @@ method name *is* the model name — there is no registry to update.
 ```python
 from faker import Faker
 
-# Guarded so the file also runs on its own, outside a built instance —
-# see cfg/sample/soleprint/station/tools/datagen/fixture.py.
+# Guarded so the file also runs on its own, outside a built instance.
 try:
     from station.tools.datagen.base import BaseDataGenerator
 except ImportError:

soleprint/station/tools/tester/tests/test_template.py

@@ -80,7 +80,7 @@ Select one via `POST /tools/tester/api/environment/select`, or set the env direc
 
 WRITING ONE
 ───────────
-The domain below is the in-repo invoicing fixture (cfg/sample) — deliberately
+The domain below is an invoicing example — deliberately
 generic. Substitute your own; the shape is the part that transfers.
 
     from ..base import ContractTestCase