@plurnk/plurnk-service 0.2.0 → 0.3.0

package/migrations/011_turn_call_metadata.sql

@@ -1,7 +0,0 @@
--- INIT: turn_call_metadata
--- Adds Turn-level call metadata fields per plurnk-grammar 0.6.0 Turn.json:
--- finish_reason and model are properties of the provider call, not the
--- model's emission payload. They belong on the Turn row alongside usage,
--- not nested into packet.assistant (which is "what the model said").
-ALTER TABLE turns ADD COLUMN finish_reason TEXT;
-ALTER TABLE turns ADD COLUMN model         TEXT NOT NULL DEFAULT 'unknown' CHECK (length(model) >= 1);

package/migrations/012_proposal_lifecycle.sql

@@ -1,22 +0,0 @@
--- INIT: proposal_lifecycle
--- log_entries gets the state⊥status lifecycle dimension. Status is the HTTP-
--- aligned outcome (200, 202, 400, etc.); state is where in the lifecycle the
--- entry lives. Most rows are 'resolved' immediately (status 200/4xx written
--- in one shot); side-effecting actions that propose first transition through
--- 'proposed' → 'resolved' (accepted) or 'proposed' → 'failed' (rejected) or
--- 'proposed' → 'cancelled' (loop aborted, timeout). Per rummy SPEC.
---
--- outcome is a short reason string when state ∈ {failed, cancelled}.
--- Opaque to most callers; a few plugins parse it (timeout, rejected,
--- loop_aborted, policy_veto, etc).
---
--- attrs is the proposal payload — opaque JSON the scheme supplies when
--- emitting status 202, retrieved by the client to render review UI, and
--- handed back to the scheme's applyResolution() on accept. File scheme uses
--- it for {path, patch_full, patched_full}; exec scheme uses {command, args,
--- cwd}; etc. Engine doesn't interpret the contents.
-ALTER TABLE log_entries ADD COLUMN state   TEXT NOT NULL DEFAULT 'resolved'
-    CHECK (state IN ('proposed', 'resolved', 'failed', 'cancelled'));
-ALTER TABLE log_entries ADD COLUMN outcome TEXT;
-ALTER TABLE log_entries ADD COLUMN attrs   TEXT NOT NULL DEFAULT '{}'
-    CHECK (json_valid(attrs));

package/migrations/013_log_entries_lifecycle_columns.sql

@@ -1,22 +0,0 @@
--- INIT: log_entries_lifecycle_columns
--- log_entries was append-only via the original log_entries_immutable trigger
--- (migration 006). The proposal lifecycle (task #42) needs to mutate state,
--- outcome, status_rx, and rx when a proposal resolves from 'proposed' to
--- 'resolved' / 'failed' / 'cancelled'. The other columns stay immutable
--- (audit invariant: the original action's identity and target never change).
---
--- Replaces the single blanket UPDATE trigger with a column-scoped one that
--- only fires when genuinely-immutable fields are touched.
-DROP TRIGGER IF EXISTS log_entries_immutable;
-
-CREATE TRIGGER log_entries_immutable_core
-BEFORE UPDATE OF
-    run_id, loop_id, turn_id, action_index, at, origin,
-    op, suffix, signal,
-    target_scheme, target_username, target_password, target_hostname,
-    target_port, target_pathname, target_params, target_fragment,
-    lineMarker, tx, mimetype_tx, mimetype_rx, attrs
-ON log_entries
-BEGIN
-    SELECT RAISE(ABORT, 'log_entries core fields are immutable; only state/outcome/status_rx/rx may change (proposal lifecycle)');
-END;

package/migrations/014_loop_flags.sql

@@ -1,9 +0,0 @@
--- INIT: loop_flags
--- Persists per-loop flags (mode, yolo, noWeb, noInteraction, noProposals)
--- declared in src/core/scheme-types.ts. Per-loop scope matches task #43's
--- design; runs may scope this longer in a future iteration.
---
--- Defaults to '{}' so existing loops read as all-false via the merge with
--- DEFAULT_LOOP_FLAGS in application code.
-ALTER TABLE loops ADD COLUMN flags TEXT NOT NULL DEFAULT '{}'
-    CHECK (json_valid(flags));

package/migrations/015_sessions_project_root.sql

@@ -1,6 +0,0 @@
--- INIT: sessions_project_root
--- Adds the workspace pointer column to sessions per AGENTS.md §Phase F.1.
--- Nullable: NULL = headless (engine runs entries-only, no disk side-effects);
--- non-null = absolute path to the client's source tree, supplied at
--- session.create or session.set_root. Server never guesses.
-ALTER TABLE sessions ADD COLUMN project_root TEXT;

package/migrations/016_persona_columns.sql

@@ -1,11 +0,0 @@
--- INIT: persona_columns
--- Three-level persona cascade (issue #150). packet.system.persona is
--- resolved at packet-build time by taking the first non-null value of:
---   loops.persona > runs.persona > sessions.persona > PATHS.defaultPersona
---
--- Nullable everywhere; null means "fall through to the next level." The
--- file-based default catches the case where no level was set via RPC.
--- Persona content is text/markdown per @plurnk/plurnk-grammar Packet.json.
-ALTER TABLE sessions ADD COLUMN persona TEXT;
-ALTER TABLE runs     ADD COLUMN persona TEXT;
-ALTER TABLE loops    ADD COLUMN persona TEXT;