fix: use != null check in resolveVersion to handle version 0 correctly

Author: ericallam

CLAUDE.md

@@ -18,15 +18,24 @@ pnpm run dev --filter webapp  # Run webapp (http://localhost:3030)
 pnpm run dev --filter trigger.dev --filter "@trigger.dev/*"  # Watch CLI and packages
 ```
 
-### Verifying Webapp Changes
+### Verifying Changes
 
-**Never run `pnpm run build --filter webapp` to verify changes.** Building proves almost nothing about correctness. Instead, run typecheck from the repo root:
+The verification command depends on where the change lives:
+
+- **Apps and internal packages** (`apps/*`, `internal-packages/*`): Use `typecheck`. **Never use `build`** for these — building proves almost nothing about correctness.
+- **Public packages** (`packages/*`): Use `build`.
 
 ```bash
-pnpm run typecheck --filter webapp   # ~1-2 minutes
+# Apps and internal packages — use typecheck
+pnpm run typecheck --filter webapp                  # ~1-2 minutes
+pnpm run typecheck --filter @internal/run-engine
+
+# Public packages — use build
+pnpm run build --filter @trigger.dev/sdk
+pnpm run build --filter @trigger.dev/core
 ```
 
-Only run typecheck after major changes (new files, significant refactors, schema changes). For small edits, trust the types and let CI catch issues.
+Only run typecheck/build after major changes (new files, significant refactors, schema changes). For small edits, trust the types and let CI catch issues.
 
 ## Testing
 

apps/webapp/CLAUDE.md

@@ -4,14 +4,16 @@ Remix 2.1.0 app serving as the main API, dashboard, and orchestration engine. Us
 
 ## Verifying Changes
 
-**Never run `pnpm run build --filter webapp` to verify changes.** Building proves almost nothing about correctness. Instead, run typecheck from the repo root:
+**Never run `pnpm run build --filter webapp` to verify changes.** Building proves almost nothing about correctness. The webapp is an app, not a public package — use typecheck from the repo root:
 
 ```bash
 pnpm run typecheck --filter webapp   # ~1-2 minutes
 ```
 
 Only run typecheck after major changes (new files, significant refactors, schema changes). For small edits, trust the types and let CI catch issues.
 
+Note: Public packages (`packages/*`) use `build` instead. See the root CLAUDE.md for details.
+
 ## Testing Dashboard Changes with Chrome DevTools MCP
 
 Use the `chrome-devtools` MCP server to visually verify local dashboard changes. The webapp must be running (`pnpm run dev --filter webapp` from repo root).

apps/webapp/app/presenters/v3/PromptPresenter.server.ts

@@ -158,7 +158,7 @@ export class PromptPresenter extends BasePresenter {
     promptId: string,
     options?: { version?: number; label?: string }
   ) {
-    if (options?.version) {
+    if (options?.version != null) {
       return this._replica.promptVersion.findUnique({
         where: {
           promptId_version: {

apps/webapp/app/services/runsReplicationService.server.ts

@@ -528,7 +528,7 @@ export class RunsReplicationService {
     this._lastAcknowledgedAt = now;
     this._lastAcknowledgedLsn = this._latestCommitEndLsn;
 
-    this.logger.info("acknowledge_latest_transaction", {
+    this.logger.debug("acknowledge_latest_transaction", {
       commitEndLsn: this._latestCommitEndLsn,
       lastAcknowledgedAt: this._lastAcknowledgedAt,
     });