Bump live version to 0.1.3; drop the closed 'Not yet on NuGet' gap 0.1.3 is published (icon release). Update the current-version references in Home, Installation and Prerelease Considerations, and the verify commands. The 'Not yet on NuGet' operational gap in Known Gaps is closed — #61 shipped via trusted publishing (the NUGET_API_KEY it named is retired) — so remove it.
Verifying the package: attest the GitHub release asset, not the re-signed nuget copy; bump to 0.1.2
Installation: NuGet is live; add package verification (provenance + signature) (#271, #61)
Update the security story to the cleared register: all 107 findings closed, fuzzer on every push, warnings softened to match Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WfLh84M9sga4pBc2iqHV5o
Prerelease Considerations: alpha warning, no production use, no user-supplied documents yet Linked from the sidebar, the Home banner and navigation table, and the Installation page's untrusted-documents section. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WfLh84M9sga4pBc2iqHV5o
Build out the wiki: install, API, promises, security, functionality, gaps, architecture, fidelity, validation, developers Captures the important content of the repository README ahead of trimming it for release. The security page states the attack vector and the open register honestly rather than politely. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WfLh84M9sga4pBc2iqHV5o