chore!: drop the in-repo npm release pipeline; compose.yml (CL-8132)

CONTRIBUTING.md

@@ -39,14 +39,9 @@ Thanks for your interest in Corbits Workbench.
    a package-owned ledger table, applied transactionally.
 8. Security issues go through [SECURITY.md](SECURITY.md), never a public
    issue.
-9. Changed a publishable `workflows/*` or `packages/*-tools` package?
-   Run `bun run changeset`, describe the change, and commit the
-   generated `.changeset/*.md` file alongside it — that's what the
-   tool-package-freshness check now expects instead of a hand-bumped
-   version. A "Version Packages" PR opened automatically off `main`
-   applies every pending changeset's version bump and changelog; merging
-   it is what actually ships the release to npm. See
-   [.changeset/config.json](.changeset/config.json) for which packages
-   are still `private` and excluded from this.
+9. Changed a publishable `workflows/*` or `packages/*-tools` package's
+   `src/`? Bump its `package.json` version — the tool-package-freshness
+   check enforces this. Nothing publishes to npm from this monorepo; a
+   package moves to its own repository before it can be published.
 
 This document will grow as the project does.

IMPLEMENTATION.md

@@ -101,7 +101,7 @@ own `noop-inference` endpoint or an unreachable placeholder host —
 enforced by `assertNeverRealProvider` in `scripts/e2e/harness.ts`. CI infers
 required-ness from `CI=true` so a missing `DATABASE_URL` fails loudly there
 instead of silently skipping. Start Postgres locally with
-`docker compose -f docker-compose.test.yml up -d`.
+`docker compose -f compose.test.yml up -d`.
 
 ## Deployment
 

README.md

@@ -39,10 +39,10 @@ brew services start postgresql@17
 ```
 
 Or, to match what CI runs against exactly, bring up
-[`docker-compose.test.yml`](docker-compose.test.yml) instead:
+[`compose.test.yml`](compose.test.yml) instead:
 
 ```sh
-docker compose -f docker-compose.test.yml up -d
+docker compose -f compose.test.yml up -d
 ```
 
 Then:
@@ -178,7 +178,7 @@ in any order:
 `<database>_e2e` database that it owns outright — drops and rebuilds its
 own schema on every run — so it can never touch your working database.
 Without `DATABASE_URL` the suite skips with a warning naming
-`docker compose -f docker-compose.test.yml up -d`; CI infers
+`docker compose -f compose.test.yml up -d`; CI infers
 required-ness from `CI=true` so that skip fails loudly there instead of
 silently passing.
 
@@ -212,7 +212,7 @@ a hard failure on CI jobs that provision Postgres.
 To run these locally against the same Postgres CI uses:
 
 ```sh
-docker compose -f docker-compose.test.yml up -d
+docker compose -f compose.test.yml up -d
 DATABASE_URL=postgres://postgres:postgres@localhost:5432/workbench bun test packages apps/hub/test
 ```