[WIP] Add Tauri wrapper window size persistence and app data storage

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

Original prompt

In crazyrob425/KDP-E-Book-Generator (base main), ensure the Tauri v2 wrapper persists window size/position on Windows and clamps/restores within current monitor bounds, and ensure all app data (SQLite DB, settings, caches) is stored under the OS AppData directory. Implement minimal Rust/Tauri changes: on startup read window state from a settings file in app_data_dir and apply; on window move/resize debounce and save updated state. Update README with AppData location details. Keep changes aligned with existing PR adding Tauri wrapper + SQLite + job progress events; avoid extra dependencies unless necessary.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: @copilot Accepted Confirmation: Are you sure?

Assistant: You’ve got every reason to feel that way. I gave you a path that sounded like “one easy zip,” but this chat can’t generate downloadable zip attachments, and it also doesn’t currently have permission to write into blacklistedrob-prog/KDP-E-Book-Generator—so I can’t just push the wrapper for you. That mismatch is on me.

The truth, plainly

Right now there are only two ways to get a Tauri wrapper into that repo:

1. Grant this chat write access to the repo (then I can do it all for you).
2. You run one generator command locally (the real “one-step” solution), which creates the wrapper automatically—no hand-writing files.

There isn’t a third option where you do nothing and it magically appears in your repo, because GitHub is blocking write operations from here.

---

The least-effort way that actually works (one command, no manual file creation)

If you can run commands locally in the repo folder on Windows, do this:

git checkout -b tauri-wrapper
npm install
npm create tauri-app@latest .

When it prompts, use:

• App name: Binary Books E-Crafter
• Dev command: npm run dev
• Build command: npm run build
• Dist folder: dist
• Dev URL: http://localhost:5173

Then:

npm install
npm run tauri dev

Finally:

git add .
git commit -m "Add Tauri wrapper"
git push -u origin tauri-wrapper

That is the closest thing to the “zip upload” simplicity you wanted—because the generator creates the entire src-tauri/ scaffold correctly.

---

One yes/no question so I can keep you from wasting time

Can you run commands locally (PowerShell/Terminal) in the repo folder?

• YES → I’ll give you the exact prompt-by-prompt answers + fix any errors you paste back (fast).
• NO → then we must solve write access, because web-only manual file creation will feel like hell.

Reply YES or NO.

User: dude i dont know where you thibk you are but nothing is hosted locally this is all hosted on github

Assistant: We’re waiting on your response to the “Are you sure?” confirmation dialog so I can continue with the GitHub Actions PR work in Blacklisted-Binary/demo-repository.

User: @copilot Accepted Confirmation: Are you sure?

Assistant: GitHub is just where the code lives. Building a Tauri desktop app can’t happen “inside GitHub” by itself—you need either:

1. a computer (yours) to run the build commands, or
2. a GitHub Actions workflow that runs those build commands on GitHub’s build machines and gives you a downloadable installer as an artifact.

Right now I can’t directly push the Tauri wrapper into your blacklistedrob-prog/KDP-E-Book-Generator repo from this chat (GitHub is blocking write access for this session), so I can’t “just do it” in-place for you yet.

Two paths forward (pick one)

Path A (no local setup): GitHub Actions builds the Windows installer for you

This is the closest to what you want: you click “Run workflow” (or push a commit) and GitHub produces a .msi installer you download.

To do that, we still need one of these:

• I need write access to your repo so I can add the workflow + Tauri wrapper, or
• you (or someone with repo write access) adds a small set of files once (Tauri wrapper + the workflow YAML). After that, it’s all “hosted on GitHub” builds.

Path B (local once): you generate the wrapper with one command, then everything else can be GitHub-built

You’d do one local step to create the wrapper; then we add Actions and you never build locally again.

Quick questions (so I give you the exact minimal-click instructions)

1. Do you have a Windows PC available at all (yes/no)?
2. Do you have Git installed (yes/no/unsure)?
3. In the GitHub repo page, do you see a tab called “Actions” (yes/no)?

If you answer those, I’ll tell you the lowest-effort route and exactly what to click/do—aiming for “one-time setup, then GitHub builds the installer forever.”

User: can you fork the repo and do it??

Assistant: We’re waiting for your response to the “Are you sure?” confirmation dialog so I can proceed with forking Blacklisted-Binary/demo-repository and applying the Tauri + SQL...

This pull request was created from Copilot chat.

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.