A resumable snapshot of the ToolNaka workstream: what was already delivered, what is still open, how each claim is proven, and the one page you need to pick the work up again.
| Area | Status | Proof |
|---|---|---|
| Hosting moved off the laptop to Vercel + Neon; domain cut over; laptop retired | DONE | go-live report · retire notes |
| Rider/delivery flows, service-request bug, uploads, monthly-bill cron | DONE | go-live report |
| Indent approval chain (Dept Manager → Plant Head) + emergency bypass | DONE | 16/16 end-to-end |
| “Nothing works” root cause: seller record + hidden import UI | DONE | 17/17 journey |
| Automatic stock sync from a spreadsheet link | DONE | 14/14 + 9/9 live |
| Payment reminders three times a week, real email delivery | DONE | live sent=true |
| PIN code decides area / city / state (India) | DONE | tap: 411001 · 302001 · 110001 |
| Third-party (“Moglix”) name removed everywhere | DONE | 0 occurrences in live bundle |
| Delivery: factory chooses; ToolNaka choice locked to the seller | DONE | 11/11 + 9/9 live |
| Delivery fee billed inside the order total | CONFIRM | changes checkout pricing |
| Rider login (status updates from a phone) | CONFIRM | adds a role back |
The ToolNaka site was migrated off a laptop-hosted setup (Windows + Cloudflare tunnel + SQLite) to Vercel with a Neon Postgres database, and toolsnaka.store now resolves directly to Vercel with a valid certificate. The local server, tunnel and auto-restart watchdog are stopped, so the site stays up with the laptop off.
On top of the migration, the product was fixed and extended: the rider/delivery app was removed, the vendor service-request panel bug was fixed, uploads became database-backed, billing moved to a scheduled job, the indent approval chain was built (department manager, then plant head, with a department scope and an emergency bypass), and the root cause of “all features not working” was eliminated — sign-up never created the seller record the catalog APIs required.
Four requests from the last active stretch were finished and verified live: PIN-code location, removal of the third-party category brand, a direct catalog import entry, and the delivery feature. Two optional items were explicitly parked pending your decision: billing the delivery fee inside the order total and a rider login. No work-in-progress code was left uncommitted or half-deployed.
Checked live on 2026-09-22: the app answers with {"status":"ok","db":"ok"}, the landing page renders, the three newest endpoints exist and reject unauthenticated writes with 401, PIN codes resolve to real cities, and the JavaScript the site serves contains the new screens and no trace of the removed brand. One earlier snapshot claim — “the health endpoint is served by Vercel” — is re-confirmed by the Server: Vercel header and by fresh serverless uptimes.
Re-runnable by anyone, no credentials needed:
| Suite | Result | What it proves |
|---|---|---|
| Buyer→seller journey (OTP → register → product → order+approval → indent+chain) | 17/17 | sign-up creates the seller record; the catalog, ordering and approval paths work end to end |
| New features (spreadsheet sync + reminders) | 14/14 | stock of 5000 → 4200 after a sheet edit; a new row is added; reminders record the right amount |
| Approval chain | 16/16 | level 1 advances to level 2; the indent is released to sellers only after final approval |
| Live pull executed by production | 9/9 | the deployed site really fetches a vendor’s sheet and updates the catalog |
| Delivery rules | 11/11 | ToolNaka delivery is locked (seller gets 403); ops assigns a rider; a hand-off locks the seller too |
| Production checks for the latest four changes | 9/9 | PIN lookups, zero brand occurrences, both new UI screens, order + lock + rider assignment |
Full ledger with evidence paths: DELIVERY/toolnaka-checkpoint-ledger.md. Nineteen items are done, each tied to a file, a report or a live check; two are parked for your confirmation; three were dropped deliberately with reasons (the rider role, local self-hosting, and Turso).
PincodeCoverage. No bulk offline dataset is bundled.Every change sits in the toolnaka-ai project behind a Vercel deployment. To roll back, promote the previous production deployment (Vercel Dashboard → Deployments → the prior one → Promote to Production); the domain follows the alias, so the site returns to the earlier build in under a minute. Database changes are additive (new tables and nullable columns) — no destructive migration was run, so rolling the app back does not break stored data. The retired laptop stack can be restarted from the retire notes if it is ever needed as a fallback.