fix(angular-ssr): remove invalid "public" property from vercel.json

[fmontes]

What

Removes the invalid "public": true property from examples/angular-ssr/vercel.json.

Why

Vercel's current vercel.json schema no longer accepts a top-level public property. Deployments of the angular-ssr example fail at build time with:

The vercel.json schema validation failed with the following message: should NOT have additional property public

Fix

Dropped the single offending line. The remaining rewrites and functions config is unchanged and schema-valid.

Fixes #36211

🤖 Generated with Claude Code

[claude]

Claude finished @fmontes's task in 34s —— View job

---

Rollback Safety Analysis

• Read rollback-unsafe categories reference
• Get full PR diff
• Analyze diff against all unsafe categories
• Apply appropriate label

Result: ✅ Safe to Roll Back

The only change in this PR is removing one line from examples/angular-ssr/vercel.json:

-  "public": true,

This is a deployment config file for an example project. It touches no database migrations, Elasticsearch mappings, data models, REST/GraphQL API contracts, OSGi interfaces, VTL viewtools, or any other category in the rollback-unsafe reference. The label AI: Safe To Rollback has been applied.

[github-actions]

🤖 Bedrock Review — deepseek.v3.2

[🟡 Medium] examples/angular-ssr/vercel.json:3 — Removing "public": true may affect Vercel deployment behavior, potentially making the project private or changing asset accessibility. This could break deployment expectations if the project relies on public hosting.

---

_{Run: #27712780303 · tokens: in: 477 · out: 60 · total: 537}