Add Angular frontend example and CLI template

[nntndfrk]

Summary

• Add examples/angular, a complete zero-native desktop example with an Angular 20 SPA frontend (signals + zoneless change detection, OnPush, ng serve pinned to 127.0.0.1:4200, production build to frontend/dist).
• Register angular as a --frontend choice in zero-native init and the templates generator, alongside next, vite, react, svelte, vue.
• Wire zig build test-example-angular and extend the CI scaffold loop to exercise the Angular template end to end.
• Update README, docs (/cli, /quick-start), packages/zero-native/README.md, and skill-data/core references to list Angular as a supported frontend.

[vercel]

@nntndfrk is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​angular/​router@​20.3.21
	npm/​@​angular/​cli@​20.3.26
	npm/​@​angular/​platform-browser@​20.3.21
	npm/​@​angular/​compiler-cli@​20.3.21
	npm/​@​angular/​forms@​20.3.21
	npm/​@​angular/​build@​20.3.26
	npm/​@​angular/​core@​20.3.21
	npm/​@​angular/​compiler@​20.3.21
	npm/​@​angular/​common@​20.3.21
	npm/​rxjs@​7.8.2

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: ? → npm/@angular/build@20.3.26 → npm/entities@4.5.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: ? → npm/@angular/build@20.3.26 → npm/entities@6.0.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@6.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report