- Shipped
- September 7, 2026 at 10:22 PM UTC
- Author
- Kamo
- Commit
- 118570e
Eleven of the fifty secrets are questions about durable data rather than about whether a member has SEEN something, so they are DERIVED and they backfill: a member who reacted to a colleague's message at the same second in March holds High Five the first time this runs. Every query was run against the live schema before it was written down, and two of them already answer TRUE for existing members. The two that count the hunt itself generate their IN-list from the catalogue rather than hard-coding it. A hand-typed list is a second place the set of secrets is defined, and the failure it produces is the worst available here: adding a fifty-first secret would leave the completion badge awardable without it, so a member would hold "found every secret" while the cabinet showed them one short. TAG_TEAM binds assigned_from_id — the member who HANDED the lead over, which is the half of the row the achievement belongs to — so the probe test's whitelist of member-binding columns gains it.