LED 123 define entity lifecycle states

.agents/skills/ledgerly-commit-message/SKILL.md

@@ -0,0 +1,87 @@
+---
+name: ledgerly-commit-message
+description: Create and validate Ledgerly commit messages. Use when committing Ledgerly changes, drafting commit messages, checking commit message format, or extracting the Jira ticket key from the current branch.
+---
+
+# Ledgerly Commit Message
+
+Use this skill whenever the user asks to commit changes, draft a commit message,
+or validate a commit message in the Ledgerly repository.
+
+## Required Format
+
+Commit messages must follow:
+
+```text
+LED-XXXXX type(scope): subject
+```
+
+Where:
+
+- `LED-XXXXX` is the Jira ticket key extracted from the current branch name.
+- `type` is one of: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`,
+  `build`, `ci`, `chore`, `revert`.
+- `scope` is optional and must be concise kebab-case or a short module name,
+  such as `fullscreen`, `mobile`, or `platform-core`.
+- `subject` must be imperative mood, lowercase, and must not end with a period.
+
+Valid examples:
+
+```text
+LED-12345 fix(platform-core): handle empty ledger state
+LED-12345 test: cover transaction context loading
+```
+
+Invalid examples:
+
+```text
+fix: handle empty ledger state
+LED-12345 fixed(platform-core): handled empty ledger state.
+LED-12345 feature: Add platform core loading
+```
+
+## Ticket Extraction
+
+Before creating a commit, get the current branch:
+
+```sh
+git branch --show-current
+```
+
+Extract the first `LED-<digits>` key from a branch matching:
+
+```text
+LED-XXXXX-description
+```
+
+Use a practical regex:
+
+```text
+\bLED-[0-9]+\b
+```
+
+If the branch does not contain a `LED-<digits>` key, stop and ask the user for
+the ticket key before committing.
+
+## Drafting Rules
+
+1. Choose the narrowest accurate `type`.
+2. Add a scope only when it clarifies the changed area.
+3. Keep the subject short, specific, lowercase, imperative, and without a final
+   period.
+4. Prefer concrete verbs: `add`, `fix`, `move`, `rename`, `remove`, `update`,
+   `cover`, `document`, `refactor`.
+5. Do not invent a Jira ticket key. Use the branch key or ask the user.
+
+## Commit Workflow
+
+When the user asks to commit:
+
+1. Inspect `git status --short`.
+2. Confirm the staged or intended files match the requested work.
+3. Extract the Jira ticket key from the current branch.
+4. Draft a valid commit message from the actual diff.
+5. Run `git commit -m "<message>"`.
+
+If unrelated user changes are present, do not stage or modify them unless the
+user explicitly asks.

.agents/skills/ledgerly-commit-message/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Ledgerly Commit Message"
+  short_description: "Format Ledgerly commits from branch tickets"
+  default_prompt: "Use $ledgerly-commit-message to create a valid Ledgerly commit message from the current branch."

.gitignore

@@ -23,3 +23,6 @@ data/sqlite.db
 
 # TypeScript build info
 tsconfig.tsbuildinfo
+
+
+coverage

.vscode/settings.json

@@ -1,7 +1 @@
-{
-  "github.copilot.chat.commitMessageGeneration.instructions": [
-    {
-      "text": "Commit message must follow the format: 'LED-XXXXX type(scope): subject'. Extract the ticket number from the current branch name (pattern: LED-XXXXX-description). Allowed types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert. Scope is optional (e.g. fullscreen, mobile, platform-core). Subject must be in imperative mood, lowercase, no period at the end."
-    }
-  ]
-}
+{}

apps/backend/drizzle/0000_careful_dust.sql → apps/backend/drizzle/0000_clammy_invisible_woman.sql

@@ -5,6 +5,7 @@ CREATE TABLE `accounts` (
 	`description` text NOT NULL,
 	`id` text PRIMARY KEY NOT NULL,
 	`initial_balance` text NOT NULL,
+	`is_closed` integer NOT NULL,
 	`is_system` integer NOT NULL,
 	`is_tombstone` integer NOT NULL,
 	`name` text NOT NULL,

apps/backend/drizzle/0001_adorable_star_brand.sql

@@ -0,0 +1 @@
+ALTER TABLE `commodities` ADD `is_closed` integer NOT NULL;

apps/backend/drizzle/0002_numerous_alice.sql

@@ -0,0 +1,26 @@
+CREATE UNIQUE INDEX `commodities_user_id_id_unique_idx` ON `commodities` (`user_id`,`id`);--> statement-breakpoint
+PRAGMA foreign_keys=OFF;--> statement-breakpoint
+CREATE TABLE `__new_accounts` (
+	`commodity_id` text NOT NULL,
+	`created_at` text NOT NULL,
+	`current_cleared_balance_local` text NOT NULL,
+	`description` text NOT NULL,
+	`id` text PRIMARY KEY NOT NULL,
+	`initial_balance` text NOT NULL,
+	`is_closed` integer NOT NULL,
+	`is_system` integer NOT NULL,
+	`is_tombstone` integer NOT NULL,
+	`name` text NOT NULL,
+	`type` text NOT NULL,
+	`updated_at` text NOT NULL,
+	`user_id` text NOT NULL,
+	FOREIGN KEY (`commodity_id`) REFERENCES `commodities`(`id`) ON UPDATE no action ON DELETE no action,
+	FOREIGN KEY (`user_id`) REFERENCES `users`(`id`) ON UPDATE no action ON DELETE cascade,
+	FOREIGN KEY (`user_id`,`commodity_id`) REFERENCES `commodities`(`user_id`,`id`) ON UPDATE no action ON DELETE no action
+);
+--> statement-breakpoint
+INSERT INTO `__new_accounts`("commodity_id", "created_at", "current_cleared_balance_local", "description", "id", "initial_balance", "is_closed", "is_system", "is_tombstone", "name", "type", "updated_at", "user_id") SELECT "commodity_id", "created_at", "current_cleared_balance_local", "description", "id", "initial_balance", "is_closed", "is_system", "is_tombstone", "name", "type", "updated_at", "user_id" FROM `accounts`;--> statement-breakpoint
+DROP TABLE `accounts`;--> statement-breakpoint
+ALTER TABLE `__new_accounts` RENAME TO `accounts`;--> statement-breakpoint
+PRAGMA foreign_keys=ON;--> statement-breakpoint
+CREATE UNIQUE INDEX `user_id_name_unique_idx` ON `accounts` (`user_id`,`name`);

apps/backend/drizzle/0003_bored_daredevil.sql

@@ -0,0 +1,24 @@
+PRAGMA foreign_keys=OFF;--> statement-breakpoint
+CREATE TABLE `__new_accounts` (
+	`commodity_id` text NOT NULL,
+	`created_at` text NOT NULL,
+	`current_cleared_balance_local` text NOT NULL,
+	`description` text NOT NULL,
+	`id` text PRIMARY KEY NOT NULL,
+	`initial_balance` text NOT NULL,
+	`is_closed` integer NOT NULL,
+	`is_system` integer NOT NULL,
+	`is_tombstone` integer NOT NULL,
+	`name` text NOT NULL,
+	`type` text NOT NULL,
+	`updated_at` text NOT NULL,
+	`user_id` text NOT NULL,
+	FOREIGN KEY (`user_id`) REFERENCES `users`(`id`) ON UPDATE no action ON DELETE cascade,
+	FOREIGN KEY (`user_id`,`commodity_id`) REFERENCES `commodities`(`user_id`,`id`) ON UPDATE no action ON DELETE no action
+);
+--> statement-breakpoint
+INSERT INTO `__new_accounts`("commodity_id", "created_at", "current_cleared_balance_local", "description", "id", "initial_balance", "is_closed", "is_system", "is_tombstone", "name", "type", "updated_at", "user_id") SELECT "commodity_id", "created_at", "current_cleared_balance_local", "description", "id", "initial_balance", "is_closed", "is_system", "is_tombstone", "name", "type", "updated_at", "user_id" FROM `accounts`;--> statement-breakpoint
+DROP TABLE `accounts`;--> statement-breakpoint
+ALTER TABLE `__new_accounts` RENAME TO `accounts`;--> statement-breakpoint
+PRAGMA foreign_keys=ON;--> statement-breakpoint
+CREATE UNIQUE INDEX `user_id_name_unique_idx` ON `accounts` (`user_id`,`name`);

apps/backend/drizzle/meta/0000_snapshot.json

@@ -1,7 +1,7 @@
 {
   "version": "6",
   "dialect": "sqlite",
-  "id": "59edadf8-a69b-4dbb-a24a-828a220d6559",
+  "id": "72b37ad6-4dd9-43c4-8017-7b838aee4e7b",
   "prevId": "00000000-0000-0000-0000-000000000000",
   "tables": {
     "accounts": {
@@ -49,6 +49,13 @@
           "notNull": true,
           "autoincrement": false
         },
+        "is_closed": {
+          "name": "is_closed",
+          "type": "integer",
+          "primaryKey": false,
+          "notNull": true,
+          "autoincrement": false
+        },
         "is_system": {
           "name": "is_system",
           "type": "integer",