Support (Secondary) Locations via collection references in Ashby Plugin

[niekert]

Description

• Add new Locations data source that extracts unique locations from jobs board
• Add location reference and secondary locations fields to jobs data source
• Allow data source selection in setup UI (Jobs vs Locations)
• Add CLAUDE.md for repository documentation

Testing

• Setup Locations Collection
  • Open Framer and create a new CMS collection
  • Launch the Ashby plugin
  • Enter your Job Board Name (see slack)
  • Select "Locations" from the Collection dropdown
  • Click "Next"
  • Map the desired fields:
  • Click "Sync" and verify locations are imported
  • Confirm unique locations are extracted from both primary and secondary job locations
• Setup Jobs Collection with Location References
  • Create another new CMS collection
  • Launch the Ashby plugin again
  • Enter the same Job Board Name
  • Select "Jobs" from the Collection dropdown
  • Click "Next"
  • Map standard job fields as needed
  • Map location reference fields:
    • Location Reference → should show the Locations collection as target
    • Secondary Locations → should show the Locations collection as target (multi-reference)
  • Click "Sync"
• Verify Data Integrity
  • Open a synced Job item
  • Confirm "Location Reference" links to the correct Location item
  • Confirm "Secondary Locations" contains all additional locations for that job
  • Cross-reference with the Ashby job board to verify accuracy
  • Check that location slugs match between Jobs references and Locations collection IDs

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

Comment @cursor review or bugbot run to trigger another review on this PR

[triozer]

LGTM!