build(Hi.WpfPlus): keep the package line on 3.1 and resume the build counter

The 3.2 line is retracted -- the major version stays fixed for commercial
positioning, so 3.1 remains the development line. Version stamp only; no code
changed on the way out or back.

VersionBuild resumes at 158, where it stood before the detour, instead of
restarting from the 143 the feed serves. Everything between was built locally and
stamped into real assemblies even though deploy.py deliberately withholds the
upload until the API has settled commercially, and re-minting a spent number with
different code is the one failure that yields two Hi.WpfPlus.dll claiming the same
version. Next upload is 3.1.159; the 143 -> 159 gap on the feed is intended.

3.2.1 was packed locally and never uploaded, so nothing outside this machine saw
the 3.2 line at all.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Hi.WpfPlus.csproj

@@ -12,8 +12,8 @@
 			HiAPI wpf canvas.
 		</Description>
     <Configurations>Debug;Release</Configurations>
-    <VersionBuild>0</VersionBuild>
+    <VersionBuild>158</VersionBuild>
-    <VersionPrefix>3.2.$(VersionBuild)</VersionPrefix>
+    <VersionPrefix>3.1.$(VersionBuild)</VersionPrefix>
     <PackageId>Hi.WpfPlus</PackageId>
     <PackageTags>HiAPI</PackageTags>
     <RuntimeIdentifiers>win-x64</RuntimeIdentifiers>
@@ -29,7 +29,7 @@
     <ProjectReference Include="..\HiDisp\HiDisp.csproj" />
   </ItemGroup>
   <ItemGroup Condition="'$(Configuration)'=='Release'">
-    <PackageReference Include="HiDisp" Version="3.2.*" />
+    <PackageReference Include="HiDisp" Version="3.1.*" />
   </ItemGroup>
   <PropertyGroup Condition="'$(Configuration)'=='Release'">
     <IsIgnoreObfuscar>true</IsIgnoreObfuscar>