@tryvitris/website-harness 0.1.0-beta.7 → 1.0.0

package/templates/site/AGENTS.md

@@ -1,5 +1,7 @@
 # __NAME__ site agent
 
+For a requested separate business admin, read `agent/refs/admin.md` and the installed harness's `docs/ADMIN.md`. Site creation `--admin` prepares next steps only. Use `vitris admin setup --plan` then reviewed `--apply` for a sibling installation; cloud provisioning, authentication and deployment are separate. Preserve existing forms, tenants, credentials and workflow progress; never deploy a shared backend as a setup side effect.
+
 This site uses the Vitris active-agent workflow. The active local agent executes workflow stages directly. The harness prepares context in `agent/CURRENT.md`, executes deterministic tools, evaluates artifacts, and advances the graph.
 
 ## Active-Agent Loop
@@ -27,9 +29,9 @@ When making later-life changes in Cursor or chat:
 
 ## Operator Guardrails
 
-- Never mark checks passed by hand or bypass gates.
+- Never mark checks passed by hand. Skip deployment review gates only when the user explicitly requests quick publish, using `vitris deploy --quick` (production requires `--environment production`); record this as build-only verification.
 - Site-specific preferences belong in `agent/request.json` or site memory.
 - Plan managed-kit updates with `vitris upgrade --site . --plan`, inspect conflicts, then use `--apply`. `npm run refresh-agent` is a compatibility alias. Package defaults are selected only when their recorded hashes match `agent/managed-files.json`; place site-specific instructions under `agent/overrides/`. Unknown copied-kit edits remain conflicts. `launch.json`, authored files, `agent/STATE.json`, preparations, leases, and receipts are preserved.
-- Cloudflare deployment is explicit via `vitris deploy` (or `wrangler deploy`).
+- Local builds and direct Cloudflare Pages uploads are the default. Use `npm run deploy:preview` for a hosted preview and `npm run deploy` only for explicitly requested production publication. Both run local verification and upload the exact staged bundle. Keep `dist/`, release bundles, receipts, and credentials out of Git. Do not enable GitHub Actions or Cloudflare Git builds unless the operator chooses hosted automation; `deployment/github-actions.yml.example` is inactive by default. Existing sites require review of their workflows and Cloudflare branch-deployment settings before migration.
 
 Two identical failures block automatic continuation. Fix the cause and use an explicit restart with a reason; ordinary resume does not reset attempts or spend. Follow parent design-stage resume instructions exactly. Active-agent reviews and independent-model reviews are labeled separately; neither implies human approval.

package/templates/site/README.md

@@ -29,13 +29,15 @@ npm run go                        # prepare the next stage → preview_ready
 npm run build                     # → dist/ local preview
 ```
 
-Default loop stops at a local preview. Launch (GitHub + Cloudflare Pages + backend tenant) is explicit — see `agent/refs/launch.md` and `launch.json`.
+Default loop stops at a local preview. Launch is explicit — see `agent/refs/launch.md` and `launch.json`. Builds and verification run locally; the deployment command uploads the finished files directly to Cloudflare Pages. GitHub stores source and history. New sites have no active GitHub deployment workflow.
 
-For a production Pages deployment, set `launch.json.publicOrigin` to the final `https://` origin. Use `npm run build && npm run preflight` as the Cloudflare Git build command, with `VITRIS_SITE_ENVIRONMENT=production` and `VITRIS_BACKEND_ORIGIN` set in build environment variables; the output directory is `dist`. The preflight rebuilds and verifies the exact publishable files with Chromium, so the build must have Playwright's browser binary installed. Any failed required check exits nonzero and stops publication. Keep preview branches on `VITRIS_SITE_ENVIRONMENT=preview` and use the generated CI workflow when branch-specific gating is needed. Do not use a bare `npm run build` as a production build command.
+Set `launch.json.pagesProject` to your Pages project and `launch.json.publicOrigin` to the final production `https://` origin. Install Chromium with `npx playwright install chromium`, authenticate using `npx wrangler login`, and run `npm run deploy:preview` to check a hosted preview. After accepting it, explicitly publish with `npm run deploy`. Ordinary deployment runs the full local verification, stages the exact checked files, uploads that bundle, records its identity, and checks the hosted URL. Failed required checks stop publication. Keep `dist/` and staged release output ignored in Git. See `deployment/README.md` for setup.
 
 To ignore local Cursor-chat traces in an existing site, add `agent/runs/traces/` to `.gitignore`. See harness `docs/tracing.md`.
 
-If this site publishes through the backend Worker, protected CI needs `VITRIS_TENANT_ID`, `VITRIS_PUBLISH_ATTESTATION_SECRET`, and `VITRIS_BACKEND_ORIGIN`; the Worker needs the matching `PUBLISH_ATTESTATION_SECRET` and its Cloudflare API credentials. The generated workflow signs the exact verified `dist/` bundle and posts it to `/api/publish-attested`. The Worker rejects stale, altered, or mismatched evidence before changing hosted content. A Pages project using Git integration can continue using its normal build path; avoid configuring both paths for the same production release.
+For an existing Git-connected Pages project, disable automatic production and preview branch deployments before adopting local direct uploads. Existing GitHub deployment workflows also need to be disabled. The optional `deployment/github-actions.yml.example` runs only after an owner installs it under `.github/workflows/`; hosted CI is an explicit alternative.
+
+If this site publishes through the authenticated backend Worker, retain its signed bundle publication contract. The optional workflow signs the exact verified `dist/` bundle and posts it to `/api/publish-attested`, using protected `VITRIS_TENANT_ID`, `VITRIS_PUBLISH_ATTESTATION_SECRET`, and `VITRIS_BACKEND_ORIGIN`; the Worker needs the matching `PUBLISH_ATTESTATION_SECRET` and its Cloudflare credentials. Review that existing publication path before changing deployment providers. Static direct uploads do not register backend tenants or configure contact forms.
 
 For interactive workflow commands on Windows, call the installed bin directly when forwarding flags, for example `node ./node_modules/@tryvitris/website-harness/bin/vitris-go.js --prepare --jev-mode off`. `npm run go -- --prepare` may be parsed differently by some npm/PowerShell versions. A prepared `agent/CURRENT.md` is the active stage; complete it with the recorded preparation ID, then prepare the next stage. Do not edit `agent/STATE.json`.
 
@@ -55,3 +57,6 @@ description: …
 ```
 
 Build flattens `<hero>` into ordinary HTML. Lead forms use `data-lead-form` and POST to the backend (`VITRIS_BACKEND_ORIGIN`).
+
+
+For an explicitly requested quick publish, use `vitris deploy --quick --environment production` (`npm run deploy:quick` in newly scaffolded sites). This rebuilds and deploys without browser, graph or launch review gates. Compilation, Cloudflare credentials, staged-file integrity and an HTTP smoke check still run. Receipts record build-only verification. Preservation sites use `--environment preview` and also skip screenshot comparisons. Ordinary deployment retains full preflight.

package/templates/site/deployment/README.md

@@ -0,0 +1,24 @@
+# Deployment
+
+Build and verify on your own computer, then upload the finished files directly to Cloudflare Pages. GitHub stores authored source and the lockfile. Keep generated `dist/`, staged bundles, receipts, and credentials out of Git.
+
+After setting `launch.json.pagesProject` and the production `launch.json.publicOrigin`, install dependencies and Chromium and authenticate with your own Cloudflare account:
+
+```sh
+npm ci
+npx playwright install chromium
+npx wrangler login
+npm run deploy:preview
+# After accepting the preview and explicitly choosing production publication:
+npm run deploy
+```
+
+The deploy command builds locally, verifies the release, stages the exact checked files, uploads them, and checks the hosted URL. New sites have no active GitHub deployment workflow. Source pushes do not publish the website.
+
+For an existing Git-connected Cloudflare Pages project, disable automatic production and preview branch deployments before using local uploads. Keep the existing project and domains. See the installed harness's `docs/CLOUDFLARE.md` for migration and optional backend publishing.
+
+Preservation sites use `npm run deploy` for temporary previews only; production remains unsupported.
+
+## Optional hosted automation
+
+`github-actions.yml.example` is inactive in this directory. An owner choosing GitHub-hosted deployment can copy it to `.github/workflows/deploy.yml`, review its triggers, and configure protected secrets. Hosted CI is subject to the provider's usage limits. Do not enable a second automatic deployment path for the same site. Backend Worker publication retains the signed bundle and preflight checks in the example.

package/templates/site/{.github/workflows/deploy.yml → deployment/github-actions.yml.example}

@@ -1,9 +1,8 @@
-name: Deploy
-# Prefer connecting the Cloudflare Pages project to this GitHub repo
-# (Dashboard → Pages → project → Settings → Builds → Connect to Git).
-# Then every branch, including update-* preview branches from the Vitris
-# concierge, builds automatically. Keep this workflow only if you are NOT
-# using Pages Git integration (Direct Upload fallback).
+name: Deploy (optional GitHub Actions)
+# Local builds and direct uploads are the default: use npm run deploy locally.
+# This example does not run from deployment/. To opt into hosted CI, copy it to
+# .github/workflows/deploy.yml and configure your own protected secrets.
+# Enable only one automatic deployment path for each site.
 on:
   push:
     branches: [main]

package/templates/site/gitignore

@@ -6,6 +6,9 @@ dist/
 .dev.vars
 scratch/
 agent/runs/traces/
+agent/release-bundles/
+agent/release-candidate.json
+agent/releases/
 .cursor/vitris-trace-hooks.json
 .cursor/hooks.json.vitris-backup
 .cursor/hooks.json.malformed

package/templates/site/package.json

@@ -11,7 +11,9 @@
     "eval": "node ./node_modules/@tryvitris/website-harness/bin/vitris-eval.js",
     "go": "node ./node_modules/@tryvitris/website-harness/bin/vitris-go.js",
     "preflight": "node ./node_modules/@tryvitris/website-harness/bin/vitris-launch-preflight.js --environment production",
-    "deploy": "npm run build && npm run preflight && wrangler pages deploy dist --project-name=__SLUG__",
+    "deploy": "node ./node_modules/@tryvitris/website-harness/bin/vitris.js deploy --site . --environment production",
+    "deploy:preview": "node ./node_modules/@tryvitris/website-harness/bin/vitris.js deploy --site . --environment preview",
+    "deploy:quick": "node ./node_modules/@tryvitris/website-harness/bin/vitris.js deploy --site . --environment production --quick",
     "verify:browser": "node ./node_modules/@tryvitris/website-harness/bin/vitris-verify-browser.js",
     "verify:performance": "node ./node_modules/@tryvitris/website-harness/bin/vitris-verify-performance.js --site .",
     "refresh-agent": "node ./node_modules/@tryvitris/website-harness/bin/vitris-refresh.js --site .",