S19: own shared agent workflows and document multi-project runner onboarding

specs/in_review/S19_multi-project

@@ -39,10 +39,15 @@ technical usage instructions rather than maintaining duplicate instructions.
 
 ### Engineering
 
-Move reusable skills, general engineering documentation, coding standards,
+Move general engineering documentation, coding standards,
 tooling, and generalized pipeline and deployment mechanisms to `engineering`.
 Include templates and a project generator for new consumers.
 
+Maintainer clarification (2026-11-10): reusable agent skills belong in
+`landscape/skills/`, as shared workflows for all projects. Engineering and application
+agent instructions reference those skills and retain project-specific review
+companions. Historical published engineering versions remain immutable.
+
 Generalize the existing CI, deployment, formatting, standards, and coverage
 helpers as needed. This includes helpers such as `ci/Pipeline.java`; substantial
 generalization is part of S19 rather than deferred merely because it requires
@@ -175,3 +180,15 @@ Application commit: `c6a495a93c31bef86080915d7c939f642861a97a`. Engineering rele
 
 [Gitea build](http://192.168.2.28:3000/wanjakrah/agiledancers/actions/runs/64) completed successfully.
 Production deployment remains a separate action.
+
+## Review follow-up — 2026-11-10
+
+Affected repositories additionally include `waterpolo-coaching`, a new consumer.
+Use the physical mini-pc as a shared Gitea user-scoped runner for `wanjakrah`,
+labelled `mini-pc`, available to existing and future projects of that owner.
+New generated projects default to that label and reuse its one-time registration.
+Record Waterpolo Coaching and its Three.js/Vite frontend deviation in systems.md.
+
+The review found that image names are derived from `<PROJECT_NAME>-backend/frontend`.
+Neither current consumer needs independently configurable image repositories.
+This follow-up does not implement that outstanding part of the original requirement.