Release ForgeFlow 0.8.1

Add advanced Git and deployment workflows, secure backups and auditing, live Gitea integration, desktop notifications, connection validation, and the premium responsive UX refresh.

docs/ACCEPTANCE.md

@@ -0,0 +1,20 @@
+# End-to-end acceptance
+
+ForgeFlow 0.8 includes a read-only acceptance harness for the real Local ->
+Gitea -> Server chain. It never deploys unless an execution flag is supplied.
+
+Set `FORGEFLOW_GITEA_URL`, `FORGEFLOW_GITEA_TOKEN`, `FORGEFLOW_REPOSITORY`
+(`owner/repository`), `FORGEFLOW_LOCAL_PATH`, `FORGEFLOW_BRANCH`,
+`FORGEFLOW_STATUS_URL` and `FORGEFLOW_HEALTH_URL` locally. Optional variables
+are `FORGEFLOW_WORKFLOW`, `FORGEFLOW_ROLLBACK_WORKFLOW` and
+`FORGEFLOW_ENVIRONMENT`. Never commit the token.
+
+```powershell
+npm run acceptance
+npm run acceptance -- --execute-deployment
+npm run acceptance -- --execute-rollback
+```
+
+The first command is read-only. The mutation flags require every read-only
+check to pass, dispatch a controlled exact-SHA workflow with a unique request
+ID, and wait for matching status plus a successful health endpoint.

docs/ARCHITECTURE.md

@@ -14,7 +14,7 @@
 | Electron main process                              |
 |                                                     |
 | IPC validation + trusted sender checks             |
-| ConfigStore -------- schema 5 + protected Gitea/SSH secrets    |
+| ConfigStore -------- schema 8 + protected Gitea/SSH secrets    |
 | GitService ----------- Git through execFile args   |
 | GiteaService --------- repositories + Actions API  |
 | RepositoryService ---- discovery + aggregation     |
@@ -69,7 +69,7 @@ per-environment lock. The runner receives no free-form command from ForgeFlow.
 ## Local state
 
 `forgeflow-config.json` lives below Electron's platform-specific user-data path
-and is written atomically. Schema version 3 contains:
+and is written atomically. Schema version 8 contains:
 
 - Gitea connection metadata and an OS-encrypted token blob where available;
 - workspace roots and explicit repository mappings;

docs/RELEASE_NOTES_0.7.0.md

@@ -0,0 +1,47 @@
+# ForgeFlow 0.7.0
+
+## Existing deployment adoption
+
+ForgeFlow can now import an existing Unraid deployment directly from the server. The server is treated as the source of truth instead of relying on guessed defaults.
+
+The discovery pass reads:
+
+- the server-side Git checkout, origin, branch and live commit;
+- the actual Compose file and normalized `docker compose config --format json` output;
+- running and stopped containers through `docker inspect`;
+- every detected port mapping, mount, network and environment-variable name;
+- Compose project and service labels;
+- image, restart policy and healthcheck metadata;
+- the matching Unraid DockerMan XML template, including WebUI, icon and shell metadata.
+
+The primary values are imported into the deployment form. The complete multi-service and multi-port runtime description is retained as detected metadata. Imported values remain editable as explicit user overrides.
+
+ForgeFlow no longer invents a host port, container port, service name, WebUI or icon when the server does not report one.
+
+## One-click troubleshooter
+
+Diagnostics now contains a general troubleshooter that scans all linked repositories and SSH/Unraid deployment profiles.
+
+Safe one-click repairs cover:
+
+- interrupted rebase, merge, cherry-pick and revert operations;
+- stale Git lock files;
+- clean fast-forward synchronization;
+- unpublished local commits;
+- refresh and recalculation of repository truth.
+
+Diverged branches are treated as an explicit higher-impact repair. ForgeFlow creates a safety branch before resetting to the upstream version and never includes that action in the automatic safe-repair batch.
+
+The troubleshooter also reports non-automatic issues such as tracked server-side changes, missing deployment folders, SSH inspection failures and missing Docker context exclusions.
+
+## Reliability fixes
+
+- Unraid DockerMan WebUI templates such as `http://[IP]:[PORT:1223]/` are now accepted and preserved.
+- Configuration writes are serialized so an older concurrent save cannot overwrite a newer snapshot.
+- A malformed configuration file is preserved as a timestamped `.corrupt-*` file and replaced with safe defaults instead of making ForgeFlow unstartable.
+- Source verification now handles Windows CRLF manifests correctly.
+- Existing deployment metadata stores field provenance, detection time and server-source-of-truth status.
+
+## Validation
+
+The release includes real Git integration coverage for aborting an interrupted merge and server-discovery mapping coverage for Compose, Docker inspect and DockerMan metadata.

docs/RELEASE_NOTES_0.8.0.md

@@ -0,0 +1,10 @@
+# ForgeFlow 0.8.0
+
+- Select and stage individual diff hunks without staging the remainder.
+- Guide interrupted merge, rebase, cherry-pick and revert resolution.
+- Read Gitea branch protection and create pull requests.
+- Open configurable editors and terminals without a shell.
+- Enforce freezes, maintenance windows, release notes and reasoned overrides.
+- Export append-only audits and credential-free encrypted configuration backups.
+- Provide native notifications, tray, close-to-tray and start-at-login.
+- Run guarded read-only, deployment and rollback acceptance checks.

docs/RELEASE_NOTES_0.8.1.md

@@ -0,0 +1,13 @@
+# ForgeFlow 0.8.1
+
+ForgeFlow 0.8.1 is a premium UX and connection-assurance release.
+
+## Highlights
+
+- A more deliberate desktop design system with refined hierarchy, depth, typography, focus states and responsive density.
+- Repository settings now show live open Gitea pull requests and link directly to them.
+- `npm run connections:check` validates the installed DPAPI-protected token against the Gitea user, ForgeFlow repository and Actions APIs without printing credentials.
+- Reduced-motion preferences are respected throughout the interface.
+- Windows packaging and compact-window behavior are revalidated after the visual redesign.
+
+The existing token and SSH private key remain local and are never copied into logs, backups or release artifacts.

docs/ROADMAP.md

@@ -1,5 +1,16 @@
 # ForgeFlow roadmap
 
+## Delivered in v0.8
+
+- partial-hunk staging with staged-only commits;
+- guided conflict resolution and safe continue/abort controls;
+- Gitea branch-protection awareness and pull-request creation;
+- configurable editor/terminal integration;
+- deployment freezes, maintenance windows, release notes and overrides;
+- append-only audit export and encrypted credential-free configuration backup;
+- native notifications, tray, close-to-tray and start-at-login;
+- guarded real-environment deploy/rollback acceptance harness.
+
 ## Delivered through v0.4
 
 - coherent Local -> Gitea -> Server desktop model;

docs/TEST_MATRIX.md

@@ -90,6 +90,19 @@ The standalone demo should be checked at minimum at:
 Required views now include setup readiness, dashboard, repository workspace,
 deployment preflight, active run, success/failure and Diagnostics.
 
+## v0.8 functional acceptance
+
+- real-repository partial hunk staging without staging the remaining changes;
+- guided merge-conflict resolution and safe continue/abort actions;
+- Gitea pull-request creation and protected-branch inspection;
+- shell-free editor and terminal argument-template expansion;
+- deployment freezes, maintenance windows, mandatory release notes and reasoned overrides;
+- authenticated encrypted configuration backup without credentials or operation history;
+- append-only audit JSONL and CSV export;
+- desktop notification, tray and close-to-tray preference integration;
+- read-only-by-default end-to-end Gitea Actions acceptance harness with explicit deploy/rollback flags;
+- interactive demo verification for repository quick actions, hunk staging and pull-request dialogs.
+
 
 ### v0.4 additions