Deploy status

Use this page when you are not sure whether you are on production, preview/staging, or local dev. The top-right badge on every page shows the same fingerprint in compact form (e.g. prod · plus the short commit SHA below — always read the live badge or /deploy-info.json, never a stale example SHA).

What you are looking at

The badge in the top-right corner (prod · e051e98) always matches this page on the same deploy. If the badge SHA differs from the table below, hard-refresh or you are on a cached tab.

Environment	production (prod)
Commit (short)	e051e98
Commit (full)	e051e98de9a69dc0c92e69f39e75b70605704d59
Branch	main
Last commit message	docs(codecanyon): step-coverage audit, gap-map + vendor-drift tooling Substep-level coverage audit of the setup-new playbook vs the Residoro source guides (STEP-INVENTORY/MATRIX/REPORT), the phases 03-10 gap-map, and the reusable vendor-drift script + recipe. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Committed	Jun 15, 2026, 4:01 AM
Built at	Monday, June 15, 2026 at 4:04:17 AM UTC
Site package	0.0.1
This site URL	https://library.zajapps.com

Quick verify (non-developer)

1. Open library.zajapps.com/zajlibrary/system/platform/resources/reference/deploy-status/ — note the Commit (short) row.
2. Compare with the badge on that page (top-right). They must match (currently e051e98 on production).
3. Local dev (npm run dev) shows local in the badge — that is expected; only prod on library.zajapps.com is the live site.

Machine-readable fingerprint

Same JSON as this page, for scripts or agents: /deploy-info.json

Operator / Vercel details (public for now)

Vercel deployment ID	dpl_D2RTfqnPSw1XhS8NNzx3hRsvKV34
Vercel deployment URL	https://zaj-library-4ye51pljk-rovonyhq.vercel.app
GitHub repo	—

When auth and admin routes land, this section moves behind a protected operator view. The public badge + short SHA stay visible so you can still confirm production at a glance.

Branch → environment (how we deploy today)

Git branch	Typical Vercel target	Public URL
main	Production	https://library.zajapps.com
dev	Preview (staging alias)	https://zaj-library-staging.vercel.app (Vercel login may be required)
Local npm run dev	—	http://127.0.0.1:4321 — badge shows local

Not a web developer?

If the badge says prod and the Commit (short) here matches the badge, you are on the latest production deploy. If you see local, you are on your machine — not the live site.

Later: auth

Operator-only fields (Vercel deployment ID, internal URLs) will move behind admin login. The badge and short commit SHA will stay public so you can always sanity-check production.

Regenerating the fingerprint (developers & agents)

When	What runs
npm run dev / predev	MCP index + deploy fingerprint (regenerate-site-artifacts.ts)
npm run build / Vercel build	Same via prebuild — Vercel env vars populate production/preview metadata
npm run preview	prepreview refreshes before serving dist/
npm run build:deploy-info	Deploy fingerprint only (fast — after git checkout)
npm run build:artifacts	MCP index + deploy fingerprint (manual)
Agent hook	.agents/scripts/ensure-site-artifacts.sh before dev/build/vercel deploy; SessionStart creates fingerprint if missing

Public JSON mirror: /deploy-info.json (also gitignored under public/ — generated at build/dev time).