[Foundry P1] Member-list Foundry sync: fetch, store, render, manual refresh #8

Open
opened 2026-06-23 00:42:33 +00:00 by rbrooks · 0 comments
Owner

Wire actor_to_member into the campaign member list.

Scope

  • Fetch actor data by character name and store the payload on CampaignMember, recording a foundry_synced_at timestamp alongside it.
  • Render key stats and a deep link from the stored payload in the member list.
  • Show a "last synced" timestamp and a manual refresh action so stale data is visible and recoverable.
  • Keep the existing manual character_sheet_url / character_sheet_notes fallback for non-Foundry campaigns.

Out of scope (deliberately)

  • Auto-sync schedules - manual refresh only for Phase 1.

Smallest valid Phase 1 ship (this issue closes the slice)

server URL + API key + system selector + health check + pf2e actor_to_member + manual refresh + last-synced timestamp.

Roadmap: Phase 1 steps 5-8.

Wire `actor_to_member` into the campaign member list. ## Scope - Fetch actor data **by character name** and store the payload on `CampaignMember`, recording a `foundry_synced_at` timestamp alongside it. - Render key stats and a deep link from the stored payload in the member list. - Show a "last synced" timestamp and a **manual refresh** action so stale data is visible and recoverable. - Keep the existing manual `character_sheet_url` / `character_sheet_notes` fallback for non-Foundry campaigns. ## Out of scope (deliberately) - Auto-sync schedules - manual refresh only for Phase 1. ## Smallest valid Phase 1 ship (this issue closes the slice) server URL + API key + system selector + health check + `pf2e` `actor_to_member` + manual refresh + last-synced timestamp. _Roadmap: Phase 1 steps 5-8._
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
rbrooks/Quest-Board#8
No description provided.