have updated the extension (v1.5) to send the counts back to the Background Script.

How to check now:

Load extension_v1.5.zip.
Open the same Extension Background Console you showed me in the screenshot (where it said "Starting KDP Extraction Sequence").
When the extraction runs, you will now see a persistent report in that console:
text
[DEBUG REPORT] ------------------------------------------------
[DEBUG REPORT] Books Visible BEFORE row change: 10
[DEBUG REPORT] Books Visible AFTER row change: 50
[DEBUG REPORT] ------------------------------------------------
This log will stay visible even after the tab closes.

I have updated the extension to Version 1.4.

New Debug Features:

Book Counting: The extension now counts the number of books (visible rows) BEFORE and AFTER the "maximize rows" action.
Console Logs: You will see these explicitly in the Inspect Element -> Console tab:
[DEBUG] Books found BEFORE change: 10
[DEBUG] Changing rows from 10 to 50
[DEBUG] Books found AFTER change: 50

The Fix:

Dual-Mode Content Script: I refactored the script to detect if it's running on "Bookshelf" or "Royalties".
Bookshelf Injection: I updated the background process to inject this script into the Bookshelf page as well.
Route Logic:
On Bookshelf: It now looks for the dropdown, sets it to Max, waits for reload, and then extracts.
On Royalties: It continues to do the existing expansion logic.

Smart Data Capture: The extension now automatically sets the "Rows per Page" dropdown to the maximum available value before extracting data. This ensures more books and royalty details are captured in a single pass, improving report accuracy and reducing manual steps.
Performance: Improved logic for handling table expansions and data synchronization.