Drop every em dash

.changeset/blue-rocks-install.md

@@ -0,0 +1,5 @@
+---
+"create-eigen-game": patch
+---
+
+The `firebase` CLI is now suggested as `curl -sL https://firebase.tools | bash` rather than `npm install -g firebase-tools`, both in the missing-tooling report and in the scaffolded project's README. That installer is Google's own, it picks a standalone binary or npm to suit the machine, and it is the one the Firebase documentation leads with. The npm install still works; it just needs a global prefix the reader may not have write access to.

.changeset/plain-words-no-dashes.md

@@ -0,0 +1,16 @@
+---
+"@eigeninteractive/server": patch
+"@eigeninteractive/kernel": patch
+"@eigeninteractive/rules": patch
+"@eigeninteractive/testkit": patch
+"create-eigen-game": patch
+---
+
+Em dashes are gone from every line this repository writes. Most of that is comments and documentation, but some of it is text that ships:
+
+- **Error and response messages.** `State updated, try again` (kernel `stateUpdated`), `Too many requests in a short window. Slow down and try again.`, `Unsupported image type '…'. Use image/jpeg, …`, `Account deletion failed. Please try again`. Dispatch on `code`, never on `error`, so nothing that follows that rule is affected.
+- **OpenAPI descriptions**, and therefore the generated `eigen_api` Dart client and the published HTTP reference. Wording only; no operation, schema or status code moved.
+- **Engine-rendered public pages.** A page title now reads `Terms of Service: My Game`, joined with a colon rather than a dash, and the `/j` share description separates the versus line with a comma.
+- **`create-eigen-game`'s own output**, including the greeting, the missing-tooling report and the scaffolded project's README.
+
+`worker-configuration.d.ts` is untouched: it is Cloudflare's generated runtime types, reproduced by `wrangler types`.

.github/dependabot.yml

@@ -2,7 +2,7 @@ version: 2
 
 # Keeps the pinned GitHub Actions current. Without this they silently drift:
 # major tags like `actions/checkout@v7` float across patches but never across
-# majors, so a workflow keeps working while falling years behind — which is
+# majors, so a workflow keeps working while falling years behind, which is
 # exactly how this repo ended up on `pnpm/action-setup@v4` after the workspace
 # moved to pnpm 11 (v6 is where pnpm 11 support landed).
 #

.github/workflows/checks.yml

@@ -11,14 +11,14 @@ name: Checks
 #
 # `workflow_call` re-executes these jobs; it does not look up whether they
 # already passed on this SHA (GitHub has no such mechanism, and it would be the
-# wrong thing anyway — main is a different commit from the PR head as soon as
+# wrong thing anyway: main is a different commit from the PR head as soon as
 # anything else merges). What is shared is the definition, not the run.
 on:
   pull_request:
     branches: [main]
   workflow_call:
 
-# Correctness only — this workflow never deploys and needs no Cloudflare
+# Correctness only. This workflow never deploys and needs no Cloudflare
 # credentials. Deploying is a deliberate `pnpm --filter <worker> deploy` from a
 # machine with `wrangler login`, because it applies D1 migrations against a real
 # database. Nothing here talks to the network beyond the package registry.
@@ -27,11 +27,11 @@ on:
 # `secrets: inherit`.
 #
 # The Workers tests run under @cloudflare/vitest-pool-workers, which boots the
-# real `workerd` runtime with local D1/R2/DO simulation — no account, no
+# real `workerd` runtime with local D1/R2/DO simulation: no account, no
 # bindings to provision, and the same runtime semantics as production. That is
 # why `pnpm -r test` is the whole story and there is no separate integration job.
 
-# Superseding a pull request's run is free — only the newest push matters. A
+# Superseding a pull request's run is free, since only the newest push matters. A
 # run reached through `workflow_call` is NOT cancellable: it gates a release, so
 # cancelling it because a second commit landed on main would abort a publish
 # mid-flight. Keying on the SHA rather than the ref keeps those runs from
@@ -55,7 +55,7 @@ jobs:
       - uses: actions/checkout@v7
         with:
           # The changesets guard at the end of this job diffs against
-          # `origin/main`, which needs a merge base — a shallow clone has none.
+          # `origin/main`, which needs a merge base, and a shallow clone has none.
           fetch-depth: 0
 
       - uses: pnpm/action-setup@v6
@@ -104,7 +104,7 @@ jobs:
       # Same shape of guard, higher stakes: migrations are generated from the
       # drizzle schemas and applied at deploy, so a schema edit that skipped
       # `db:generate` ships code expecting columns the database does not have.
-      # Nothing else catches it — the tests run against migrations, so schema
+      # Nothing else catches it: the tests run against migrations, so schema
       # and migrations drift together silently until a real deploy.
       #
       # `< /dev/null` matters: drizzle-kit prompts when a change is ambiguous
@@ -120,15 +120,15 @@ jobs:
           # A brand-new migration is an untracked file, which `git diff` alone
           # would not see.
           test -z "$(git status --porcelain -- packages/server/migrations packages/server/src/do/migrations)" \
-            || { echo "::error::db:generate produced a new migration file — commit it."; git status --short -- packages/server/migrations packages/server/src/do/migrations; exit 1; }
+            || { echo "::error::db:generate produced a new migration file. Commit it."; git status --short -- packages/server/migrations packages/server/src/do/migrations; exit 1; }
 
       # worker-configuration.d.ts is generated from wrangler.jsonc bindings and
       # committed. Typecheck only catches a binding that is *used* and missing;
       # a renamed or removed binding stays green until runtime.
       #
       # IF THIS FAILS AND `wrangler types` SHOWS NO DIFF LOCALLY: you have an
       # `examples/rps/.dev.vars`. It is gitignored, absent here, and `wrangler
-      # types` READS IT — so generating locally bakes your local secret names
+      # types` READS IT, so generating locally bakes your local secret names
       # into the committed file and it stops being reproducible from committed
       # inputs. Move `.dev.vars` aside, regenerate, commit that, and move it
       # back. This guard exists precisely to catch that contamination.
@@ -142,7 +142,7 @@ jobs:
       # actually SHIP, which nothing else here can see.
       #
       # A change to a published package with no `.changeset/*.md` merges green,
-      # produces no version pull request, and is never released — silently, with
+      # produces no version pull request, and is never released, silently, with
       # no artifact anywhere to notice. That is the failure mode worth
       # automating against; forgetting to MERGE the version PR is not, because
       # it leaves an open pull request titled "Release: version packages" at the
@@ -154,11 +154,11 @@ jobs:
       #
       # Skipped on the version pull request itself, which by construction edits
       # every published package while deleting the changesets that describe
-      # them — exactly the shape this guard rejects. Without the exclusion it is
+      # them, which is exactly the shape this guard rejects. Without the exclusion it is
       # a required check that branch can never satisfy.
       #
-      # For a change that genuinely should not release — a comment, a test, an
-      # internal refactor — `pnpm changeset --empty` records that decision as a
+      # For a change that genuinely should not release (a comment, a test, an
+      # internal refactor) `pnpm changeset --empty` records that decision as a
       # committed file rather than leaving the guard to be argued with.
       - name: Changes to published packages are described by a changeset
         if: github.event_name == 'pull_request' && github.head_ref != 'changeset-release/main'
@@ -168,7 +168,7 @@ jobs:
 
   # The Dart client is generated from openapi.json and committed, so that a
   # breaking wire change arrives as a reviewable Dart diff in the same pull
-  # request that changed the schema — rather than surfacing days later in
+  # request that changed the schema, rather than surfacing days later in
   # another repository. This job is what makes "committed" mean "current".
   #
   # It is separate from `check` because it is the only thing here that needs
@@ -209,10 +209,10 @@ jobs:
           git diff --exit-code -- clients/dart \
             || { echo "::error::The Dart client is stale. Run 'pnpm dart-client' and commit clients/dart."; exit 1; }
           test -z "$(git status --porcelain -- clients/dart)" \
-            || { echo "::error::Generation produced new files under clients/dart — commit them."; git status --short -- clients/dart; exit 1; }
+            || { echo "::error::Generation produced new files under clients/dart. Commit them."; git status --short -- clients/dart; exit 1; }
 
       # Proves the artifact we would publish actually compiles, and keeps the
-      # pub.dev score honest — `dart analyze` is what pana grades.
+      # pub.dev score honest, since `dart analyze` is what pana grades.
       - name: Analyze
         run: dart analyze
         working-directory: clients/dart
@@ -224,8 +224,8 @@ jobs:
   # Scaffolds a real project and compiles both halves of it.
   #
   # Everything else here checks a package. This checks the thing a new user
-  # actually runs, which nothing did before: `templates/app-overlay` — the Dart
-  # files that import `package:eigen_flutter/eigen_flutter.dart` — was never
+  # actually runs, which nothing did before: `templates/app-overlay`, the Dart
+  # files that import `package:eigen_flutter/eigen_flutter.dart`, was never
   # compiled anywhere, so the `eigen_flutter` range the scaffolder pins was an
   # assertion no build had tested. eigen-flutter's own `example/` is a different
   # tree and does not stand in for it.
@@ -273,12 +273,12 @@ jobs:
       # This does leave real coverage out, which an earlier version of this
       # comment denied. The Gradle config the scaffolder appends, the icons it
       # generates, and the manifest entries `eigen_flutter`'s plugin merges are
-      # none of them Dart sources — and that gap is what let a corrupted wrapper
+      # none of them Dart sources, and that gap is what let a corrupted wrapper
       # jar and corrupted launcher PNGs ship in every scaffolded project while
       # this job stayed green.
       #
       # Adding a release build was measured rather than estimated: 9m32s against
-      # this job's 2m06s, or 6m07s with `~/.gradle` cached — and the caching
+      # this job's 2m06s, or 6m07s with `~/.gradle` cached, and the caching
       # needs a restore/save split to be worth anything, because every runner is
       # a fresh VM. `gradle/actions/setup-gradle` does not work here at all; it
       # keys on a Gradle project in the workspace, and the build happens in a

.github/workflows/publish-eigen-api.yml

@@ -14,8 +14,8 @@ name: Publish eigen_api
 # Do not restructure this workflow expecting the constraint to lift.
 #
 # Hence the handoff: release.yml publishes to npm, then pushes an
-# `eigen_api-v<version>` tag with a PAT — a tag pushed by the built-in
-# GITHUB_TOKEN would deliberately not trigger anything — and that tag fires this
+# `eigen_api-v<version>` tag with a PAT (a tag pushed by the built-in
+# GITHUB_TOKEN would deliberately not trigger anything) and that tag fires this
 # workflow, whose OIDC token now carries a tag ref that pub.dev accepts.
 #
 # The alternative is storing a long-lived pub.dev credential in GitHub secrets
@@ -25,7 +25,7 @@ name: Publish eigen_api
 # pub.dev setup, once (eigen_api → Admin → Automated publishing):
 #   - Repository:   eigeninteractive/eigen-server
 #   - Tag pattern:  eigen_api-v{{version}}
-# No credential is stored anywhere — the OIDC identity is the authentication.
+# No credential is stored anywhere: the OIDC identity is the authentication.
 on:
   push:
     tags: ["eigen_api-v*"]
@@ -49,7 +49,7 @@ jobs:
 
       # The tag names the version; the committed pubspec must already carry it
       # (version-packages stamped it in the version PR). A mismatch means the
-      # tag was pushed against the wrong commit — fail rather than publish it.
+      # tag was pushed against the wrong commit, so fail rather than publish it.
       - name: Tag matches pubspec version
         working-directory: clients/dart
         run: |
@@ -58,7 +58,7 @@ jobs:
           [ "$tag" = "$pkg" ] || {
             echo "::error::tag eigen_api-v$tag does not match pubspec version $pkg"; exit 1; }
 
-      # The generated code is committed, so nothing is generated here — publish
+      # The generated code is committed, so nothing is generated here. Publish
       # exactly what the tag points at.
       - name: Dry run
         run: dart pub publish --dry-run