Skip to content

0.7.0 — the em-dash counter reaches every channel - #83

Merged
peopleworks merged 1 commit into
mainfrom
release-0.7.0
Sep 7, 2026
Merged

peopleworks merged 1 commit into
mainfrom
release-0.7.0

Conversation

@peopleworks

Copy link
Copy Markdown
Owner

Since v0.6.0 the only change in src/ is #80. That is a scoring change, so anyone still on 0.6.0 — NuGet, the MCP registry, the CLI, the desktop app — is being told their code blocks and table separators are an LLM rhythm crutch. It ships alone rather than waiting for company.

The six places, .mcp/server.json carrying it twice

File
src/SignsOfAI.Core/SignsOfAI.Core.csproj 13
src/SignsOfAI.Cli/SignsOfAI.Cli.csproj 16
src/SignsOfAI.Mcp/SignsOfAI.Mcp.csproj 15
src/SignsOfAI.Mcp/.mcp/server.json 4 and 12
src/SignsOfAI.UI/Services/DesktopRelease.cs 23

Calibration

Re-run so the page declares the engine that produced the numbers. Only the engine field moved — threshold 30, 2 of 296 flagged, rateLow, rateHigh, every language and group row, and the corpus fingerprint 78bda061bde3dc99 are all unchanged.

⚠️ Order of operations — this is the 1 September trap, armed again

DesktopRelease.Version is now 0.7.0, and the workflow refuses a desktop-v* tag that disagrees with it. Cut desktop-v0.7.0 from this branch before merging, or the download button on the live site points at a 404 for as long as it takes to cut it.

  1. gh release create desktop-v0.7.0 --target release-0.7.0 (from this branch)
  2. merge this PR
  3. gh release create v0.7.0 → NuGet publishes
  4. wait for NuGet to index
  5. only then the MCP registry, which is manual and separate: cd src/SignsOfAI.Mcp/.mcp (not the project root), mcp-publisher login github — the device code expires in minutes

424 tests.

🤖 Generated with Claude Code

https://claude.ai/code/session_015PEbbiYSNPw7jE3LrPNhyF

Since v0.6.0 the only change in src/ is #80: `rhet.em-dash` no longer counts a
document's own markup as punctuation. That is a scoring change, so anyone still
on 0.6.0 — NuGet, the MCP registry, the CLI, the desktop app — is being told
their code blocks and table separators are an LLM rhythm crutch. It travels
alone rather than waiting for company.

Version bumped in the six places it lives, `.mcp/server.json` carrying it twice:

  src/SignsOfAI.Core/SignsOfAI.Core.csproj
  src/SignsOfAI.Cli/SignsOfAI.Cli.csproj
  src/SignsOfAI.Mcp/SignsOfAI.Mcp.csproj
  src/SignsOfAI.Mcp/.mcp/server.json          (twice)
  src/SignsOfAI.UI/Services/DesktopRelease.cs

Calibration re-run so the page declares the engine that produced the numbers.
Only the `engine` field moved: threshold 30, 2 of 296 flagged, both bounds,
every language and group row, the corpus fingerprint, all unchanged.

`DesktopRelease.Version` is now 0.7.0, and the workflow refuses a `desktop-v*`
tag that disagrees with it. So `desktop-v0.7.0` has to be cut before this
merges, or the download button points at a 404 the way it did on 1 September.

424 tests.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015PEbbiYSNPw7jE3LrPNhyF
@peopleworks
peopleworks merged commit 3e02f7c into main Sep 7, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant