SquadNote trial-participant feature stays open across Plane cycles until mobile checks and release are complete

A DEV Community article describes how a SquadNote feature ticket, SQN-30, was kept active when a weekly Plane cycle ended with mobile verification still outstanding. The author argues that marking the item Done just to close the cycle would misrepresent the unfinished checks. Plane documentation indicates unfinished work keeps its state and can move to another cycle, and a single work item can belong to both a cycle and a release module. The proposal separates development acceptance from production distribution by adding a distribution and post-release verification task alongside SQN-30. The workflow was built from existing acceptance criteria and verification records, with no Plane settings or states changed, and it was not operated over multiple weeks.