Merge pull request #58 from beNative/codex/prepare-for-github-release-including-version-update

chore: prepare 0.6.2 release

Author: beNative

README.md

@@ -33,14 +33,16 @@ DocForge is a desktop application designed to streamline the process of creating
 4.  **Create:** Start creating, organizing, and refining your documents!
 
 For detailed instructions on usage and features, please refer to the [Functional Manual](./FUNCTIONAL_MANUAL.md).
+To review the history of changes, see the [Version Log](./VERSION_LOG.md).
 
 ## Release Preparation
 
 To create a new public build of DocForge:
 
 1. Update the version in `package.json` and regenerate the lockfile with `npm version <new-version> --no-git-tag-version`.
 2. Review the Markdown documentation (README, manuals, and version log) so the release notes accurately reflect recent changes.
-3. Run `npm run publish` to build the application and publish the artifacts to the configured GitHub release target via Electron Builder.
+3. Sync the documentation copies under `docs/` (README, manuals, version log) with any updates made at the project root.
+4. Run `npm run publish` to build the application and publish the artifacts to the configured GitHub release target via Electron Builder.
 
 ## Application Icon Workflow
 

VERSION_LOG.md

@@ -1,5 +1,22 @@
 # Version Log
 
+## v0.6.2 - The Documentation Polish Update
+
+This maintenance release focuses on keeping the documentation set in sync with the
+project's release workflow so the publishing checklist is easy to follow.
+
+### 🛠 Improvements
+
+-   Synced the release preparation guidance between the project README and the
+    documentation bundle to avoid diverging instructions.
+-   Linked the README to the version history so maintainers can quickly review
+    prior changes when drafting release notes.
+
+### 🐛 Fixes
+
+-   Corrected outdated documentation references that omitted the release
+    preparation steps from the published docs bundle.
+
 ## v0.6.1 - The Release Prep Update
 
 This maintenance release focuses on preparing DocForge for distribution by polishing the release workflow and tidying up the documentation set.

docs/README.md

@@ -32,4 +32,22 @@ DocForge is a desktop application designed to streamline the process of creating
 3.  **Configure:** Launch DocForge, open the Settings view, and select your detected LLM service and a model to use for refinement tasks.
 4.  **Create:** Start creating, organizing, and refining your documents!
 
-For detailed instructions on usage and features, please refer to the [Functional Manual](./FUNCTIONAL_MANUAL.md).
+For detailed instructions on usage and features, please refer to the [Functional Manual](./FUNCTIONAL_MANUAL.md).
+To review the history of changes, see the [Version Log](./VERSION_LOG.md).
+
+## Release Preparation
+
+To create a new public build of DocForge:
+
+1. Update the version in `package.json` and regenerate the lockfile with `npm version <new-version> --no-git-tag-version`.
+2. Review the Markdown documentation (README, manuals, and version log) so the release notes accurately reflect recent changes.
+3. Sync the documentation copies under `docs/` (README, manuals, version log) with any updates made at the project root.
+4. Run `npm run publish` to build the application and publish the artifacts to the configured GitHub release target via Electron Builder.
+
+## Application Icon Workflow
+
+- The canonical artwork lives at `assets/icon.svg`. Keep this SVG under version control to simplify brand updates.
+- `npm run build` (and any script that calls it) automatically validates the SVG and regenerates `icon.icns`, `icon.ico`, and a high-resolution `icon.png` via the `scripts/prepare-icons.mjs` helper.
+- If the SVG is missing or invalid the script logs a warning and leaves existing binary icons untouched, allowing packaging to proceed with the previously generated assets.
+- Run `npm run prepare:icons` to regenerate the platform-specific icons on demand without rebuilding the JavaScript bundles.
+

docs/VERSION_LOG.md

@@ -1,5 +1,22 @@
 # Version Log
 
+## v0.6.2 - The Documentation Polish Update
+
+This maintenance release focuses on keeping the documentation set in sync with the
+project's release workflow so the publishing checklist is easy to follow.
+
+### 🛠 Improvements
+
+-   Synced the release preparation guidance between the project README and the
+    documentation bundle to avoid diverging instructions.
+-   Linked the README to the version history so maintainers can quickly review
+    prior changes when drafting release notes.
+
+### 🐛 Fixes
+
+-   Corrected outdated documentation references that omitted the release
+    preparation steps from the published docs bundle.
+
 ## v0.6.1 - The Release Prep Update
 
 This maintenance release focuses on preparing DocForge for distribution by polishing the release workflow and tidying up the documentation set.

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "docforge",
-  "version": "0.6.1",
+  "version": "0.6.2",
   "description": "An application to manage and refine documents.",
   "main": "dist/main.js",
   "scripts": {