fix: resolve build issues and implement memory UPSERT logic

[clousky2020]

Summary

• antigravityHeaders.ts: Restore ANTIGRAVITY_LOAD_CODE_ASSIST_* exports to fix build failures caused by downstream imports in oauth.ts and gemini.ts
• next.config.mjs: Add @ngrok/ngrok to serverExternalPackages and webpack externals to handle native .node modules
• Memory system: Implement UPSERT logic in createMemory to prevent duplicate entries with the same apiKeyId + key combination
• i18n: Complete Chinese translations for CLI tools and memory dashboard
• Test fixes: Use unique keys in pagination tests to comply with the new unique constraint

Test plan

• Unit tests: all 3231 tests pass (6 pre-existing failures on base branch, unrelated to this PR)
• Build: npm run build succeeds
• Type check: passes
• Lint: passes

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request implements UPSERT logic for memory entries in the store, ensuring that existing records with the same key are updated rather than duplicated. It also migrates the memory dashboard to use i18n translations, updates the Chinese localization file, and configures @ngrok/ngrok as an external package in the Webpack configuration. Feedback includes a missing expires_at field in the SQL update statement which causes a state mismatch, and the use of a mirror-specific registry URL in the lockfile that should be reverted to the official registry.

[gemini-code-assist]

The UPDATE statement in the UPSERT logic is missing the expires_at field. This means that when an existing memory entry is updated, its expiration time will not be updated in the database, even though the returned updatedMemory object reflects the new value. This leads to a state mismatch between the application and the database.

Suggested change

	const stmt = db.prepare(
	"UPDATE memories SET content = ?, metadata = ?, updated_at = ?, session_id = ?, type = ? WHERE id = ?"
	);
	stmt.run(
	memory.content,
	JSON.stringify(updatedMetadata),
	now,
	memory.sessionId,
	memory.type,
	existing.id
	);
	const stmt = db.prepare(
	"UPDATE memories SET content = ?, metadata = ?, updated_at = ?, session_id = ?, type = ?, expires_at = ? WHERE id = ?"
	);
	stmt.run(
	memory.content,
	JSON.stringify(updatedMetadata),
	now,
	memory.sessionId,
	memory.type,
	memory.expiresAt instanceof Date ? memory.expiresAt.toISOString() : (memory.expiresAt ?? null),
	existing.id
	);

[gemini-code-assist]

The registry for react-markdown has been changed to registry.npmmirror.com. Committing mirror-specific URLs to the lockfile can cause issues for other developers or CI environments that do not use or trust this mirror. It is recommended to use the official registry.npmjs.org.

Suggested change

	"resolved": "https://registry.npmmirror.com/react-markdown/-/react-markdown-10.1.0.tgz",
	"resolved": "https://registry.npmjs.org/react-markdown/-/react-markdown-10.1.0.tgz",

[clousky2020]

Review feedback addressed: 1) Added expires_at to UPSERT UPDATE statement in store.ts, 2) Reverted react-markdown registry to official npmjs.org URL. Both fixes in commit 9509aa4.