feat: file a batch unattended, parking what needs a decision

intake batch files every ready album in one pass. An album that needs a person is parked -- recorded with the reason and left exactly where it is -- and the run moves on. A genuine failure is reported and also not fatal, because the next album has nothing to do with it; the command exits non-zero at the end if anything failed, so a script can tell "finished" from "finished with problems".

This is the biggest practical blocker on a large collection: one mistagged mp3 in a directory of two hundred downloads used to stop everything behind it, and resume stopped at the first ready album whatever state it was in.

Parking is a journal phase (needs_attention), not a line in a log, so the album stays findable: library verify and the journal screen show it with its reason, and running the batch again parks it again rather than losing it.

In the interface, b on the album list runs the same batch with the progress on the working screen and a summary that names every album it parked, rather than only counting them. The album list marks parked albums in place of their status line, and n jumps the cursor to the next one, which is how somebody works through the backlog a batch leaves behind.

Closes 1c36deb