@team-semicolon/semicolony-cli 4.18.51

package/migrations/027_kb_manager_skill.sql

@@ -0,0 +1,22 @@
+-- 027_kb_manager_skill.sql
+-- KB Manager 스킬을 skill_definitions에 등록
+-- 모든 봇이 semicolony CLI를 통해 KB에 접근할 수 있도록 함
+
+INSERT INTO skill_definitions (name, display_name, description, prompt, package, is_active, metadata, version)
+VALUES (
+  'kb-manager',
+  'KB Manager',
+  'SEMICOLONY KB 조회/검색/수정. semicolony CLI를 통해 팀 Knowledge Base에 접근.',
+  E'---\nname: kb-manager\ndescription: SEMICOLONY KB 조회/검색/수정. semicolony CLI를 통해 팀 Knowledge Base에 접근.\n---\n\n# KB Manager\n\n## 환경 설정\n```bash\nsource ~/.semicolony.env\n```\n\n## 명령어\n\n| 작업 | 명령어 |\n|------|--------|\n| 검색 | `semicolony kb search \"검색어\" --domain <domain> --format json` |\n| 정확 조회 | `semicolony kb get <domain> <key> [sub_key] --format json` |\n| 목록 | `semicolony kb list --domain <domain> --format json` |\n| 쓰기 | `semicolony kb upsert <domain> <key> [sub_key] --content \"내용\"` |\n| 온톨로지 | `semicolony kb ontology --action <action> --format json` |\n\n## 예시\n```bash\n# 팀원 조회\nsemicolony kb get <org> team alice\n\n# 서비스 PO 조회\nsemicolony kb get my-service po\n\n# 검색\nsemicolony kb search \"PO\" --service my-service\n\n# 의사결정 기록\nsemicolony kb upsert <org> decision 2026-03-24/example --content \"의사결정 내용\"\n\n# 라우팅 테이블 (저장 위치 판단용)\nsemicolony kb ontology --action routing-table --format json\n\n# 타입 스키마 조회\nsemicolony kb ontology --action schema --type service --format json\n\n# 서비스 인스턴스 목록\nsemicolony kb ontology --action instances --format json\n```\n\n## 규칙\n- psql 직접 쿼리 금지 — 반드시 이 명령어 사용 (임베딩 자동 생성, 스키마 검증)\n- 세션 인사이트 저장 시: ontology routing-table 먼저 확인 → 적절한 domain+key로 upsert\n- 도메인 구조가 불확실하면: ontology --action list 또는 ontology --action instances로 확인\n',
+  'core',
+  true,
+  '{"bot_ids": []}',
+  '2.0'
+)
+ON CONFLICT (name, office_id) DO UPDATE SET
+  prompt = EXCLUDED.prompt,
+  display_name = EXCLUDED.display_name,
+  description = EXCLUDED.description,
+  version = EXCLUDED.version,
+  metadata = EXCLUDED.metadata,
+  is_active = true;

package/migrations/028_skill_definitions_to_semicolony.sql

@@ -0,0 +1,19 @@
+-- 028: skill_definitions를 semicolony 스키마로 이식 + KB skill 엔트리 제거
+--
+-- 목적: semicolony.skill_definitions를 유일한 SoT로 확립
+-- 영향: CLI, 대시보드의 skill_definitions 참조를 semicolony 스키마로 전환
+--       KB에서 skill 키 엔트리 완전 제거 (56 rows)
+
+BEGIN;
+
+-- 1. public → semicolony 스키마 이동 (atomic, 인덱스/제약조건 보존)
+ALTER TABLE public.skill_definitions SET SCHEMA semicolony;
+
+-- 2. KB skill 엔트리 삭제 (56 rows)
+DELETE FROM semicolony.knowledge_base WHERE key = 'skill';
+
+-- 3. kb_type_schema에서 skill 스킴 제거
+DELETE FROM semicolony.kb_type_schema
+WHERE type_key = 'organization' AND scheme_key = 'skill';
+
+COMMIT;

package/migrations/029_agents_citation_max_lines.sql

@@ -0,0 +1,6 @@
+-- 029: AGENTS.md max_lines 150 → 155 (citation + 쓰기 고지 규칙 추가로 줄 수 증가)
+UPDATE semicolony.bot_workspace_standard
+SET content_rules = jsonb_set(content_rules, '{max_lines}', '155'),
+    updated_at = NOW()
+WHERE path_pattern = 'AGENTS.md'
+  AND spec_version = '2.0';

package/migrations/030_team_ontology.sql

@@ -0,0 +1,54 @@
+-- 030_team_ontology.sql
+-- team scheme_type 추가 + 팀원 10명 도메인 등록
+-- 액션아이템 추적용 KB 구조 기반
+--
+-- 변경 내용:
+--   1. ontology_types에 'team' 타입 추가
+--   2. kb_type_schema에 team 타입 허용 키 등록 (action-item, profile, preference)
+--   3. 팀원 10명 ontology 도메인 등록
+--
+-- 선행 조건: 022_kb_schema_enforcement.sql 적용 완료
+
+BEGIN;
+
+-- ============================================================
+-- 1. team 엔티티 타입 등록
+-- ============================================================
+
+INSERT INTO semicolony.ontology_types (type_key, schema, description) VALUES
+('team', '{
+  "type": "object",
+  "properties": {
+    "content": {"type": "string"},
+    "metadata": {
+      "type": "object",
+      "properties": {
+        "name": {"type": "string"},
+        "role": {"type": "string"},
+        "slack_id": {"type": "string"}
+      }
+    }
+  }
+}', '팀원 개인 도메인 — 액션아이템, 프로필, 선호 등')
+ON CONFLICT (type_key) DO NOTHING;
+
+-- ============================================================
+-- 2. team 타입 허용 키 등록 (kb_type_schema)
+-- ============================================================
+
+INSERT INTO semicolony.kb_type_schema (type_key, scheme_key, scheme_description, required, value_hint, sort_order, key_type)
+VALUES
+  ('team', 'action-item', '액션 아이템 추적',    false, 'action-item/current, action-item/2026-W13', 1, 'collection'),
+  ('team', 'profile',     '팀원 프로필',         false, '역할, 연락처, 선호 등',                       2, 'singleton'),
+  ('team', 'preference',  '팀원 업무 선호/스타일', false, '소통 선호, 업무 시간대 등',                    3, 'singleton')
+ON CONFLICT (type_key, scheme_key) DO NOTHING;
+
+-- ============================================================
+-- 3. 팀원 ontology 도메인 — 인스턴스별 수동 등록
+-- ============================================================
+-- 이 migration 은 'team' (이후 'person' 으로 통합 — 081 참조) 타입 스키마만 등록한다.
+-- 팀원 도메인 자체는 인스턴스별로 다르므로 `semicolony kb ontology --action register` 또는
+-- `semicolony onto register <name> --type person` 으로 직접 등록할 것.
+-- (이전 버전은 세미콜론 내부 팀원 10명 시드를 포함했으나 OSS 누출 방지를 위해 제거됨.)
+
+COMMIT;

package/migrations/031_gfp_tables.sql

@@ -0,0 +1,101 @@
+-- 031_gfp_tables.sql
+-- GFP (Greenfield Project Pipeline) v2 — Visual Planning Pipeline
+-- 4 tables: gfp_projects, gfp_phase_sections, gfp_materials, gfp_research_tasks
+--
+-- 선행 조건: semicolony schema 존재
+
+BEGIN;
+
+-- ============================================================
+-- 1. gfp_projects — 프로젝트 메타
+-- ============================================================
+
+CREATE TABLE IF NOT EXISTS semicolony.gfp_projects (
+  gfp_id          UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  project_name    VARCHAR(200) NOT NULL,
+  service_domain  VARCHAR(100),
+  owner_name      VARCHAR(100) NOT NULL,
+  owner_contact   VARCHAR(200),
+  current_phase   SMALLINT NOT NULL DEFAULT 0,
+  status          VARCHAR(20) NOT NULL DEFAULT 'active',
+  metadata        JSONB DEFAULT '{}',
+  created_at      TIMESTAMPTZ NOT NULL DEFAULT NOW(),
+  updated_at      TIMESTAMPTZ NOT NULL DEFAULT NOW()
+);
+
+-- ============================================================
+-- 2. gfp_phase_sections — 페이즈별 섹션 (핵심 테이블)
+-- ============================================================
+
+CREATE TABLE IF NOT EXISTS semicolony.gfp_phase_sections (
+  section_id    UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  gfp_id        UUID NOT NULL REFERENCES semicolony.gfp_projects(gfp_id) ON DELETE CASCADE,
+  phase         SMALLINT NOT NULL,
+  section_key   VARCHAR(100) NOT NULL,
+  title         VARCHAR(200) NOT NULL,
+  content       TEXT NOT NULL DEFAULT '',
+  ordinal       SMALLINT NOT NULL DEFAULT 0,
+  status        VARCHAR(20) NOT NULL DEFAULT 'draft',
+  reviewer_note TEXT,
+  source        VARCHAR(50) NOT NULL DEFAULT 'manual',
+  created_at    TIMESTAMPTZ NOT NULL DEFAULT NOW(),
+  updated_at    TIMESTAMPTZ NOT NULL DEFAULT NOW(),
+  UNIQUE(gfp_id, phase, section_key)
+);
+
+CREATE INDEX IF NOT EXISTS idx_gfp_sections_project
+  ON semicolony.gfp_phase_sections(gfp_id, phase, ordinal);
+
+-- ============================================================
+-- 3. gfp_materials — 사전 기획안 업로드
+-- ============================================================
+
+CREATE TABLE IF NOT EXISTS semicolony.gfp_materials (
+  material_id   UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  gfp_id        UUID NOT NULL REFERENCES semicolony.gfp_projects(gfp_id) ON DELETE CASCADE,
+  content       TEXT NOT NULL,
+  phase_mapping JSONB,
+  created_at    TIMESTAMPTZ NOT NULL DEFAULT NOW()
+);
+
+-- ============================================================
+-- 4. gfp_research_tasks — GrowthClaw 리서치
+-- ============================================================
+
+CREATE TABLE IF NOT EXISTS semicolony.gfp_research_tasks (
+  task_id        UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  gfp_id         UUID NOT NULL REFERENCES semicolony.gfp_projects(gfp_id) ON DELETE CASCADE,
+  task_type      VARCHAR(50) NOT NULL,
+  reference_urls TEXT[] DEFAULT '{}',
+  input_prompt   TEXT NOT NULL,
+  status         VARCHAR(20) NOT NULL DEFAULT 'queued',
+  result         TEXT,
+  created_at     TIMESTAMPTZ NOT NULL DEFAULT NOW(),
+  updated_at     TIMESTAMPTZ NOT NULL DEFAULT NOW()
+);
+
+-- ============================================================
+-- 5. updated_at 트리거
+-- ============================================================
+
+CREATE OR REPLACE FUNCTION semicolony.gfp_set_updated_at()
+RETURNS TRIGGER AS $$
+BEGIN
+  NEW.updated_at = NOW();
+  RETURN NEW;
+END;
+$$ LANGUAGE plpgsql;
+
+CREATE TRIGGER trg_gfp_projects_updated
+  BEFORE UPDATE ON semicolony.gfp_projects
+  FOR EACH ROW EXECUTE FUNCTION semicolony.gfp_set_updated_at();
+
+CREATE TRIGGER trg_gfp_sections_updated
+  BEFORE UPDATE ON semicolony.gfp_phase_sections
+  FOR EACH ROW EXECUTE FUNCTION semicolony.gfp_set_updated_at();
+
+CREATE TRIGGER trg_gfp_research_updated
+  BEFORE UPDATE ON semicolony.gfp_research_tasks
+  FOR EACH ROW EXECUTE FUNCTION semicolony.gfp_set_updated_at();
+
+COMMIT;

package/migrations/031_kb_manager_domain_register.sql

@@ -0,0 +1,12 @@
+-- 031_kb_manager_domain_register.sql
+-- kb-manager 스킬에 도메인 등록 프로토콜 추가
+-- CLI에 semicolony kb ontology --action register 명령어 추가에 맞춰 스킬 prompt 갱신
+--
+-- 변경 내용:
+--   1. skill_definitions의 kb-manager prompt 업데이트 (도메인 등록 섹션 추가)
+
+UPDATE semicolony.skill_definitions
+SET prompt = E'---\nname: kb-manager\ndescription: SEMICOLONY KB 조회/검색/수정. semicolony CLI를 통해 팀 Knowledge Base에 접근.\n---\n\n# KB Manager\n\n## 환경 설정\n```bash\nsource ~/.semicolony.env\n```\n\n## 명령어\n\n| 작업 | 명령어 |\n|------|--------|\n| 검색 | `semicolony kb search \"검색어\" --domain <domain>` |\n| 정확 조회 | `semicolony kb get <domain> <key> [sub_key]` |\n| 목록 | `semicolony kb list --domain <domain>` |\n| 쓰기 | `semicolony kb upsert <domain> <key> [sub_key] --content \"내용\"` |\n| 온톨로지 | `semicolony kb ontology --action <action>` |\n| 도메인 등록 | `semicolony kb ontology --action register --domain <name> --type <type>` |\n\n## 예시\n```bash\n# 팀원 조회\nsemicolony kb get <org> team alice\n\n# 서비스 PO 조회\nsemicolony kb get my-service po\n\n# 검색\nsemicolony kb search \"PO\" --service my-service\n\n# 의사결정 기록\nsemicolony kb upsert <org> decision 2026-03-24/example --content \"의사결정 내용\"\n\n# 라우팅 테이블 (저장 위치 판단용)\nsemicolony kb ontology --action routing-table\n\n# 타입 스키마 조회\nsemicolony kb ontology --action schema --type service\n\n# 서비스 인스턴스 목록\nsemicolony kb ontology --action instances\n```\n\n## 조회 프로토콜 (읽기)\n\n정확한 domain/key 경로를 모를 때:\n1. `semicolony kb search \"검색어\"` — 결과에서 `[domain] key/sub_key` 확인\n2. 결과의 full key 경로로 `semicolony kb get <domain> <key> <sub_key>` 실행\n\n도메인 자체를 모를 때:\n- `semicolony kb ontology --action instances` — 서비스 도메인 목록\n- `semicolony kb ontology --action routing-table` — 전체 domain→key 매핑\n\n## 저장 프로토콜 (쓰기)\n\n1. `semicolony kb ontology --action routing-table` — 저장 위치 확인\n2. `semicolony kb upsert <domain> <key> [sub_key] --content \"내용\"`\n\n## 도메인 등록 프로토콜\n\n새 도메인(서비스, 팀원, 봇 등)이 필요할 때:\n\n### Step 1: 타입 확인\n```bash\nsemicolony kb ontology --action types\n```\n사용 가능한 타입: service, team, person, bot, organization, decision, process 등\n\n### Step 2: 타입 스키마 확인 (필수 키 파악)\n```bash\nsemicolony kb ontology --action schema --type <type>\n```\n`*` 표시가 required 키 — 등록 시 자동으로 placeholder entry 생성됨\n\n### Step 3: 도메인 등록\n```bash\n# 기본 (필수 KB entry 자동 생성)\nsemicolony kb ontology --action register --domain <name> --type <type> --description \"설명\"\n\n# 서비스 그룹 지정\nsemicolony kb ontology --action register --domain <name> --type <type> --service <service> --description \"설명\"\n\n# 또는 onto 서브커맨드\nsemicolony onto register <name> --type <type> --description \"설명\"\n```\n\n### Step 4: 필수 데이터 입력\n등록 후 placeholder로 생성된 필수 키에 실제 데이터 입력:\n```bash\nsemicolony kb upsert <domain> <key> --content \"실제 내용\"\n```\n\n### 예시: 팀원 도메인 등록\n```bash\n# 1. team 타입 스키마 확인\nsemicolony kb ontology --action schema --type team\n\n# 2. 도메인 등록\nsemicolony kb ontology --action register --domain alice --type team --description \"Alice — 팀원\"\n\n# 3. 필수 데이터 입력\nsemicolony kb upsert alice profile --content \"역할: 프론트엔드 개발자\"\n```\n\n## 규칙\n- psql 직접 쿼리 금지 — 반드시 이 명령어 사용 (임베딩 자동 생성, 스키마 검증)\n- search 결과의 key/sub_key 경로를 그대로 get에 사용할 것\n- 도메인/키를 추측하지 말고 ontology 또는 search로 확인\n- 새 도메인 필요 시 반드시 ontology register로 등록 (직접 DB INSERT 금지)\n',
+    version = '3.0',
+    updated_at = NOW()
+WHERE name = 'kb-manager' AND office_id IS NULL;

package/migrations/032_gfp_skill_and_callback.sql

@@ -0,0 +1,40 @@
+-- 032_gfp_skill_and_callback.sql
+-- GFP 스킬 등록 + 봇 콜백을 위한 인프라
+--
+-- 1. gfp-manager 스킬 등록 (봇이 GFP 프로젝트/섹션 조회·수정 가능)
+-- 2. gfp_projects.service_domain → ontology 자동 등록을 위한 트리거
+-- 3. KB write-back 출처 추적을 위한 gfp_phase_sections.kb_written_at 컬럼
+
+BEGIN;
+
+-- ============================================================
+-- 1. gfp-manager 스킬 등록
+-- ============================================================
+
+INSERT INTO semicolony.skill_definitions (name, display_name, description, prompt, package, is_active, metadata, version)
+VALUES (
+  'gfp-manager',
+  'GFP Pipeline Manager',
+  'GFP(Greenfield Project Pipeline) 프로젝트 조회/섹션 수정/리서치 결과 반영. 봇이 GFP DB에 접근.',
+  E'---\nname: gfp-manager\ndescription: GFP(Greenfield Project Pipeline) 프로젝트 조회/섹션 수정/리서치 결과 반영.\n---\n\n# GFP Pipeline Manager\n\nGFP 프로젝트의 섹션 생성/수정, 리서치 결과 반영, 상태 변경을 위한 스킬.\n봇(PlanClaw, GrowthClaw 등)이 대시보드 API를 통해 GFP DB에 접근한다.\n\n## API Endpoints\n\nBase URL: `${SEMICOLONY_DASHBOARD_URL}` (default: http://localhost:3000)\n\n### 프로젝트 조회\n```bash\n# 프로젝트 목록\ncurl -s ${SEMICOLONY_DASHBOARD_URL}/api/gfp | jq\n\n# 프로젝트 상세 (progress 포함)\ncurl -s ${SEMICOLONY_DASHBOARD_URL}/api/gfp/{gfp_id} | jq\n```\n\n### 섹션 조회/수정\n```bash\n# 섹션 목록 (페이즈별)\ncurl -s \"${SEMICOLONY_DASHBOARD_URL}/api/gfp/{gfp_id}/sections?phase=1\" | jq\n\n# 섹션 생성/수정 (upsert)\ncurl -X POST ${SEMICOLONY_DASHBOARD_URL}/api/gfp/{gfp_id}/sections \\\n  -H \"Content-Type: application/json\" \\\n  -d ''{ \"phase\": 1, \"section_key\": \"overview\", \"title\": \"Overview\", \"content\": \"...\", \"status\": \"pending-review\", \"source\": \"planclaw\" }''\n\n# 섹션 내용 업데이트 (재생성 결과 반영)\ncurl -X PATCH ${SEMICOLONY_DASHBOARD_URL}/api/gfp/{gfp_id}/sections \\\n  -H \"Content-Type: application/json\" \\\n  -d ''{ \"section_id\": \"...\", \"action\": \"update-content\", \"content\": \"수정된 내용\", \"status\": \"pending-review\" }''\n```\n\n### 봇 콜백 (결과 반영)\n```bash\n# PlanClaw: 재생성 결과 반영\ncurl -X POST ${SEMICOLONY_DASHBOARD_URL}/api/gfp/callback \\\n  -H \"Content-Type: application/json\" \\\n  -d ''{ \"type\": \"section-regeneration\", \"section_id\": \"...\", \"content\": \"재생성된 내용\", \"bot_id\": \"planclaw\" }''\n\n# GrowthClaw: 리서치 결과 반영\ncurl -X POST ${SEMICOLONY_DASHBOARD_URL}/api/gfp/callback \\\n  -H \"Content-Type: application/json\" \\\n  -d ''{ \"type\": \"research-result\", \"task_id\": \"...\", \"result\": \"리서치 결과 마크다운\", \"bot_id\": \"growthclaw\" }''\n```\n\n### 리서치 작업\n```bash\n# 리서치 목록\ncurl -s ${SEMICOLONY_DASHBOARD_URL}/api/gfp/{gfp_id}/research | jq\n\n# 리서치 결과 업데이트\ncurl -X PATCH ${SEMICOLONY_DASHBOARD_URL}/api/gfp/{gfp_id}/research \\\n  -H \"Content-Type: application/json\" \\\n  -d ''{ \"task_id\": \"...\", \"status\": \"completed\", \"result\": \"리서치 결과\" }''\n```\n\n## 규칙\n- 섹션 수정 시 status를 반드시 \"pending-review\"로 설정 (PO 재검토 필요)\n- source 필드로 출처 명시: planclaw / growthclaw / imported / manual\n- 콜백 API 사용 시 bot_id 필수\n',
+  'core',
+  true,
+  '{"bot_ids": ["planclaw", "growthclaw"]}',
+  '1.0'
+)
+ON CONFLICT (name, office_id) DO UPDATE SET
+  prompt = EXCLUDED.prompt,
+  display_name = EXCLUDED.display_name,
+  description = EXCLUDED.description,
+  version = EXCLUDED.version,
+  metadata = EXCLUDED.metadata,
+  is_active = true;
+
+-- ============================================================
+-- 2. kb_written_at 컬럼 추가 (KB write-back 추적)
+-- ============================================================
+
+ALTER TABLE semicolony.gfp_phase_sections
+  ADD COLUMN IF NOT EXISTS kb_written_at TIMESTAMPTZ;
+
+COMMIT;

package/migrations/032_kebab_case_keys.sql

@@ -0,0 +1,33 @@
+-- 032_kebab_case_keys.sql
+-- KB 스키마 키 네이밍 컨벤션 통일: snake_case → kebab-case
+-- 영향: kb_type_schema (스키마 정의) + knowledge_base (실제 엔트리)
+
+BEGIN;
+
+-- ============================================================
+-- 1. kb_type_schema: 스키마 키 이름 변환
+-- ============================================================
+
+UPDATE semicolony.kb_type_schema SET scheme_key = 'base-information'    WHERE scheme_key = 'base_information';
+UPDATE semicolony.kb_type_schema SET scheme_key = 'current-situation'   WHERE scheme_key = 'current_situation';
+UPDATE semicolony.kb_type_schema SET scheme_key = 'service-url'         WHERE scheme_key = 'service_url';
+UPDATE semicolony.kb_type_schema SET scheme_key = 'tech-stack'          WHERE scheme_key = 'tech_stack';
+UPDATE semicolony.kb_type_schema SET scheme_key = 'slack-channel'       WHERE scheme_key = 'slack_channel';
+UPDATE semicolony.kb_type_schema SET scheme_key = 'gateway-config'      WHERE scheme_key = 'gateway_config';
+UPDATE semicolony.kb_type_schema SET scheme_key = 'cron-schedule'       WHERE scheme_key = 'cron_schedule';
+UPDATE semicolony.kb_type_schema SET scheme_key = 'slack-config'        WHERE scheme_key = 'slack_config';
+
+-- ============================================================
+-- 2. knowledge_base: 실제 엔트리 key 변환
+-- ============================================================
+
+UPDATE semicolony.knowledge_base SET key = 'base-information'    WHERE key = 'base_information';
+UPDATE semicolony.knowledge_base SET key = 'current-situation'   WHERE key = 'current_situation';
+UPDATE semicolony.knowledge_base SET key = 'service-url'         WHERE key = 'service_url';
+UPDATE semicolony.knowledge_base SET key = 'tech-stack'          WHERE key = 'tech_stack';
+UPDATE semicolony.knowledge_base SET key = 'slack-channel'       WHERE key = 'slack_channel';
+UPDATE semicolony.knowledge_base SET key = 'gateway-config'      WHERE key = 'gateway_config';
+UPDATE semicolony.knowledge_base SET key = 'cron-schedule'       WHERE key = 'cron_schedule';
+UPDATE semicolony.knowledge_base SET key = 'slack-config'        WHERE key = 'slack_config';
+
+COMMIT;

package/migrations/033_skill_workspace_rules.sql

@@ -0,0 +1,10 @@
+-- 033_skill_workspace_rules.sql
+-- 스킬 디렉토리 SKILL.md 검증 규칙을 bot_workspace_standard에 추가
+
+INSERT INTO semicolony.bot_workspace_standard
+  (path_pattern, entry_type, level, severity, category, bot_scope, content_rules, description, spec_version)
+VALUES
+  ('skills/*/SKILL.md', 'glob', 'required', 'warn', 'structure', 'all',
+   '{"max_lines": 500, "required_patterns": ["^---"]}',
+   '각 스킬에 SKILL.md 필수 (frontmatter + 500줄 이하)', '2.0')
+ON CONFLICT DO NOTHING;

package/migrations/034_current_to_date_keys.sql

@@ -0,0 +1,13 @@
+-- 034_current_to_date_keys.sql
+-- action-item, kpi: current 서브키 → 날짜 기반({YYYY-MM-DD}) 컨벤션으로 변경
+-- 기존 current 서브키를 폐기하고 날짜 기반 서브키로 통일
+
+-- action-item: value_hint 업데이트
+UPDATE semicolony.kb_type_schema
+SET value_hint = '날짜 기반 서브키 사용. 예: action-item/2026-03-29. 최신은 가장 큰 날짜로 조회.'
+WHERE scheme_key = 'action-item';
+
+-- kpi: value_hint 업데이트
+UPDATE semicolony.kb_type_schema
+SET value_hint = '날짜 기반 서브키 사용. 예: kpi/2026-03-29. 최신은 가장 큰 날짜로 조회.'
+WHERE scheme_key = 'kpi';

package/migrations/034_current_to_date_keys.ts

@@ -0,0 +1,104 @@
+#!/usr/bin/env npx tsx
+/**
+ * 034_current_to_date_keys.ts
+ *
+ * KB 데이터 마이그레이션: action-item/current, kpi/current → 날짜 기반 서브키
+ * - action-item/current → action-item/{YYYY-MM-DD} (updated_at 기준)
+ * - kpi/current → kpi/{YYYY-MM-DD} (updated_at 기준)
+ *
+ * 사용법:
+ *   npx tsx packages/cli/migrations/034_current_to_date_keys.ts [--dry-run]
+ */
+
+import pg from "pg";
+
+const DATABASE_URL = process.env.DATABASE_URL;
+
+if (!DATABASE_URL) {
+  console.error("DATABASE_URL 환경변수가 필요합니다");
+  process.exit(1);
+}
+
+const DRY_RUN = process.argv.includes("--dry-run");
+
+async function main() {
+  const pool = new pg.Pool({ connectionString: DATABASE_URL });
+
+  try {
+    // 1. action-item/current 엔트리 조회
+    const actionItems = await pool.query(`
+      SELECT kb_id, domain, key, sub_key, content, embedding, updated_at
+      FROM semicolony.knowledge_base
+      WHERE key = 'action-item' AND sub_key = 'current'
+    `);
+
+    console.log(`action-item/current 엔트리: ${actionItems.rows.length}건`);
+
+    // 2. kpi/current 엔트리 조회
+    const kpiItems = await pool.query(`
+      SELECT kb_id, domain, key, sub_key, content, embedding, updated_at
+      FROM semicolony.knowledge_base
+      WHERE key = 'kpi' AND sub_key = 'current'
+    `);
+
+    console.log(`kpi/current 엔트리: ${kpiItems.rows.length}건`);
+
+    const allItems = [...actionItems.rows, ...kpiItems.rows];
+
+    if (allItems.length === 0) {
+      console.log("마이그레이션 대상 없음");
+      return;
+    }
+
+    for (const row of allItems) {
+      const dateStr = new Date(row.updated_at).toISOString().split("T")[0]; // YYYY-MM-DD
+      const newSubKey = dateStr;
+
+      console.log(`  ${row.domain}/${row.key}/current → ${row.domain}/${row.key}/${newSubKey}`);
+
+      if (DRY_RUN) continue;
+
+      // 동일 날짜 서브키가 이미 존재하는지 확인
+      const existing = await pool.query(
+        `SELECT kb_id FROM semicolony.knowledge_base WHERE domain = $1 AND key = $2 AND sub_key = $3`,
+        [row.domain, row.key, newSubKey]
+      );
+
+      if (existing.rows.length > 0) {
+        // 이미 존재하면 current 엔트리만 삭제
+        console.log(`    (이미 ${newSubKey} 존재 — current만 삭제)`);
+      } else {
+        // 새 날짜 키로 INSERT
+        await pool.query(
+          `INSERT INTO semicolony.knowledge_base (domain, key, sub_key, content, embedding, metadata, version, created_by, updated_at)
+           SELECT domain, key, $1, content, embedding, metadata, version, created_by, updated_at
+           FROM semicolony.knowledge_base WHERE kb_id = $2`,
+          [newSubKey, row.kb_id]
+        );
+      }
+
+      // current 엔트리 삭제
+      await pool.query(
+        `DELETE FROM semicolony.knowledge_base WHERE kb_id = $1`,
+        [row.kb_id]
+      );
+    }
+
+    if (!DRY_RUN) {
+      // 검증
+      const remaining = await pool.query(
+        `SELECT COUNT(*)::int as cnt FROM semicolony.knowledge_base WHERE sub_key = 'current' AND key IN ('action-item', 'kpi')`
+      );
+      console.log(`\n남은 current 서브키: ${remaining.rows[0].cnt}건`);
+    }
+
+    console.log("\n마이그레이션 완료");
+  } finally {
+    await pool.end();
+  }
+}
+
+main().catch((err) => {
+  console.error("에러:", err);
+  process.exit(1);
+});

package/migrations/035_bot_budgets.sql

@@ -0,0 +1,51 @@
+-- 035_bot_budgets.sql
+-- 봇 예산 관리 + 비용 집계 뷰
+-- Paperclip 컨셉 통합: 에이전트별 월간 예산 + 자동 정지
+
+BEGIN;
+
+-- ============================================================
+-- 1. bot_budgets — 봇별 월간 예산 설정
+-- ============================================================
+
+CREATE TABLE IF NOT EXISTS semicolony.bot_budgets (
+  bot_id              TEXT PRIMARY KEY REFERENCES semicolony.bot_status(bot_id),
+  monthly_budget_usd  NUMERIC(10,2),
+  alert_threshold_pct INT NOT NULL DEFAULT 80,
+  auto_pause          BOOLEAN NOT NULL DEFAULT false,
+  created_at          TIMESTAMPTZ NOT NULL DEFAULT NOW(),
+  updated_at          TIMESTAMPTZ NOT NULL DEFAULT NOW()
+);
+
+-- ============================================================
+-- 2. bot_cost_summary — 월별 비용 집계 뷰
+-- ============================================================
+
+CREATE OR REPLACE VIEW semicolony.bot_cost_summary AS
+SELECT
+  bot_id,
+  date_trunc('month', created_at)::date AS month,
+  COUNT(*) AS query_count,
+  COALESCE(SUM(token_input), 0) AS total_input_tokens,
+  COALESCE(SUM(token_output), 0) AS total_output_tokens,
+  COALESCE(SUM((metadata->>'cost_usd')::numeric), 0) AS total_cost_usd,
+  COALESCE(AVG(latency_ms), 0)::int AS avg_latency_ms
+FROM semicolony.bot_query_logs
+GROUP BY bot_id, date_trunc('month', created_at);
+
+-- ============================================================
+-- 3. bot_cost_daily — 일별 비용 집계 뷰 (트렌드용)
+-- ============================================================
+
+CREATE OR REPLACE VIEW semicolony.bot_cost_daily AS
+SELECT
+  bot_id,
+  created_at::date AS day,
+  COUNT(*) AS query_count,
+  COALESCE(SUM(token_input), 0) AS total_input_tokens,
+  COALESCE(SUM(token_output), 0) AS total_output_tokens,
+  COALESCE(SUM((metadata->>'cost_usd')::numeric), 0) AS total_cost_usd
+FROM semicolony.bot_query_logs
+GROUP BY bot_id, created_at::date;
+
+COMMIT;

package/migrations/036_gfp_stitch_design.sql

@@ -0,0 +1,35 @@
+-- 036_gfp_stitch_design.sql
+-- GFP Phase 3 (Design System) + Stitch 브릿지 지원
+--
+-- 1. gfp_materials에 material_type 컬럼 추가 (planning-doc | stitch-export)
+-- 2. DesignClaw를 gfp-manager 스킬 사용 봇에 추가
+
+BEGIN;
+
+-- ============================================================
+-- 1. gfp_materials.material_type 컬럼
+-- ============================================================
+ALTER TABLE semicolony.gfp_materials
+  ADD COLUMN IF NOT EXISTS material_type VARCHAR(50) DEFAULT 'planning-doc';
+
+COMMENT ON COLUMN semicolony.gfp_materials.material_type IS
+  'Material type: planning-doc (기존 기획안), stitch-export (Stitch CSS export)';
+
+-- ============================================================
+-- 2. gfp-manager 스킬에 designclaw 봇 추가
+-- ============================================================
+UPDATE semicolony.skill_definitions
+  SET metadata = jsonb_set(
+    metadata,
+    '{bot_ids}',
+    (metadata->'bot_ids') || '["designclaw"]'::jsonb
+  )
+WHERE name = 'gfp-manager'
+  AND NOT (metadata->'bot_ids' @> '"designclaw"'::jsonb);
+
+-- ============================================================
+-- 3. GfpSectionSource에 'designclaw' 허용 (CHECK 제약이 없으면 무시)
+-- ============================================================
+-- gfp_phase_sections.source는 VARCHAR이므로 별도 제약 없이 'designclaw' 값 사용 가능
+
+COMMIT;

package/migrations/037_gfp_qa_sections.sql

@@ -0,0 +1,13 @@
+-- GFP Phase 3 Q&A support: structured clarification questions
+-- qa_items stores Q&A items as JSONB array
+-- slack_thread_ts tracks Slack thread for answer collection
+
+ALTER TABLE semicolony.gfp_phase_sections
+  ADD COLUMN IF NOT EXISTS qa_items JSONB,
+  ADD COLUMN IF NOT EXISTS slack_thread_ts VARCHAR(50);
+
+COMMENT ON COLUMN semicolony.gfp_phase_sections.qa_items IS
+  'Structured Q&A items for clarification sections. Array of {id, question, sub_bullets[], answer, answered_at, answered_via}';
+
+COMMENT ON COLUMN semicolony.gfp_phase_sections.slack_thread_ts IS
+  'Slack thread timestamp for Q&A answer collection via threaded replies';

package/migrations/038_gfp_phase_split.sql

@@ -0,0 +1,26 @@
+BEGIN;
+
+-- GFP Phase 3 분리: Clarification(Q&A) + Design System(디자인)
+-- Phase 3 → Clarification(3) + Design System(4), 이후 Phase +1 shift → 10단계(0-9)
+
+-- 1. Shift phases 8→9, 7→8, 6→7, 5→6, 4→5 (descending to avoid UNIQUE violation)
+UPDATE semicolony.gfp_phase_sections SET phase = 9 WHERE phase = 8;
+UPDATE semicolony.gfp_phase_sections SET phase = 8 WHERE phase = 7;
+UPDATE semicolony.gfp_phase_sections SET phase = 7 WHERE phase = 6;
+UPDATE semicolony.gfp_phase_sections SET phase = 6 WHERE phase = 5;
+UPDATE semicolony.gfp_phase_sections SET phase = 5 WHERE phase = 4;
+
+-- 2. Move phase 3 design-prefixed sections → phase 4
+UPDATE semicolony.gfp_phase_sections SET phase = 4
+WHERE phase = 3
+  AND (section_key LIKE 'ref-%' OR section_key LIKE 'ds-%'
+    OR section_key LIKE 'impl-%' OR section_key LIKE 'review-%'
+    OR section_key LIKE 'handoff-%' OR section_key LIKE 'stitch-%'
+    OR section_key = 'design-system' OR section_key LIKE 'design-%');
+
+-- 3. Phase 3 non-design sections (Q&A) stay at 3
+
+-- 4. Shift gfp_projects.current_phase for existing projects
+UPDATE semicolony.gfp_projects SET current_phase = current_phase + 1 WHERE current_phase >= 4;
+
+COMMIT;

package/migrations/039_meeting_audio_data.sql

@@ -0,0 +1,2 @@
+-- 회의 오디오를 DB에 저장 (컨테이너 /tmp 휘발 문제 해결)
+ALTER TABLE semicolony.meetings ADD COLUMN IF NOT EXISTS audio_data bytea;

package/migrations/040_bot_commitments.sql

@@ -0,0 +1,68 @@
+BEGIN;
+
+CREATE TABLE IF NOT EXISTS semicolony.bot_commitments (
+  id              TEXT PRIMARY KEY,          -- "cmt-{botId}-{timestamp}-{rand4}"
+  bot_id          TEXT NOT NULL,             -- FK 논리적: semicolony.bot_status.bot_id
+  status          VARCHAR(20) NOT NULL DEFAULT 'pending',
+                  -- pending → active → done | failed | expired
+  title           TEXT NOT NULL,             -- "Typography+Layout+Imagery+Motion 섹션 생성"
+  description     TEXT,
+  source_type     VARCHAR(30),               -- 'github-issue' | 'slack' | 'cron' | 'manual'
+  source_ref      TEXT,                      -- "{org}/{repo}#42" or channel:thread
+  deadline_at     TIMESTAMPTZ,
+  steps           JSONB DEFAULT '[]'::jsonb, -- [{"label":"Typography","done":false}]
+  metadata        JSONB DEFAULT '{}'::jsonb, -- 확장용 (session_key, fail_reason, notes 등)
+  last_heartbeat_at TIMESTAMPTZ,
+  created_at      TIMESTAMPTZ NOT NULL DEFAULT NOW(),
+  updated_at      TIMESTAMPTZ NOT NULL DEFAULT NOW(),
+  completed_at    TIMESTAMPTZ
+);
+
+-- 활성 커밋먼트 조회 인덱스 (watchdog 최적화)
+CREATE INDEX IF NOT EXISTS idx_commitments_active
+  ON semicolony.bot_commitments (status, deadline_at)
+  WHERE status IN ('pending', 'active');
+
+CREATE INDEX IF NOT EXISTS idx_commitments_bot
+  ON semicolony.bot_commitments (bot_id, status);
+
+-- updated_at 자동 갱신 트리거
+CREATE OR REPLACE FUNCTION semicolony.trg_commitments_updated()
+RETURNS TRIGGER AS $$ BEGIN NEW.updated_at = NOW(); RETURN NEW; END; $$ LANGUAGE plpgsql;
+
+CREATE TRIGGER trg_commitments_updated
+  BEFORE UPDATE ON semicolony.bot_commitments
+  FOR EACH ROW EXECUTE FUNCTION semicolony.trg_commitments_updated();
+
+-- 완료 시 completed_at 자동 채움
+CREATE OR REPLACE FUNCTION semicolony.trg_commitments_completed()
+RETURNS TRIGGER AS $$
+BEGIN
+  IF NEW.status IN ('done','failed','expired') AND OLD.status NOT IN ('done','failed','expired') THEN
+    NEW.completed_at = NOW();
+  END IF;
+  RETURN NEW;
+END;
+$$ LANGUAGE plpgsql;
+
+CREATE TRIGGER trg_commitments_completed
+  BEFORE UPDATE ON semicolony.bot_commitments
+  FOR EACH ROW EXECUTE FUNCTION semicolony.trg_commitments_completed();
+
+-- 워치독용 뷰
+CREATE OR REPLACE VIEW semicolony.v_active_commitments AS
+SELECT c.*,
+  CASE
+    WHEN c.deadline_at IS NOT NULL AND c.deadline_at < NOW() THEN 'overdue'
+    WHEN c.last_heartbeat_at IS NOT NULL
+         AND c.last_heartbeat_at < NOW() - INTERVAL '30 minutes' THEN 'stale'
+    ELSE 'on-track'
+  END AS health,
+  EXTRACT(EPOCH FROM (NOW() - COALESCE(c.last_heartbeat_at, c.created_at))) / 60.0
+    AS minutes_since_heartbeat,
+  EXTRACT(EPOCH FROM (NOW() - c.deadline_at)) / 60.0
+    AS minutes_overdue
+FROM semicolony.bot_commitments c
+WHERE c.status IN ('pending', 'active');
+
+COMMIT;

package/migrations/041_palette_previews.sql

@@ -0,0 +1,13 @@
+-- 041: Standalone palette preview storage (DesignClaw 독립 색상 상담용)
+
+CREATE TABLE IF NOT EXISTS semicolony.palette_previews (
+  preview_id  UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  title       TEXT,
+  colors_json JSONB NOT NULL,       -- ColorGroup[]
+  bot_id      TEXT NOT NULL DEFAULT 'designclaw',
+  created_at  TIMESTAMPTZ NOT NULL DEFAULT now(),
+  expires_at  TIMESTAMPTZ NOT NULL DEFAULT now() + INTERVAL '30 days'
+);
+
+CREATE INDEX IF NOT EXISTS idx_palette_previews_created
+  ON semicolony.palette_previews (created_at DESC);