- 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>
- 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>
- Eight wrong passwords from anywhere on the network locked the only
local administrator out for fifteen minutes, again and again. The
password is 256 random bits, so the limit only has to bound the
scrypt work: after eight failures, checks are spaced two seconds
apart, globally, and a burst cannot run them at once.
- The launcher let the Next.js development server listen on the LAN,
handing every visitor its source maps and hot-reload channel. Only
the production build may now listen beyond loopback. A listener
bound to one address is also checked for readiness there, and the
banner shows the configured port.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Detect actual service and Runner readiness, restore LAN access after network changes, protect production web builds with rollback, honor cancellation during executor startup, and show truthful cached-data and credential states.
Add authenticated LAN access, native Claude execution, checkpoint and budget recovery, and signed POC build/deploy/rollback contracts. Include local service management, regression coverage, and evidence from the completed POC delivery.