Repository navigation
Bring frontend-template to the ezspecificity baseline on Angular 20 #11
Description
What to build
The template was last updated 2025-10 and has missed fixes that landed in later apps. Bring it up to the ezspecificity-frontend baseline and remove @moleculemaker/dev-tool, which is being retired (the template carries its own deployment files; job pages are built from each app's Figma).
Part of the pre-work for a repeatable process for building AlphaSynthesis / AlphaSynBio apps (pilot: EZKinetics, live on prod by 2026-12-31).
Acceptance criteria
- Shared status poll so the result fetch cannot miss completion (ezspecificity fix)
- nginx gzip and Cache-Control;
exec nginxin the entrypoint - Legacy compiled PrimeNG SCSS theme removed; theming via a single
definePresetpreset - dev-tool dependency, schematics references and
init/newjobscripts removed; README updated - Angular 20 / PrimeNG 20; build, lint and existing tests pass
Blocked by
None - can start immediately
Activity
matthewberry commentedon Oct 19, 2026
From review of #9:
LoadingComponent extends JobResult, so<app-loading>runs a second status poll alongside the result page's. #9 shares the poll within one instance, which takes it from 4 to 2 requests per 10 s, not to 1. Fold in here: pass the parent'sstatusResponse$(or the status itself) into<app-loading>as an input so there is one poll per page.