S19: record successful implementation and Gitea validation

specs/S19-validation.md

@@ -0,0 +1,35 @@
+# S19 implementation validation
+
+Affected repositories: `agiledancers`, `landscape`, `engineering`.
+
+All S19 acceptance checks completed on 2026-11-08:
+
+- The two new repositories are published and checked out under ~/Projecten/git/.
+- The source inventory records ownership, source attribution and preserved licenses.
+- Engineering v1.0.0 supplies generalized mechanisms, templates, a project generator,
+  version pinning, bootstrap and upgrade instructions.
+- Seven bootstrap/generator tests cover all component selections, actual Maven
+  regeneration with generated/ absent, drift, moved tags and project-file preservation.
+- The formatter integration checks, 19 CI tests and 34 release tests passed.
+- A generated example built/tested through the common pipeline; actual isolated
+  deployments of two digest-pinned revisions and rollback passed.
+- Agile Dancers passed its full pipeline from the Gitea checkout: 73 backend tests,
+  19 standards regression tests, 32 frontend tests, 4 browser tests, both images,
+  and combined backend coverage 1771/1841 (96.20%). The workflow checked the
+  generated snapshot against the published engineering tag and commit first.
+- Both standalone Docker source builds passed locally using a disposable test
+  database and BuildKit secrets for the backend.
+- Current project/landscape Markdown links were checked; no unresolved links remain
+  in the checked documentation. Historical evidence remains application-owned.
+
+Application commit: `c6a495a93c31bef86080915d7c939f642861a97a`.
+
+Successful [Gitea build](http://192.168.2.28:3000/wanjakrah/agiledancers/actions/runs/64).
+
+[Application evidence](http://192.168.2.28:3000/wanjakrah/agiledancers/src/commit/c6a495a93c31bef86080915d7c939f642861a97a/docs/S19-validation.md).
+
+No production deployment was performed. Live NAS SSH authentication, production
+credentials and rollback of pre-S19 retained releases remain explicit operational
+validation limits. The release-state schema, existing Compose project and database
+volume remain compatible; review legacy health-hook compatibility before production
+rollback. Business-system extraction is outside S19.

specs/S19.md

@@ -0,0 +1,9 @@
+# S19 — Multi-project engineering setup
+
+Affected repositories: `agiledancers`, `landscape`, `engineering`.
+
+This stable reference follows the specification through its lifecycle.
+
+- [Specification](in_review/S19_multi-project)
+- [Resource classification](../S19-classification.md)
+- [Application validation](http://192.168.2.28:3000/wanjakrah/agiledancers/src/commit/c6a495a93c31bef86080915d7c939f642861a97a/docs/S19-validation.md)

specs/implemented/S18_new-rules-for-plotting-dance-groups-in-show.md

@@ -9,8 +9,8 @@ so that the complete show is manageable for dancers and enjoyable for audiences.
 
 Refinement confirmed by the maintainer on 2026-11-03. This specification records
 the agreed design. Implementation and validation are complete and ready for review.
-See [validation evidence](../../docs/s18-validation.md) and
-[the applied scheduling rules](../../show-scheduling-rules.md).
+See [validation evidence](http://192.168.2.28:3000/wanjakrah/agiledancers/src/commit/c6a495a93c31bef86080915d7c939f642861a97a/docs/s18-validation.md) and
+[the applied scheduling rules](http://192.168.2.28:3000/wanjakrah/agiledancers/src/commit/c6a495a93c31bef86080915d7c939f642861a97a/show-scheduling-rules.md).
 
 ## Show scope and configuration
 

specs/in_review/S19_multi-project

@@ -2,7 +2,7 @@ As developer
 I want to separate landscape documentation and reusable engineering resources from Agile Dancers
 so that I adhere to ADR1 and can start and maintain multiple projects with a complete, versioned engineering setup.
 
-Status: IN_PROGRESS
+Status: IN_REVIEW
 
 Architecture: ADR1, Application size (`adr/approved/ADR1_application-size.md` before migration).
 
@@ -165,3 +165,13 @@ Complete the following before considering S19 implemented:
 
 Production deployment is a separate action. Business capability extraction,
 runtime system boundaries, and migration of application data are outside S19.
+
+## Implementation evidence
+
+Implemented on 2026-11-08. See [validation](../S19-validation.md).
+
+Application commit: `c6a495a93c31bef86080915d7c939f642861a97a`. Engineering release: `v1.0.0` at
+`c25ce11a1bb8bf97f24d5e2b12d98680a9c573ca`.
+
+[Gitea build](http://192.168.2.28:3000/wanjakrah/agiledancers/actions/runs/64) completed successfully.
+Production deployment remains a separate action.