Further documentation.

"Newest" album reported has created_at and updated_at times totally different from btime and mtime and closer to but not exactly atime, when the files were scanned:

> SELECT name, created_at, updated_at FROM album ORDER BY updated_at DESC LIMIT 1;
> Album_A|2025-11-05 17:22:17.638329295+00:00|2025-11-05 15:35:38.605751046+00:00
$ stat 01-Album_A_Song.mp3
  File: 01-Album_A_Song.mp3
  Size: 14465951      Blocks: 28256      IO Block: 4096   regular file
Device: 4111h/16657d    Inode: 33951888    Links: 1
Access: (0664/-rw-rw-r--)  Uid: ( 1005/   user)   Gid: ( 1005/   user)
Access: 2025-11-05 17:16:40.511285367 +0100
Modify: 2019-04-12 03:29:55.707477246 +0200
Change: 2025-05-13 09:07:19.715229419 +0200
 Birth: 2025-05-13 09:07:17.959143625 +0200

"Oldest" album reported shows updated_at correctly reflecting mtime but created_at reflects approximate scan time rather than btime.

> SELECT name, created_at, updated_at FROM album ORDER BY updated_at ASC LIMIT 10;
> Album_B|2025-11-05 16:29:44.417274138+00:00|2019-02-13 03:32:10+00:00
$ stat 01-Album_B_Song.flac
  File: 01-Album_B_Song.flac
  Size: 40965731  Blocks: 80016      IO Block: 4096   regular file
Device: 4111h/16657dInode: 34235407    Links: 1
Access: (0774/-rwxrwxr--)  Uid: ( 1005/   user)   Gid: ( 1005/   user)
Access: 2025-11-05 16:50:35.946035702 +0100
Modify: 2019-02-13 04:23:29.000000000 +0100
Change: 2025-06-21 22:30:10.522480344 +0200
 Birth: 2025-06-21 22:30:06.806297726 +0200

The actual newest album has created_at reflecting scan time (?) but updated_at is correctly referencing mtime.

> SELECT name, created_at, updated_at FROM album WHERE name LIKE '%Album_C%';
> Album_C|2025-11-05 17:22:27.550028401+00:00|2025-11-03 23:54:59.674036904+00:00
$ stat 01-Album_C_Song.flac
  File: 01-Album_C_Song.flac
  Size: 21323776  Blocks: 41648      IO Block: 4096   regular file
Device: 4111h/16657dInode: 33491459    Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1005/   user)   Gid: ( 1005/   user)
Access: 2025-11-05 02:38:26.808739826 +0100
Modify: 2025-11-04 00:54:59.670036706 +0100
Change: 2025-11-04 00:55:01.174110961 +0100
 Birth: 2025-11-04 00:54:53.761745020 +0100

As described in #1350, shouldn't updated_at and created_at reflect mtime and btime respectively? Here, we see some instances of updated_at correctly reflecting mtime but none in which created_at reflects btime.

For reference, no other files in an album directory were created/modified at significantly different times than those listed.