[Twest2]

Cleans up the docs people actually read so they're easier to follow. No behavior changes. The technical details taken out of user docs move to ARCHITECTURE.md, so maintainers and AI agents still have them.

What changed

Fixes

• README: the two "Share a guide" links pointed at a heading that doesn't exist (#share-a-guide-with-a-link). They now go to #share-a-guide-with-a-web-link.
• Privacy and Security summaries only mentioned Google Drive and GitHub. They now list every optional online feature, including OneDrive, Dropbox, Nextcloud, Confluence and Wiki.js. Security also lists the Microsoft Store as a release channel.
• Google Drive's "Settings that sync" (and the privacy policy) now include the interface language, which core/shared-settings.js syncs.

Less clutter

• README: removed a sharing bullet that repeated the privacy check. The Install section now mentions the Store once, plus the badge.
• Getting Started: replacing or retaking a screenshot gets its own short section instead of a ten-line bullet. The branding paragraph that listed every option now points to BRANDING.md. The Export, language, linked-guide and data folder notes are shorter.
• AI agents: setup steps now come first. The lopsided can/can't table is now two plain lists. The undo section no longer covers internal details such as update_step and pruning.
• Ollama AI: five overlapping bullets reduced to four short ones.
• Wiki.js / Branding: shorter two-step-verification, annotation-color and agent notes.
• Microsoft Store / Windows installer: the %APPDATA% move is explained in a few lines. The cleanup steps for the old folder are in a collapsed section.
• Chocolatey: shorter Update and ".exe" sections. Silent-install switches move under For IT admins. The intro paragraph is unchanged.
• Contributing: CI job internals move to ARCHITECTURE.md#tests-and-ci.

How to stop a recording

• Getting Started has a new Stop recording section. The old wording ("the red StepForge icon in the system tray") was easy to miss: the icon is a plain red dot, not the StepForge logo, "system tray" isn't a term most people know, and Windows often hides the icon behind the ^ arrow.
• Windows: the red dot beside the clock, how to find it behind ^, and what clicking and right-clicking do. As a fallback, opening StepForge from the Start menu also pauses recording and brings it back.
• GNOME: ● StepForge REC → Stop recording, or the Stop recording button in the StepForge window.
• It also notes that the click that stops recording is never a step, though clicks made while looking for the dot can be, and that Ctrl+Shift+2 pauses without bringing StepForge back.
• The README quick start and the Linux guide now use the same wording, and Troubleshooting links to the section.

One page for every sync service

• Google Drive came first, so GOOGLE_DRIVE.md was the page that explained how sync works. OneDrive, Dropbox and Nextcloud had a sign-in page that linked back to it.
• CLOUD_ACCOUNTS.md is now Sync your guides between computers. It covers how sync works once for every service, then has a short section per service: Google Drive, OneDrive and Dropbox, and Nextcloud/WebDAV. The merge rules for synced settings are in plain language instead of spec detail.
• GOOGLE_DRIVE.md is now a short pointer to the new page, so outside links keep working. Links inside the repo point to the new page.
• Fixed: the docs and privacy policy said deleting a guide only deletes it on this computer. Since deletion sync (2026-09-21), a deleted guide moves to the Trash on your other computers, and one recovery copy is kept under Recently deleted.
• Documented More → Guide information… → Include this guide in cloud sync, which keeps one guide on this computer only. Labels now match the app: Auto-sync, Guides in Drive, Replace OneDrive with this computer.

Moved to ARCHITECTURE.md: a new AI Agents (MCP) section (snapshot rules, blur-bypass protection, concurrent edits, brand tools), the settings-sync error rule, the one-hour grace period before unused parts are cleaned up, linked-guide lock behavior, and the CI layout.

Not changed

• File names and the headings the app links to (BRANDING.md#advanced-css, etc.).
• The download-badge block (README: Microsoft Store downloads badge from Partner Center analytics #192) and the issue/PR templates (Update the issue and pull request templates #193), to avoid conflicts.
• Maintainer release guides, GITHUB_PAGES.md, CONFLUENCE.md, the Linux guides and the BRANDING CSS reference tables. These were already clear or are reference material.

Checks

• Every relative link and #anchor in the repo's Markdown resolves. Before this PR, the two README links above were broken.
• license, packaging-linux and download-badges unit tests and test_repo_structure.sh pass.