Website build error

[aaronpowell]

Build error on website as we didn't handle when model is an array

[github-actions]

⚠️ This PR targets main, but PRs should target staged.

The main branch is auto-published from staged and should not receive direct PRs.
Please close this PR and re-open it against the staged branch.

You can change the base branch using the Edit button at the top of this PR,
or run: gh pr edit 1136 --base staged

[Copilot]

Pull request overview

Fixes the website build failure caused by agent frontmatter using model as an array (instead of a single string), so the Agents page can render and filter safely.

Changes:

• Update escapeHtml (and agent page types) to accept model as string | string[] and render arrays safely.
• Update Agents page model filtering logic to support item.model as an array.
• Adjust Astro/Vite build settings (sourcemaps + chunk warning threshold), and update one agent to use a multi-model model list.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
website/src/scripts/utils.ts	Makes escapeHtml handle string[] so SSR rendering won’t crash when model is an array.
website/src/scripts/pages/agents.ts	Updates model typing and filtering to handle array-valued models.
website/src/scripts/pages/agents-render.ts	Updates RenderableAgent.model typing to allow arrays.
website/astro.config.mjs	Changes Vite build settings (sourcemap + chunk warning limit).
agents/dotnet-self-learning-architect.agent.md	Switches model frontmatter to an array and reformats content.

Comments suppressed due to low confidence (1)

website/src/scripts/pages/agents.ts:54

• The model filtering logic will still behave incorrectly when an agent's model is an array because the generated agents.json filter list currently collects model values as-is. That means filters.models will contain the entire array as a single option (stringified like "a,b,c"), and selecting it will never match here because this predicate checks for individual model entries. Please normalize models so filters contain individual strings (flatten arrays during data generation, or defensively split/flatten filter values before comparison).

      return item.model && (Array.isArray(item.model) ? item.model.some(m => currentFilters.models.includes(m)) : currentFilters.models.includes(item.model));

[Copilot]

This inline conditional is difficult to read and maintain, and it duplicates the concept of “normalize model(s) to a list then match any”. Consider extracting a small helper (e.g., normalize to string[] once per item) to keep the filter predicate clearer and easier to extend.

This issue also appears on line 54 of the same file.

[Copilot]

This changes build output behavior (disables sourcemaps and raises chunkSizeWarningLimit) but the PR description only mentions handling model as an array. Please either (1) update the PR description to justify these Vite config changes, or (2) split them into a separate PR so the website build fix can be reviewed independently.