Repository navigation
Redesign how game systems and the Foundry module update: automatic, pinned, or approve-first #685
Description
AutoPinOnInstall already reads each campaign's pin mode: only 'preserve' freezes a campaign at its previous version when a new module version installs, so the default empty mode and 'promote' both leave the campaign tracking the latest installed version — the 'Auto-update (track latest installed)' label is already true for every campaign. A writer (campaigns.SetFoundryModulePinMode) and a validator (foundry_vtt.IsValidPinMode) already exist for that mode, but no route or UI control calls the writer, so no campaign can actually be put into 'preserve' mode today. What's left is a small UI control (and a route, if one doesn't already reach the setter) so an owner can choose 'preserve', or closing this issue if that option isn't wanted.
Decided (2026-09-23): option B. The label promises "track latest", so the behaviour should do that; keep "preserve" as the second, explicitly named mode.
References: keyxmakerx/Cordinator#21, Cordinator reports/chronicle/2026-05-20-c-updater-cluster.md, internal/plugins/foundry_vtt/owner_tab.templ:161
Where this came from
Cordinator/plans/BACKLOG.mdline 761 — Open bug queue > C-UPDATER-CLUSTER item 21 — operator decision needed- Checked against
mainon 2026-09-23: internal/plugins/foundry_vtt/owner_tab.templ:161 still shows 'Auto-update (track latest installed)'; pin_mode.go stores preserve/promote/pinned (Chunk 1) but service.go:35-41 says AutoPinOnInstall still follows preserve-state regardless of pin_mode (Chunk 2 held since 2026-05-20).
- Checked against
Old tracking IDs (so a search for them lands here): C-FMC-6, C-FMC-CHUNK-2, C-UPDATER-CLUSTER
Activity
keyxmakerx commentedon Sep 25, 2026
Checked against
mainon 2026-09-25 while cleaning up comments. The description above is out of date:AutoPinOnInstallalready reads the pin mode. Only"preserve"freezes a campaign at the previous version. An empty mode (the default) or"promote"does nothing, so the campaign keeps tracking the latest installed version. The "Auto-update (track latest installed)" label is therefore already true for every campaign.campaigns.SetFoundryModulePinMode(throughfoundryCampaignSettingsAdapterininternal/app/routes.go), and a validator,foundry_vtt.IsValidPinMode, but no route or control calls either. Nothing in the product can set it today.So option B has shipped on the server side. What's left is a small UI control plus a route if the operator wants "preserve" to be selectable, or closing this issue if not.
Generated by Claude Code
keyxmakerx commentedon Sep 25, 2026
Decided 2026-09-25 on the sign-off page. Redesign the whole update flow instead of adding a second dropdown to today's card. It's part of the admin redesign (#681, item A2).
The operator's requirements:
It needs a new mockup before building.
Generated by Claude Code
[-]Make 'Auto-update' pinning actually move campaigns to new versions[/-][+]Redesign how game systems and the Foundry module update: automatic, pinned, or approve-first[/+]keyxmakerx commentedon Sep 25, 2026
Signed 2026-09-25 on the sign-off page (card "ui-685", version 3). Part of the admin redesign #681, item A2.
What was approved
Build, in order: #755 (server), #756 (admin views), #757 (campaign Settings → Updates). Each ships as its own PR built to this mockup. The mockup's HTML is below so the contract outlives the sign-off page.
Signed mockup (HTML: Today, Admin · package detail, Admin · package list at scale, Campaign owner)
Generated by Claude Code