mirror of
https://github.com/tiennm99/tiennm99bot.git
synced 2026-10-11 03:13:46 +00:00
tiennm99
2d42f40ca7
The previous commit's regression test never reached the guard it was named for. It broke the pack record with dropPackRecord, which now also clears the confirmation, so the callback returned at the pending.Get miss long before the allowlist. The test passed with the entire guard reverted - shipping the fix with its own detector inoperative, which is the defect that let five earlier rounds report a false clean. Replace it with a table that leaves the confirmation intact and breaks the record three ways, one per disjunct: record gone, record unconfirmed, record moved on. Reverting the guard now fails two cases; each disjunct was mutated individually. The !found disjunct is an equivalent mutant: ownsSet already returns false for a zero-value record's empty Name, so no test can kill it. Kept and commented, because that redundancy is an accident of ownsSet's empty-string guard rather than something this check should rely on. Also revert the set-name half of the previous commit's resume change. Carrying the retyped title is right; re-deriving Pack.Name was not. The name comes from the bot username, which can change at BotFather, and the stored one identifies the set the interrupted attempt may already have created - refreshing it orphaned that set and aimed later commands at a different name, contradicting ownsSet's own documented rule. Pinned.