Long-Lived API Token for Programmatic Puzzle Connections

Currently, connecting to Puzzle programmatically requires an interactive OAuth flow that needs to be re-authorized periodically — which works fine for individual use but isn’t practical for hosted apps connecting on a user’s behalf.

A long-lived token (either a static API key or an OAuth refresh token scoped to a single workspace) would unlock use cases that public Shared Views and embeds can’t cover, such as keeping boards private behind a login, letting an app list and select workspaces and sections dynamically, and writing back to a board as plans change — all without requiring the user to re-authenticate each time.