2 Commits

Author SHA1 Message Date
eust-w
fb67484dd1 🔥 Run WishForge from the cluster only: drop the Mac deployment and its copies
- The cluster's settings come only from the operator inputs kept in
  .wishforge/cluster-poc (carried keys, signing key, plans, profiles,
  host keys); the Mac's .env.local and service files are no longer read
- restore puts back one of the node's snapshots inside the cluster: the
  files are checked against the manifest before anything is emptied, the
  backup container restores the database, row counts decide
- Snapshots also keep Fanyu's Runner records
- Remove migrate, the Mac backup copy and its launchd job, and the Mac
  public entry (frp gateway) code and manifests
- Mark the Mac operating guides as retired

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-02 02:31:17 +08:00
eust-w
c5a6c6160d 🚀 Deploy WishForge to the POC cluster, with check Pods and daily backups
- cluster-poc.mjs: image (in-cluster Kaniko), bootstrap, secrets, apply,
  migrate --rehearsal|--final, public HTTPS entry, backup and restore
- One restricted Pod (platform, executor, Runner, PostgreSQL, Temporal,
  MinIO, Caddy, backup) listening only on loopback except Caddy
- Protected checks run in per-workspace check Pods; cancellation during
  start-up now always removes them
- Daily snapshots on the node (consistent dump with row counts, Temporal
  online backup), copied to the Mac by launchd with SHA-256 checks and a
  notification on failure; restore verified on the rehearsal copy
- Downloads and uploads survive the Mac's lossy link to the cluster
- Local public entry, evidence isolation labels, acceptance records

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-01 16:27:07 +08:00