Publish curated ForgeFlow source from 2c0a6c36d1a4303d927a453d98462924183c126d

README.md

@@ -19,6 +19,12 @@ ForgeFlow is a Windows desktop application for teams that use Git, Gitea and sel
 
 *The captures use example repositories and demo state; they are not a live infrastructure dashboard.*
 
+### Inspect repository policy
+
+![Git Validator with demo policy findings](docs/screenshots/git-validator.png)
+
+*The demo Git Validator separates findings and recommendations from deployment revision evidence. A policy score is not a runtime health check.*
+
 ## Key capabilities
 
 | Area | What ForgeFlow helps you do |
@@ -71,6 +77,15 @@ For server-pull deployments, the host fetches the **exact approved commit** with
 
 Start with the [setup guide](docs/SETUP_GUIDE.md), [deployment setup](docs/DEPLOYMENT_SETUP.md), [SSH and Unraid deployment](docs/SSH_UNRAID_DEPLOYMENT.md), and [migration example](docs/DEPLOYMENT_MIGRATION_EXAMPLE.md). Keep runtime data and credentials outside Git. The [diagnostics guide](docs/DIAGNOSTICS.md) explains safe support bundles.
 
+## Your first repository session
+
+1. Configure the Gitea account and select a local checkout you are authorized to manage.
+2. Review the branch, working-tree changes and remote state before staging a commit.
+3. Inspect the proposed diff, commit deliberately and verify the push result.
+4. Configure a deployment target only when you need deployment; review its exact revision and confirmation before starting it.
+
+Repository state, CI validation, deployment acceptance and runtime verification are separate evidence. A completed push is not proof that the application is running the same revision.
+
 ## Develop and verify
 
 ```powershell