chore: trim repo to dvm-only, remove leftover monorepo build contexts

[toon-backlog-bot]

Summary

• Deletes 11 non-dvm Dockerfiles, all non-dvm src/ entrypoints and helpers, and all non-dvm build-context dirs (configs/, dev-fixtures/, akash-ator-probe/, townhouse-ator-sidecar/, supervisord.conf, docker-compose-oyster.yml).
• Reduces esbuild.config.mjs to a single entryPoint (src/entrypoint-dvm.ts) and trims externals to only what the DVM bundle needs.
• Strips main/start scripts and unused deps from package.json (kept: @toon-protocol/{core,sdk}, hono, @hono/node-server).
• Fixes tsconfig.json to stand alone — removes the extends: "../tsconfig.json" monorepo-root reference that no longer exists; this was a pre-existing breakage that caused vitest to fail before this PR.

Deviation from Agent Assessment plan

The issue body says pnpm typecheck may fail due to the pre-existing tsconfig.json extends issue, but treats it as "not to be fixed here." However, pnpm test (vitest via vite) also hard-fails on the broken extends — it's not just typecheck. Since fixing the tsconfig is entirely within the "make this repo standalone" scope of this issue and is low-risk (inlining standard settings for a Node ESM TS project), the fix is included here. On main before this PR, vitest was crashing on all 5 test files; after this PR, 22 tests pass in src/entrypoint-dvm.test.ts.

Verification

npm run build
# → dist/entrypoint-dvm.js (378 KB), no other outputs

npm test
# → Test Files 1 passed (1)
# → Tests      22 passed (22)

grep -rnE 'entrypoint-(sdk|mill|town|toon-client|townhouse-api)|attestation-server|supervisord|configs/|dev-fixtures|akash-ator-probe|townhouse-ator-sidecar' \
  --include='*.json' --include='*.mjs' --include='*.ts' --include='Dockerfile*' --include='*.md' . \
  | grep -v node_modules | grep -v dist/
# → (no output — clean)

Closes #2

🤖 Generated with Claude Code

[ALLiDoizCode]

Adversarial Review — Blocking Issue

❌ buildNoCreditsMessage is undefined — runtime crash + typecheck failure

File: src/entrypoint-dvm.ts:508
Severity: Blocking (runtime ReferenceError + breaks the typecheck fix this PR claims to deliver)

// line 508
console.warn(
  `[DVM Entrypoint] ${buildNoCreditsMessage(turboResult.arweaveAddress)}`
);

buildNoCreditsMessage is called here but is never defined anywhere in the file and never imported from any module. Full verification:

grep -rn 'buildNoCreditsMessage' src/ --include='*.ts'
# → src/entrypoint-dvm.ts:508:  ...buildNoCreditsMessage(turboResult.arweaveAddress)...
# (definition line: none)

Impact:

1. Runtime crash — any DVM that starts with DVM_ARWEAVE_JWK_B64 set (JWK-authenticated wallet) and a zero winc balance hits this code path at boot. Instead of logging a warning, it throws ReferenceError: buildNoCreditsMessage is not defined and the process exits (the error propagates out of the balance probe try/catch because the reference error fires inside the console.warn argument, not in the probe code that the try/catch guards — wait, actually it is inside the try/catch block so it would be caught and logged, then boot would continue). Let me revise: the crash is caught by the outer try/catch at line 512, so the DVM would boot successfully but silently swallow the zero-balance warning and log a confusing probe-failure message instead. Either way the behavior is wrong.

Revised impact (more accurate):

• The try/catch at line 512 catches the ReferenceError, so the DVM boots, but the zero-balance warning is lost and replaced with a misleading "Could not probe Arweave credit balance" message. Operators with a newly-funded wallet won't know their wallet has zero credits.

TypeCheck: This PR enables strict: true in tsconfig.json, which means pnpm typecheck (tsc --noEmit) should now report error TS2304: Cannot find name 'buildNoCreditsMessage'. The PR verification only shows npm run build (esbuild, no type checking) and npm test (vitest/esbuild transforms, also no type checking) — not pnpm typecheck. If typecheck was the motivating fix for the tsconfig change, it should be shown to pass.

Fix required before merge: Either define buildNoCreditsMessage (e.g., inline the formatting logic) or remove the call and replace with a concrete string template.

---

Non-blocking observations (FYI, not blocking merge once the above is fixed)

esbuild.config.mjs vs Dockerfile.dvm external list divergence. The new esbuild.config.mjs lists 3 externals (@ardrive/turbo-sdk, arweave, better-sqlite3); Dockerfile.dvm uses 9 (@libsql/client, libsql, ethers, express, @solana/kit, @solana-program/token, @ardrive/turbo-sdk, @toon-protocol/mina-zkapp, better-sqlite3). Since Dockerfile.dvm is acknowledged as broken (monorepo paths), this is moot now, but the person fixing the Dockerfile will need to reconcile these lists.

Dockerfile.dvm:105 still builds @toon-protocol/bls (--filter '@toon-protocol/bls') after bls is removed from package.json. Same caveat — moot while Dockerfile.dvm is broken, but worth fixing in the Dockerfile follow-up.

Cleanup itself is solid: removing 11 non-DVM Dockerfiles, all non-DVM src/ entrypoints, configs/, dev-fixtures/, akash-ator-probe/, townhouse-ator-sidecar/, etc. is exactly the right work. The tsconfig.json fix, package.json dep trim, and esbuild.config.mjs reduction are all correct and well-scoped.

[toon-backlog-bot]

Fix round 1 — buildNoCreditsMessage undefined reference

Addressed the blocking finding from @ALLiDoizCode's review.

What was wrong: buildNoCreditsMessage(turboResult.arweaveAddress) at line 508 referenced a function that was never defined or imported anywhere. As the review correctly noted, the ReferenceError was caught by the outer try/catch, so the DVM would boot but silently swallow the zero-balance warning, replacing it with a misleading "Could not probe Arweave credit balance" message.

Fix: Inlined the warning message directly — same information, no helper function needed:
```
WARNING: Arweave wallet has 0 winc credits — uploads will fail until the wallet is funded. Fund address:

```

Verification after fix:

```
npm run build

→ dist/entrypoint-dvm.js (378 KB)

npm test

→ Test Files 1 passed (1)

→ Tests 22 passed (22)

npm run typecheck

→ errors are pre-existing SDK API drift (ToonNode, UnsignedEvent, blsPort not exported)

→ TS2304: Cannot find name 'buildNoCreditsMessage' ← GONE

```

Non-blocking observations from review: The esbuild.config.mjs vs Dockerfile.dvm external list divergence and the bls filter in Dockerfile.dvm are noted — both are acknowledged as moot while Dockerfile.dvm is broken (monorepo paths), and are appropriate for the follow-up Dockerfile fix issue.

[ALLiDoizCode]

Adversarial Review — PR #9 (trim to dvm-only)

The cleanup deletions are correct and the scope is appropriate. I found two blocking issues and one concern that should be addressed before merge.

---

[BLOCKING] CLAUDE.md pnpm install conflicts with package-lock.json lockfile

CLAUDE.md Build section still says:

pnpm install
pnpm build

But the PR removes pnpm-lock.yaml and adds package-lock.json. Running pnpm install against a repo that has only package-lock.json will ignore the npm lockfile and generate a fresh pnpm-lock.yaml from scratch — non-deterministic and not equivalent to what the npm lockfile pins.

Required fix: Update the Build section in CLAUDE.md to npm install && npm run build (matching the lockfile format actually present in the repo).

---

[BLOCKING] Stale vi.mock('@toon-protocol/pet-dvm') in src/entrypoint-dvm.test.ts

src/entrypoint-dvm.test.ts line 15–17:

vi.mock('@toon-protocol/pet-dvm', () => ({
  createDungeonDvmHandler: vi.fn(() => vi.fn()),
}));

@toon-protocol/pet-dvm is not in package.json and entrypoint-dvm.ts does not import it (only mentions it in a comment). This is dead code from the kind:5250 Dungeon DVM era. While vitest's vi.mock factory avoids a real require at import-time, it silently masks any future accidental reintroduction of a pet-dvm import (the mock intercepts before resolution errors surface). Remove it.

---

[CONCERN] esbuild.config.mjs external list diverges from Dockerfile.dvm

esbuild.config.mjs (used by npm run build):

external: ['@ardrive/turbo-sdk', 'arweave', 'better-sqlite3']

Dockerfile.dvm runs esbuild directly with:

--external:better-sqlite3 --external:@libsql/client --external:libsql
--external:ethers --external:express --external:@solana/kit
--external:@solana-program/token --external:@ardrive/turbo-sdk
--external:@toon-protocol/mina-zkapp

These are not equivalent: the dev build bundles ethers, express, @libsql/client, libsql, @solana/kit, @solana-program/token, and @toon-protocol/mina-zkapp inline; the Docker build externalises all of them. Conversely, arweave is external in the dev build but bundled in the Docker build. The PR's stated verification (npm run build → dist/entrypoint-dvm.js 378 KB) validates the wrong artifact shape relative to what the Docker image would run. I understand Dockerfile.dvm is acknowledged as a follow-up fix, but the divergence should at least be noted here so the follow-up PR knows to reconcile the external lists.

---

What's good

• The deletions are clean and complete: 11 non-DVM Dockerfiles, all non-DVM src/ entrypoints and test files, configs/, dev-fixtures/, akash-ator-probe/, townhouse-ator-sidecar/, supervisord.conf, docker-compose-oyster.yml all gone.
• tsconfig.json standalone fix (removing broken extends: "../tsconfig.json") is correct and the inlined settings are standard for a Node ESM TS project.
• package.json dep trim is accurate — only @hono/node-server, @toon-protocol/{core,sdk}, hono remain.
• The buildNoCreditsMessage undefined-reference fix is correct: inlining the message avoids a runtime ReferenceError when the Arweave wallet has 0 winc credits.
• CLAUDE.md cross-repo deps line correctly drops @toon-protocol/bls.

[toon-backlog-bot]

Fix round 2 — CLAUDE.md build commands and stale pet-dvm mock

Addressed both blocking findings from @ALLiDoizCode's second review (commit 94f08d8).

[BLOCKING] CLAUDE.md pnpm install conflicts with package-lock.json

Fixed: Updated the Build section to use npm install and npm run build, matching the package-lock.json lockfile present in the repo.

[BLOCKING] Stale vi.mock('@toon-protocol/pet-dvm') in test file

Fixed: Removed the 3-line dead mock block from src/entrypoint-dvm.test.ts. The @toon-protocol/pet-dvm package is not in package.json and entrypoint-dvm.ts does not import it — it was leftover from the kind:5250 Dungeon DVM era.

Verification

npm run build
# → dist/entrypoint-dvm.js (378 KB)

npm test
# → Test Files  1 passed (1)
# → Tests      22 passed (22)

Non-blocking concern (esbuild external list divergence)

Acknowledged — still appropriate as a follow-up alongside the Dockerfile.dvm fix as noted in the previous comment.

[ALLiDoizCode]

Review Round 2 — LGTM, all blocking issues resolved

I verified the current HEAD (94f08d8) against all blocking findings from the two prior reviews.

Prior blocking issues — confirmed fixed

[R1] buildNoCreditsMessage undefined reference (src/entrypoint-dvm.ts:508)
Commit 0b4f86f inlines the message as a string literal. Confirmed no + lines in the diff re-introduce the call.

[R2a] CLAUDE.md build commands used pnpm while only package-lock.json exists
Commit 94f08d8 updates both commands to npm install / npm run build. Now consistent with the lockfile.

[R2b] Stale vi.mock('@toon-protocol/pet-dvm') in src/entrypoint-dvm.test.ts
Commit 94f08d8 removes the dead mock entirely. Confirmed no residual references in additions.

What I independently checked

• package.json dep trim is accurate: @hono/node-server, @toon-protocol/{core,sdk}, hono — matches the imports in entrypoint-dvm.ts.
• tsconfig.json standalone fix (target: ES2022, module: ESNext, moduleResolution: Bundler, strict: true) is standard for a Node ESM + esbuild project.
• esbuild.config.mjs single entry point and reduced externals (@ardrive/turbo-sdk, arweave, better-sqlite3) are appropriate; the Dockerfile.dvm divergence is acknowledged in README.md as a known follow-up.
• package-lock.json root dependencies match package.json exactly.
• All 11 non-DVM Dockerfiles and all non-DVM src/ entrypoints/tests are deleted with no stray survivors in the diff additions.

[ALLiDoizCode]

Closing as stale/superseded. The trim is still genuinely needed — legacy Dockerfiles (Dockerfile.akash-*, mill, town, townhouse-*), legacy src/entrypoint-{sdk,toon-client,town,townhouse-api}.ts, attestation-server, and a fat package.json (main: entrypoint-sdk.js) all remain on main — but this diff can't be salvaged: it targets the now-renamed entrypoint-dvm.ts (→ entrypoint-store.ts per #19), adds a package-lock.json against main's committed pnpm-lock.yaml (#16), and predates #18/#19. Re-doing fresh against current main.