epiq 0.7.2 → 0.7.4

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "epiq",
-	"version": "0.7.2",
+	"version": "0.7.4",
 	"license": "MIT",
 	"type": "module",
 	"description": "EPIQ - CLI based issue tracker",
@@ -30,10 +30,10 @@
 		"build:gui:types": "tsc --noEmit -p source/gui/client/tsconfig.json",
 		"build:gui": "npm run build:gui:types && mkdir -p dist/gui && cp source/gui/index.html dist/gui/index.html && cp source/gui/favicon.ico dist/gui/favicon.ico && esbuild source/gui/client/main.tsx --bundle --format=esm --target=es2020 --outfile=dist/gui/main.js",
 		"build:npm": "node source/scripts/write-version.mjs && rm -rf ./dist && npm run build:gui && esbuild source/Index.tsx --bundle --packages=external --platform=node --format=esm --target=node18 --minify --outfile=dist/index.js --banner:js='#!/usr/bin/env node' && esbuild source/mcp/index.ts --bundle --packages=external --platform=node --format=esm --target=node18 --minify --outfile=dist/mcp.js --banner:js='#!/usr/bin/env node'",
-		"build:sea:bundle": "node source/scripts/write-version.mjs && rm -rf ./dist && esbuild source/Index.tsx --bundle --platform=node --format=cjs --target=node18 --minify --outfile=dist/sea.cjs",
-		"build:sea": "node --build-sea source/config/sea-config.json",
+		"build:sea:bundle": "node source/scripts/write-version.mjs && node source/scripts/build-sea.mjs",
+		"build:sea": "node source/scripts/build-sea.mjs",
 		"build:publish": "npm run build:npm",
-		"build:binary": "npm run build:sea:bundle && npm run build:sea",
+		"build:binary": "node source/scripts/write-version.mjs && node source/scripts/build-sea.mjs",
 		"watch:npm": "node source/scripts/write-version.mjs && rm -rf ./dist && node source/scripts/watch-npm.mjs",
 		"dev": "IS_LOCAL=true tsc --watch --noEmit",
 		"dev:start": "IS_LOCAL=true tsx source/Index.tsx",

package/readme.md

@@ -6,15 +6,15 @@ _Distributed terminal-native issue tracker backed by Git._
 
 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.
 
-> Manage your projects in a visual terminal kanban board or through the browser GUI, while keeping all state local, Git-backed, and versioned.
+> Manage your projects in a visual terminal kanban board (or through the browser GUI), while keeping all state local, Git-backed, and versioned.
 
-With great attention to user ergonomics and developer experience, epiq makes project management painless and friction free.
+With great attention to user ergonomics and developer experience, epiq strives to make project management painless and friction free.
 
 ![Epiq cli gif view](https://raw.githubusercontent.com/ljtn/epiq/main/source/assets/epiq-cli.gif)
 
-## Terminal UI + Browser GUI
+## Terminal + Browser
 
-Epiq also includes a browser-based interface powered by the same Git-backed event engine.
+Epiq originated from the command line, but also features a browser interface powered by the same Git-backed event engine.
 
 ![Epiq gui view](https://raw.githubusercontent.com/ljtn/epiq/main/source/assets/epiq-gui.gif)
 
@@ -22,24 +22,9 @@ Epiq also includes a browser-based interface powered by the same Git-backed even
 
 Epiq is a self hosted, vim-inspired issue tracker that brings developer experience to project management. It renders either as ASCII, or as a web GUI, and persists state as an immutable distributed event log, versioned and synchronized through Git.
 
-An easy to use browser GUI is available, powered by the same Git-backed state engine.
-
 ![Epiq cli kanban view](https://raw.githubusercontent.com/ljtn/epiq/main/source/assets/overview.png)
 ![Epiq cli log view](https://raw.githubusercontent.com/ljtn/epiq/main/source/assets/log.png)
 
-## Features
-
-- 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
-- Filtering — query issues by description, tags, assignees, etc.
-- Autocompletion — minimize typing, stay in flow, reuse previous commands
-- Multi-user — collaborative synchronization via Git
-- Traceable event log — state is a full history of every change ever made
-- Browser GUI — graphical interface powered by the same Git-backed state
-- MCP integration — Model Context Protocol support for agent interaction
-
 ## Why Epiq?
 
 Most issue trackers live outside your workflow. Epiq brings issue tracking where you already work - you editor.
@@ -54,6 +39,19 @@ These design choices result in a system that is:
 - **Command driven** — scriptable and automation-friendly, ready for the agentic era
 - **Versioned** — changes are tracked and recoverable through Git
 
+## Features
+
+- 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
+- Filtering — query issues by description, tags, assignees, etc.
+- Autocompletion — minimize typing, stay in flow, reuse previous commands
+- Multi-user — collaborative synchronization via Git
+- Traceable event log — state is a full history of every change ever made
+- Browser GUI — graphical interface powered by the same Git-backed state
+- MCP integration — Model Context Protocol support for agent interaction
+
 ---
 
 ## Installation
@@ -230,4 +228,4 @@ Epiq follows a **local-first** model:
 
 ---
 
-🫡 Project management for people who live in the terminal. And everyone else!
+🫡 Never leave your editor!