fix: Harden instance rename against interleaving and lost unwinds

2026-08-12 11:08:36 +00:00
parent f534b74066
commit cdc50b7aaf
10 changed files with 220 additions and 64 deletions
@@ -150,8 +150,8 @@ type Instance struct {
 	// rename cooldown. It is a pointer because absent means "never renamed"; a
 	// zero time.Time would read as year 1 — an inert cooldown, but only by
 	// accident. Staff renames deliberately leave it alone.
-	RenamedAt      *time.Time    `bson:"renamed_at,omitempty" json:"renamed_at,omitempty"`
-	InjectFailedAt *time.Time    `bson:"inject_failed_at,omitempty" json:"inject_failed_at,omitempty"`
+	RenamedAt      *time.Time `bson:"renamed_at,omitempty" json:"renamed_at,omitempty"`
+	InjectFailedAt *time.Time `bson:"inject_failed_at,omitempty" json:"inject_failed_at,omitempty"`
 	// NoticesSent holds the lifecycle notice keys already emailed for the
 	// CURRENT term ("expiring", "expired", "delete_7", "delete_1"). Renewal
 	// clears it, so the next term starts the sequence again. It is what stops a