chore(cli): retire the abandoned tsup build path (#10185) (#10601)

`packages/cli` has built with `tsc -p tsconfig.build.json` since the oclif
migration (bbea22f, 2026-02-18), which in one commit switched `build` from
`tsup` to `tsc`, introduced `oclif.commands.target: "./dist/commands"`, and
pointed the `bin` field at the new `bin/run.js`. The tsup config was left
behind by that commit and has never been invoked since.

It was not inert, though. It declared `clean: true` with only `src/bin.ts` and
`src/index.ts` as entries, so running the obvious `tsup` next to a
`tsup.config.ts` wipes `dist/` and emits no `dist/commands/**` — leaving a CLI
that resolves zero commands, the "command not found" signature
`scripts/cli-build-prerequisite.mjs` exists to classify.

Removed:
- `packages/cli/tsup.config.ts` — invoked by no script, no turbo task, no CI
  step and no doc; in no tsc program either (the package tsconfig is
  `include: ["src"]`, the root one excludes `packages`).
- `packages/cli/src/bin.ts` — the carcass of the pre-oclif Commander entry
  point, gutted to a 13-line re-export by dd1e67b in the same migration.
  Its only referrer repo-wide was the tsup entry above.
- the `tsup` devDependency — the config's import was its only use in the
  package.

Verified by comparing the command surface oclif actually resolves (via
`Config.load`) before and after: identical, 60 commands and 68 topics, same
flags and aliases. The sole build-output difference is that `dist/bin.js` is
no longer emitted.


Claude-Session: https://claude.ai/code/session_019bmVFqoQPq63zhKrxdYG1r

Co-authored-by: Claude <noreply@anthropic.com>

Author: Elon Musk

.changeset/cli-retire-abandoned-tsup-config.md

@@ -0,0 +1,21 @@
+---
+"@objectstack/cli": patch
+---
+
+Remove the abandoned tsup build path from `packages/cli` (#10185): the
+`tsup.config.ts`, the orphaned `src/bin.ts` it was the only referrer of, and
+the now-unused `tsup` devDependency.
+
+The package has built with `tsc -p tsconfig.build.json` since the oclif
+migration, which also introduced `oclif.commands.target: "./dist/commands"`
+and moved the `bin` field onto `bin/run.js`. The tsup config was left behind
+by that commit and never invoked again — but it was not inert. It declared
+`clean: true` with only `src/bin.ts` and `src/index.ts` as entries, so anyone
+running the obvious `tsup` next to a `tsup.config.ts` would wipe `dist/` and
+emit no `dist/commands/**` at all, leaving a CLI that resolves zero commands.
+Deleting it removes the trap rather than documenting it.
+
+No published behaviour changes: the resolved oclif command surface is
+identical before and after (60 commands, 68 topics). The only build-output
+difference is that `dist/bin.js` — a re-export of `execute` from
+`@oclif/core` that nothing imported — is no longer emitted.

packages/cli/package.json

@@ -119,7 +119,6 @@
     "@oclif/plugin-plugins": "^5.4.87",
     "@types/better-sqlite3": "^7.6.13",
     "@types/node": "^26.2.0",
-    "tsup": "^8.5.1",
     "typescript": "^6.0.3",
     "vitest": "^4.1.10"
   },