Add reusable Vercel deploy, example caller, and Supreme AI CI/CD deploy workflow

[wesship]

Motivation

• Provide a concrete go-live path for app repos to call a reusable Vercel deploy and obtain the deployed URL programmatically.
• Make Vercel deployments more robust for monorepos/Lovable outputs by allowing a configurable working-directory and exposing deployment_url to callers.
• Harden the Supreme AI deployment hub pipeline with an end-to-end CI/CD workflow that validates, builds, publishes an image, and deploys with health checks.

Description

• Added .github/workflows/vercel-deploy.yml, a reusable Vercel deploy workflow that accepts typed inputs (environment, working-directory, production, node-version, vercel-version), validates the working directory, runs vercel pull/vercel build, performs a prebuilt vercel deploy, extracts the *.vercel.app URL and publishes it to GITHUB_OUTPUT as deployment_url and to GITHUB_STEP_SUMMARY.
• Added .github/workflows/vercel-app-deploy-example.yml, an example caller workflow that demonstrates how to call the reusable workflow, pass required secrets, and propagate deployment_url to downstream jobs.
• Added .github/workflows/supreme-ai-deploy.yml, a CI/CD pipeline that installs deps, runs lint/tests/build, builds and pushes a Docker image to GHCR, SSH-deploys the container on a remote host, and runs health check retries with failure logs; it also validates required secrets and defaults the service bind to 127.0.0.1 for safety.
• Updated profile/README.md with a go-live quick start, required/optional secret list, deployability checklist, Vercel notes (Lovable support), and recommendations for production hardening.

Testing

• Validated the workflow YAML syntax by running ruby -e "require 'yaml'; YAML.load_file('.github/workflows/supreme-ai-deploy.yml'); YAML.load_file('.github/workflows/vercel-deploy.yml'); YAML.load_file('.github/workflows/vercel-app-deploy-example.yml'); puts 'YAML OK'", which printed YAML OK indicating the files parse as valid YAML.

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 67fcd6d27b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Guard Node validation step for non-app repositories

This workflow is added to the .github repository, but it unconditionally runs npm ci on every push/PR; in this repo there is no package.json/lockfile, so the validate job fails immediately and the pipeline can never reach image build or deploy. If this file is intended as a template for another repo, it should be limited to manual/reusable execution or gated so it does not run in repos without a Node project.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Remove automatic push trigger from example deploy caller

The example workflow runs on push to main and invokes the reusable deploy with working-directory: ., which in this repository has no app sources (package.json), so each push triggers a failing deployment run. Example caller workflows should be manual-only or stored as documentation snippets to avoid permanent red checks in the hosting repo.

Useful? React with 👍 / 👎.