Run CI orchestration and setup as Java 25 source programs

docs/s4-validation.md

@@ -1,7 +1,8 @@
 # S4 verification evidence
 
 Date: 2026-10-28. Status: repository implementation and local container verification
-passed; operational Gitea acceptance remains pending. S4 is **not complete**.
+passed; Gitea and runner configuration are operational. Main publication is
+awaiting approval to merge PR #1. S4 is **not complete**.
 
 ## Verified locally
 
@@ -56,7 +57,8 @@ Local image IDs (not registry digests):
       `linux/amd64`; repository variable `TARGET_PLATFORM=linux/amd64` configured.
 - [x] Activate and verify the Docker Desktop HTTP-registry setting.
 - [x] Repository `REGISTRY_USER`/`REGISTRY_TOKEN` secrets configured using the
-      supplied token files. Registry access is verified by actual publication below.
+      supplied token files. A temporary Docker login with the registry token
+      succeeded; actual publication still awaits a main-branch merge.
 - [x] Runner ID 1 (`agiledancers-mini-pc`) registered, service started and
       online in Gitea. Real feature/failure jobs ran on this runner.
 - [ ] Confirm server settings permit every branchpush (including messages with
@@ -86,3 +88,30 @@ attempt identifier for containers and diagnostic artifact names. The Gitea v3
 artifact-list API returns an empty list despite successful uploads; artifacts
 were verified by downloading the run-page archive URLs. This is separate from
 artifact availability and does not require a server upgrade.
+
+
+## Ready for review; main merge not authorized
+
+[PR #1](http://192.168.2.28:3000/wanjakrah/agiledancers/pulls/1) remains open at
+the maintainer's explicit request. No main merge or application image publication
+was performed.
+
+[Feature run #3](http://192.168.2.28:3000/wanjakrah/agiledancers/actions/runs/3),
+API run/job ID 4, commit `834584dae06b5976936a5e739871f1164cf81bcd`, succeeded.
+The two container E2E tests passed and diagnostics were uploaded as
+`diagnostics-4-20261028164607460012324`, confirming unique attempt names work.
+
+The main branch currently contains only its initial commit. PR #1 therefore
+includes the prior application history from `feature/setup` as well as S4. Its
+scope is documented in the PR description. A main merge needs explicit approval;
+only then can real main publication/pullback/rerun acceptance be completed.
+
+
+## Java 25 helper migration
+
+CI orchestration, setup and behavior tests now run through `java ci/Ci.java`.
+The shell/Python helpers have been removed. The source launcher compiles helper
+classes in memory without external dependencies or preview flags. Fourteen Java
+behavior tests pass, including JSON/configuration preservation, publication gates,
+partial recovery and process deadlines. A real feature run validates this revision
+before updating the existing open PR; no merge to main is authorized.