fix(ag-ui): advanced markers ignore clicks — set gmpClickable

[blove]

Marker clicks on the App-mode map did nothing (no info window / focus / Remove). Regression from the AdvancedMarkerElement migration: legacy Marker is clickable by default, AdvancedMarkerElement is not — without gmpClickable: true it never fires click/gmp-click, so (mapClick) stays silent. The "use gmp-click" console hint was the symptom.

Fix: pass { gmpClickable: true } via the marker [options] (+7 lines).

Verified: live in Chrome (markers report gmpClickable=true, click opens the info window with Remove), lint 0 errors, unit ✓, build ✓ against post-#747 main.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
threadplane	Ready	Preview, Comment	Jul 6, 2026 3:11pm

[github-actions]

Automated approval: this PR received an intelligent (AI) code review. See the review comments on this PR.

[github-actions]

Claude finished @blove's task in 37s —— View job

---

Code Review

• Gather context
• Read changed file and diff
• Post review findings

---

Verdict: LGTM

The fix is correct and minimal. AdvancedMarkerElement silently drops all pointer events unless gmpClickable: true is set — the legacy Marker was clickable by default, so this is an easy-to-miss migration gotcha. Setting it once on a shared readonly options object is the right approach.

A few quick observations:

Correctness — The root cause diagnosis is accurate. Without gmpClickable, the underlying element never fires click/gmp-click, so @angular/google-maps's (mapClick) output stays permanently silent regardless of what the template binds.

No binding conflicts — advancedMarkerOptions only carries gmpClickable: true; it doesn't re-declare position, content, or title, so there's no risk of the [options] merge shadowing the per-marker inputs.

Shared object is safe — All markers sharing the same options reference is correct here since gmpClickable is uniform and the object is never mutated after construction.

Comment quality — The explanatory comment at the property declaration is worth keeping; this is a non-obvious platform behaviour that would trip up anyone unfamiliar with the AdvancedMarkerElement migration story.

No issues found.