docs(blotter): enforce plain-English wording for end users

Rewrite two release entries that leaked dev jargon (v0.7.4 "Pretext feed
sizing" / "mobile scroll perf", v0.7.3 "compact account history") and tighten
the release skill's Step 3 with a non-negotiable plain-English rule plus
good/bad examples. Mirror the rule inline in AGENTS.md so agents editing the
blotter outside the skill still see it.
This commit is contained in:
Tommaso Casaburi
2026-04-17 14:30:41 +07:00
parent b81bcd8c55
commit 2b79432f16
5 changed files with 72 additions and 20 deletions
+2 -2
View File
@@ -4,14 +4,14 @@
"id": "release-0.7.4",
"kind": "release",
"timestamp": 1775736000,
"message": "v0.7.4: Pretext feed sizing, mobile scroll perf, Android USB dev preview",
"message": "v0.7.4: Smoother feed sizing, smoother mobile scrolling, Android USB dev preview",
"version": "0.7.4"
},
{
"id": "release-0.7.3",
"kind": "release",
"timestamp": 1774008000,
"message": "v0.7.3: In-app desktop updates, opt-in thread auto-refresh, compact account history",
"message": "v0.7.3: In-app desktop updates, opt-in thread auto-refresh, performant account history",
"version": "0.7.3"
},
{