Change explore page title color to primary

[qingqing-ux]

Summary

• Update CommunityHeader title color from --ui-color-title (grey) to --ui-color-primary-main
• Sync design file community-explore.pen with the color change

Test plan

• Verify explore page title displays in primary color
• Check visual consistency across community pages

🤖 Generated with Claude Code

[gemini-code-assist]

Warning

Gemini encountered an error creating the summary. You can try again by commenting /gemini summary.

[xgopilot]

This PR is a large feature accumulation branch (600 files), not just the title change. The actual work is substantial and well-structured: code editor generalization to IXGoProject, copilot tool-call streaming refactor, update checker via ETag, browser version detection, community user profile/avatar editing, and sprite gen model reorganization. New docs in docs/develop/generalization/ are accurate and match the implementation. A few targeted issues below.

[xgopilot]

currentEtag is only set once (when null) and never updated after a change is detected. Once a new deployment is found, every subsequent poll will return hasUpdate = true (since currentEtag still holds the old value), causing onUpdate to fire on every interval until stop() is called. The ETag should be updated after detecting a change:

Suggested change

	if (this.currentEtag == null) this.currentEtag = etag
	const hasUpdate = this.currentEtag != null && this.currentEtag !== etag
	this.currentEtag = etag
	return hasUpdate

[xgopilot]

The ETag is compared raw. PR #2979 (merged to dev) fixed a false-positive caused by weak ETag W/ prefixes — servers may return W/"abc" on one request and "abc" (strong form) on another, making them appear different even when the content is identical. This branch appears to be missing that normalization fix. Consider rebasing or cherry-picking commit e75e672e.

Suggested change

	const hasUpdate = this.currentEtag != null && this.currentEtag !== etag
	const normalizedEtag = etag.replace(/^W\//, '')
	const hasUpdate = this.currentEtag != null && this.currentEtag !== normalizedEtag
	this.currentEtag = normalizedEtag
	return hasUpdate

[xgopilot]

This row is stale relative to the changes in this very PR. The new xgo-code-editor/code-editor.ts introduced here already accepts IXGoProject instead of SpxProject, so CodeEditor is no longer "deeply coupled to spx APIs". The row should be removed from the "future work" table or moved to the "now framework-agnostic" table.

[xgopilot]

check is an async function passed to setInterval, so JavaScript doesn't wait for it to complete before firing the next tick. If checkForUpdates() (a network request) takes longer than intervalMs, concurrent calls can overlap and race on this.currentEtag. Consider tracking in-flight state:

Suggested change

	const check = async () => {
	let inFlight = false
	const check = async () => {
	if (!navigator.onLine || inFlight) return
	inFlight = true
	try {
	const hasUpdate = await this.checkForUpdates()
	if (hasUpdate && this.updateCheckTimer != null) onUpdate()
	} catch (error) {
	capture(error, 'Failed to check for updates')
	} finally {
	inFlight = false
	}
	}