runcastle 1.0.24 → 1.0.26

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,24 @@
1
+ CREATE TABLE `project_findings` (
2
+ `project_id` text NOT NULL,
3
+ `key` text NOT NULL,
4
+ `source` text NOT NULL,
5
+ `evidence` text,
6
+ `established_at` integer NOT NULL,
7
+ `established_sha` text,
8
+ PRIMARY KEY(`project_id`, `key`)
9
+ );
10
+ --> statement-breakpoint
11
+ CREATE TABLE `project_preps` (
12
+ `id` text PRIMARY KEY NOT NULL,
13
+ `project_id` text NOT NULL,
14
+ `status` text NOT NULL,
15
+ `started_at` integer NOT NULL,
16
+ `ended_at` integer,
17
+ `summary` text,
18
+ `head_sha` text
19
+ );
20
+ --> statement-breakpoint
21
+ ALTER TABLE `projects` ADD `setup_command` text;--> statement-breakpoint
22
+ ALTER TABLE `projects` ADD `verify_commands` text;--> statement-breakpoint
23
+ ALTER TABLE `projects` ADD `known_failures` text;--> statement-breakpoint
24
+ ALTER TABLE `projects` ADD `db_reset_command` text;
@@ -0,0 +1,2 @@
1
+ ALTER TABLE `projects` ADD `drive_setup_command` text;--> statement-breakpoint
2
+ ALTER TABLE `projects` ADD `drive_stop_command` text;
@@ -0,0 +1 @@
1
+ ALTER TABLE `projects` ADD `drive_env` text;
@@ -0,0 +1,21 @@
1
+ PRAGMA foreign_keys=OFF;--> statement-breakpoint
2
+ CREATE TABLE `__new_sessions` (
3
+ `id` text PRIMARY KEY NOT NULL,
4
+ `feature_id` text,
5
+ `project_id` text,
6
+ `kind` text NOT NULL,
7
+ `cc_session_id` text,
8
+ `transcript_path` text,
9
+ `status` text NOT NULL,
10
+ `worktree_path` text NOT NULL
11
+ );
12
+ --> statement-breakpoint
13
+ -- `project_id` is NEW in this migration, so it is deliberately absent from the
14
+ -- SELECT: the old `sessions` table has no such column and drizzle's generated
15
+ -- statement named it on both sides, which fails with "no such column". Existing
16
+ -- rows are all feature sessions and correctly take NULL here — they derive
17
+ -- their project through `feature_id` exactly as before.
18
+ INSERT INTO `__new_sessions`("id", "feature_id", "kind", "cc_session_id", "transcript_path", "status", "worktree_path") SELECT "id", "feature_id", "kind", "cc_session_id", "transcript_path", "status", "worktree_path" FROM `sessions`;--> statement-breakpoint
19
+ DROP TABLE `sessions`;--> statement-breakpoint
20
+ ALTER TABLE `__new_sessions` RENAME TO `sessions`;--> statement-breakpoint
21
+ PRAGMA foreign_keys=ON;