S19: establish engineering repository

VALIDATION.md

@@ -0,0 +1,30 @@
+# S19 validation — 2026-11-08
+
+- Bootstrap and project generator: **7 tests passed**. Covers deterministic
+  regeneration, modified/added/missing files, moved tags, obsolete-file removal,
+  project-file preservation, symlinks, existing destinations, all three component
+  selections and actual Maven regeneration with generated/ absent.
+- Formatter integration: passed read-only checks, formatting, import cleanup,
+  UTF-8, idempotence, parser failures and discovery of newly added files.
+- Shared CI behavior: **19 tests passed**, including optional components,
+  configuration precedence, path containment, publication gates, existing-tag
+  preservation, architecture checks and bounded process execution.
+- Shared release behavior: **34 tests passed**, including recovery, ambiguous
+  outcomes, locking, actual remote shell, digest checks and readiness timeouts.
+- Generated recipe-demo: backend verification, standards and coverage, frontend
+  lint/tests/build and both prebuilt Docker images passed using the common recipe.
+- Real isolated deployment test: pushed uniquely named example images to the
+  internal Gitea registry, prepared digests, deployed two synthetic revisions,
+  rolled back, and verified both container revision labels. Temporary local
+  Compose containers were removed. Registry test images remain as evidence.
+- Agile Dancers consumer: full pipeline passed with **73 backend tests**,
+  **32 frontend tests**, **4 browser tests**, **19 standards regression tests**,
+  both prebuilt images and combined backend coverage **1771/1841 (96.20%)**.
+- Agile Dancers standalone Docker source builds: backend and frontend passed.
+  Backend verification used a disposable PostgreSQL instance and BuildKit secrets;
+  no production database or deployment was involved.
+
+No production deployment was performed. Live NAS SSH connectivity, production
+credentials and production rollback across existing retained releases remain
+operational validation limits. Legacy release-state JSON remains compatible;
+pre-S19 retained releases use current health/settings as documented in README.md.