SQLite ordered List and GetByChannel by created_at while NellDB reversed
document order, i.e. by session ID. Both documented "newest first", both
passed the shared suite, and neither meant recency -- so a cutover
between backends could change which session a restart resumes, and
Touch, the live path that makes a session the newest one, changed
nothing on either.
Recency is now LastActiveAt when set and CreatedAt otherwise, on both
sides, with an index matching the SQLite expression.
The conformance suite gains the case that would have caught this: three
sessions whose creation order, ID order and use order all disagree, plus
a Touch, asserted against List and GetByChannel on both backends.
Refs archie-core-8u8.2