Sloth-ninja puts JessicaOSS on its own front door

The fork can now publish directly to jessicaoss.com instead of relying on a manual dashboard setup.

infrastructure

Sloth-ninja has completed a small but important piece of launch plumbing: connecting JessicaOSS's live service to its own web address during deployment.

The change fixes a failed first publish that had nowhere to attach the service. The account did not have the platform's default temporary address, and the custom domain route had been held back until its DNS setup was ready. That decision is now settled.

Future deployments can publish the service, attach jessicaoss.com, and check that it is live in one normal release step. The manual configuration task disappears from the process.

This matters to teams watching JessicaOSS as a product, because a reliable public address is the difference between a working build and something people can actually reach.

So what Legal-tech teams evaluating the fork can see that Sloth-ninja is moving it from development work toward a deployable public 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
`b125a02b`	Enable Worker custom-domain route for jessicaoss.com apex	sloth-ninja	2026-07-19	↗ GitHub
Publish failed: no workers.dev subdomain registered and route was commented pending the DNS decision. Zone is live; attach at deploy. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

SHA

Subject

Author

Date

b125a02b

Enable Worker custom-domain route for jessicaoss.com apex

sloth-ninja

2026-07-19

↗ GitHub

Publish failed: no workers.dev subdomain registered and route was
commented pending the DNS decision. Zone is live; attach at deploy.

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