Sloth-ninja makes JessicaOSS deploy reliably to Cloudflare

A small packaging decision removes the ambiguity that was stopping live releases from reaching the site.

infrastructureworkflow

JessicaOSS had two competing signals about how its web app should be built. Automated deployment tooling chose the wrong one, then failed when it tried to use software unavailable in the Cloudflare release environment.

Sloth-ninja has removed that ambiguity and made the project's existing npm setup the single source of truth. This is deliberately a narrow exception to the fork's usual preference for minimal changes: it fixes both the initial build selection and the later deployment handoff, while preserving the project's usual automated checks.

The change has also been verified against the live Cloudflare worker after merge, rather than relying only on local validation.

So what Legal product teams evaluating JessicaOSS should care because dependable deployment is the unglamorous prerequisite for turning a fork into a usable service.

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from Sloth-ninja/JessicaOSS, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`3621b180`	Remove upstream bun.lock: hijacked packager detection in build and deploy	sloth-ninja	2026-07-19	↗ GitHub
commit body wrangler autoconfig delegates deploy to opennextjs-cloudflare, whose bun-lockfile detection ran 'bun wrangler deploy' (bun not installed). npm/package-lock.json is canonical for this fork. Recorded rule-8 deviation + lesson correction. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

SHA

Subject

Author

Date

3621b180

Remove upstream bun.lock: hijacked packager detection in build and deploy

sloth-ninja

2026-07-19

↗ GitHub

commit body

wrangler autoconfig delegates deploy to opennextjs-cloudflare, whose
bun-lockfile detection ran 'bun wrangler deploy' (bun not installed).
npm/package-lock.json is canonical for this fork. Recorded rule-8
deviation + lesson correction.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-1177.md from inside the repo you want the changes in.