fix(runtime): hydrate unpinned task worktrees from a commit-keyed dependency cache (#1251)

[mrthankyou]

Ordinary task worktrees now receive the launch checkout's initialized submodule files from a shared, content-addressed dependency cache. This fixes empty dependency directories that made task-local Forge commands clone dependencies over the network. Fixes #1251.

Each read verifies the cache against the recorded manifest. Missing or damaged entries are rebuilt from Git objects at the recorded commits. Persisted pre-cache workflows keep their historical runtime entry points, and older pinned runs can recover the exact dependency bytes from their recorded execution snapshot when no Git objects remain. New execution snapshots omit dependency copies.

Ordinary tasks restore dependency edits and record the changed paths and exact count; pinned tasks continue to reject edits. Runtime reports restate the records and display a fixed notice. Credential-bearing filenames are omitted before durable recording, including pending records, so restart or credential rotation cannot expose them later. Ordinary filenames remain visible, and a path list may be empty while its exact change count remains positive.

The final implementation also preserves both invariant warnings and dependency metadata in verification markers, handles filesystem-valid unusual filenames during restoration, and serializes cache replacement so concurrent repair cannot remove another publisher's valid entry. Dead-owner recovery uses the existing journal lock. Historical workflow verification checks worktree bindings before any cache write.

Validation:

• 342 artifact tests and 30 targeted runtime tests for schema/publication safety.
• 34 focused tests for cache, restoration, and lifecycle behavior before integration; 19 targeted tests on the final integrated head.
• Regression demonstrations fail on the old code for unusual filenames and concurrent cache replacement.
• Runtime build, test compilation, strict changed-lines lint, formatting, schema parity, and documentation checks passed.
• All 17 checks passed on the final commit before merge: https://github.com/monad-developers/ultrafuzz/actions/runs/38658615722 .

Limits: dependency records describe edits still present when the agent finishes; they do not detect edits already reverted by the agent. Cache entries are not pruned automatically. Gitlink changes still fail validation, and pinned runs retain strict dependency checks.

Confidence Score: 5/5

The PR appears safe to merge; both numbered previous findings are fixed.

Summary

Task worktrees now get recorded submodule files from a shared dependency cache.

• Ordinary task worktrees get submodules from a cache keyed by the launch checkout.
• Ordinary tasks record dependency edits, restore files, and carry the record into reports.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Launch records dependency files and hashes] --> B[Shared dependency cache]
  B --> C[Hydrate task worktree]
  C --> D[Agent runs]
  D --> E{Pinned run?}
  E -->|Yes| F[Reject dependency edits]
  E -->|No| G[Save edit record and restore files]
  G --> H[Verification marker]
  H --> I[Report metadata and fixed notice]
  J[Recorded Git objects] -->|Rebuild missing cache| B
  K[Historical execution snapshot] -->|Recover older runs| B

Loading

_{Reviews (4) · Last reviewed commit: "Merge unstable after reviewed bugfixes" · Reviewed by Greptile}