Remove format from CI validation

Author: KSemenenko

.github/workflows/build-validation.yml

@@ -34,10 +34,6 @@ jobs:
         timeout-minutes: 60
         uses: "./.github/steps/install_dependencies"
 
-      - name: Format
-        shell: pwsh
-        run: dotnet format DotPilot.slnx --verify-no-changes
-
       - name: Build
         shell: pwsh
         run: dotnet build DotPilot.slnx -warnaserror

AGENTS.md

@@ -132,7 +132,7 @@ For this app:
 - unit tests currently use `NUnit` through the default `VSTest` runner
 - UI tests live in `DotPilot.UITests` and are a mandatory part of normal verification; the harness must provision or resolve browser-driver prerequisites automatically instead of skipping when local setup is missing
 - a canceled, timed-out, or hanging `DotPilot.UITests` run is a harness failure to fix, not an acceptable substitute for a real pass or fail result in CI
-- `format` uses `dotnet format --verify-no-changes`
+- `format` uses `dotnet format --verify-no-changes` as a local pre-push check; GitHub Actions validation should not spend CI time rechecking formatting drift that must already be fixed before push
 - coverage uses the `coverlet.collector` integration on `DotPilot.Tests` with the repo runsettings file to keep generated Uno artifacts out of the coverage path
 - desktop release publishing uses `dotnet publish DotPilot/DotPilot.csproj -c Release -f net10.0-desktop`; the validation workflow stays focused on build and automated tests, while the release workflow owns desktop publish outputs for macOS, Windows, and Linux
 - `LangVersion` is pinned to `latest` at the root

github-actions-yaml-review.plan.md

@@ -2,7 +2,7 @@
 
 ## Goal
 
-Review the current GitHub Actions validation and release workflows, record concrete risks with line-level evidence, and capture any durable CI policy that emerged from the user conversation, including mandatory `-warnaserror` enforcement for local and CI builds.
+Review the current GitHub Actions validation and release workflows, record concrete risks with line-level evidence, and capture any durable CI policy that emerged from the user conversation, including mandatory `-warnaserror` enforcement for local and CI builds and keeping formatting as a local pre-push concern instead of a CI gate.
 
 ## Scope
 
@@ -11,7 +11,7 @@ Review the current GitHub Actions validation and release workflows, record concr
 - `.github/workflows/build-validation.yml`
 - `.github/workflows/release-publish.yml`
 - shared workflow assumptions from `.github/steps/install_dependencies/action.yml`
-- root governance updates needed to capture durable CI runner policy and mandatory `-warnaserror` build usage
+- root governance updates needed to capture durable CI runner policy, mandatory `-warnaserror` build usage, and local-only formatting policy
 
 ### Out Of Scope
 
@@ -56,13 +56,19 @@ Review the current GitHub Actions validation and release workflows, record concr
   - no duplicate non-value build step remains after the change
   Done when: CI and local build policy both require `-warnaserror`.
 
-- [x] Step 4: Produce the workflow review findings.
+- [x] Step 4: Apply the explicitly requested formatting-gate policy.
+  Verification:
+  - `build-validation.yml` no longer runs `dotnet format`
+  - `AGENTS.md` keeps format as a local pre-push check instead of a CI job step
+  Done when: formatting is enforced locally but not re-run as a GitHub Actions validation gate.
+
+- [x] Step 5: Produce the workflow review findings.
   Verification:
   - findings reference exact files and lines
   - findings are ordered by severity
   Done when: the user can act on the review without needing another pass to discover the real problems.
 
-- [x] Step 5: Validate touched YAML/policy files.
+- [x] Step 6: Validate touched YAML/policy files.
   Verification:
   - `dotnet build DotPilot.slnx -warnaserror`
   - `actionlint .github/workflows/build-validation.yml`