# Preview Handoff Requirements

Status: GitHub complete, Cloudflare Preview Deploy complete by CEO/Codex workflow, Production blocked.

Date: 2026-07-04

## Purpose

This document lists the GitHub URL, PR, and Preview Deploy information needed before MCC v1.1 can be checked outside local development.

It does not approve production deployment, external authentication, Google Drive real connection, paid AI API usage, or Version4.

## Current State

| Item | State |
| --- | --- |
| Local MCC v1.1 | Ready and tested locally |
| Current branch | `main` |
| Latest local commit before GitHub docs update | `abac87f Merge remote MCC repository baseline` |
| GitHub remote | Configured: `https://github.com/uetomo202-code/mia-command-center.git` |
| GitHub push | Complete on `main` |
| GitHub PR | Not created |
| Cloudflare Preview | Complete |
| Preview alias | `https://preview-mcc-v1-1.mia-command-center.pages.dev` |
| Production Deploy | Not approved |
| Version4 | Not started |

## GitHub URL Needed From Tomoki

Recommended repository:

```text
mia-command-center
```

Tomoki provided the repository URL. Active remote:

```text
https://github.com/uetomo202-code/mia-command-center.git
```

Codex used:

```powershell
git push -u origin main
git remote -v
```

## PR Information

Current recommendation:

- First push can go directly to `main` only if the new repository is empty and private.
- If Tomoki wants PR review before Preview Deploy, create a branch such as `preview/mcc-v1-1`.

PR information needed if PR flow is chosen:

| Field | Recommended Value |
| --- | --- |
| Branch | `preview/mcc-v1-1` |
| Base | `main` |
| Title | `Prepare MCC v1.1 preview` |
| Required checks | `npm test`, `npm run test:smoke`, secret scan |
| Approval gate | Tomoki Delivery Approval for Preview only |

## Cloudflare Preview Inputs

Cloudflare Pages setup should wait until GitHub push is done.

| Setting | Value |
| --- | --- |
| Framework preset | None |
| Build command | `npm run preview:build` |
| Output directory | `dist/cloudflare-preview` |
| Root directory | repository root |
| Environment secrets | none for current preview |

Local preview artifact command:

```powershell
npm run preview:build
```

Wrangler preview deploy command after Cloudflare authentication:

```powershell
npm run preview:deploy
```

Preview is complete for the current CEO review cycle.

Latest Preview:

```text
https://preview-mcc-v1-1.mia-command-center.pages.dev
```

Production remains blocked.

## Tomoki Next Actions

1. Authenticate Cloudflare if Preview Deploy should be executed from this machine.
   Use `npx wrangler login`, or set `CLOUDFLARE_API_TOKEN` outside git for the current machine/session.
2. Confirm the Cloudflare Pages project name `mia-command-center`.
3. Run `npm run preview:deploy`.
4. Check the Preview URL on desktop and mobile.
5. Do not approve Production Deploy until Preview is checked on real devices.

## Codex Next Actions After Cloudflare Login

1. Run `npm run preview:deploy`.
2. Capture the Preview URL.
3. Report commit hash, branch, and Preview URL.
4. Re-run local checks.
5. Stop before Production Deploy.

## Stop Conditions

- Missing repository URL.
- Authentication failure.
- Request to publish production.
- Secret/token handling.
- Google OAuth.
- Paid AI API activation.
- Version4 scope change.
