Delete docs.ps1: it is an installed file, not a committed one (#14)

Resolves W-D6 for docs.ps1. The repository was carrying a hand-written copy of
a file the documentation tooling generates.

The item was filed under a wrong premise and correcting it is what resolved it.
docs.ps1, docs/Dockerfile and docs/.dockerignore all date from the initial
commit -- before the template was installed in W0, which wrote only build/ and
.config/ -- so they were never stale vendored copies. And setup-docs.ps1
rewrites docs.ps1 with four substitutions, so the installed form never matches
the raw template and the byte-comparison that flagged this was never valid.

docs.ps1 is therefore a generated file, and committing a hand-written
substitute meant carrying a permanent invisible fork of something the tooling
owns. Invoke-SetupDocs writes the real one.

Checked rather than assumed: nothing under .github/workflows executes it; all
seventeen references are prose or absolute URLs so no relative link resolves to
it; and upstream's parameter set is a superset of the deleted one, so every
documented command still works once the installer runs. README.md therefore
needed no edit, which also avoided regenerating docs/src/pages/index.md by hand.

The gain is the one flagged when this was filed: the installed docs.ps1
regenerates the README-derived site root every run, retiring the by-hand
replication needed because there is no pwsh in the agent environment. The cost,
recorded in CLAUDE.md and the contributor guide: until the next installer run,
./docs.ps1 does not exist in a fresh checkout.

docs/Dockerfile and docs/.dockerignore are retained -- they are the Docker
build context the preview depends on, so removing them would leave no way to
build the site locally at all.

Author: The-Running-Dev

CLAUDE.md

@@ -101,7 +101,12 @@ build context:
 - `docs/Dockerfile` — extends `ghcr.io/the-running-dev/docs-template` and `COPY . .`
   overlays the above onto `/template`.
 
-Run it with **`docs.ps1`** (repo root; needs Docker Desktop running):
+Run it with **`docs.ps1`** (repo root; needs Docker Desktop running). **It is installed by
+`Invoke-SetupDocs`, not committed** — the installer rewrites it for this project's paths and
+tag, so it is generated rather than vendored. A hand-written copy predating the template used
+to be committed here and was deleted; if the file is missing, run the installer. The installed
+version also regenerates `docs/src/pages/index.md` from `README.md` on every run, which
+retires doing that by hand:
 
 | Command | Does |
 |---|---|

docs.ps1

@@ -18,6 +18,15 @@ image. This page covers building and checking it.
 | `./docs.ps1 -Live` | Same, but bind-mounts `docs/` so edits hot-reload |
 | `./docs.ps1 -BuildOnly` | Build the image only |
 
+> **`docs.ps1` is installed, not committed.** It comes from the documentation template
+> along with `build/` and `.config/`, and is written by `Invoke-SetupDocs` — which rewrites
+> it for this project's paths and image tag, so it is a *generated* file rather than a
+> vendored one. If it is not present in your checkout, run the installer.
+>
+> It was previously committed here in a hand-written form that predated the template and
+> had drifted from it; the installed version additionally regenerates the README-derived
+> site root on every run, which is why the local copy was dropped rather than reconciled.
+
 ## What is authored, and what is generated
 
 Everything under `docs/docs/` is authored directly. **Exactly one page on the site is

docs/docs/guide/documentation-site.md

@@ -11,7 +11,7 @@ filed and merged upstream afterwards, and the vendored gate re-synced to pick it
 | W-D3 site links | Done for `src/engine/` and `docs.ps1` via two new `guide/` pages; the two companion-repository links stay on the code host, which is correct |
 | W-D4 upstream gap | Done — filed and merged upstream as [#56](https://github.com/The-Running-Dev/Docusaurus-Template/pull/56), then vendored back |
 | W-D5 gate sync | Done — vendored gate is byte-identical to upstream again |
-| W-D6 preview toolchain | **Open** — `docs.ps1`, `docs/Dockerfile`, `docs/.dockerignore` are well behind upstream; found while doing W-D5, deliberately not folded into it |
+| W-D6 preview toolchain | Done for `docs.ps1` — deleted, since it is an *installed* file the repository should not have been carrying. `docs/Dockerfile` and `docs/.dockerignore` retained; see below |
 | W-D7 nested parentheses | Done — fixed upstream as [#57](https://github.com/The-Running-Dev/Docusaurus-Template/pull/57) with a scanner, then vendored back |
 
 **Scope:** How the published site is organised and linked, plus the vendored-tooling debt
@@ -213,10 +213,45 @@ local overrides and are not in scope.
 correctness fix with no behaviour change here; these three change how the site is previewed
 and built locally, and `docs.ps1`'s own header prose is repo-specific — it may be locally
 authored rather than a stale vendor copy, which has to be established before overwriting it.
-Worth noting that upstream's `docs.ps1` would remove a real pain: the homepage regeneration
-this repository currently does by replicating the generator's logic by hand, because there is
+
+### Resolution — `docs.ps1` deleted
+
+**It was locally authored, and that was the defect.** All three files date from the initial
+commit, *before* the template was installed in W0 — which wrote only `build/` and `.config/`.
+So they were never stale vendored copies, and the byte-comparison that first flagged them was
+never a valid test: `setup-docs.ps1` **rewrites** `docs.ps1` with four substitutions (script
+directory, config directory, image tag, base image), so the installed form never matches the
+raw template anyway.
+
+That reframes the item. `docs.ps1` is a **generated** file — the installer's output — and
+committing a hand-written substitute meant the repository carried a permanent, invisible fork
+of a file the tooling owns. Deleting it is the fix; `Invoke-SetupDocs` writes the real one.
+
+Deletion is safe and was checked rather than assumed:
+
+- **No CI dependency.** Nothing in `.github/workflows/` executes it; the only `docs.ps1`
+  mention in `docs-ci.yml` is a comment about `setup-docs.ps1`.
+- **No broken links.** Its seventeen references are prose or absolute URLs — no relative
+  markdown link resolves to it, so neither the gate nor the Docusaurus build is affected.
+- **The references stay true.** Upstream's parameter set is a superset of the deleted one —
+  same `-Live`, `-BuildOnly`, `-Port`, `-Tag`, `-BaseImage`, plus `-NoHomepage` — so every
+  documented command still works once the installer runs. `README.md` therefore needed no
+  edit, which also avoided regenerating `docs/src/pages/index.md` by hand.
+
+**The gain is the one flagged when this was filed:** the installed `docs.ps1` regenerates the
+README-derived site root on every run, retiring the by-hand replication of
+`ConvertTo-DocumentationHomepage.ps1`'s logic that this repository has needed because there is
 no `pwsh` in the agent environment.
 
+**The cost, stated plainly:** between this change and the next `Invoke-SetupDocs` run, `./docs.ps1`
+does not exist in a fresh checkout. `CLAUDE.md` and the contributor guide now say so and say
+what to run.
+
+**`docs/Dockerfile` and `docs/.dockerignore` are retained.** They are also installer outputs,
+but they are the Docker *build context* the preview depends on, and deleting them would leave
+no way to build the site locally at all until the installer runs. Their drift is recorded
+above and is not causing a problem; revisit if the installer is re-run for another reason.
+
 Also worth reporting, though not ours to fix:
 `docs/getting-started/installing-the-docs-system.md` upstream went stale with #52 — it still
 tells non-`/` consumers to add `docs/src/pages/index.md` by hand and calls