From be4382472c19b08da9c4a7e29a5395fa917e947a Mon Sep 17 00:00:00 2001 From: dingo Date: Sat, 19 Sep 2026 19:12:28 -0400 Subject: [PATCH] Record verified scheduler CI and confirmed Argo readiness --- deploy/README.md | 13 ++++++++----- docs/STATUS.md | 9 ++++++--- docs/engineering/VALIDATION.md | 9 ++++++++- 3 files changed, 22 insertions(+), 9 deletions(-) diff --git a/deploy/README.md b/deploy/README.md index 25a7f9a..fc3c477 100644 --- a/deploy/README.md +++ b/deploy/README.md @@ -7,8 +7,10 @@ broader checks and a bounded **stateless proof Job**. It is not a region server. Cluster execution must be recorded separately from image publication. The expanded [run 1402](https://git.aeternalisgames.com/dingo/AEvolution/actions/runs/1402) -passed all checks and published `4c2cc04`. The dev Kustomize manifest already pins -that verified image digest. Argo bootstrap examples still need the actual +passed all checks and published `4c2cc04`. The maintainer's later GitOps commit +`20e609d` pins the verified run 1399 image instead; M1.6 preserves that selection. +The maintainer confirms Argo is ready to pick up deployment additions. Bootstrap +examples still need the actual application namespace and destination; do not apply examples unchanged. ## Gitea and Harbor @@ -59,8 +61,9 @@ instrumentation, not future concurrency. Record actual results in VALIDATION.md. ## Argo settings and promotion -Reuse the maintainer's application once its GitOps source is confirmed. For an -application watching this repository directly: +Reuse the maintainer's confirmed application. The following are bootstrap +settings for an application watching this repository directly, not an inspection +of the live application's configuration: | Field | Value | |---|---| @@ -81,7 +84,7 @@ Before syncing: 1. Wait for successful checks and publication of the intended commit. 2. Update `deploy/kubernetes/dev/kustomization.yaml` to the published - `sha256:<64 hex>` digest, review and commit it. It currently pins run 1402; + `sha256:<64 hex>` digest, review and commit it. It currently pins run 1399; no floating tag or fallback image is used. 3. Run `kubectl kustomize deploy/kubernetes/dev`. Check exactly three resources, all in evolution-dev, the selected digest and no unresolved marker. diff --git a/docs/STATUS.md b/docs/STATUS.md index fb92c34..5dbc2ba 100644 --- a/docs/STATUS.md +++ b/docs/STATUS.md @@ -31,8 +31,10 @@ analysis/sanitizers/fuzzing and runtime smoke verification. Images target [Run 1402](https://git.aeternalisgames.com/dingo/AEvolution/actions/runs/1402) passed all jobs for source commit `4c2cc04`: Linux checks, separate TSan and image -smoke/publish. The dev manifest now pins the published image at -`sha256:8fce2b462c9907f38d3fb832afeb70d0bff068dd832b2171e861186dbcb8e6b9`. +smoke/publish. That verified image was previously pinned. The maintainer's +subsequent GitOps commit `20e609d` selects the run 1399 image at +`sha256:0c6c6e1ac28de2ce0648fd0992ca694963e303ef5c9414fe5ac668937136800d`; +the M1.6 change preserves that independent deployment choice. Windows checks also pass; full commands and intermediate CI failures are recorded in the validation report. M0's engineering proof is verified; dev cluster execution is the remaining delivery check, not a claim of persistent-world readiness. @@ -69,7 +71,8 @@ exact-tick admission, bounded ordered lifecycle commands, receipts and atomic rollback on rejection. Windows Release, clang-tidy, ASan and formatting checks pass. Permutations across 32 seeds, restored continuation, duplicate/late/future inputs, limits and exhaustion are covered. The no-input golden and snapshot v1 -are unchanged. Linux CI evidence is recorded in the validation report after push. +are unchanged. Gitea run 1407 passed all Linux checks, ECS, TSan and image jobs; +evidence is recorded in the validation report. Nonempty batches copy world state; this favors a clear transaction boundary for the proof, not a measured realtime performance claim. No thread pool or gameplay input protocol is introduced. diff --git a/docs/engineering/VALIDATION.md b/docs/engineering/VALIDATION.md index 80f056f..e3f594e 100644 --- a/docs/engineering/VALIDATION.md +++ b/docs/engineering/VALIDATION.md @@ -146,4 +146,11 @@ capacity and tick/ID exhaustion. Golden `d61ad5bf0c928c76` remains unchanged. The copy-and-commit implementation allocates before publishing world state and statically checks noexcept publication/receipt moves. Allocation-failure injection was not run. No scheduler throughput claim, concurrency validation, durable input -journal or Kubernetes execution is implied. Linux CI is pending this source push. +journal or Kubernetes execution is implied. + +[Gitea run 1407](https://git.aeternalisgames.com/dingo/AEvolution/actions/runs/1407) +passed all four jobs for source `b620edfd6f8097172acf055402a24620cb078358`: +Linux checks, the ECS experiment, separate TSan, and image smoke/publication. +This closes the pending Linux validation for M1.6. The maintainer's independent +dev image pin from `20e609d` was preserved during rebase. Kustomize renders the +three expected dev resources successfully; no cluster execution is claimed.