Give the cache chown a command that works, record the pop-culture exclusion, and read the plan's breaking unit off the versioning table

AGENTS.md

@@ -5,8 +5,9 @@
 - A change under `data/` or to the shape pin adds its `CHANGELOG.md` entry under `Unreleased` in the same PR, and so does a change to a flag, an exit code, an exported name, a fence, a builtin or the lowest Go; what is major is the README's Versioning table.
 - One-line commit messages: no ticket prefix, no repo name, no authorship trailers.
 - Merges are fast-forward only, which `tea pr merge` cannot spell — every style it
-  offers fails with "is it still open?". Use
+  offers fails with "is it still open?", as does a merge whose required checks are
-  `tea api -X POST /repos/larvit/fejkdata/pulls/<n>/merge -f Do=fast-forward-only`.
+  still pending, so read the checks before believing the style is the problem. Use
+  `tea api /repos/{owner}/{repo}/pulls/<n>/merge -f Do=fast-forward-only`.
 - Hard tabs. No comment by default; delete a restatement, a rationale, history, or a file preamble.
 - One spelling per result: reject the other at `New`, and let the error name the spelling to use.
 - A standing choice a reader would relitigate goes under Decisions in the README, not in a comment.

README.md

@@ -1151,6 +1151,10 @@ App developers writing tests and fixtures, in Go and at a shell:
   tells the two apart, `sex[f].first-name[Kim]`, the ambiguity error spells each
   row inside its parent, and a name repeating inside one parent row is refused at
   load, since nothing could then select it.
+- **No pop-culture catalogues.** Every other faker ships film, band and character
+  names; fejkdata ships none. They are the one kind of value a fixture never needs to
+  be real, they carry trademarks a test database has no business holding, and the
+  weights that make a real register worth shipping do not exist for them.
 - **`misc` is what every locale shares.** A category whose facts differ by country
   belongs in that country's locale, read from the register that country's own
   records use; `misc` takes only sources that are international. NHTSA vPIC and
@@ -1238,6 +1242,15 @@ docker compose run --rm --user "$(id -u):$(id -g)" fmt   # gofmt -w .
 docker compose run --rm --user "$(id -u):$(id -g)" tidy  # go mod tidy
 ```
 
+A `--user` command answering `permission denied` on `/cache` has met root-owned
+files in the `gocache` volume: Docker creates the volume root-owned, and every
+command above that omits `--user` writes into it as root. Hand it back, and again
+whenever it recurs:
+
+```sh
+docker compose run --rm --user root --entrypoint chown test -R "$(id -u):$(id -g)" /cache
+```
+
 Every pull request runs `docker build .` against both the latest and the lowest
 supported Go, and must pass before it can be merged — unless it changes none of
 the files the build and its tests read, nor the workflow itself, in which case
@@ -1258,14 +1271,6 @@ in its own commit:
 REPIN=1 docker compose run --rm --user "$(id -u):$(id -g)" test
 ```
 
-The `gocache` volume takes the uid of whichever command created it, so a fresh
-checkout whose first command ran as root answers this one with `permission denied`.
-Give it back:
-
-```sh
-docker run --rm -v "${PWD##*/}_gocache":/cache alpine:3.23.3 chown -R "$(id -u):$(id -g)" /cache
-```
-
 A shipped table built from a source is rebuilt by its script under
 [`data-import/`](data-import), one command per dataset, fetching the source named in
 [`DATA-LICENSES.md`](DATA-LICENSES.md). Downloads are cached under

todo.md

@@ -1,16 +1,15 @@
 # Plan
 
-Ordered as the releases that ship it. Research notes:
+Ordered as the releases that ship it.
-`~/code/claude-handoffs/fejkdata/2026-09-16/`.
 
 ## v0.1.0
 
 ### Data
 
-Shape: T = table, t = template, c = choice. Every factual list is read from a
+Shape: T = table, t = template, c = choice. Read every factual list from a register
-register by a `data-import/` script, per README goal 10.
+by a `data-import/` script, as README goal 10 asks.
 
-- Add the remaining `misc` tables and templates from the table below, closing step 4.
+- Add the remaining `misc` tables and templates from the table below.
 - Read `misc.emoji` from the Unicode `emoji-test.txt` register, and `misc.car` from an
   international make and model source; vPIC and Mobility Sweden are national, so they
   build `en_US.car` and `sv_SE.car`.
@@ -26,11 +25,13 @@ register by a `data-import/` script, per README goal 10.
   another category, and report a struct column's draw conflict with the path spelling
   a tag takes.
 - Let `geo.SE.locality[Lund].address` descend from a selected row into the template
-  beside the family: the path step reaches a sibling category and the outer selector's
+  beside the family: require the path step to reach a sibling category, and seed every
-  pins seed every draw group of the render.
+  draw group of the render from the outer selector's pins.
-- Decide whether `email.local` and `username` share one handle list — a reference
+- Decide whether `email.local` and `username` share one handle list, and read the
-  between shipped categories is a major once tagged, so it lands before v0.1.0 or not
+  handles from the shipped name tables rather than the hand-written list they use
-  at all.
+  today — a reference between shipped categories breaks a consumer once tagged, so it
+  lands before v0.1.0 or not at all. `price` and `url` stay curated: a price format is
+  no register fact, and the domains are RFC 2606's reserved ones.
 
 `misc` (locale-neutral)
 
@@ -95,7 +96,8 @@ register by a `data-import/` script, per README goal 10.
 ### Open questions to settle
 
 - Decide whether `misc.browser` becomes a parent of `misc.useragent`, so
-  `misc.browser[Chrome].useragent` resolves. Adding a `parent` after v0.1.0 is a major.
+  `misc.browser[Chrome].useragent` resolves. Adding a `parent` after v0.1.0 breaks a
+  consumer, so it rides a 0.(x+1).0.
 - Decide whether `misc.timezone` keeps every zone tzdb names: one added recently,
   `Europe/Kyiv` among them, is rejected by a consumer resolving it against older
   tzdata, and the population weight makes that zone likelier, not rarer. Today the
@@ -103,7 +105,7 @@ register by a `data-import/` script, per README goal 10.
   alternative.
 - Decide whether `misc.territory.country` is renamed `sovereign`: it holds a code, and
   `country` collides with the `misc.country` path it replaced. A rename after v0.1.0
-  is a major.
+  breaks a consumer, so it rides a 0.(x+1).0.
 - Decide whether `parent: territory` stays, given a `--data-path` override of
   `misc.territory` now fails `New` unless `misc.timezone` is overridden with it.
 
@@ -126,10 +128,24 @@ register by a `data-import/` script, per README goal 10.
   `--min-population` and `--streets-per-locality`. The default embed stays under ~1 MB
   per country and `New` under ~50 ms.
 - Add the locales nb_NO, da_DK, fi_FI, de_DE, en_GB, nl_NL, fr_FR and es_ES, with
-  person, address, phone, national id, company and date names each, and the `geo` trees
+  person, address, phone, national id, company and date names each, and the `geo/`
-  NO, DK, FI, NL, FR, AU, CA, ES, GB and DE under them.
+  trees NO, DK, FI, NL, FR, AU, CA, ES, GB and DE their `address` reads by reference;
+  AU and CA get a tree with no locale of their own.
 - Add `{btc()}` and `{eth()}`, which need sha256 and keccak for Base58Check and EIP-55.
 - Pair a street with its exact postnummer, which needs an application to Lantmäteriet;
-  today a street goes to the nearest postal code centroid.
+  today a street goes to the nearest postal code centroid. It rewrites shipped rows, so
+  it is a major once 1.0 is cut and a minor before that.
+
+## v1.0.0
+
+- Cut it once the shipped data is in its record shape and one full minor has shipped
+  with no breaking change, per the README's Versioning table. Nothing else is planned
+  for it: what it needs is v0.1.0's record-shape work, then a quiet minor.
+
+## Not release-bound
+
+- Give the Go services a `user:` so `/cache` stops collecting root-owned files: today
+  every command documented without `--user` writes as root and breaks the next
+  `--user` one, which the README answers with a chown a reader has to repeat.
 - Publish a homepage with an in-browser generator: the library compiled to WebAssembly,
   so visitors generate as much data as they like in their own browser.