Throwing in the towel. My solution works for the test input.
I get this message for the answer: "Curiously, it's the right answer for someone else; you might be logged in to the wrong account or just unlucky. In any case, you need to be using your puzzle input."
Day 3 of #adventofcode is a bust. I found a fatal issue in Teliva: if running the app ever shows an error, I get thrown back to the editor. So I can't see any prints. So my usual strategy of debug by print doesn't work.
So I need to rethink how Teliva displays run-time errors. Now I hazily remember Turbo Pascal having a "press any key to continue" prompt on run-time error.
I did finish after all. An hour into the day, after doing other stuff (going over review jam feedback with Teliva, creating a list of bugs), it occurred to me to get "press any key" by adding just one line of code to Teliva and recompiling. That got me debugging again.
But this video is going to be useless. Across two sessions, I have an hour of me umming and aahing, muttering and swearing.