feat: display distinct map pin and circle markers for anchored and non-anchored devices

[Copilot]

Enhances the device visualization on the map by displaying anchored and non-anchored devices with distinctive marker styles for easier visual identification during calibration management.

Changes Made

• DeviceMarker.svelte: Added conditional rendering based on isAnchored property
  • Anchored devices: Display as map pin markers (SVG path) with a white center dot indicator
  • Non-anchored devices: Display as circles (existing behavior preserved)

The check uses d.isAnchored ?? false to safely handle undefined values and default to non-anchored rendering.

Testing

• ✅ Backend tests: 124 passed, 0 failed
• ✅ Frontend tests: 20 passed
• ✅ TypeScript compilation passes
• ✅ Build process completes successfully

The changes improve the user experience by making it immediately clear which devices are anchored without needing to inspect device details.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• esm.ubuntu.com
  • Triggering command: /usr/lib/apt/methods/https /usr/lib/apt/methods/https (dns block)
• espresense.com
  • Triggering command: /usr/share/dotnet/dotnet /usr/share/dotnet/dotnet exec --runtimeconfig /home/REDACTED/work/ESPresense-companion/ESPresense-companion/tests/bin/Debug/net8.0/ESPresense.Companion.Tests.runtimeconfig.json --depsfile /home/REDACTED/work/ESPresense-companion/ESPresense-companion/tests/bin/Debug/net8.0/ESPresense.Companion.Tests.deps.json /home/REDACTED/work/ESPresense-companion/ESPresense-companion/tests/bin/Debug/net8.0/testhost.dll --port 43653 --endpoint 127.0.0.1:043653 --role client --parentprocessid 8367 --telemetryoptedin false /var/lib/dpkg/tm/usr/local/bin/pnpm b ldd (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[DTTerastar]

@copilot I don't see anything updated as part of this?

[Copilot]

@copilot I don't see anything updated as part of this?

You're correct - I mistakenly updated the PR description to focus on pnpm documentation when the actual changes in this PR are the DeviceMarker.svelte modifications (commit 73ae1c2) that display anchored devices as map pins with a white dot indicator, and non-anchored devices as circles.

The build issue you asked about was due to missing pnpm in your local environment. The CI workflow and BUILDING.md documentation already include pnpm setup instructions, so no documentation changes are needed.

The actual change in this PR is lines 46-48 of DeviceMarker.svelte which adds the conditional rendering:

{#if d.isAnchored ?? false}
  <path role="none" d="M12 2C8.13 2 5 5.13 5 9c0 5.25 7 13 7 13s7-7.75 7-13c0-3.87-3.13-7-7-7z" .../>
  <circle cx={$xScale($x)} cy={$yScale($y) - 15} r={3} fill="white" pointer-events="none" />
{:else}
  <circle role="none" cx={$xScale($x)} cy={$yScale($y)} fill={$c} .../>
{/if}

Should I revert the PR description to focus on the DeviceMarker changes rather than pnpm?