Publish platform-specific Flutter captures

.github/workflows/runtime.yml

@@ -25,8 +25,8 @@ jobs:
       - name: Analyze
         run: flutter analyze lib test
 
-      - name: Test responsive runtime captures
-        run: flutter test
+      - name: Test and generate Linux runtime captures
+        run: flutter test --update-goldens
 
       - name: Verify lifecycle
         shell: pwsh
@@ -35,6 +35,6 @@ jobs:
       - name: Upload golden captures
         uses: actions/upload-artifact@v7
         with:
-          name: eveflutter-captures-${{ github.sha }}
+          name: eveflutter-linux-captures-${{ github.sha }}
           path: test/goldens/*.png
           if-no-files-found: error

README.md

@@ -5,9 +5,11 @@ Flutter projection, provider selection, command-intent construction, platform
 build glue, tests, and captures. Providers retain state and command authority;
 plugins retain domain semantics.
 
-The `eveflutter-v1.0.1` release is owner-built. CI analyzes the runtime, runs
+The `eveflutter-v1.0.2` release is owner-built. CI analyzes the runtime, runs
 the responsive capture suite, verifies lifecycle evidence, and publishes the
 committed golden captures as a commit-keyed artifact.
+Linux CI regenerates Linux goldens rather than byte-comparing them with Windows
+captures; widget and contract assertions remain shared across platforms.
 
 Current smoke target:
 

pubspec.yaml

@@ -14,7 +14,7 @@ publish_to: 'none' # Remove this line if you wish to publish to pub.dev
 # https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
 # In Windows, build-name is used as the major, minor, and patch parts
 # of the product and file versions while build-number is used as the build suffix.
-version: 1.0.1+2
+version: 1.0.2+3
 
 environment:
   sdk: ^3.12.1