Automate release workflow and update documentation for 0.6.5

[beNative]

Summary

• bump DocForge to v0.6.5 and document the automated release update in the version log
• refresh the README and manuals so the release preparation checklist reflects the new tag-driven workflow
• add a GitHub Actions release pipeline that builds installers for all supported platforms when a version tag is pushed

Testing

• npm test

---

https://chatgpt.com/codex/tasks/task_e_68f35fee97748332b997d423485cc124

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Prevent Windows artifacts from overwriting each other

This workflow builds separate Windows x64 and ia32 packages but the upload loop sends every file in release/ to the same GitHub release using gh release upload … --clobber. Electron Builder emits identically named assets for those two architectures (DocForge Setup <version>.exe, latest.yml, etc.), so the second Windows job will overwrite the first and its metadata, leaving only one installer and a mismatched latest.yml for auto‑updates. Give each architecture a distinct filename or upload path before calling gh release upload so both Windows builds survive the matrix run.

Useful? React with 👍 / 👎.