@team-semicolon/semicolony-cli 4.18.51

package/migrations/042_gfp_parallel_tracks.sql

@@ -0,0 +1,37 @@
+-- 042: GFP Parallel Tracks — SemiClaw 시작점 + InfraClaw 병렬 트랙
+-- Track A (plan): PlanClaw Phase 1-9
+-- Track B (infra): InfraClaw Phase 0-2
+
+-- gfp_phase_sections에 track 컬럼 추가
+ALTER TABLE semicolony.gfp_phase_sections
+  ADD COLUMN track VARCHAR(10) NOT NULL DEFAULT 'plan';
+
+-- UNIQUE 제약조건 변경: track 포함
+ALTER TABLE semicolony.gfp_phase_sections
+  DROP CONSTRAINT gfp_phase_sections_gfp_id_phase_section_key_key;
+ALTER TABLE semicolony.gfp_phase_sections
+  ADD CONSTRAINT gfp_phase_sections_gfp_id_track_phase_section_key_key
+  UNIQUE(gfp_id, track, phase, section_key);
+
+-- gfp_projects에 infra_phase 컬럼 추가
+ALTER TABLE semicolony.gfp_projects
+  ADD COLUMN infra_phase SMALLINT DEFAULT NULL;
+
+-- 인프라 요구사항 테이블
+CREATE TABLE semicolony.gfp_infra_requests (
+  request_id    UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  gfp_id        UUID NOT NULL REFERENCES semicolony.gfp_projects(gfp_id) ON DELETE CASCADE,
+  source_phase  SMALLINT NOT NULL,
+  source_section_id UUID REFERENCES semicolony.gfp_phase_sections(section_id),
+  category      VARCHAR(50) NOT NULL,
+  title         VARCHAR(200) NOT NULL,
+  description   TEXT,
+  priority      VARCHAR(10) NOT NULL DEFAULT 'normal',
+  status        VARCHAR(20) NOT NULL DEFAULT 'pending',
+  slack_thread_ts VARCHAR(50),
+  created_at    TIMESTAMPTZ NOT NULL DEFAULT NOW(),
+  updated_at    TIMESTAMPTZ NOT NULL DEFAULT NOW()
+);
+
+CREATE INDEX idx_gfp_infra_requests_project
+  ON semicolony.gfp_infra_requests(gfp_id, status);

package/migrations/043_blocker_key.sql

@@ -0,0 +1,13 @@
+-- 043_blocker_key.sql
+-- service 타입에 blocker collection 키 추가
+-- 블로커 추적: 상태(active/resolved), 시작일, 해결일, 담당자, 출처
+-- sub_key 패턴: blocker/{YYYY-MM-DD}/{slug}
+
+INSERT INTO semicolony.kb_type_schema
+  (type_key, scheme_key, scheme_description, required, value_hint, sort_order, key_type)
+VALUES
+  ('service', 'blocker', '블로커 추적 (active/resolved 상태, 시작일/해결일 관리)',
+   false,
+   'blocker/{YYYY-MM-DD}/{slug}',
+   200, 'collection')
+ON CONFLICT (type_key, scheme_key) DO NOTHING;

package/migrations/044_gfp_stitch_screenshots.sql

@@ -0,0 +1,9 @@
+-- 044: GFP Stitch screenshot storage
+-- Stitch SDK에서 생성된 스크린샷 base64 데이터 + 공유 URL 저장
+
+ALTER TABLE semicolony.gfp_materials
+  ADD COLUMN IF NOT EXISTS screenshot_data TEXT,
+  ADD COLUMN IF NOT EXISTS stitch_share_url VARCHAR(500);
+
+COMMENT ON COLUMN semicolony.gfp_materials.screenshot_data IS 'Base64-encoded PNG screenshot from Stitch getImage()';
+COMMENT ON COLUMN semicolony.gfp_materials.stitch_share_url IS 'Public shareable URL from Stitch getShareUrl()';

package/migrations/045_service_table_rename_and_projection.sql

@@ -0,0 +1,150 @@
+-- 045: GFP → Service 테이블 리네이밍 + Projection Key 시스템
+--
+-- 변경 사항:
+--   A. gfp_* 테이블 → service_* 리네이밍
+--   B. 제약조건 / 인덱스 / 트리거 리네이밍
+--   C. 하위 호환 VIEW (gfp_* → service_*)
+--   D. service_domain → ontology.domain FK 연계 (기존 데이터 정합성 보장)
+--   E. kb_type_schema에 source 컬럼 + projection 키 등록
+--   F. lifecycle / launched_at 컬럼 추가
+--
+-- PK 컬럼명 gfp_id는 이 마이그레이션에서 유지 (코드 변경 최소화).
+-- 후속 마이그레이션에서 project_id로 rename 가능.
+--
+-- 선행 조건: 044_gfp_stitch_screenshots.sql 적용 완료
+
+BEGIN;
+
+-- ============================================================
+-- A. 테이블 리네이밍
+-- ============================================================
+
+ALTER TABLE semicolony.gfp_projects        RENAME TO service_projects;
+ALTER TABLE semicolony.gfp_phase_sections  RENAME TO service_sections;
+ALTER TABLE semicolony.gfp_materials       RENAME TO service_materials;
+ALTER TABLE semicolony.gfp_research_tasks  RENAME TO service_research_tasks;
+ALTER TABLE semicolony.gfp_infra_requests  RENAME TO service_infra_requests;
+
+-- ============================================================
+-- B. 제약조건 / 인덱스 / 트리거 리네이밍
+-- ============================================================
+
+-- B-1. UNIQUE 제약조건
+ALTER TABLE semicolony.service_sections
+  RENAME CONSTRAINT gfp_phase_sections_gfp_id_track_phase_section_key_key
+  TO service_sections_gfp_id_track_phase_section_key_key;
+
+-- B-2. FK 제약조건
+ALTER TABLE semicolony.service_sections
+  RENAME CONSTRAINT gfp_phase_sections_gfp_id_fkey
+  TO service_sections_project_fkey;
+
+ALTER TABLE semicolony.service_materials
+  RENAME CONSTRAINT gfp_materials_gfp_id_fkey
+  TO service_materials_project_fkey;
+
+ALTER TABLE semicolony.service_research_tasks
+  RENAME CONSTRAINT gfp_research_tasks_gfp_id_fkey
+  TO service_research_tasks_project_fkey;
+
+ALTER TABLE semicolony.service_infra_requests
+  RENAME CONSTRAINT gfp_infra_requests_gfp_id_fkey
+  TO service_infra_requests_project_fkey;
+
+ALTER TABLE semicolony.service_infra_requests
+  RENAME CONSTRAINT gfp_infra_requests_source_section_id_fkey
+  TO service_infra_requests_section_fkey;
+
+-- B-3. 인덱스
+ALTER INDEX semicolony.idx_gfp_sections_project
+  RENAME TO idx_service_sections_project;
+
+ALTER INDEX semicolony.idx_gfp_infra_requests_project
+  RENAME TO idx_service_infra_requests_project;
+
+-- B-4. 트리거
+ALTER TRIGGER trg_gfp_projects_updated ON semicolony.service_projects
+  RENAME TO trg_service_projects_updated;
+
+ALTER TRIGGER trg_gfp_sections_updated ON semicolony.service_sections
+  RENAME TO trg_service_sections_updated;
+
+ALTER TRIGGER trg_gfp_research_updated ON semicolony.service_research_tasks
+  RENAME TO trg_service_research_tasks_updated;
+
+-- B-5. 트리거 함수 리네이밍
+ALTER FUNCTION semicolony.gfp_set_updated_at() RENAME TO service_set_updated_at;
+
+-- ============================================================
+-- C. 하위 호환 VIEW (전환 기간 2주 후 제거 예정)
+-- ============================================================
+
+CREATE VIEW semicolony.gfp_projects        AS SELECT * FROM semicolony.service_projects;
+CREATE VIEW semicolony.gfp_phase_sections  AS SELECT * FROM semicolony.service_sections;
+CREATE VIEW semicolony.gfp_materials       AS SELECT * FROM semicolony.service_materials;
+CREATE VIEW semicolony.gfp_research_tasks  AS SELECT * FROM semicolony.service_research_tasks;
+CREATE VIEW semicolony.gfp_infra_requests  AS SELECT * FROM semicolony.service_infra_requests;
+
+-- ============================================================
+-- D. service_domain → ontology FK 연계
+-- ============================================================
+
+-- D-1. 기존 데이터 정합성 보장:
+--       service_domain이 NOT NULL인데 ontology에 없는 경우 자동 등록
+INSERT INTO semicolony.ontology (domain, entity_type, service, schema, description, tags)
+SELECT DISTINCT
+  sp.service_domain,
+  'service',
+  sp.service_domain,
+  '{}'::jsonb,
+  sp.project_name || ' (auto-registered by migration 045)',
+  ARRAY['gfp-migrated']
+FROM semicolony.service_projects sp
+WHERE sp.service_domain IS NOT NULL
+  AND NOT EXISTS (
+    SELECT 1 FROM semicolony.ontology o WHERE o.domain = sp.service_domain
+  );
+
+-- D-2. FK 추가 (NULL 허용 — service_domain이 nullable)
+ALTER TABLE semicolony.service_projects
+  ADD CONSTRAINT service_projects_ontology_domain_fkey
+  FOREIGN KEY (service_domain) REFERENCES semicolony.ontology(domain);
+
+-- ============================================================
+-- E. kb_type_schema — source 컬럼 + projection 키 등록
+-- ============================================================
+
+-- E-1. source 컬럼 추가
+ALTER TABLE semicolony.kb_type_schema
+  ADD COLUMN IF NOT EXISTS source VARCHAR(20) NOT NULL DEFAULT 'manual';
+
+-- E-2. service 타입에 projection 키 등록
+INSERT INTO semicolony.kb_type_schema
+  (type_key, scheme_key, scheme_description, required, value_hint, sort_order, key_type, source)
+VALUES
+  ('service', 'spec',         'PM 파이프라인 스펙 산출물 (자동 동기화)',           false, 'spec/discovery, spec/prd, spec/design-system', 20, 'collection', 'projection'),
+  ('service', 'pm-status',    '프로젝트 진행 상태 (자동 동기화)',                  false, NULL,                                           21, 'singleton',  'projection'),
+  ('service', 'infra-status', '인프라 트랙 진행 상태 (자동 동기화)',               false, NULL,                                           22, 'singleton',  'projection'),
+  ('service', 'pm-summary',   '프로젝트 라이프사이클 요약 (자동 동기화)',           false, NULL,                                           23, 'singleton',  'projection'),
+  ('service', 'gfp-id',       '(레거시) 프로젝트 ID 참조 — pm-status로 통합 예정', false, NULL,                                           24, 'singleton',  'projection'),
+  ('service', 'gfp-status',   '(레거시) 진행 상태 — pm-status로 통합 예정',       false, NULL,                                           25, 'singleton',  'projection')
+ON CONFLICT (type_key, scheme_key) DO UPDATE SET
+  source = EXCLUDED.source,
+  key_type = EXCLUDED.key_type,
+  scheme_description = EXCLUDED.scheme_description,
+  sort_order = EXCLUDED.sort_order;
+
+-- ============================================================
+-- F. lifecycle / launched_at 컬럼
+-- ============================================================
+
+ALTER TABLE semicolony.service_projects
+  ADD COLUMN IF NOT EXISTS lifecycle   VARCHAR(20) NOT NULL DEFAULT 'build',
+  ADD COLUMN IF NOT EXISTS launched_at TIMESTAMPTZ;
+
+-- 완료된 프로젝트는 lifecycle = 'ops'로 마이그레이션
+UPDATE semicolony.service_projects
+SET lifecycle = 'ops', launched_at = updated_at
+WHERE status = 'completed';
+
+COMMIT;

package/migrations/046_service_ops_tables.sql

@@ -0,0 +1,75 @@
+-- 046: Service Ops Phase Tables — 운영 라이프사이클 확장
+--
+-- build → ops → sunset 전환을 위한 이터레이션/인시던트 테이블.
+-- service_sections.iteration_id로 build/ops phase 섹션을 구분.
+--
+-- 선행 조건: 045_service_table_rename_and_projection.sql 적용 완료
+
+BEGIN;
+
+-- ============================================================
+-- 1. service_iterations — 운영 이터레이션 사이클
+-- ============================================================
+
+CREATE TABLE IF NOT EXISTS semicolony.service_iterations (
+  iteration_id  UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  project_id    UUID NOT NULL REFERENCES semicolony.service_projects(gfp_id) ON DELETE CASCADE,
+  title         VARCHAR(200) NOT NULL,
+  goal          TEXT,
+  status        VARCHAR(20) NOT NULL DEFAULT 'planned',
+  started_at    TIMESTAMPTZ,
+  completed_at  TIMESTAMPTZ,
+  retrospective TEXT,
+  created_at    TIMESTAMPTZ NOT NULL DEFAULT NOW(),
+  updated_at    TIMESTAMPTZ NOT NULL DEFAULT NOW()
+);
+
+-- status: planned | active | completed
+CREATE INDEX idx_service_iterations_project
+  ON semicolony.service_iterations(project_id, status);
+
+-- updated_at 트리거 연결
+CREATE TRIGGER trg_service_iterations_updated
+  BEFORE UPDATE ON semicolony.service_iterations
+  FOR EACH ROW EXECUTE FUNCTION semicolony.service_set_updated_at();
+
+-- ============================================================
+-- 2. service_incidents — 운영 인시던트
+-- ============================================================
+
+CREATE TABLE IF NOT EXISTS semicolony.service_incidents (
+  incident_id   UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  project_id    UUID NOT NULL REFERENCES semicolony.service_projects(gfp_id) ON DELETE CASCADE,
+  iteration_id  UUID REFERENCES semicolony.service_iterations(iteration_id),
+  severity      VARCHAR(10) NOT NULL DEFAULT 'medium',
+  title         VARCHAR(200) NOT NULL,
+  description   TEXT,
+  root_cause    TEXT,
+  resolution    TEXT,
+  status        VARCHAR(20) NOT NULL DEFAULT 'open',
+  occurred_at   TIMESTAMPTZ NOT NULL DEFAULT NOW(),
+  resolved_at   TIMESTAMPTZ,
+  created_at    TIMESTAMPTZ NOT NULL DEFAULT NOW(),
+  updated_at    TIMESTAMPTZ NOT NULL DEFAULT NOW()
+);
+
+-- severity: low | medium | high | critical
+-- status: open | investigating | resolved | postmortem
+CREATE INDEX idx_service_incidents_project
+  ON semicolony.service_incidents(project_id, status);
+
+CREATE TRIGGER trg_service_incidents_updated
+  BEFORE UPDATE ON semicolony.service_incidents
+  FOR EACH ROW EXECUTE FUNCTION semicolony.service_set_updated_at();
+
+-- ============================================================
+-- 3. service_sections.iteration_id — ops phase 섹션 연결
+-- ============================================================
+
+ALTER TABLE semicolony.service_sections
+  ADD COLUMN IF NOT EXISTS iteration_id UUID REFERENCES semicolony.service_iterations(iteration_id);
+
+-- iteration_id IS NULL = build phase 섹션 (기존 동작 유지)
+-- iteration_id IS NOT NULL = ops phase 작업 항목
+
+COMMIT;

package/migrations/047_update_gfp_manager_skill.sql

@@ -0,0 +1,16 @@
+-- 047: gfp-manager 스킬 → service-project-manager 리프레이밍
+--
+-- GFP는 이제 "프로젝트 관리 시스템"이 아니라 "신규 서비스를 띄우는 파이프라인".
+-- service_* 테이블이 모든 서비스의 SoT.
+-- 스킬 프롬프트를 이 맥락으로 업데이트.
+--
+-- 선행 조건: 045_service_table_rename_and_projection.sql 적용 완료
+
+UPDATE semicolony.skill_definitions
+SET
+  display_name = 'Service Project Manager',
+  description  = '서비스 프로젝트 관리 — service_* 테이블 CRUD. GFP(신규 서비스 파이프라인) + 기존 서비스 운영 공통.',
+  prompt = E'---\nname: service-project-manager\ndescription: 서비스 프로젝트 관리 — service_* 테이블 CRUD, 섹션 생성/수정, 리서치 결과 반영.\n---\n\n# Service Project Manager\n\nservice_* 테이블(구 gfp_*)의 프로젝트/섹션/리서치 관리 스킬.\n봇(PlanClaw, DesignClaw, GrowthClaw, InfraClaw 등)이 대시보드 API를 통해 접근.\n\n## 핵심 개념\n\n- **service_projects**: 모든 서비스의 메타데이터 (lifecycle: build → ops → sunset)\n- **GFP Pipeline**: 신규 서비스를 service_projects에 등록하고 Phase 0~9를 진행하는 파이프라인\n- **Projection Key**: KB의 spec/*, pm-status 등은 파이프라인이 자동 동기화 — 봇이 직접 쓰면 CLI가 거부\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&track=plan\" | 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# DesignClaw: Stitch 디자인 결과\ncurl -X POST ${SEMICOLONY_DASHBOARD_URL}/api/gfp/callback \\\n  -H \"Content-Type: application/json\" \\\n  -d ''{ \"type\": \"stitch-export\", \"gfp_id\": \"...\", \"content\": \"...\", \"bot_id\": \"designclaw\" }''\n```\n\n### 인프라 요청 (Track B)\n```bash\n# 인프라 요구사항 생성\ncurl -X POST ${SEMICOLONY_DASHBOARD_URL}/api/gfp/{gfp_id}/infra-requests \\\n  -H \"Content-Type: application/json\" \\\n  -d ''{ \"source_phase\": 2, \"category\": \"oauth\", \"title\": \"OAuth 설정 필요\" }''\n```\n\n## Data Routing 규칙\n\n| 데이터 | 쓰기 대상 | 금지 |\n|--------|-----------|------|\n| 섹션 콘텐츠 | PM API (이 스킬) | KB spec/* 직접 쓰기 ✗ |\n| 서비스 메타데이터 | KB (`semicolony kb upsert`) | PM 테이블 직접 수정 ✗ |\n| 진행 상태 | (자동) pm-pipeline | 봇이 pm-status 직접 쓰기 ✗ |\n\n## 규칙\n- 섹션 수정 시 status를 반드시 \"pending-review\"로 설정\n- source 필드로 출처 명시: planclaw / growthclaw / designclaw / infraclaw / imported / manual\n- 콜백 API 사용 시 bot_id 필수\n- **Projection Key 쓰기 금지**: spec/*, pm-status, gfp-status, infra-status는 파이프라인이 자동 관리\n',
+  metadata = '{"bot_ids": ["planclaw", "growthclaw", "designclaw", "infraclaw"]}',
+  version  = '2.0'
+WHERE name = 'gfp-manager';

package/migrations/048_service_migration_skill.sql

@@ -0,0 +1,23 @@
+-- 048: service-migration 스킬 등록
+--
+-- 기존 운영 서비스를 service_projects 테이블에 이식하는 스킬.
+-- SemiClaw가 Slack에서 트리거하거나 CLI에서 직접 실행.
+
+INSERT INTO semicolony.skill_definitions (name, display_name, description, prompt, package, is_active, metadata, version)
+VALUES (
+  'service-migration',
+  'Service Migration',
+  '기존 운영 서비스를 service_projects 테이블에 이식. KB 엔트리 감사(audit) + 자동 매핑.',
+  E'---\nname: service-migration\ndescription: 기존 운영 서비스를 service_projects 테이블에 이식\n---\n\n# Service Migration\n\n기존 운영 서비스를 `service_projects` 테이블에 등록하는 스킬.\nGFP(신규 서비스 파이프라인)를 거치지 않은 서비스를 경량 온보딩.\n\n## 트리거\n- \"기존 서비스 등록해줘 {domain}\"\n- \"미등록 서비스 전체 등록해줘\"\n- \"서비스 목록 보여줘\"\n\n## CLI 실행\n```bash\n# 단일 서비스 이식\nsemicolony service migrate --domain {domain}\n\n# 미등록 전체 일괄 이식\nsemicolony service migrate --all\n\n# 미리보기 (DB 변경 없음)\nsemicolony service migrate --all --dry-run\n\n# 서비스 목록 (등록/미등록)\nsemicolony service list\n```\n\n## 이식 흐름\n1. KB에서 base-information, po, status, tech-stack 등 자동 수집\n2. KB status → lifecycle+status 매핑 (active→ops, hold→paused, deprecated→sunset)\n3. service_projects INSERT (lifecycle=''ops'')\n4. pm-summary projection key 자동 생성\n5. 감사(audit) 리포트 출력\n\n## 감사 리포트 해석\n- **mapped**: service_projects 컬럼에 매핑된 KB 엔트리\n- **metadata**: JSONB에 저장된 추가 정보 (repo, slack-channel 등)\n- **kb-only**: KB에만 존재하는 정상 엔트리 (kpi, milestone 등)\n- **warnings**: 비표준 키 → kb_type_schema 등록 제안\n- **missingRequired**: 필수 키 누락 → 사용자에게 보완 요청\n\n## Data Routing\n- service_projects 테이블 = 실행 상태 SoT\n- KB = 서비스 참조 지식 SoT\n- projection key (spec/*, pm-status 등)는 파이프라인만 쓰기 가능\n',
+  'core',
+  true,
+  '{"bot_ids": ["semiclaw"]}',
+  '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;

package/migrations/049_service_features.sql

@@ -0,0 +1,39 @@
+-- 049: service_features — 서비스 기능 관리 테이블
+--
+-- 운영 중인 서비스의 기능 목록을 DB 기반으로 관리.
+-- 계층 구조(parent_id), 카테고리별 분류, 기능 개선 → GitHub Issue 연동.
+--
+-- 선행 조건: 045_service_table_rename_and_projection.sql
+
+BEGIN;
+
+CREATE TABLE IF NOT EXISTS semicolony.service_features (
+  feature_id  UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  project_id  UUID NOT NULL REFERENCES semicolony.service_projects(gfp_id) ON DELETE CASCADE,
+  name        VARCHAR(200) NOT NULL,
+  description TEXT,
+  category    VARCHAR(50) NOT NULL DEFAULT 'core',
+  status      VARCHAR(20) NOT NULL DEFAULT 'active',
+  parent_id   UUID REFERENCES semicolony.service_features(feature_id) ON DELETE SET NULL,
+  sort_order  SMALLINT NOT NULL DEFAULT 0,
+  metadata    JSONB DEFAULT '{}',
+  created_at  TIMESTAMPTZ NOT NULL DEFAULT NOW(),
+  updated_at  TIMESTAMPTZ NOT NULL DEFAULT NOW()
+);
+
+-- category: core | growth | infra | ux | integration
+-- status: active | planned | in-dev | deprecated
+-- metadata: { endpoints: [], github_issue_url, tech_notes }
+
+CREATE INDEX idx_service_features_project
+  ON semicolony.service_features(project_id, category, sort_order);
+
+CREATE INDEX idx_service_features_parent
+  ON semicolony.service_features(parent_id)
+  WHERE parent_id IS NOT NULL;
+
+CREATE TRIGGER trg_service_features_updated
+  BEFORE UPDATE ON semicolony.service_features
+  FOR EACH ROW EXECUTE FUNCTION semicolony.service_set_updated_at();
+
+COMMIT;

package/migrations/050_service_kpi_action_items.sql

@@ -0,0 +1,87 @@
+-- 050: service_kpi_metrics & service_action_items
+--
+-- KPI 지표와 액션 아이템을 개별 레코드로 관리.
+-- KB markdown blob → DB 구조화 레코드 전환.
+--
+-- 선행 조건: 046_service_ops_tables.sql (iterations, incidents)
+
+BEGIN;
+
+-- ============================================================
+-- 1. service_kpi_metrics — 개별 KPI 지표 레코드
+-- ============================================================
+
+CREATE TABLE IF NOT EXISTS semicolony.service_kpi_metrics (
+  metric_id       UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  project_id      UUID NOT NULL REFERENCES semicolony.service_projects(gfp_id) ON DELETE CASCADE,
+  iteration_id    UUID REFERENCES semicolony.service_iterations(iteration_id),
+  period          DATE NOT NULL,
+  metric_name     VARCHAR(100) NOT NULL,
+  metric_label    VARCHAR(200),
+  category        VARCHAR(50) NOT NULL DEFAULT 'common',
+  current_value   NUMERIC,
+  baseline_value  NUMERIC,
+  target_value    NUMERIC,
+  unit            VARCHAR(30),
+  wow_change      NUMERIC,
+  signal          VARCHAR(10) NOT NULL DEFAULT 'neutral',
+  achieved        BOOLEAN DEFAULT FALSE,
+  source          VARCHAR(50) DEFAULT 'bot',
+  metadata        JSONB DEFAULT '{}',
+  created_at      TIMESTAMPTZ NOT NULL DEFAULT NOW(),
+  updated_at      TIMESTAMPTZ NOT NULL DEFAULT NOW()
+);
+
+-- category: common | service-specific | search | engagement
+-- signal: green | yellow | red | neutral
+-- source: bot | manual | api | import
+
+CREATE INDEX idx_service_kpi_metrics_project_period
+  ON semicolony.service_kpi_metrics(project_id, period DESC);
+
+CREATE INDEX idx_service_kpi_metrics_lookup
+  ON semicolony.service_kpi_metrics(project_id, metric_name, period DESC);
+
+CREATE TRIGGER trg_service_kpi_metrics_updated
+  BEFORE UPDATE ON semicolony.service_kpi_metrics
+  FOR EACH ROW EXECUTE FUNCTION semicolony.service_set_updated_at();
+
+-- ============================================================
+-- 2. service_action_items — 개별 액션 아이템 레코드
+-- ============================================================
+
+CREATE TABLE IF NOT EXISTS semicolony.service_action_items (
+  action_item_id  UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  project_id      UUID NOT NULL REFERENCES semicolony.service_projects(gfp_id) ON DELETE CASCADE,
+  iteration_id    UUID REFERENCES semicolony.service_iterations(iteration_id),
+  description     TEXT NOT NULL,
+  assignee        VARCHAR(100),
+  deadline        DATE,
+  status          VARCHAR(20) NOT NULL DEFAULT 'open',
+  priority        VARCHAR(10) NOT NULL DEFAULT 'normal',
+  category        VARCHAR(50),
+  source          VARCHAR(50) DEFAULT 'manual',
+  related_url     TEXT,
+  sort_order      SMALLINT NOT NULL DEFAULT 0,
+  completed_at    TIMESTAMPTZ,
+  metadata        JSONB DEFAULT '{}',
+  created_at      TIMESTAMPTZ NOT NULL DEFAULT NOW(),
+  updated_at      TIMESTAMPTZ NOT NULL DEFAULT NOW()
+);
+
+-- status: open | completed | cancelled
+-- priority: low | normal | high | urgent
+-- source: manual | bot | dashboard | import
+
+CREATE INDEX idx_service_action_items_project_status
+  ON semicolony.service_action_items(project_id, status);
+
+CREATE INDEX idx_service_action_items_assignee
+  ON semicolony.service_action_items(assignee, status)
+  WHERE assignee IS NOT NULL;
+
+CREATE TRIGGER trg_service_action_items_updated
+  BEFORE UPDATE ON semicolony.service_action_items
+  FOR EACH ROW EXECUTE FUNCTION semicolony.service_set_updated_at();
+
+COMMIT;

package/migrations/051_update_service_migration_skill_prompt.sql

@@ -0,0 +1,9 @@
+-- 051: service-migration 스킬 프롬프트 강화
+--
+-- 문제: 봇이 KB 엔트리만 보고 "이미 등록됨"으로 판단 → 실제 service_projects 미등록 서비스를 놓침
+-- 해결: CLI 실행 필수 지시 + KB ≠ 등록 경고 + 판단 기준 명확화
+
+UPDATE semicolony.skill_definitions
+SET prompt = E'---\nname: service-migration\ndescription: 기존 운영 서비스를 service_projects 테이블에 이식\n---\n\n# Service Migration\n\n기존 운영 서비스를 `service_projects` 테이블에 등록하는 스킬.\nGFP(신규 서비스 파이프라인)를 거치지 않은 서비스를 경량 온보딩.\n\n## ⚠️ 핵심 원칙 (NON-NEGOTIABLE)\n\n1. **\"등록됨\" = `service_projects` 테이블에 행이 있는 것**. KB 엔트리가 있다고 등록된 것이 아님.\n2. **판단 금지**: KB를 조회해서 자체적으로 등록 여부를 판단하지 마라.\n3. **반드시 CLI 실행**: 아래 CLI 명령을 직접 실행하고, 그 결과로 응답하라.\n\n## 트리거\n- \"기존 서비스 등록해줘 {domain}\"\n- \"미등록 서비스 전체 등록해줘\"\n- \"서비스 목록 보여줘\"\n\n## 실행 방법 (반드시 CLI 실행)\n\n### 단일 서비스 이식\n```bash\nsemicolony service migrate --domain {domain}\n```\nCLI가 내부적으로: service_projects 중복 체크 → KB audit → INSERT → pm-summary 생성\n\n### 미등록 전체 일괄 이식\n```bash\nsemicolony service migrate --all\n```\n\n### 미리보기 (DB 변경 없음)\n```bash\nsemicolony service migrate --all --dry-run\n```\n\n### 서비스 목록 (등록/미등록 확인)\n```bash\nsemicolony service list\n```\n\n## 올바른 워크플로우\n1. 사용자가 \"기존 서비스 등록해줘 {domain}\" 요청\n2. `semicolony service migrate --domain {domain}` CLI 실행\n3. CLI 출력 결과를 그대로 사용자에게 전달\n4. 이미 등록된 경우 CLI가 \"이미 등록됨\" 메시지를 출력함 — 이것만 신뢰\n\n## ❌ 잘못된 워크플로우\n1. 사용자가 \"기존 서비스 등록해줘 {domain}\" 요청\n2. `semicolony kb get {domain} base-information` 등 KB 조회\n3. KB 엔트리가 있으니 \"이미 등록됨\"이라고 판단 ← **이것이 버그**\n\n## 이식 흐름 (CLI 내부 동작)\n1. service_projects 테이블에서 중복 체크\n2. KB에서 base-information, po, status, tech-stack 등 자동 수집\n3. KB status → lifecycle+status 매핑 (active→ops, hold→paused, deprecated→sunset)\n4. service_projects INSERT (lifecycle=''ops'')\n5. pm-summary projection key 자동 생성\n6. 감사(audit) 리포트 출력\n\n## 감사 리포트 해석\n- **mapped**: service_projects 컬럼에 매핑된 KB 엔트리\n- **metadata**: JSONB에 저장된 추가 정보 (repo, slack-channel 등)\n- **kb-only**: KB에만 존재하는 정상 엔트리 (kpi, milestone 등)\n- **warnings**: 비표준 키 → kb_type_schema 등록 제안\n- **missingRequired**: 필수 키 누락 → 사용자에게 보완 요청\n\n## Data Routing\n- service_projects 테이블 = 실행 상태 SoT\n- KB = 서비스 참조 지식 SoT\n- projection key (spec/*, pm-status 등)는 파이프라인만 쓰기 가능\n',
+    version = '1.1'
+WHERE name = 'service-migration';

package/migrations/052_feature_iteration_link.sql

@@ -0,0 +1,11 @@
+-- 052: service_features에 iteration_id FK 추가 (스프린트 기반 기능 관리)
+BEGIN;
+
+ALTER TABLE semicolony.service_features
+  ADD COLUMN IF NOT EXISTS iteration_id UUID REFERENCES semicolony.service_iterations(iteration_id);
+
+CREATE INDEX IF NOT EXISTS idx_service_features_iteration
+  ON semicolony.service_features(iteration_id)
+  WHERE iteration_id IS NOT NULL;
+
+COMMIT;

package/migrations/052_services_table_rename.sql

@@ -0,0 +1,149 @@
+-- 052: service_projects → services 테이블 리네이밍 + PK gfp_id → service_id
+--
+-- 변경 사항:
+--   A. service_projects → services 리네이밍
+--   B. PK/FK 컬럼 gfp_id/project_id → service_id 통일
+--   C. 제약조건 / 인덱스 리네이밍
+--   D. 트리거 리네이밍
+--   E. 하위 호환 VIEW 재생성 (gfp_id alias 포함)
+--
+-- 선행 조건: 051 이하 모든 마이그레이션 적용 완료
+
+BEGIN;
+
+-- ============================================================
+-- A. 테이블 리네이밍
+-- ============================================================
+
+-- 기존 하위 호환 VIEW 제거 (테이블 리네임 시 CASCADE 방지)
+DROP VIEW IF EXISTS semicolony.gfp_projects CASCADE;
+DROP VIEW IF EXISTS semicolony.gfp_phase_sections CASCADE;
+DROP VIEW IF EXISTS semicolony.gfp_materials CASCADE;
+DROP VIEW IF EXISTS semicolony.gfp_research_tasks CASCADE;
+DROP VIEW IF EXISTS semicolony.gfp_infra_requests CASCADE;
+
+ALTER TABLE semicolony.service_projects RENAME TO services;
+
+-- ============================================================
+-- B. PK/FK 컬럼 리네이밍: gfp_id / project_id → service_id
+-- ============================================================
+
+-- B-1. 메인 테이블 PK
+ALTER TABLE semicolony.services RENAME COLUMN gfp_id TO service_id;
+
+-- B-2. 자식 테이블 (gfp_id → service_id)
+ALTER TABLE semicolony.service_sections RENAME COLUMN gfp_id TO service_id;
+ALTER TABLE semicolony.service_materials RENAME COLUMN gfp_id TO service_id;
+ALTER TABLE semicolony.service_research_tasks RENAME COLUMN gfp_id TO service_id;
+ALTER TABLE semicolony.service_infra_requests RENAME COLUMN gfp_id TO service_id;
+
+-- B-3. 자식 테이블 (project_id → service_id)
+ALTER TABLE semicolony.service_iterations RENAME COLUMN project_id TO service_id;
+ALTER TABLE semicolony.service_incidents RENAME COLUMN project_id TO service_id;
+ALTER TABLE semicolony.service_features RENAME COLUMN project_id TO service_id;
+
+-- ============================================================
+-- C. 제약조건 리네이밍
+-- ============================================================
+
+-- C-1. services 테이블
+ALTER TABLE semicolony.services
+  RENAME CONSTRAINT gfp_projects_pkey TO services_pkey;
+ALTER TABLE semicolony.services
+  RENAME CONSTRAINT service_projects_ontology_domain_fkey TO services_ontology_domain_fkey;
+
+-- C-2. service_sections
+ALTER TABLE semicolony.service_sections
+  RENAME CONSTRAINT service_sections_gfp_id_track_phase_section_key_key
+  TO service_sections_service_id_track_phase_section_key_key;
+ALTER TABLE semicolony.service_sections
+  RENAME CONSTRAINT service_sections_project_fkey TO service_sections_service_fkey;
+
+-- C-3. service_materials
+ALTER TABLE semicolony.service_materials
+  RENAME CONSTRAINT service_materials_project_fkey TO service_materials_service_fkey;
+
+-- C-4. service_research_tasks
+ALTER TABLE semicolony.service_research_tasks
+  RENAME CONSTRAINT service_research_tasks_project_fkey TO service_research_tasks_service_fkey;
+
+-- C-5. service_infra_requests
+ALTER TABLE semicolony.service_infra_requests
+  RENAME CONSTRAINT service_infra_requests_project_fkey TO service_infra_requests_service_fkey;
+
+-- C-6. service_iterations
+ALTER TABLE semicolony.service_iterations
+  RENAME CONSTRAINT service_iterations_project_id_fkey TO service_iterations_service_fkey;
+
+-- C-7. service_incidents
+ALTER TABLE semicolony.service_incidents
+  RENAME CONSTRAINT service_incidents_project_id_fkey TO service_incidents_service_fkey;
+
+-- C-8. service_features
+ALTER TABLE semicolony.service_features
+  RENAME CONSTRAINT service_features_project_id_fkey TO service_features_service_fkey;
+
+-- C-9. 인덱스 리네이밍 (project → service)
+ALTER INDEX semicolony.idx_service_sections_project RENAME TO idx_service_sections_service;
+ALTER INDEX semicolony.idx_service_infra_requests_project RENAME TO idx_service_infra_requests_service;
+ALTER INDEX semicolony.idx_service_iterations_project RENAME TO idx_service_iterations_service;
+ALTER INDEX semicolony.idx_service_incidents_project RENAME TO idx_service_incidents_service;
+ALTER INDEX semicolony.idx_service_features_project RENAME TO idx_service_features_service;
+
+-- (PK constraint rename이 backing index도 자동 rename하므로 별도 인덱스 rename 불필요)
+
+-- ============================================================
+-- D. 트리거 리네이밍
+-- ============================================================
+
+ALTER TRIGGER trg_service_projects_updated ON semicolony.services
+  RENAME TO trg_services_updated;
+
+-- ============================================================
+-- E. 하위 호환 VIEW (gfp_id alias 포함)
+-- ============================================================
+
+-- service_projects → services (gfp_id alias)
+CREATE VIEW semicolony.service_projects AS
+  SELECT service_id AS gfp_id,
+         project_name, service_domain, owner_name, owner_contact,
+         current_phase, infra_phase, status, lifecycle, launched_at,
+         metadata, created_at, updated_at
+  FROM semicolony.services;
+
+-- gfp_projects → services (레거시)
+CREATE VIEW semicolony.gfp_projects AS
+  SELECT * FROM semicolony.service_projects;
+
+-- gfp_phase_sections → service_sections (gfp_id alias)
+CREATE VIEW semicolony.gfp_phase_sections AS
+  SELECT service_id AS gfp_id,
+         section_id, phase, track, section_key, title, content,
+         ordinal, status, reviewer_note, source,
+         kb_written_at, qa_items, slack_thread_ts,
+         iteration_id, created_at, updated_at
+  FROM semicolony.service_sections;
+
+-- gfp_materials → service_materials (gfp_id alias)
+CREATE VIEW semicolony.gfp_materials AS
+  SELECT service_id AS gfp_id,
+         material_id, content, phase_mapping, material_type,
+         screenshot_data, stitch_share_url, created_at
+  FROM semicolony.service_materials;
+
+-- gfp_research_tasks → service_research_tasks (gfp_id alias)
+CREATE VIEW semicolony.gfp_research_tasks AS
+  SELECT service_id AS gfp_id,
+         task_id, task_type, reference_urls, input_prompt,
+         status, result, created_at, updated_at
+  FROM semicolony.service_research_tasks;
+
+-- gfp_infra_requests → service_infra_requests (gfp_id alias)
+CREATE VIEW semicolony.gfp_infra_requests AS
+  SELECT service_id AS gfp_id,
+         request_id, source_phase, source_section_id, category,
+         title, description, priority, status,
+         slack_thread_ts, created_at, updated_at
+  FROM semicolony.service_infra_requests;
+
+COMMIT;