@team-semicolon/semicolony-cli 4.18.51

package/migrations/110_kb_manager_skill_l2_cleanup.sql

@@ -0,0 +1,34 @@
+-- 110: kb-manager 스킬 프롬프트 L2 leakage 정리
+-- migrations 027/031 가 skill_definitions(name='kb-manager') 의 prompt 에
+-- 'reus' (팀원 닉네임), 'by-buyer' (세미콜론 L2 서비스), 그리고 027 의 경우
+-- '/Users/reus/Desktop/Sources/...' 하드코딩 경로까지 박아 두었다.
+-- 027/031 인라인 텍스트는 일반화 (이 migration 시리즈와 함께 적용),
+-- 기존 인스턴스의 row 는 이 migration 이 정확 매칭일 때만 갱신.
+--
+-- 관련 인벤토리: docs/L2-INVENTORY.md (HIGH — kb-manager skill_definitions row)
+
+BEGIN;
+
+UPDATE semicolony.skill_definitions
+SET
+  prompt = REPLACE(
+    REPLACE(
+      REPLACE(
+        REPLACE(
+          REPLACE(prompt,
+            'semicolony kb get semicolon team reus', 'semicolony kb get <org> team alice'),
+          'semicolony kb get by-buyer po', 'semicolony kb get my-service po'),
+        'semicolony kb search "PO" --service by-buyer', 'semicolony kb search "PO" --service my-service'),
+      'semicolony kb upsert semicolon decision 2026-03-24/example', 'semicolony kb upsert <org> decision 2026-03-24/example'),
+    'export SEMICOLONY_ROOT="/Users/reus/Desktop/Sources/semicolon/projects/semicolony"\ncd $SEMICOLONY_ROOT/packages/cli\n', ''
+  ),
+  updated_at = NOW()
+WHERE name = 'kb-manager'
+  AND office_id IS NULL
+  AND (
+    prompt LIKE '%semicolony kb get semicolon team reus%'
+    OR prompt LIKE '%--service by-buyer%'
+    OR prompt LIKE '%/Users/reus/Desktop/Sources/semicolon/projects/semicolony%'
+  );
+
+COMMIT;

package/migrations/111_drop_l2_team_ontology_seeds.sql

@@ -0,0 +1,20 @@
+-- 111: 030 이 시드한 세미콜론 팀원 ontology rows 정리
+-- migration 030 가 OSS fresh install 시 세미콜론 팀원 10명 (reus, garden, roki, yeomso,
+-- bon, kyago, bae, harry, goni, kai) 의 ontology row 를 자동 시드했음.
+-- 030 인라인은 이 migration 시리즈와 함께 INSERT 블록 제거.
+-- 기존 인스턴스에서 이미 시드된 row 는 KB 데이터가 0건일 때만 삭제 (108 과 동일 패턴).
+--
+-- 관련 인벤토리: docs/L2-INVENTORY.md (HIGH — migration 030 team seeds)
+
+BEGIN;
+
+DELETE FROM semicolony.ontology o
+WHERE o.domain IN (
+  'reus','garden','roki','yeomso','bon','kyago','bae','harry','goni','kai'
+)
+  AND o.entity_type IN ('team', 'person')
+  AND NOT EXISTS (
+    SELECT 1 FROM semicolony.knowledge_base kb WHERE kb.domain = o.domain
+  );
+
+COMMIT;

package/migrations/112_fix_pipeline_schema_and_role_trigger.sql

@@ -0,0 +1,83 @@
+-- 112: pipeline 키 스키마 정합화 + role/po 트리거 services 드리프트 복구
+--
+-- 두 이슈 동시 수정:
+--   1. `semicolony kb upsert <domain> role po` 가 `relation "semicolony.services" does not exist` 로 실패
+--      (migration 072 가 만든 trg_sync_role_po 트리거가 migration 101 에서 DROP 된 services 테이블을 참조)
+--   2. service 타입 `pipeline` 키가 schema=singleton 이지만 실제 데이터는 sub_key='config' (migration-100 이식 + SoT 문서)
+--      → 신규 도메인 등록 시 sub_key='' 로 들어가 도메인 간 형태 갈라짐
+--
+-- KB 트래킹:
+--   - semicolony process kb-role-upsert-services-drift  (2026-04-27)
+--   - semicolony process pipeline-key-schema-sot-mismatch (2026-04-27)
+--
+-- 선행 조건: 111
+
+BEGIN;
+
+-- ============================================================
+-- 1. role/po 동기화 트리거 재구성: services 테이블 → KB pipeline/config metadata
+-- ============================================================
+-- 기존 트리거는 DROP 된 semicolony.services.owner_name 을 UPDATE 하려 해서 항상 실패.
+-- pipeline/config metadata.owner_name 이 이제 SoT 이므로 그곳을 업데이트한다.
+-- 무한 재귀 방지: pipeline/config 업데이트는 key='role' 조건과 매칭되지 않으므로 트리거 재진입 없음.
+
+DROP TRIGGER IF EXISTS trg_sync_role_po ON semicolony.knowledge_base;
+
+CREATE OR REPLACE FUNCTION semicolony.sync_role_po_to_owner()
+RETURNS TRIGGER AS $$
+DECLARE
+  _owner text;
+BEGIN
+  IF NEW.key = 'role' AND NEW.sub_key = 'po' THEN
+    _owner := TRIM(SPLIT_PART(NEW.content, ',', 1));
+    UPDATE semicolony.knowledge_base
+       SET metadata  = jsonb_set(COALESCE(metadata, '{}'::jsonb), '{owner_name}', to_jsonb(_owner), true),
+           updated_at = NOW()
+     WHERE domain = NEW.domain
+       AND key = 'pipeline'
+       AND sub_key = 'config';
+  END IF;
+  RETURN NEW;
+END;
+$$ LANGUAGE plpgsql;
+
+CREATE TRIGGER trg_sync_role_po
+  AFTER INSERT OR UPDATE ON semicolony.knowledge_base
+  FOR EACH ROW
+  WHEN (NEW.key = 'role' AND NEW.sub_key = 'po')
+  EXECUTE FUNCTION semicolony.sync_role_po_to_owner();
+
+-- ============================================================
+-- 2. pipeline 키 schema: singleton → collection (sub_key='config' SoT)
+-- ============================================================
+-- 기존 17개 도메인은 sub_key='config' 로 존재 (migration-100).
+-- service-metadata-sot 문서, 글로벌 CLAUDE.md, 코드(channel-router, dashboard 등)
+-- 모두 'pipeline/config' 를 가정. schema 만 어긋나 있어 schema 를 데이터에 맞춘다.
+
+UPDATE semicolony.kb_type_schema
+   SET key_type = 'collection',
+       value_hint = 'sub_key=''config'' 고정. metadata: {service_id, project_name, owner_name, current_phase, infra_phase, status, lifecycle, service_type, parent_service_id, tech_stack, service_url, repo, slack_channel, launched_at, ...}',
+       scheme_description = '프로젝트 파이프라인 워크플로우 상태 (sub_key=''config'' 단일 사용)'
+ WHERE type_key = 'service'
+   AND scheme_key = 'pipeline';
+
+-- ============================================================
+-- 3. 신규 등록 도메인 백필: pipeline (sub_key='') → pipeline/config
+-- ============================================================
+-- migration-100 이후 등록되었지만 schema=singleton 강제로 sub_key='' 로 들어간 행을
+-- sub_key='config' 로 이동. 충돌 시(이미 config 가 있으면) sub_key='' 행은 그대로 두고
+-- 사람이 확인 후 정리하도록 남긴다.
+
+UPDATE semicolony.knowledge_base AS kb
+   SET sub_key = 'config',
+       updated_at = NOW()
+ WHERE key = 'pipeline'
+   AND sub_key = ''
+   AND NOT EXISTS (
+     SELECT 1 FROM semicolony.knowledge_base kb2
+      WHERE kb2.domain = kb.domain
+        AND kb2.key = 'pipeline'
+        AND kb2.sub_key = 'config'
+   );
+
+COMMIT;

package/migrations/113_kb_history.sql

@@ -0,0 +1,53 @@
+-- 113_kb_history.sql
+-- P1-5: KB 변경 이력 — knowledge_base 의 INSERT/UPDATE/DELETE 자동 기록
+--
+-- 목적: context push / kb upsert 가 잘못된 값으로 덮어썼을 때 롤백·감사·diff 분석 가능.
+-- snapshot 형식: kb_snapshot JSONB 에 OLD/NEW 행 통째 직렬화 (스키마 확장에 robust).
+
+CREATE TABLE IF NOT EXISTS semicolony.knowledge_base_history (
+  history_id BIGSERIAL PRIMARY KEY,
+  kb_id BIGINT,
+  operation TEXT NOT NULL CHECK (operation IN ('insert', 'update', 'delete')),
+  changed_by VARCHAR(100),
+  changed_at TIMESTAMPTZ DEFAULT NOW(),
+  -- INSERT/DELETE: 해당 행 통째. UPDATE: 변경 전(OLD) 행 통째.
+  kb_snapshot JSONB NOT NULL
+);
+
+CREATE INDEX IF NOT EXISTS idx_kb_history_kb_id
+  ON semicolony.knowledge_base_history(kb_id);
+CREATE INDEX IF NOT EXISTS idx_kb_history_changed_at
+  ON semicolony.knowledge_base_history(changed_at DESC);
+-- 도메인/키 검색 위해 JSONB 부분 인덱스 (kb_snapshot.domain / .key)
+CREATE INDEX IF NOT EXISTS idx_kb_history_domain_key
+  ON semicolony.knowledge_base_history(
+    (kb_snapshot->>'domain'),
+    (kb_snapshot->>'key')
+  );
+
+CREATE OR REPLACE FUNCTION semicolony.kb_history_trigger_fn() RETURNS trigger AS $$
+BEGIN
+  IF TG_OP = 'INSERT' THEN
+    INSERT INTO semicolony.knowledge_base_history(kb_id, operation, changed_by, kb_snapshot)
+      VALUES (NEW.kb_id, 'insert', NEW.created_by, to_jsonb(NEW));
+    RETURN NEW;
+  ELSIF TG_OP = 'UPDATE' THEN
+    INSERT INTO semicolony.knowledge_base_history(kb_id, operation, changed_by, kb_snapshot)
+      VALUES (OLD.kb_id, 'update', COALESCE(NEW.created_by, OLD.created_by), to_jsonb(OLD));
+    RETURN NEW;
+  ELSIF TG_OP = 'DELETE' THEN
+    INSERT INTO semicolony.knowledge_base_history(kb_id, operation, changed_by, kb_snapshot)
+      VALUES (OLD.kb_id, 'delete', OLD.created_by, to_jsonb(OLD));
+    RETURN OLD;
+  END IF;
+  RETURN NULL;
+END;
+$$ LANGUAGE plpgsql;
+
+DROP TRIGGER IF EXISTS kb_history_trigger ON semicolony.knowledge_base;
+CREATE TRIGGER kb_history_trigger
+  AFTER INSERT OR UPDATE OR DELETE ON semicolony.knowledge_base
+  FOR EACH ROW EXECUTE FUNCTION semicolony.kb_history_trigger_fn();
+
+COMMENT ON TABLE semicolony.knowledge_base_history IS
+  'P1-5: KB 변경 이력. AFTER INSERT/UPDATE/DELETE 트리거로 자동 기록.';

package/migrations/114_runtime_target_columns.sql

@@ -0,0 +1,26 @@
+-- 114_runtime_target_columns.sql
+-- P5-6: ExecutionTarget / Runtime Portable DB 스키마 확장
+--
+-- 봇이 어떤 호스트에서 어떤 모델로 어떤 도구·투사 채널과 결합해 동작할지를
+-- DB SoT 로 표현. 기존 capability 는 packages/common/src/runtime 인터페이스에
+-- 코드로만 있었지만, 봇 인스턴스별 선호/제약은 DB 가 SoT.
+--
+-- 모든 컬럼 nullable — 기존 봇은 변경 없이 동작 (회귀 0).
+
+ALTER TABLE semicolony.bot_status
+  ADD COLUMN IF NOT EXISTS runtime_hint TEXT[],
+  ADD COLUMN IF NOT EXISTS tool_capabilities TEXT[],
+  ADD COLUMN IF NOT EXISTS projection_targets JSONB;
+
+COMMENT ON COLUMN semicolony.bot_status.runtime_hint IS
+  'P5-6: 선호 호스트 우선순위 배열. 예: [''claude-code'', ''codex-cli'', ''ollama-cli'']. RuntimeHarness 가 첫 번째 사용 가능 host 선택.';
+
+COMMENT ON COLUMN semicolony.bot_status.tool_capabilities IS
+  'P5-6: 봇이 호출 가능한 도구 이름 배열. ToolGateway register 결과와 매칭. 예: [''kb_get'', ''kb_upsert'', ''commitments_create''].';
+
+COMMENT ON COLUMN semicolony.bot_status.projection_targets IS
+  'P5-6: 기본 투사 타깃 JSONB 배열. 예: [{"channel":"slack-block","destination":"C123","options":{"botId":"semiclaw"}}]. ProjectionEmitter.emitAll 에 전달.';
+
+-- 인덱스 — runtime_hint 로 호스트별 봇 조회 자주 발생 시
+CREATE INDEX IF NOT EXISTS idx_bot_status_runtime_hint
+  ON semicolony.bot_status USING GIN (runtime_hint);

package/migrations/115_runtime_source_columns.sql

@@ -0,0 +1,52 @@
+-- 115_runtime_source_columns.sql
+-- 2026-05-06: OpenClaw + slack-router 공존 운영 — runtime_source 메타 추가.
+-- Codex review (semicolon-plan-review): "두 운영 루프가 commitments/cron 공유 시
+-- source 구분 필수. 최소값: slack-router | openclaw | manual | cron"
+--
+-- 모든 컬럼 nullable — 회귀 0. 기존 row 는 source_type 기반 추론 backfill.
+
+-- ── bot_commitments ──
+ALTER TABLE semicolony.bot_commitments
+  ADD COLUMN IF NOT EXISTS runtime_source TEXT;
+
+COMMENT ON COLUMN semicolony.bot_commitments.runtime_source IS
+  '운영 런타임 출처. slack-router | openclaw | manual | cron. 2026-05-06 추가 (KB semicolony decision/openclaw-architecture-b-coexist).';
+
+-- backfill: source_type → runtime_source 추론
+UPDATE semicolony.bot_commitments
+SET runtime_source = CASE
+  WHEN source_type = 'slack-inbox' THEN 'slack-router'
+  WHEN source_type = 'cron' THEN 'cron'
+  WHEN source_type = 'claude-code-local' THEN 'manual'
+  WHEN source_type LIKE 'openclaw%' THEN 'openclaw'
+  ELSE NULL
+END
+WHERE runtime_source IS NULL;
+
+CREATE INDEX IF NOT EXISTS idx_bot_commitments_runtime_source
+  ON semicolony.bot_commitments (runtime_source)
+  WHERE runtime_source IS NOT NULL;
+
+-- ── bot_cron_jobs ──
+ALTER TABLE semicolony.bot_cron_jobs
+  ADD COLUMN IF NOT EXISTS runtime_source TEXT;
+
+COMMENT ON COLUMN semicolony.bot_cron_jobs.runtime_source IS
+  '잡을 fire 하는 런타임. cron(=cron-poller, Architecture B) | openclaw(=OpenClaw 자체 cron) | manual.';
+
+-- 기본 backfill: 기존 cron 잡은 cron-poller 가 fan-out 하던 것이므로 'cron'
+UPDATE semicolony.bot_cron_jobs
+SET runtime_source = 'cron'
+WHERE runtime_source IS NULL;
+
+-- ── action_items ──
+ALTER TABLE semicolony.action_items
+  ADD COLUMN IF NOT EXISTS runtime_source TEXT;
+
+COMMENT ON COLUMN semicolony.action_items.runtime_source IS
+  '액션 아이템 생성 런타임. slack-router | openclaw | manual | cron.';
+
+-- 기본 backfill: 기존 action_item 은 사용자 직접 / 봇이 만든 것이라 'manual'
+UPDATE semicolony.action_items
+SET runtime_source = 'manual'
+WHERE runtime_source IS NULL;

package/migrations/116_commitment_pattern_health.sql

@@ -0,0 +1,81 @@
+-- 116_commitment_pattern_health.sql
+-- 2026-05-06: PAL 스타일 패턴 단위 실패 누적 추적 (C3 of Ouroboros adoption).
+-- Ouroboros routing/escalation.py 의 EscalationManager 패턴을 SEMICOLONY 에 변형 차용.
+-- 검증 근거: /tmp/ouroboros-sandbox/evidence/c3_results.json — 실 SEMICOLONY failed
+-- commitment 500개 replay 시 16 escalation + 432 stagnation, 7 cron 패턴이 Frontier
+-- 까지 도달 (cron poller 250x, commitment-watchdog 71x 등 침묵 실패 누적).
+--
+-- 이번 마이그레이션은 추적 스키마만 도입한다. 알림 부수효과(Slack DM, #bot-ops 포스팅)
+-- 는 PR2 에서 슬랙 라우터에 부착. 이 PR 은 신호를 DB 에 적재하고, fail/done 전이에서
+-- 카운터를 갱신하는 데까지만 한다 — 회귀 0.
+
+-- ── pattern health 추적 ─────────────────────────────────────────────────────
+CREATE TABLE IF NOT EXISTS semicolony.commitment_pattern_health (
+  -- 패턴 키: "{bot_id}::{canonical_prefix}#{hash}".
+  --   - canonical_prefix: title 을 NFKC + invisibles strip + whitespace collapse +
+  --     lowercase 후 첫 60 code point.
+  --   - hash: sha256(canonical title) 의 첫 10 hex — prefix 가 같지만 본문이 다른
+  --     title 들을 분리.
+  -- 키 생성/정규화 SoT 는 packages/cli/src/commitment-escalation.ts.
+  pattern_id TEXT PRIMARY KEY,
+
+  bot_id TEXT NOT NULL,
+  title_prefix TEXT NOT NULL,
+
+  consecutive_failures INTEGER NOT NULL DEFAULT 0
+    CHECK (consecutive_failures >= 0),
+
+  last_failure_at TIMESTAMPTZ,
+  last_success_at TIMESTAMPTZ,
+
+  -- 에스컬레이션 상태머신: none → notified (2 fails) → paged (5 fails)
+  -- 성공 시 즉시 'none' 으로 리셋. 알림 부수효과는 PR2.
+  state TEXT NOT NULL DEFAULT 'none'
+    CHECK (state IN ('none', 'notified', 'paged')),
+
+  -- 상태 전환을 마지막으로 관측한 시각. 진단/대시보드용.
+  -- ⚠ 알림 dedup 용도로는 신뢰하지 말 것 — 동시 실패 호출 시 두 트랜잭션 모두
+  --   "전이 발생" 으로 관측될 수 있다. PR2 에서 별도 claim 컬럼 또는
+  --   notification dedup 테이블로 idempotency 를 잡는다.
+  state_changed_at TIMESTAMPTZ NOT NULL DEFAULT NOW(),
+
+  created_at TIMESTAMPTZ NOT NULL DEFAULT NOW(),
+  updated_at TIMESTAMPTZ NOT NULL DEFAULT NOW()
+);
+
+COMMENT ON TABLE semicolony.commitment_pattern_health IS
+  '봇 약속의 (bot_id, title_prefix) 패턴별 연속 실패 누적과 에스컬레이션 상태. '
+  'Ouroboros C3 (PAL escalation 변형). 2026-05-06 추가.';
+
+COMMENT ON COLUMN semicolony.commitment_pattern_health.pattern_id IS
+  '"{bot_id}::{canonical_prefix}#{sha256_10}". canonical = NFKC + invisibles strip + '
+  'whitespace collapse + lowercase. SoT: packages/cli/src/commitment-escalation.ts.';
+
+COMMENT ON COLUMN semicolony.commitment_pattern_health.state IS
+  'none | notified (2회 연속 실패) | paged (5회 연속 실패). '
+  '성공 1회로 즉시 none 으로 reset.';
+
+-- 활성 escalation 모니터링 인덱스 — paged 상태 패턴이 가장 시급.
+CREATE INDEX IF NOT EXISTS idx_commitment_pattern_health_active_state
+  ON semicolony.commitment_pattern_health (state, last_failure_at DESC)
+  WHERE state <> 'none';
+
+-- bot 별 health 조회 (대시보드용).
+CREATE INDEX IF NOT EXISTS idx_commitment_pattern_health_bot_id
+  ON semicolony.commitment_pattern_health (bot_id);
+
+-- updated_at 자동 갱신 트리거 — bot_commitments 와 동일 컨벤션.
+CREATE OR REPLACE FUNCTION semicolony.fn_commitment_pattern_health_updated_at()
+RETURNS TRIGGER AS $$
+BEGIN
+  NEW.updated_at := NOW();
+  RETURN NEW;
+END;
+$$ LANGUAGE plpgsql;
+
+DROP TRIGGER IF EXISTS trg_commitment_pattern_health_updated
+  ON semicolony.commitment_pattern_health;
+
+CREATE TRIGGER trg_commitment_pattern_health_updated
+  BEFORE UPDATE ON semicolony.commitment_pattern_health
+  FOR EACH ROW EXECUTE FUNCTION semicolony.fn_commitment_pattern_health_updated_at();

package/migrations/117_commitment_pattern_alert_claims.sql

@@ -0,0 +1,33 @@
+-- 117_commitment_pattern_alert_claims.sql
+-- 2026-05-06: PR2 of Ouroboros C3 — alert claim 컬럼 추가.
+--
+-- PR1 은 state 전환을 추적했지만 (notified/paged), 동시 실패 호출 시 두 caller
+-- 모두 state_changed=true 를 관측할 수 있다 (CTE old 가 pre-lock 값을 읽음).
+-- 알림 부수효과는 race-safe 가 아니라는 뜻이다.
+--
+-- PR2 는 DB-backed claim 으로 idempotency 를 잡는다:
+--   - notified_at: 'notified' 상태 진입 후 첫 성공한 claim 시각.
+--   - paged_at: 'paged' 상태 진입 후 첫 성공한 claim 시각.
+-- claim 패턴: UPDATE … SET notified_at = NOW() WHERE pattern_id = $1
+--             AND state = 'notified' AND notified_at IS NULL RETURNING …;
+-- 첫 caller 만 row 를 받고 (rowCount=1), 나머지는 0 — 이게 알림 발송 권한.
+--
+-- success 시 (state → 'none') 두 컬럼 모두 NULL 로 reset 해서, 다음 회복-실패
+-- 사이클에서 새 claim 가능.
+
+ALTER TABLE semicolony.commitment_pattern_health
+  ADD COLUMN IF NOT EXISTS notified_at TIMESTAMPTZ,
+  ADD COLUMN IF NOT EXISTS paged_at TIMESTAMPTZ;
+
+COMMENT ON COLUMN semicolony.commitment_pattern_health.notified_at IS
+  '"notified" 상태 진입 후 첫 알림 claim 시각. 알림 dedup 용 — '
+  'UPDATE … WHERE notified_at IS NULL RETURNING 으로 atomic 발송 권한 결정.';
+
+COMMENT ON COLUMN semicolony.commitment_pattern_health.paged_at IS
+  '"paged" 상태 진입 후 첫 알림 claim 시각. notified_at 와 동일한 dedup 패턴.';
+
+-- 미발송 alert 빠르게 찾기.
+CREATE INDEX IF NOT EXISTS idx_commitment_pattern_health_pending_alert
+  ON semicolony.commitment_pattern_health (state, last_failure_at DESC)
+  WHERE (state = 'notified' AND notified_at IS NULL)
+     OR (state = 'paged' AND paged_at IS NULL);

package/migrations/118_retire_semiclaw_semicolonybot_alias.sql

@@ -0,0 +1,30 @@
+-- 118_retire_semiclaw_semicolonybot_alias
+--
+-- 2026-04-23 의 migration 104 가 'semiclaw → semicolonybot' 리브랜드 1단계로 alias 를 깔았다.
+-- 그러나 2026-05-06 의사결정(KB: semicolony decision/semicolonybot-independent-agent-2026-05-06)으로
+-- SemiColonyBot 은 SemiClaw 의 후계가 아니라 별 system_guide 에이전트로 분리되었다.
+--
+-- 현재 alias 가 살아 있는 동안에는:
+--   * channel-router 의 모든 'semiclaw' 입력(직접 [Route: semiclaw] / 하드코딩된
+--     orchestrator 폴백 / phase 폴백 등)이 'semicolonybot' 으로 재라우팅된다.
+--   * SemiColonyBot 의 runtime_source 는 'slack-router-system' (persona only, inbox 없음).
+--   * 결과적으로 orchestrator 트래픽이 처리 불능 상태로 빠지는 잠재적 버그.
+--
+-- 본 마이그레이션은 alias 를 retire(soft delete) 한다. 향후 다시 켜고 싶다면
+-- retired_at = NULL 로 되돌리면 된다. 'orphan' 로 보존되는 row 자체는 삭제하지
+-- 않는다 (감사용).
+--
+-- 별 후속 정리 항목 (이 PR 범위 밖):
+--   * SemiColonyBot bot_status row 의 role 을 'orchestrator' → 'system_management' 로 정리
+--   * SemiColonyBot 의 bot_delegation 행들(SemiClaw 복제) 정리 — persona only 이므로 위임 불필요
+--   * SemiColonyBot 의 seat_id (snamanager0) 가 다른 봇에 할당되지 않은 sanity check
+
+BEGIN;
+
+UPDATE semicolony.bot_id_aliases
+SET retired_at = NOW()
+WHERE alias = 'semiclaw'
+  AND canonical_bot_id = 'semicolonybot'
+  AND retired_at IS NULL;
+
+COMMIT;

package/migrations/119_commitment_events.sql

@@ -0,0 +1,51 @@
+-- 119_commitment_events
+--
+-- Ouroboros C5 — Event Replay (dual-write phase).
+-- 자세한 설계: /tmp/ouroboros-sandbox/evidence/c5_schema_draft.md (action item 4b406bbd)
+--   · taxonomy: 8 종 — commitment_created/status_changed/heartbeat/step_done/
+--     claimed/released/stale_reaped/cron_run_recorded
+--   · idempotency_key UNIQUE — 같은 이벤트 재기록 방지 (재시도 흡수)
+--   · transaction boundary: EscalationQueryable 패턴 (caller 의 client 받아 같이 commit/rollback)
+--   · projector acceptance: 7일 dual-write 동안 divergence=0 이면 read source flip 검토
+--   · write failure policy: best-effort, 원본 mutation 차단하지 않음
+--
+-- 이 마이그레이션은 *append-only* 이벤트 로그를 만들 뿐이며, 기존 bot_commitments
+-- 의 read 경로는 건드리지 않는다. dual-write phase 동안에는 bot_commitments 가
+-- SoT, commitment_events 는 audit/replay 용 redundant write.
+
+BEGIN;
+
+CREATE TABLE IF NOT EXISTS semicolony.commitment_events (
+  event_id        BIGSERIAL PRIMARY KEY,
+  commitment_id   TEXT      NOT NULL,
+  event_type      TEXT      NOT NULL CHECK (event_type IN (
+    'commitment_created', 'status_changed', 'heartbeat', 'step_done',
+    'claimed', 'released', 'stale_reaped', 'cron_run_recorded'
+  )),
+  payload         JSONB     NOT NULL DEFAULT '{}'::jsonb,
+  occurred_at     TIMESTAMPTZ NOT NULL,
+  recorded_at     TIMESTAMPTZ NOT NULL DEFAULT NOW(),
+  bot_id          TEXT,
+  source_type     TEXT,
+  runtime_source  TEXT,
+  idempotency_key TEXT      NOT NULL,
+  UNIQUE (idempotency_key)
+);
+
+CREATE INDEX IF NOT EXISTS idx_commitment_events_by_commitment_time
+  ON semicolony.commitment_events (commitment_id, occurred_at);
+
+CREATE INDEX IF NOT EXISTS idx_commitment_events_recent
+  ON semicolony.commitment_events (recorded_at DESC);
+
+CREATE INDEX IF NOT EXISTS idx_commitment_events_by_bot_recent
+  ON semicolony.commitment_events (bot_id, recorded_at DESC)
+  WHERE bot_id IS NOT NULL;
+
+COMMENT ON TABLE semicolony.commitment_events IS
+  'Append-only event log for bot_commitments lifecycle (Ouroboros C5 dual-write phase, migration 119, 2026-05-06). '
+  'During dual-write phase, bot_commitments remains read source. After 7+ days '
+  'with zero replay divergences, read source flips to events table (separate PR). '
+  'Write failures are logged but do not block the original mutation.';
+
+COMMIT;

package/migrations/120_host_signals.sql

@@ -0,0 +1,51 @@
+-- 120_host_signals
+--
+-- BE-1 v2 — host filesystem signal snapshots for /api/system/health.
+-- 액션아이템 3ac42503 의 후속 인프라.
+--
+-- 배경:
+--   semicolony-dashboard (Next.js) 는 OKE Docker pod 안에서 동작 → host 의 pgrep / PID 파일 /
+--   ~/.openclaw-{bot}/auth-profiles.json / log 파일에 직접 접근 불가.
+--
+--   따라서 v2 는 push 모델로 동작:
+--     1. host(=Reus Mac mini) 에서 동작하는 sidecar daemon (별 트랙) 이 pgrep/PID/auth
+--        파일을 주기적으로 스캔
+--     2. 결과 스냅샷을 이 테이블에 UPSERT
+--     3. dashboard /api/system/health 는 이 테이블을 읽어 신선한 (recorded_at >
+--        NOW() - 5min) 행만 client 응답에 포함
+--
+-- v1 (DB-only) 와 호환: 이 테이블이 비어있어도 API 는 정상 동작 (host_signals=null/empty).
+
+BEGIN;
+
+CREATE TABLE IF NOT EXISTS semicolony.host_signals (
+  id            BIGSERIAL PRIMARY KEY,
+  source_host   TEXT NOT NULL,            -- 예: 'reus-mac-mini' — sidecar self-id
+  signal_type   TEXT NOT NULL CHECK (signal_type IN (
+    'process',          -- pgrep 결과 (slack-router/discord-router/openclaw-gateway)
+    'pid_file',         -- ~/.semicolony/run/*.pid 살아있는 PID
+    'auth_profile',     -- auth-profiles.json expires + token 형식
+    'log_grep',         -- 로그 패턴 매칭 (Slack connected/socket failed 등)
+    'ancestry'          -- ps PPID/TTY 검증 (cmux ancestry 가드와 동일)
+  )),
+  target_id     TEXT NOT NULL,            -- bot_id 또는 process 이름 (예: 'slack-router', 'planclaw')
+  status        TEXT NOT NULL CHECK (status IN ('ok', 'degraded', 'fail', 'expired', 'unknown')),
+  payload       JSONB NOT NULL DEFAULT '{}'::jsonb,  -- pid, ppid, tty, expires_at, log_tail 등 구체적인 값
+  observed_at   TIMESTAMPTZ NOT NULL,     -- sidecar 가 관측한 실제 시점
+  recorded_at   TIMESTAMPTZ NOT NULL DEFAULT NOW(),
+  expires_at    TIMESTAMPTZ,              -- 명시적 TTL — 없으면 freshness 만 사용
+  UNIQUE (source_host, signal_type, target_id)
+);
+
+CREATE INDEX IF NOT EXISTS idx_host_signals_recent
+  ON semicolony.host_signals (recorded_at DESC);
+
+CREATE INDEX IF NOT EXISTS idx_host_signals_target
+  ON semicolony.host_signals (target_id, signal_type, recorded_at DESC);
+
+COMMENT ON TABLE semicolony.host_signals IS
+  'Host-level filesystem/process signals pushed by sidecar daemons. '
+  'semicolony-dashboard reads only — write path is sidecar (host-resident) '
+  'because dashboard pod has no host fs/process access. Migration 120, 2026-05-07.';
+
+COMMIT;

package/migrations/121_agent_spec_derived_runtime_metadata.sql

@@ -0,0 +1,68 @@
+-- 121_agent_spec_derived_runtime_metadata
+--
+-- AgentSpec projection metadata for derived/helper bots.
+--
+-- derived_from:
+--   Canonical source bot for derived runtime sessions such as semiclaw-overflow.
+--
+-- reply_as:
+--   Persona/bot id used when a derived runtime should reply as another bot.
+--   Example: semiclaw-overflow has bot_id=semiclaw-overflow but reply_as=semiclaw.
+
+BEGIN;
+
+ALTER TABLE semicolony.bot_status
+  ADD COLUMN IF NOT EXISTS derived_from TEXT REFERENCES semicolony.bot_status(bot_id),
+  ADD COLUMN IF NOT EXISTS reply_as     TEXT REFERENCES semicolony.bot_status(bot_id);
+
+COMMENT ON COLUMN semicolony.bot_status.derived_from IS
+  'Source bot id for derived/helper runtime sessions rendered through AgentSpec.';
+
+COMMENT ON COLUMN semicolony.bot_status.reply_as IS
+  'Bot/persona id to use when a derived runtime replies externally.';
+
+INSERT INTO semicolony.bot_status (
+  bot_id,
+  name,
+  emoji,
+  role,
+  workspace_path,
+  status,
+  kb_domains,
+  budget_per_message,
+  slack_username,
+  slack_icon_emoji,
+  created_by_bot_id,
+  template_bot_id,
+  runtime_hint,
+  tool_capabilities,
+  projection_targets,
+  derived_from,
+  reply_as
+)
+SELECT
+  'semiclaw-overflow',
+  'SemiClaw Overflow',
+  emoji,
+  'Derived overflow worker for SemiClaw',
+  REPLACE(workspace_path, 'semiclaw', 'semiclaw-overflow'),
+  status,
+  kb_domains,
+  budget_per_message,
+  slack_username,
+  slack_icon_emoji,
+  '__genesis__',
+  'semiclaw',
+  runtime_hint,
+  tool_capabilities,
+  projection_targets,
+  'semiclaw',
+  'semiclaw'
+FROM semicolony.bot_status
+WHERE bot_id = 'semiclaw'
+ON CONFLICT (bot_id) DO UPDATE SET
+  derived_from = EXCLUDED.derived_from,
+  reply_as = EXCLUDED.reply_as,
+  template_bot_id = COALESCE(semicolony.bot_status.template_bot_id, EXCLUDED.template_bot_id);
+
+COMMIT;

package/migrations/122_agent_spec_derived_fk_policy.sql

@@ -0,0 +1,18 @@
+-- 122_agent_spec_derived_fk_policy
+--
+-- Derived/helper bot references must not block retirement/deletion of a source bot.
+-- If the source disappears, the derived runtime falls back to its own identity.
+
+BEGIN;
+
+ALTER TABLE semicolony.bot_status
+  DROP CONSTRAINT IF EXISTS bot_status_derived_from_fkey,
+  DROP CONSTRAINT IF EXISTS bot_status_reply_as_fkey;
+
+ALTER TABLE semicolony.bot_status
+  ADD CONSTRAINT bot_status_derived_from_fkey
+    FOREIGN KEY (derived_from) REFERENCES semicolony.bot_status(bot_id) ON DELETE SET NULL,
+  ADD CONSTRAINT bot_status_reply_as_fkey
+    FOREIGN KEY (reply_as) REFERENCES semicolony.bot_status(bot_id) ON DELETE SET NULL;
+
+COMMIT;

package/migrations/123_agent_spec_projection_skip_targets.sql

@@ -0,0 +1,24 @@
+-- 123_agent_spec_projection_skip_targets
+--
+-- Some bot_status rows are helper/runtime support identities, not full projected
+-- OpenClaw/ClaudeCode personas. Keep the policy in bot_status instead of
+-- hardcoding helper names in renderers.
+
+BEGIN;
+
+ALTER TABLE semicolony.bot_status
+  ADD COLUMN IF NOT EXISTS is_helper BOOLEAN NOT NULL DEFAULT FALSE,
+  ADD COLUMN IF NOT EXISTS skip_projection_targets TEXT[] NOT NULL DEFAULT '{}';
+
+COMMENT ON COLUMN semicolony.bot_status.is_helper IS
+  'True for helper/support bot identities that should not be treated as full projected personas.';
+
+COMMENT ON COLUMN semicolony.bot_status.skip_projection_targets IS
+  'AgentSpec runtime targets to skip for this bot_id. Values: claude-code, codex-skill, openclaw.';
+
+UPDATE semicolony.bot_status
+SET is_helper = TRUE,
+    skip_projection_targets = ARRAY['openclaw']
+WHERE bot_id = 'kb-sidekick';
+
+COMMIT;

package/migrations/124_bot_commitments_notify.sql

@@ -0,0 +1,26 @@
+-- P2-C (2026-05-28): bot_commitments 변경 NOTIFY trigger
+-- Dashboard 의 /api/bots/stream SSE handler 가 LISTEN 'semicolony_commitment_change' 로 받음.
+-- Payload: { id, bot_id, status, runtime_source, source_type }
+
+CREATE OR REPLACE FUNCTION semicolony.notify_bot_commitment_change()
+RETURNS TRIGGER AS $$
+DECLARE
+  payload JSON;
+BEGIN
+  payload := json_build_object(
+    'op', TG_OP,
+    'id', COALESCE(NEW.id, OLD.id),
+    'bot_id', COALESCE(NEW.bot_id, OLD.bot_id),
+    'status', COALESCE(NEW.status, OLD.status),
+    'runtime_source', COALESCE(NEW.runtime_source, OLD.runtime_source),
+    'source_type', COALESCE(NEW.source_type, OLD.source_type)
+  );
+  PERFORM pg_notify('semicolony_commitment_change', payload::text);
+  RETURN COALESCE(NEW, OLD);
+END;
+$$ LANGUAGE plpgsql;
+
+DROP TRIGGER IF EXISTS trig_bot_commitments_notify ON semicolony.bot_commitments;
+CREATE TRIGGER trig_bot_commitments_notify
+AFTER INSERT OR UPDATE OR DELETE ON semicolony.bot_commitments
+FOR EACH ROW EXECUTE FUNCTION semicolony.notify_bot_commitment_change();