fix(project-files): requeue rendered-artifact search after commit and trim Project read transactions

[waleedlatif1]

Summary

All changes are on flag-gated Project file paths (behind the projects rollout) plus small shared helpers whose workspace behavior is unchanged.

• Lock upgrade in Project artifact reads. readArtifact holds the Project lock and the source row shared, but its final transaction called markFileSearchArtifactReadyInTx, which takes the Project lock exclusively and file rows FOR UPDATE. Every compiled render did this (a cache hit still returns artifactKey), so concurrent generated-document reads in one Project could deadlock or wait out the 5 s Project lock timeout. The read now records the search completion and requeues after commit via requeueFileSearchForRenderedArtifact (lock-free current check, then its own transaction). That transaction now takes the owner lock under the 1 s artifact-ready bound instead of the 5 s Project lock bound; a timeout is caught and logged and never fails the read.
• Fewer authorized transactions. Artifact, inline, and CSV preview reads authorize from their own snapshots (prepareFromSnapshot) instead of a separate preflight. Artifact inputs are snapshotted and admitted only when the source references any; the final transaction still rechecks the source, every input, and provenance after storage reads. Artifact: 4 transactions / 3 admissions → 2 / 2 without inputs, 3 / 3 with. Inline and CSV: 3 → 2. Search: drops the nested listProjectFileFolders use case.
• Artifact inputs. Downloads run with bounded concurrency after checking declared sizes against the per-file and total budgets. Each read is capped at its declared size plus the unclaimed budget, and the first failure aborts the rest. The request signal now reaches render, downloads, and compile.
• Project inline delivery streams instead of buffering. It fences the file head after storage opens and serves workspaceFileCacheControl(contentAddressed) like workspace inline. It no longer lists every Project folder.
• Project search admits, withholds stale previews, and reports provenance after its snapshot commits. loadFileSearchDelivery returns an explicit current set, and provenance is classified only when a content gate or delivery observer needs it.
• Foreign page embeds. A Project page that embeds another owner's image now fails as a missing input (not_found) instead of a 500, through a typed ProjectPageForeignEmbedError.
• Cleanup.
  • Page inline limits are exported from page-document.server.ts and reused.
  • knip.jsonc narrows the project-files.ts entry to types.
  • SearchProjectFileContentInput is un-exported.
  • The CI isolate build step uses paths: ["."] and JOBS=4, matching docker/app.Dockerfile.

Expected rebase conflicts in the open Project file stack:

• feat(project-files): add cross-owner copy and bulk transfers #9018: none expected.
• feat(project-files): add public sharing and protected delivery #9019 and feat(files): Project file browser and Mothership integration #9034 (still based on pre-squash feat(project-files): add rendered delivery and indexed search #9017): conflicts in artifacts.ts, previews.ts, search.ts, artifact-ready.ts, delivery.ts, and checks.yml; take staging's side.
  • The feat(files): Project file browser and Mothership integration #9034 inline route must present the new stream result (stream, contentLength, contentAddressed).
  • readProjectFileArtifact keeps file.folderPath for its VFS paths.

Type of Change

• Bug fix

Testing

• Biome on all changed files; lib/workspace-files/page-compile.test.ts.
• New integration checks in content-rendered.integration.ts:
  • A generated artifact read beside a concurrent shared Project holder completes and requeues search. On the previous code it times out on the exclusive Project lock.
  • A contended requeue gives up within its short bound without failing the read.
  • A Project page embedding another owner's image is not_found.
• Type-check, audits, and integration suites run in CI.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Oct 15, 2026 1:43am UTC

[cubic-dev-ai]

All reported issues were addressed across 13 files

_{Turn on auto-fix | Re-trigger cubic}

[greptile-apps]

Confidence Score: 5/5

[High impact] The changes since the previous review appear safe to merge.

Summary

This PR moves rendered-artifact search requeues after commit and reduces transactions on Project file reads.

• Rendered files check their inputs before and after they are built.
• Rendered artifact reads requeue search after the read commits.
• Project inline files stream to callers instead of buffering first.
• CSV previews use their file snapshot for authorization.
• Project search hides previews that no longer match current files.
• CI builds the Project rendering addon with a fixed job limit.

No new actionable issues were found in the changes since the previous review.

Diagram

sequenceDiagram
  participant Reader as Project artifact reader
  participant DB as Database
  participant Search as Search requeue
  Reader->>DB: Check source and inputs under shared Project lock
  DB-->>Reader: Commit and release locks
  Reader->>Reader: Admit content and report delivery
  Reader->>Search: Requeue rendered artifact
  Search->>DB: Acquire exclusive Project lock with short timeout
  alt Lock acquired
    Search->>DB: Mark revision pending and enqueue search
  else Lock times out
    Search-->>Reader: Log failure without failing the read
  end

Loading

_{Reviews (2) · Last reviewed commit: "test(project-files): start requeue check..." · Reviewed by Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 13 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}