Sloth-ninja makes JessicaOSS deployment-proof

A small configuration change removes the package-manager guesswork that blocked the fork's first production launch.

infrastructurebranding

An inherited build marker led the hosting setup to choose the wrong tool, even though JessicaOSS is maintained with npm. Sloth-ninja has now made that choice explicit, so the frontend build follows the fork's intended setup without removing upstream material and widening the fork's differences.

The production build now completes successfully, uses the live API rather than a local development address, keeps the JessicaOS branding, and passes its frontend checks. It is a narrow operational fix, but one that turns a failed first deployment into a repeatable release path.

So what Teams assessing JessicaOSS as a deployable legal-AI product should care because reliability at release time is now less dependent on build-tool guesswork.

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
`697a1bb6`	Fix OpenNext packager detection: explicit npm build command	sloth-ninja	2026-07-19	↗ GitHub
commit body Upstream ships frontend/bun.lock, so OpenNext auto-detected bun (not installed, exit 127). Pin buildCommand to 'npx next build'; keep the upstream lockfile per minimal-diff rule 8. Lesson recorded. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

SHA

Subject

Author

Date

697a1bb6

Fix OpenNext packager detection: explicit npm build command

sloth-ninja

2026-07-19

↗ GitHub

commit body

Upstream ships frontend/bun.lock, so OpenNext auto-detected bun (not
installed, exit 127). Pin buildCommand to 'npx next build'; keep the
upstream lockfile per minimal-diff rule 8. Lesson recorded.

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-1178.md from inside the repo you want the changes in.