S19: shared mini-pc runner and landscape workflows #21
Reference in New Issue
Block a user
Delete Branch "feature/S19_shared-runner"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Share the physical mini-pc runner across existing and future projects and adopt engineering v2.0.0. Agent workflows now live in landscape; generated skill copies are removed. Deployment credentials remain application-owned.
Validation: pinned-resource check passed; 8 bootstrap/generator tests, 21 CI tests, 34 release tests and formatter integration passed. A new generated repository completed its full frontend CI workflow on the shared runner. This PR's application workflow provides consumer validation. No production deployment is included.
Consumer validation passed on shared runner mini-pc: http://192.168.2.28:3000/wanjakrah/agiledancers/actions/runs/66. A newly generated frontend project also completed its full workflow using the default runner without a separate registration. Production deployment is excluded.
Main validation and new-project acceptance:
Main build and image publication passed on runner mini-pc: http://192.168.2.28:3000/wanjakrah/agiledancers/actions/runs/67 (commit
23cb4d408f).A fresh frontend-only project generated from engineering v2.0.0 without --runner completed its full build on shared runner ID 2 after Actions/platform setup. Successful run ID 69, source edb093f4373504d1ad7f71e6f075bdf743f14ed4. It had zero repository-scoped runner registrations. The disposable acceptance repository was removed after recording this evidence. No production deployment was performed.