docs: sync record states the autostash behaviour, not the change (#180)

Files changed:
- CHANGES.md
- VERSION
- tools/CONTRACT.md
- tools/chemenu/commands/git_publish.py

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2

CHANGES.md

@@ -59,7 +59,7 @@ concern - readable here, never shipped as something to parse.
 
 ---
 
-## 8.0.0-beta.46 - 2026-10-06 - publish/sync merge generated files mechanically and carry non-overlapping uncommitted work through a rebase
+## 8.0.0-beta.47 - 2026-10-06 - sync record: the autostash note states the behaviour, not the change
 
 **Author:** Torben Nehmer
 
@@ -157,8 +157,15 @@ concern - readable here, never shipped as something to parse.
 - wiki-ingest and wiki-manage call xref add with --rel, not the --rel-a/--rel-b removed in 4.0.0
 - raw accept: an occupied folder name held by a captured bundle points at --replaces-bundle
 - kb/CONVENTIONS.md.template: the guideline filter is a default, not a setup question
+- sync record: the autostash note states the behaviour, not the change
 <!-- /wikitool:bumps -->
 
+### sync record: the autostash note states the behaviour, not the change
+
+One note in `sync`'s command record, written with 8.0.0-beta.46, said that uncommitted changes no
+incoming commit touches "no longer" stop a rebase - a sentence about the change, which a reader of
+the record has nothing to compare against. It now states what `sync` does (Gitea #180).
+
 ### publish/sync merge generated files mechanically and carry non-overlapping uncommitted work through a rebase
 
 Every ingest touches `kb/index.md` and `kb/log.md`, so two ingests on two checkouts - or two