I'm parked on you

Pick an option on each card and press Done; your answer goes straight back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.

1PMS-sync canary work-order leg: Option A (fresh WO per run, cancel in finally) vs Option B (protected-fixture registry consulted by every bench sweep + drift test). Both add: seeder refuses a terminal WO.

In plain terms. Should the nightly AppFolio sync check make its own fresh test ticket each night, or should every bench cleanup skip its one saved ticket?

Fresh ticket each nightthe raiser's pick Cleanups skip its ticket I'm not sure — go find out Take it to the engineering bridge

1 other session waiting on this same answer.

Why, and what was tried

The session raising this recommends: Fresh ticket each night
No sweep can ever starve it again; option B needs five cleanup paths (and every future one) to remember a registry.
Tried first, unsuccessfully: Traced 14 red nights: fixture WOs 1489 and 1715 were both cancelled by bench sweeps that don't know the fixture exists; two prior fixes and two re-seeds didn't hold. Re-seeding now is pointless since the next Morpheus night sweeps any open bench ticket. Design doc: PR #21738.

337f0971 (adopted from 6be5d26d) is parked on this. 1 other session waiting on this same answer.

Asked by more than one session. Your answer above goes back to all of them.

337f0971 asked it this way:
pms-sync-canary work-order leg: Option A (create a fresh WO per armed run on the Test-Sync unit, round-trip priority, cancel in finally) or Option B (benchProtectedWorkOrderIds registry consulted by every bench cancel/delete sweep + drift test)? Both add: seeder refuses a terminal ticket. Design: docs/planning/alerts/automation_run_failure-co.propflow.pms-sync-canary-daily.md

Pick an option above, then press Done.