OmaSession 0.6.0

• Each restore keeps its own log in ~/.local/state/omasession/restores/ instead of overwriting last-restore.log, so a manual restore no longer erases what the login restore did. The log records what started the restore, the session it replayed (a copy is kept next to it), the last save, Chrome's profile state before the restore touched it, and the folder and program saved for each terminal it opened. A login restore also records how the previous boot ended. The newest 20 are kept, and last-restore.log is now a copy of the latest one.
• omasession report [dir] gathers the latest restore log, its session, the state files and the journal lines from this boot and the previous one into a single folder.
• The panel's Chrome and Ghostty cards moved to an Apps tab next to Windows, Layout and Saved, so the panel is shorter and the tabs sit right under the summary.
• A new Log tab lists the kept restores with how many windows each one placed and the lines worth reading first. When the latest restore had problems, the tab gets a dot and the header says so. From there you can open the full log or report a problem, which gathers the report and opens a GitHub issue with the outcome filled in for you to review and send.
• omasession restores [--json] lists the kept restores. Each restore also writes a short result.json next to its log. omasession report takes --restore <name> to pick one and --issue to prepare the bug report.
• omasession help lists every command again. uninstall and config had been cut off.

This release is tagged at commit 803d9980947dde0cf23953b35a0b4ac4485ab563.