epiq 1.2.3 → 1.3.1

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "epiq",
-	"version": "1.2.3",
+	"version": "1.3.1",
 	"license": "MIT",
 	"type": "module",
 	"description": "EPIQ - ergonomic, distributed CLI-first issue tracker TUI ready for the agentic era",

package/readme.md

@@ -2,8 +2,6 @@
 
 _Distributed terminal-native issue tracker backed by Git._
 
-[![GitHub Sponsors](https://img.shields.io/badge/Sponsor-Epiq-pink?logo=github)](https://github.com/sponsors/ljtn)
-
 **[See docs →](https://ljtn.github.io/epiq/docs.html)**
 
 Issue tracking is a core part of software development, but it often becomes a painful context-switching exercise with poor ergonomics. Epiq provides issue tracking as a portable, integrated part of the development environment, with access to all the powerful tooling developers are used to.
@@ -46,7 +44,7 @@ These design choices result in a system that is:
 - Issue tracking — track work in tickets with name, description, tags, assignees, history log, etc.
 - Ergonomics — fast keyboard-driven UX, command line with history, syntax highlighting etc.
 - Command palette — press `?` to open a scrollable overview of all available commands and descriptions
-- Time travel — inspect your app 1h, 1 week or 1 year ago
+- Time travel — inspect your board 1h, 1 week or 1 year ago
 - Filtering — query issues by description, tags, assignees, etc.
 - Autocompletion — minimize typing, stay in flow, reuse previous commands
 - Multi-user — collaborative synchronization via Git
@@ -251,5 +249,6 @@ Epiq follows a **local-first** model:
 > Frequent synchronization reduces divergence and keeps the system predictable
 
 ---
+[![GitHub Sponsors](https://img.shields.io/badge/Sponsor-Epiq-pink?logo=github)](https://github.com/sponsors/ljtn)
 
 🫡 Never leave your editor!