Why would Dreamweaver not update all files that contain a particular library item?

I'm using Dreamweaver along with Gitkraken. If I switch branches with, say, the library item "mainmenu145.lbi" open (I'm working on a refactoring while maintaining a current website), and that Lib item changes with that switch, when I switch back to Dreamweaver, it asks if I want to update the files that use that library item. I say yes, and here's what DW shows me in the progress window:

updated comexp:routes:409:409_red4.html

    item Library:mainmenu145.lbi

    item Library:footer3_145.lbi

updated comexp:routes:409:409_red5.html

    item Library:mainmenu145.lbi

    item Library:footer3_145.lbi

updated index_145_menu.html

    item Library:mainmenu145.lbi

    item Library:footer3_145.lbi

updated index_145_menu3.html

    item Library:footer3_145.lbi

updated comexp:routes:409:409_red3.html

    item Library:topdrawer_145.lbi

Done.

  files examined: 9

  files updated: 5

  files which could not be updated: 0

total time: (0:00:05)

I'm not sure what to make of this. First of all, I'm not sure why I'm dealing with "footer3_145.lbi" at all, as it isn't open, and hasn't changed, at least to DW's knowledge. If I have no library items open during a branch switch, I'm not shown the lib item dialog at all, even if I'd made a change to a lib item... historically Dreamweaver simply sees the changed parent html files as well as the changed lib item file and they change in the background like any other unopened changed file – no need to update library items if that library item isn't open. But here, for some reason, footer3 keeps showing up as though it's been updated, even though it's not open.

Secondly, why are 9 files examined, but only 5 updated, yet it tells me that there were 0 that could not be updated? Seems to me the math is that 4 items couldn't be updated (though I would have no idea why that would be the case). I thought it might be a problem with my html structure, but it isn't. Even if it was, presumably I would at least be shown that certain files could not be updated.

This behavior started only recently, but I have no clue what could have triggered it. Anybody have any ideas what's going on here?