The esbuild header advertised a build output that stopped existing in #3400. Nineteen lines below, the same file said the opposite.
esbuild.config.mjs:6 * - dist/server.mjs — ork-elicit (setup-wizard form elicitation)
^^^^^^^^^^^^^^^ advertises an output
esbuild.config.mjs:25 // The ork-elicit entry point was retired (EPIC C mechanism 11)
esbuild.config.mjs:28 await build({
esbuild.config.mjs:30 entryPoints: ['./src/docs-server.ts'],
esbuild.config.mjs:31 outfile: './dist/docs-server.mjs'
^^^^^^^^^^^^^^^^^^^^ the only thing actually built
Verified rather than taken from the PR body: there is exactly one build() call in the file, and nothing produces dist/server.mjs.
| Location | Tense | Verdict |
|---|---|---|
| esbuild.config.mjs:6 | present — "bundles ... to" | stale claim, removed here |
| esbuild.config.mjs:25 | past — "was retired" | keep |
| setup/references/configure-wizard.md:34 | past — "that consolidated" | keep |
| release-sync/SKILL.md:92 | past — "This used to prefer" | keep |
The repo's own authoring rule says it directly: historical and citation prose is exempt. "Deprecated in v1.0" is accurate documentation; rewriting it to look current is the opposite of a cleanup. Only line 6 asserts something false in the present tense.
The description called this "the last stale ork-elicit reference in the repo." It is the last stale claim — three mentions remain, and all three should stay. Also worth recording: .mcp.json is untracked, so the ork-elicit server entry removed there today was a local operator edit, not a repo change.