feat(db): hold a run's manifest digest outside the run

[dibenkobit]

What Changed

agent_runs gains a nullable manifest_sha256, filled from the digest the harness already computes when it finishes writing a run manifest. One additive migration, 0001.

manifest_sha256 is also added to AgentRunSchema, validated as 64 lowercase hex — an anchor that is present but malformed is worse than one that is absent.

The comment on manifest_path is corrected in the same change. It claimed the path led to "this session's full transcript", which was not true of a stdout capture and is the only line in the codebase that said so.

Why

A run manifest names every artifact with its digest. The manifest sits in <agent cwd>/.openlab-artifacts/run-<uuid>/, inside the working directory of an agent that runs with --dangerously-skip-permissions, and the lab kept only the path to it.

So the record attested to nothing. Whatever could alter an artifact could restate its digest in the same breath, and nothing outside that directory disagreed. Not a threat model about attackers so much as ordinary agent behaviour: an agent tidying its own workspace is enough.

One value, held where the directory it describes cannot reach it, is what makes the rest of the chain mean something. Everything else was already there.

Verification

The upgrade path is the risk in a migration, so it was exercised rather than reasoned about — a database built at the released schema, seeded with an investigation and an agent run, then migrated:

released schema: seeded a run
after upgrade: [["run-1","abc"]]

The existing row survives and the column takes a value. The release build copies packages/db/migrations recursively, so 0001 ships with no change to the packaging.

The projection test now asserts both the path and the digest reach SQLite, so a value that stopped at the snapshot would fail it.

pnpm check (lint, typecheck, 9 workspaces of tests, build) passes.

Independent of #12 and #13; can go in any order.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included screenshots for any UI changes, with a before only where one existed — no UI changes; the column is not rendered
• I included a video for animation/interaction changes — not applicable

---

Claude Opus 5 (1M context) via Claude Code.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.}

Note

Store manifest SHA-256 digest on agent run records

• Adds a manifest_sha256 column to the agent_runs table via a new migration (0001_spooky_shocker.sql) and updates the ORM schema and snapshot projection to read/write it.
• Extends AgentRunOutcome with a manifestSha256 field and passes it through finishAgentRun so successful runs persist the digest alongside the manifest path.
• Adds an optional manifest_sha256 field to AgentRunSchema with a 64-character lowercase hex validation rule.

^{Macroscope summarized 7c77e2f.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
openlab-landing	Ready	Preview	Aug 7, 2026 3:07pm