@evident-ai/runner-synchroniser 3.5.2-dev.4f7b3ac → 3.5.2-dev.4f96188

package/README.md

@@ -325,6 +325,7 @@ before looking at everything" would report the wrong conclusion to the operator.
 | `SESSION-DB-REPLICA-SEPARATION-UNVERIFIED` | `separateCorruptReplica` (`replica-recovery.ts`) | A separation could not be proven | remaining objects or list error |
 | `SESSION-DB-LOCAL-DISCARD-FAILED` | `verifySessionDb` (`session-db-verify.ts`) | The local DB or a sidecar could not be proven gone | removed and surviving paths |
 | `SESSION-DB-VERIFY-TIMEOUT` | the boot wrapper around `session-db-verify` | Verification did not finish before its outer deadline; the message says whether corruption was already proven and whether separation had started | timeout and refusal reason |
+| `SESSION-DB-VERIFY-SKIPPED` | `evident run`'s session-DB step | The start serves a session database without verifying it: the restore flag was absent, OpenCode was already serving it, or the health check returned an authentication challenge. `flag-absent` is expected on a `/resume` start by design. | `reason` (`flag-absent`\|`opencode-serving`\|`opencode-auth-challenge`) |
 
 The walkback markers describe each attempt and its progress. The final outcome markers
 describe whether the active prefix and local files were proven safe; `entrypoint.sh` reuses

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@evident-ai/runner-synchroniser",
-  "version": "3.5.2-dev.4f7b3ac",
+  "version": "3.5.2-dev.4f96188",
   "description": "Restores and syncs the Evident runner's OpenCode credential stores (and litestream config) to an object store, so a runner survives task replacement with almost no state loss.",
   "type": "module",
   "main": "./dist/cli.js",