Cut 0.5.0, so today's correction reaches somebody - #71
Merged
Conversation
The web app has had the length floor since the merge, because Pages deploys on push. Everyone else is on 0.4.0: the Windows app, and every project that took a dependency on SignsOfAI.Core. So the same paragraph gets "Signs of AI writing" from a downloaded build and no verdict at all from the browser tab beside it, which is precisely the drift VerdictBands exists to prevent — one engine giving two answers about the same text, across a distribution boundary instead of a code one. What 0.5.0 carries, in the order it matters to somebody using it: - The verdict has a length condition (#59). Below the shortest text the boundary was measured on — 662 words — the score stands alone and the page says why. The evidence is untouched. - Six chat.* rules: the assistant's own turn left inside a document, in both languages, and the published false-positive rate did not move to carry them. - A page that explains the Windows app and offers it, instead of a GitHub releases search URL. - The desktop app says which build it is, and can ask whether to look for a newer one. The calibration is restamped so the report signs itself 0.5.0 rather than quoting a threshold under a version that never measured it. Same corpus fingerprint, same 0 of 90, same 4.1%. Also corrected in the MCP manifest: it still said "the other seven tools never call it" from before write_report shipped. Ten tools, eight of them offline. The README was fixed in #46 and this file was missed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015PEbbiYSNPw7jE3LrPNhyF
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version bump only — no behaviour change beyond what is already on
main.Why now
The web app has had the length floor since #69 merged, because Pages deploys on push. Everyone else
is on 0.4.0: the Windows app, and every project depending on
SignsOfAI.Core.So the same paragraph gets "Signs of AI writing" from a downloaded build and no verdict at all
from the browser tab beside it. That is exactly the drift
VerdictBandsexists to prevent — oneengine giving two answers about the same text, across a distribution boundary instead of a code one.
What 0.5.0 carries
chat.*rules — the assistant's own turn left inside a document, both languages — and the published rate did not move to carry them./downloadpage that explains the Windows app, instead of a GitHub releases search URL.What changed here
<Version>→0.5.0in Core, Cli, Mcp..mcp/server.json→0.5.0twice (the manifest version and the package version).DesktopRelease.Version→0.5.0. The desktop release workflow refuses adesktop-v*tag thatdisagrees with this, so it has to land before the tag is cut.
0.5.0rather than quoting a threshold under aversion that never measured it. Same corpus fingerprint
123fa5b9ebca3f29, same 0 of 90, same4.1%, same
662 – 9,328range.write_reportshipped. Ten tools, eight offline. The README was corrected in Say exactly what can leave the device, because "only" was wrong #46 and this file was missed.
417 tests.
After merging
gh release create v0.5.0→ NuGet workflow packs and pushes Core, Cli, Mcp.gh release create desktop-v0.5.0→ the Windows build, after the constant is onmain.cd src/SignsOfAI.Mcp/.mcpthenmcp-publisher login github— the device code expires in minutes.Note that #70 only helps from the next release onward: somebody on 0.4.0 has no notice strip, so
they will not hear about 0.5.0 from the app. The first build that can tell anybody is this one.
🤖 Generated with Claude Code
https://claude.ai/code/session_015PEbbiYSNPw7jE3LrPNhyF