# Deploy Instructions - skygorilla-live

## Goal

Ship the `skygorilla-live/` capability surface to a public URL with Furnace as the deploy/runtime truth and Stratum as the data truth. Firebase is legacy evidence only, not an active source of truth for hosting or data.

## State

- `https://skygorilla-live.pages.dev/` is the active live URL
- `https://skygorilla-live.web.app/` still returns HTTP 404 and is now legacy-only
- `public/index.html` is the local landing surface
- `public/capabilities/` mirrors `../capabilities/`

## Furnace-first path

1. `cd C:\Users\Nero3D\Desktop\skygorilla-workspace\skygorilla-live`
2. Publish `public/` through the selected live host.
3. Verify `capabilities/deploy-status.json` matches the deployed surface.

## Cloudflare Pages fallback

1. `wrangler login`
2. `wrangler pages project create skygorilla-live --production-branch main`
3. `wrangler pages deploy public --project-name skygorilla-live --branch main --commit-dirty true`

## Local preview

The current fallback is a local static server on `http://127.0.0.1:8765/`.

```powershell
python -m http.server 8765 --bind 127.0.0.1 --directory public/
```

## Legacy note

Firebase-specific hosting commands are retained only in historical receipts outside this public mirror. They are not the active hosting or data path.

## Blocker

No blocker remains for the Cloudflare Pages deployment. The only legacy gap is that the old Firebase hostname still resolves to HTTP 404.