PiSharp 0.99.1

PiSharp 0.99.1

The public product and package version is 0.99.1, matching the upstream Pi
v0.99.1 porting baseline at commit
d86654abb8862e201933517d6f1fce9f88dd117f. The intended release tag is v0.99.1.
This note prepares release metadata; it does not record creation of a tag,
publication of a binary release, or publication of NuGet packages.

Qualification status

Fresh 0.99.1 artifacts have not yet been qualified. Earlier private package
versions, including 0.1.0-private.cb338cb1, retain their original byte identities
and receipts. They must not be renamed, repacked, or described as tested 0.99.1
artifacts. Version-specific source, restore locks, products, archives, package
dependencies and consumers require new exact evidence.

The existing bounded provider observations and remaining differences are recorded
in provider source projection.
The three approved provider differences
do not establish complete provider parity or close the complete native gate.
Matching the upstream version identifies the baseline; it makes no additional
compatibility claim.

Version identities

Directory.Build.props supplies VersionPrefix=0.99.1 when no explicit prefix is
provided. Explicitly admitted private builds can still supply their own version;
that does not change the public release baseline. Public packaging must pass
PiSharpReleaseVersion=0.99.1 together with the exact source commit and provenance
to the existing opt-in distribution and native SDK targets. Their explicit-input
and provenance checks remain unchanged.

Product/package versions and CLR assembly identities are separate. The normal
SDK-derived assembly version is 0.99.1.0. PiSharp.ExtensionHost deliberately
retains assembly version 1.0.0.0, required by the existing approved supervisor
system-import profile. Its product/file version can identify 0.99.1, but its
unchanged CLR identity is not permission to reuse old bytes: the existing exact
hash, metadata and approval checks still apply. Do not globally override
AssemblyVersion during release preparation.

The existing source locks contain earlier project-version ranges. They are
historical inputs, not evidence of a successful 0.99.1 locked restore. Generate
and review new locks in an isolated admitted copy using the existing offline
cache/feed closure, then perform the required locked restores. Preserve source
locks until their exact replacements and dependent integrity pins are reviewed.

Artifact scope

The existing reviewed routes cover a Windows native CLI payload and three
ordinary .NET library packages: PiSharp.Contracts,
PiSharp.Extensions.Abstractions and PiSharp.Extensions.Runtime. This note
adds no installer, platform, signing, dependency acquisition or public package
publication claim. Build and inspect fresh versioned products, then exercise
the actual produced packages through the separately reviewed consumer route.
Keep the complete producer and consumer budgets; never shorten operations to
fit a coordination window.