Everything I could decide myself is decided. What's left needs
you. Each one has a recommendation from Fable — if you agree, pick it and
press Done. "I'm not sure" is a real answer and becomes work for me.
You don't need to open the session — pressing Done sends your answer back and it picks up.
13 questions on this
0 of 3 answered
Tried first, unsuccessfully: Not Fable-shaped: all three are authority/commitment calls — a production behaviour change (dropped lease attachments), merge authority on a PR that grew a real blocker, and a machine config change. fable-decide routes this class to a human. The engineering behind each is finished and measured.
1PR #6013 upgrades every build to Node 24. One service — the renewal worker — reads PDFs using a library called pdf-parse, and that library is broken on Node 24.18 and up. The Dockerfile line says 'node:24-slim' with no exact version, so it will pick up a broken one. What happens if it ships as-is: when a signed lease PDF comes in, the text extraction returns nothing, the code treats that as 'reject', and the lease attachment is silently dropped with only a warning in the logs. You escalated this five days ago and nothing has landed since.
In plain terms. Moving the renewal worker to newer Node breaks PDF reading. Which way out?
Fable recommends: Pin it to node:24.17-slim — under the break, ships today, revisit later It is one line, it keeps the PR's guard happy (the guard accepts a minor pin), and it unblocks everything else today. The pdf-parse upgrade is real work that should not hold up the CI fix that 13 days of dead Dependabot PRs are waiting on.
2#5784 (grading corpus gate) and #6013 (Node 24 CI fix) are both mine to finish now. #5784 was never actually broken — its tests were cancelled 11 days ago and nobody re-ran them. #6013 needs the PDF answer above first. You said 'you merge' earlier, so I want to confirm that still stands now that #6013 turned out to have a real blocker in it.
In plain terms. Once the tests pass, should I merge these two myself?
Fable recommends: Merge #5784 only; bring #6013 back to me when it is green #5784 is a clean case with nothing left to decide. #6013 now carries a real production behaviour change (dropped lease attachments) that you flagged yourself, so it deserves your eyes on the final shape even if you already approved the direction.
3The repo runs a check before every push that installs dependencies. That check uses whatever Node this Mac defaults to, which is currently version 20 — too old for the new setup. So pushes to propflowai fail from here unless they are forced through. I got today's push through, but the next one hits the same wall.
In plain terms. This Mac can't push to the main repo right now. Fix it?
Fable recommends: Set this Mac's default Node to 24 The repo already declares it needs Node 24 and up, so the Mac is simply out of date with what the project asks for. nvm is already installed and already has 24.