@sascha384/tic 2.0.0 → 2.0.1

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "tic",
   "description": "Issue tracking skills for Claude Code",
-  "version": "2.0.0",
+  "version": "2.0.1",
   "author": {
     "name": "Sascha Krug"
   },

package/README.md

@@ -1,15 +1,15 @@
 # tic
 
-A terminal UI for issue tracking, built for developers who live in the terminal. Track work items across multiple backends — local markdown files, GitHub Issues, GitLab Issues, Azure DevOps Work Items, and Jira.
+A terminal UI for issue tracking, built for developers who live in the terminal. Track work items across multiple backends — GitHub Issues, GitLab Issues, Azure DevOps Work Items, and Jira — with local SQLite storage.
 
 Built with TypeScript and [Ink](https://github.com/vadimdemedes/ink).
 
 ## Features
 
 - **Keyboard-driven TUI** — browse, create, edit, and manage work items without leaving the terminal
-- **Multiple backends** — local markdown, GitHub (via `gh`), GitLab (via `glab`), Azure DevOps (via `az`), Jira (via REST API)
+- **Multiple backends** — GitHub (via `gh`), GitLab (via `glab`), Azure DevOps (via `az`), Jira (via REST API)
 - **Automatic backend detection** — selects backend based on git remote, or configure manually
-- **Local markdown storage** — work items stored as markdown files with YAML frontmatter in a `.tic/` directory
+- **SQLite storage** — all data stored locally in `.tic/tic.db` with optional sync to remote backends
 - **CLI commands** — scriptable commands for all operations (`tic item list`, `tic item create`, etc.)
 - **Work item types** — organize by epic, issue, and task (configurable)
 - **Iterations** — group work into sprints or milestones
@@ -39,16 +39,18 @@ tic init           # Initialize (auto-detects backend from git remote)
 tic                # Launch the TUI
 ```
 
-For local storage, `tic init` creates a `.tic/` directory to store your work items. For GitHub, GitLab, or Azure DevOps projects, it detects the backend from the git remote automatically. You can also specify a backend explicitly:
+`tic init` creates a `.tic/` directory with a SQLite database to store your work items. For GitHub, GitLab, or Azure DevOps projects, it detects the backend from the git remote automatically. You can also specify a backend explicitly:
 
 ```bash
 tic init --backend github
 tic init --backend gitlab
 tic init --backend azure
 tic init --backend jira
-tic init --backend local
+tic init --backend none
 ```
 
+The TUI also auto-initializes on first run if no `.tic/` directory exists.
+
 ## Usage
 
 ### List View
@@ -123,70 +125,22 @@ Deleting an item automatically cleans up references — children have their pare
 
 ## Storage
 
-Work items live in `.tic/` at the root of your project:
+All data lives in `.tic/` at the root of your project:
 
 ```
 .tic/
-├── config.yml          # Types, statuses, iterations, settings
-├── items/
-│   ├── 1.md            # Work item #1
-│   ├── 2.md            # Work item #2
-│   └── ...
-├── templates/          # Work item templates
-│   └── bug-report.md   # Template with YAML frontmatter
-└── trash/              # Soft-deleted items (for undo)
+├── tic.db              # SQLite database (all items, config, undo log)
+└── items/              # Markdown mirrors (for sync / human-readable export)
+    ├── 1.md
+    ├── 2.md
+    └── ...
 ```
 
-Each item is a markdown file with YAML frontmatter:
-
-```markdown
----
-id: 1
-title: Implement user login
-type: task
-status: in-progress
-iteration: sprint-1
-priority: high
-assignee: alice
-labels: auth, backend
-parent: 3
-depends_on:
-  - 2
-created: 2026-01-15T10:00:00.000Z
-updated: 2026-01-20T14:30:00.000Z
----
-
-Full description of the work item goes here.
-
-## Comments
-
----
-author: alice
-date: 2026-01-18T09:00:00.000Z
-
-Decided to use JWT tokens for this.
-```
+The SQLite database (`.tic/tic.db`) is the single source of truth for work items, config, templates, and undo history. When a remote backend is configured, `SyncManager` also writes markdown mirrors to `.tic/items/` via `FilesBackend`.
 
-Configuration in `.tic/config.yml`:
-
-```yaml
-types:
-  - epic
-  - issue
-  - task
-statuses:
-  - backlog
-  - todo
-  - in-progress
-  - review
-  - done
-iterations:
-  - default
-current_iteration: default
-next_id: 1
-```
+Configuration (types, statuses, iterations, etc.) is stored in the `project_config` table and managed via the TUI settings screen or `tic config` CLI commands.
 
-You can edit these files directly — they're plain text. Customize types, statuses, and iterations by editing `config.yml`.
+If upgrading from a legacy `.tic/config.yml` setup, the database will automatically migrate the YAML config on first open.
 
 ## Claude Code Integration
 
@@ -240,7 +194,7 @@ Add `--json` to any command for machine-readable output, or `--quiet` to suppres
 
 | Backend | CLI Tool | Detection |
 |---------|----------|-----------|
-| Local markdown | — | Default fallback |
+| Local only (SQLite) | — | Default fallback |
 | GitHub Issues | [`gh`](https://cli.github.com/) | `github.com` in git remote |
 | GitLab Issues | [`glab`](https://gitlab.com/gitlab-org/cli) | `gitlab.com` in git remote |
 | Azure DevOps Work Items | [`az`](https://learn.microsoft.com/en-us/cli/azure/) | `dev.azure.com` or `visualstudio.com` in git remote |

package/drizzle/0000_next_vance_astro.sql

@@ -0,0 +1,183 @@
+CREATE TABLE `comments` (
+	`id` integer PRIMARY KEY AUTOINCREMENT NOT NULL,
+	`work_item_id` text NOT NULL,
+	`author` text DEFAULT '' NOT NULL,
+	`body` text NOT NULL,
+	`created` text NOT NULL,
+	FOREIGN KEY (`work_item_id`) REFERENCES `work_items`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE INDEX `idx_comment_item` ON `comments` (`work_item_id`);--> statement-breakpoint
+CREATE TABLE `file_sync_state` (
+	`item_id` text PRIMARY KEY NOT NULL,
+	`hash` text NOT NULL,
+	`synced_at` text NOT NULL
+);
+--> statement-breakpoint
+CREATE TABLE `iterations` (
+	`name` text PRIMARY KEY NOT NULL,
+	`sort_order` integer DEFAULT 0 NOT NULL
+);
+--> statement-breakpoint
+CREATE TABLE `jira_config` (
+	`id` integer PRIMARY KEY DEFAULT 1 NOT NULL,
+	`site` text DEFAULT '' NOT NULL,
+	`project` text DEFAULT '' NOT NULL,
+	`board_id` text DEFAULT '' NOT NULL
+);
+--> statement-breakpoint
+CREATE TABLE `project_config` (
+	`id` integer PRIMARY KEY DEFAULT 1 NOT NULL,
+	`backend` text DEFAULT 'none' NOT NULL,
+	`current_iteration` text DEFAULT '' NOT NULL,
+	`next_id` integer DEFAULT 1 NOT NULL,
+	`branch_mode` text DEFAULT 'branch' NOT NULL,
+	`branch_command` text DEFAULT '' NOT NULL,
+	`copy_to_clipboard` integer DEFAULT true NOT NULL,
+	`auto_update` integer DEFAULT true NOT NULL,
+	`default_type` text DEFAULT 'issue' NOT NULL,
+	`show_detail_panel` integer DEFAULT false NOT NULL,
+	`default_view` text DEFAULT '' NOT NULL
+);
+--> statement-breakpoint
+CREATE TABLE `saved_view_filters` (
+	`view_name` text NOT NULL,
+	`field` text NOT NULL,
+	`value` text NOT NULL,
+	PRIMARY KEY(`view_name`, `field`, `value`),
+	FOREIGN KEY (`view_name`) REFERENCES `saved_views`(`name`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE TABLE `saved_view_sort_entries` (
+	`view_name` text NOT NULL,
+	`column` text NOT NULL,
+	`direction` text NOT NULL,
+	`sort_order` integer NOT NULL,
+	PRIMARY KEY(`view_name`, `sort_order`),
+	FOREIGN KEY (`view_name`) REFERENCES `saved_views`(`name`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE TABLE `saved_views` (
+	`name` text PRIMARY KEY NOT NULL
+);
+--> statement-breakpoint
+CREATE TABLE `statuses` (
+	`name` text PRIMARY KEY NOT NULL,
+	`sort_order` integer DEFAULT 0 NOT NULL
+);
+--> statement-breakpoint
+CREATE TABLE `sync_queue` (
+	`id` integer PRIMARY KEY AUTOINCREMENT NOT NULL,
+	`action` text NOT NULL,
+	`item_id` text NOT NULL,
+	`timestamp` text NOT NULL,
+	`comment_data` text,
+	`template_slug` text
+);
+--> statement-breakpoint
+CREATE INDEX `idx_queue_item` ON `sync_queue` (`item_id`,`action`);--> statement-breakpoint
+CREATE TABLE `template_deps` (
+	`template_slug` text NOT NULL,
+	`depends_on_id` text NOT NULL,
+	PRIMARY KEY(`template_slug`, `depends_on_id`),
+	FOREIGN KEY (`template_slug`) REFERENCES `templates`(`slug`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE TABLE `template_labels` (
+	`template_slug` text NOT NULL,
+	`label` text NOT NULL,
+	PRIMARY KEY(`template_slug`, `label`),
+	FOREIGN KEY (`template_slug`) REFERENCES `templates`(`slug`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE TABLE `templates` (
+	`slug` text PRIMARY KEY NOT NULL,
+	`name` text NOT NULL,
+	`type` text DEFAULT '' NOT NULL,
+	`status` text DEFAULT '' NOT NULL,
+	`priority` text DEFAULT '' NOT NULL,
+	`assignee` text DEFAULT '' NOT NULL,
+	`iteration` text DEFAULT '' NOT NULL,
+	`parent` text,
+	`description` text DEFAULT '' NOT NULL
+);
+--> statement-breakpoint
+CREATE TABLE `undo_item_snapshot` (
+	`undo_id` integer PRIMARY KEY NOT NULL,
+	`title` text NOT NULL,
+	`type` text NOT NULL,
+	`status` text NOT NULL,
+	`iteration` text NOT NULL,
+	`priority` text NOT NULL,
+	`assignee` text NOT NULL,
+	`description` text NOT NULL,
+	`parent` text,
+	`created` text NOT NULL,
+	`updated` text NOT NULL,
+	FOREIGN KEY (`undo_id`) REFERENCES `undo_stack`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE TABLE `undo_item_snapshot_deps` (
+	`undo_id` integer NOT NULL,
+	`depends_on_id` text NOT NULL,
+	PRIMARY KEY(`undo_id`, `depends_on_id`),
+	FOREIGN KEY (`undo_id`) REFERENCES `undo_stack`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE TABLE `undo_item_snapshot_labels` (
+	`undo_id` integer NOT NULL,
+	`label` text NOT NULL,
+	PRIMARY KEY(`undo_id`, `label`),
+	FOREIGN KEY (`undo_id`) REFERENCES `undo_stack`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE TABLE `undo_stack` (
+	`id` integer PRIMARY KEY AUTOINCREMENT NOT NULL,
+	`action` text NOT NULL,
+	`item_id` text NOT NULL,
+	`created_at` text NOT NULL
+);
+--> statement-breakpoint
+CREATE TABLE `work_item_deps` (
+	`work_item_id` text NOT NULL,
+	`depends_on_id` text NOT NULL,
+	PRIMARY KEY(`work_item_id`, `depends_on_id`),
+	FOREIGN KEY (`work_item_id`) REFERENCES `work_items`(`id`) ON UPDATE no action ON DELETE cascade,
+	FOREIGN KEY (`depends_on_id`) REFERENCES `work_items`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE INDEX `idx_dep_target` ON `work_item_deps` (`depends_on_id`);--> statement-breakpoint
+CREATE TABLE `work_item_labels` (
+	`work_item_id` text NOT NULL,
+	`label` text NOT NULL,
+	PRIMARY KEY(`work_item_id`, `label`),
+	FOREIGN KEY (`work_item_id`) REFERENCES `work_items`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE INDEX `idx_label` ON `work_item_labels` (`label`);--> statement-breakpoint
+CREATE TABLE `work_item_types` (
+	`name` text PRIMARY KEY NOT NULL,
+	`sort_order` integer DEFAULT 0 NOT NULL
+);
+--> statement-breakpoint
+CREATE TABLE `work_items` (
+	`id` text PRIMARY KEY NOT NULL,
+	`title` text NOT NULL,
+	`type` text NOT NULL,
+	`status` text NOT NULL,
+	`iteration` text DEFAULT '' NOT NULL,
+	`priority` text DEFAULT '' NOT NULL,
+	`assignee` text DEFAULT '' NOT NULL,
+	`description` text DEFAULT '' NOT NULL,
+	`parent` text,
+	`created` text NOT NULL,
+	`updated` text NOT NULL,
+	`deleted_at` text
+);
+--> statement-breakpoint
+CREATE INDEX `idx_status` ON `work_items` (`status`);--> statement-breakpoint
+CREATE INDEX `idx_type` ON `work_items` (`type`);--> statement-breakpoint
+CREATE INDEX `idx_assignee` ON `work_items` (`assignee`);--> statement-breakpoint
+CREATE INDEX `idx_priority` ON `work_items` (`priority`);--> statement-breakpoint
+CREATE INDEX `idx_iteration` ON `work_items` (`iteration`);--> statement-breakpoint
+CREATE INDEX `idx_parent` ON `work_items` (`parent`);