5 Commits

Author SHA1 Message Date
eust-w
a6b713f5df 🧪 Treat Go table cases with random hex names as the same baseline failure
A table test that names its case with a 16–32 hex id (an org, a token)
fails as a different string at the start commit and after the change.
The baseline then treats that case as new, so a frontend-only wish
cannot pass Go tests that were already red.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-11-02 11:23:52 +08:00
eust-w
9df1778989 🧪 Compare with the start commit in a repository like the workspace's
The tests that run again at the commit a run started from get that
commit in a repository of their own, checked out, with the same origin:
a test that needs Git no longer fails there only for want of it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-02 07:21:05 +08:00
eust-w
35c00f076d 🧪 Do not hold a change to failures already on its branch
- Checks run in a repository of their own holding only the commit (and
  the commit the run started from, as refs/wishforge/base), so code that
  asks Git which commit it is gets the true answer; the verifier's
  repository and configuration stay out of reach
- A frontend test gets two minutes before it fails, instead of one that
  never settles holding the whole suite until the check is killed
- When frontend or Go tests fail, the same tests run at the commit the
  run started from; only failures that were not there before fail the
  change

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-02 05:37:14 +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
eust-w
4e5ab1719c ✨ Enable local Claude delivery to Gitea and POC
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.
2026-10-22 16:21:33 +08:00