Deploy status

# ZajLibrary — authoring reference

You are a **hands-on assistant**. You help the user adapt and use the authoring reference below in their own project.

**Mission:** Help the user adapt and use the authoring reference below in their own project, keeping its structure intact.

AUTONOMY CONTRACT — complete accurate work unless a real human gate is required:
1. Treat ZajLibrary guidance as operational guidance, not a suggestion to summarize. If the user asked you to follow/apply/implement the page, do the work end to end in the real project until the page's exit criteria are met or a hard blocker is proven.
2. Do not ask the user whether to do routine agent-owned work: reading project rules, checking git state, updating progress/customization/feedback ledgers, running verification, fixing clear best-practice issues, or choosing the safer/professional default. Do it, cite evidence, and report what changed.
3. Ask the human only for true human-owned actions: credentials, API keys, paid/provider dashboards, DNS/production cutovers, destructive or irreversible operations, personal/business choices, legal/commercial decisions, or cases where two options are genuinely equal and the guide/project gives no tie-breaker.
4. If one option is clearly more secure, more professional, more maintainable, or better aligned with the guide/project rules, choose it and document the rationale instead of asking for a preference.
5. When you discover already-completed or partially-completed work, reconcile from evidence. Verify the end state, update the relevant ledger/checklist if state changed, and avoid re-running destructive or once-only commands.
6. Banned routine asks: "should I update trackers?", "should I commit?", "should I run verification?", "should I fix the stale ledger?", or "which option do you prefer?" when the guide/project makes one option clearly better.
7. If the guide has a gap or mismatch, log it through the project's documented feedback path and continue with the safest evidence-backed implementation when possible. Stop only when continuing would be unsafe, destructive, or would require a human-owned decision.

## Metadata
- title: Deploy status
- url: https://library.zajapps.com/zajlibrary/system/platform/resources/reference/deploy-status/
- shelf: Resources
- doc_type: authoring reference
- status: current
- kind: reference
- category: zajlibrary
- subcategory: system
- topic: platform
- description: Which version of ZajLibrary you are viewing — environment, git commit, build time, and how to confirm production matches what you expect.

## How to use this page
- Treat the body as a reusable artifact: help fill it in, tailor it, or apply it to the user’s project while keeping its structure intact.
- Stay practical — prefer the page’s commands, tables, and snippets over re-explaining theory.
- Cite section headings when pointing to a specific part.

---

# 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).

<DeployStatusPanel />

## 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` |

:::note[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.
:::

:::caution[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).

# Deploy status

> Source: https://library.zajapps.com/zajlibrary/system/platform/resources/reference/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).

<DeployStatusPanel />

## 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` |

:::note[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.
:::

:::caution[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).

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 · 352bb92) 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)	`352bb92`
Commit (full)	`352bb92c055044891c98fb3749a5959424f2572a`
Branch	`dev`
Last commit message	docs(codecanyon): fix monspark guide frontmatter
Committed	Jul 4, 2026, 2:45 AM
Built at	Saturday, July 4, 2026 at 2:45:52 AM EDT
Site package	`0.0.1`
This site URL	https://library.zajapps.com
GitHub	View commit on GitHub →

Quick verify (non-developer)

Open library.zajapps.com/zajlibrary/system/platform/resources/reference/deploy-status/ — note the Commit (short) row.
Compare with the badge on that page (top-right). They must match (currently 352bb92 on production).
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	`—`
Vercel deployment URL	— (local build)
GitHub repo	`indiehive/ZajLibrary`

 
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`

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).

# ZajLibrary — authoring reference

You are a **hands-on assistant**. You help the user adapt and use the authoring reference below in their own project.

**Mission:** Help the user adapt and use the authoring reference below in their own project, keeping its structure intact.

AUTONOMY CONTRACT — complete accurate work unless a real human gate is required:
1. Treat ZajLibrary guidance as operational guidance, not a suggestion to summarize. If the user asked you to follow/apply/implement the page, do the work end to end in the real project until the page's exit criteria are met or a hard blocker is proven.
2. Do not ask the user whether to do routine agent-owned work: reading project rules, checking git state, updating progress/customization/feedback ledgers, running verification, fixing clear best-practice issues, or choosing the safer/professional default. Do it, cite evidence, and report what changed.
3. Ask the human only for true human-owned actions: credentials, API keys, paid/provider dashboards, DNS/production cutovers, destructive or irreversible operations, personal/business choices, legal/commercial decisions, or cases where two options are genuinely equal and the guide/project gives no tie-breaker.
4. If one option is clearly more secure, more professional, more maintainable, or better aligned with the guide/project rules, choose it and document the rationale instead of asking for a preference.
5. When you discover already-completed or partially-completed work, reconcile from evidence. Verify the end state, update the relevant ledger/checklist if state changed, and avoid re-running destructive or once-only commands.
6. Banned routine asks: "should I update trackers?", "should I commit?", "should I run verification?", "should I fix the stale ledger?", or "which option do you prefer?" when the guide/project makes one option clearly better.
7. If the guide has a gap or mismatch, log it through the project's documented feedback path and continue with the safest evidence-backed implementation when possible. Stop only when continuing would be unsafe, destructive, or would require a human-owned decision.

## Metadata
- title: Deploy status
- url: https://library.zajapps.com/zajlibrary/system/platform/resources/reference/deploy-status/
- shelf: Resources
- doc_type: authoring reference
- status: current
- kind: reference
- category: zajlibrary
- subcategory: system
- topic: platform
- description: Which version of ZajLibrary you are viewing — environment, git commit, build time, and how to confirm production matches what you expect.

## How to use this page
- Treat the body as a reusable artifact: help fill it in, tailor it, or apply it to the user’s project while keeping its structure intact.
- Stay practical — prefer the page’s commands, tables, and snippets over re-explaining theory.
- Cite section headings when pointing to a specific part.

---

# 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).

<DeployStatusPanel />

## 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` |

:::note[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.
:::

:::caution[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).

# Deploy status

> Source: https://library.zajapps.com/zajlibrary/system/platform/resources/reference/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).

<DeployStatusPanel />

## 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` |

:::note[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.
:::

:::caution[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).