zugzbot 1.0.21 → 1.0.22

package/.opencode/oh-my-design/.claude/skills/omd-remember/SKILL.md

@@ -1,46 +0,0 @@
-<!-- omd:installed-skill — managed by `omd install-skills`. Do not edit; rerun the command to refresh. -->
-
----
-name: omd:remember
-description: "디자인 선호/교정을 .omd/preferences.md 에 append합니다. 사용자가 '기억해', '앞으로는 ~해', '우리는 ~하지 않아', 'remember that' 같은 발화를 하거나 디자인 원칙을 명시할 때 트리거됩니다."
----
-
-# omd:remember — Preference Logger
-
-사용자의 디자인 선호/교정을 `.omd/preferences.md`에 append-only로 기록한다. 나중에 `omd:learn`이 배치로 DESIGN.md에 반영.
-
-## 트리거 발화 패턴
-
-- "기억해 둬", "앞으로는 ~로 해"
-- "우리는 ~한다 / ~하지 않는다"
-- "remember that ...", "going forward ..."
-- "rule of thumb: ..."
-- 사용자가 당신의 디자인 선택을 명시적으로 교정
-
-## 실행
-
-Bash 툴로 한 번 실행:
-
-```bash
-omd remember "<사용자 발화를 한 문장 영문으로 요약>"
-```
-
-옵션:
-- `--scope <value>` — 명시적으로 지정할 때. 기본값은 note 내용에서 자동 추론. 허용: `visualTheme | color | typography | spacing | voice | motion | layout | components.<name>`
-- `--context <text>` — 관련 파일 경로나 PR 번호 (e.g. `src/components/Button.tsx`, `#1234`)
-- `--agent <name>` — 보통 생략 (환경변수 자동 감지). override 필요 시: `claude-code | codex | opencode | cursor`
-
-## 응답
-
-커맨드 출력(`Logged pref_xxx ... → ./.omd/preferences.md`)을 그대로 보여주면 된다. 사용자에게 장황한 확인 불필요.
-
-## omd:apply 스킬과의 관계
-
-- **자동 감지**: 일반 UI 작업 중 교정이 발생하면 `omd:apply` 스킬이 자동으로 이 커맨드를 호출한다.
-- **명시적 호출**: 사용자가 UI 작업 없이 디자인 원칙을 선언하는 경우, 이 스킬이 직접 트리거된다.
-
-## 금지
-
-- `.omd/preferences.md` 파일을 직접 편집하지 말 것 — 항상 `omd remember` 경유.
-- 같은 내용을 중복 기록하지 말 것 (같은 세션 내에서).
-- 사용자에게 "기록할까요?" 묻지 말 것 — 감지 즉시 기록 + 간결 알림.

package/.opencode/oh-my-design/.claude/skills/omd-sync/SKILL.md

@@ -1,40 +0,0 @@
-<!-- omd:installed-skill — managed by `omd install-skills`. Do not edit; rerun the command to refresh. -->
-
----
-name: omd:sync
-description: "DESIGN.md shim 파일들(CLAUDE.md / AGENTS.md / .cursor/rules/omd-design.mdc)을 관리합니다. 'shim 업데이트', 'AGENTS.md 동기화', 'CLAUDE.md drift 확인' 같은 요청에 트리거됩니다."
----
-
-# omd:sync — Shim Maintenance
-
-DESIGN.md가 모든 주요 AI 코딩 에이전트 (Claude Code, Codex, OpenCode, Cursor)에게 보이도록 shim 파일 3종을 관리한다.
-
-## 관리 대상
-
-- `CLAUDE.md` — Claude Code용 `@./DESIGN.md` import
-- `AGENTS.md` — Codex CLI + OpenCode 공용 pointer
-- `.cursor/rules/omd-design.mdc` — Cursor auto-attach rule
-
-각 파일은 `<!-- omd:start v=1 hash=... -->` ~ `<!-- omd:end -->` marker block으로 관리된다. Cursor mdc는 frontmatter 포함 전체 파일이 관리 단위.
-
-## 사용
-
-사용자 요청에 따라 다음 중 하나를 Bash 툴로 실행:
-
-```bash
-omd sync              # 인터랙티브 — drift 시 overwrite/skip/show/quit 프롬프트
-omd sync --force      # drift 포함 무조건 덮어쓰기
-omd sync --check      # 상태만 검사 (CI/pre-commit, unclean 시 exit 1)
-```
-
-## 언제 실행하나
-
-- `DESIGN.md` 변경 직후 (shim hash 갱신)
-- 새 프로젝트에 처음 도입 (shim 3종 생성)
-- `.claude` / `.cursor` 디렉토리 추가 후
-- CI에서 상태 확인 (`--check`)
-
-## 금지
-
-- shim 파일을 직접 편집하지 말 것. 반드시 `omd sync` 경유.
-- marker block 외부 유저 content는 보존된다 (CLAUDE.md / AGENTS.md만). mdc는 omd 전용이라 전체 덮어쓰기.

package/.opencode/oh-my-design/.claude/skills/omd-token-backfill/SKILL.md

@@ -1,57 +0,0 @@
----
-name: omd-token-backfill
-description: "기존 references/<id>/DESIGN.md(엄격히 작성된 산문)에서 머신리더블 `tokens:` 블록(DTCG-lite: colors/typography/rounded/spacing/shadow/components)을 역추적(prose-derived)해 frontmatter에 backfill. token↔prose 정합성 게이트로 검증하고 token-status 체크리스트를 갱신. 배치(기본 10개)로 며칠에 나눠 실행. '토큰 백필', 'tokens 블록 채워', 'X에 토큰 추가', '토큰 배치 돌려', '남은 레퍼런스 토큰화' 류에 트리거. 신규 reference의 토큰은 omd-add-reference Phase 4.5가 담당(여긴 기존 ref 전용)."
----
-
-# omd:token-backfill — existing-reference token backfill
-
-기존 200개 레퍼런스에 `tokens:` 블록을 채운다. 산문이 이미 실측(.verification.md) +
-각 사 DS 토큰명(stripe `--hds-*`, kurly `KPDS`, toss `blue500`)을 담고 있으므로 **재조사가
-아니라 구조화 lift** 다. 신뢰도는 정직하게 `source: prose-derived` 로 라벨링한다.
-
-## 핵심 원칙
-1. **비파괴**: 산문 본문은 건드리지 않는다. frontmatter에 `tokens:` 블록만 **추가**.
-   (단, 토큰값과 산문이 충돌하면 그 값 하나만 정합성 통일 — 전면 리라이트 금지.)
-2. **정합성 게이트가 진실**: `tokens.colors`의 모든 hex는 산문(§2)·`primary_color` 어딘가에
-   존재해야 한다. catalog-integrity 가 강제. ungrounded면 토큰을 고치거나 산문에 명시.
-3. **스키마 레퍼런스 = `references/stripe/DESIGN.md`** 의 tokens 블록(getdesign.md 정렬).
-
-## 배치 사이즈
-**기본 10개 / run** (가벼운 transcription, 정합성 게이트가 값 오류를 기계적으로 잡음 → diff
-리뷰 가능 단위). 첫 1~2배치 diff 확인 후 15까지 상향 가능. 재개는 token-status가 보장.
-
-## 절차 (run 1회)
-1. **다음 배치 선정** — `cd web && node scripts/token-status.mjs` → `PENDING` 목록에서 앞 10개.
-2. **각 ref마다** (`references/<id>/DESIGN.md` 읽기):
-   - (로직 보조) `GLOBAL_ROOT=$(npm root -g) node web/scripts/extract-tokens.mjs <id> --json`
-     로 라이브 primary 후보 + ΔE drift 확보(primary가 산문과 어긋나면 flag).
-   - (LLM) §2 색·§3 타이포 표·§5 스페이싱·§6 shadow·§4 컴포넌트를 **새 스키마로 구조화**:
-     - `colors`: 의미론적 역할+variant (primary/primary-hover/brand/canvas/foreground/
-       muted/on-primary/hairline/error/success …) — **산문에 적힌 hex만** 사용.
-     - `typography`: `family` + 명명 토큰 `{size, weight, lineHeight, tracking, use}` (§3 표 그대로).
-     - `spacing`(명명/배열) · `rounded`(`sm/md/lg/full`) · `shadow`(tier).
-     - **`components`는 구조화 객체로** (flat 문자열 금지 — catalog-integrity가 강제): 한 줄당
-       `name: { type: <button|input|card|badge|tab|toggle|toast|dialog|listItem|avatar>, bg, fg, radius, padding, font, use }`.
-       `type` 필수(범위 밖→가장 가까운 것). 컴포넌트 bg/fg hex는 grounding된 colors 재사용(새 hex 금지).
-       **`components_harvested: true`** 추가. (스키마: `spec/components-schema.md`)
-     - `source: prose-derived`, `extracted: "<오늘>"`, primary가 drift면 `note`에 기록.
-   - frontmatter에 블록 삽입(기존 minimal 블록 있으면 교체). 산문 본문 불변.
-   - design-md 미러 동기화(`design-md/<id>/DESIGN.md` 복사).
-3. **검증 + 체크리스트** — `cd web && node scripts/build-registry.mjs && npx vitest run` →
-   정합성 게이트 통과 확인. `node scripts/token-status.mjs` 로 done 카운트 갱신 확인.
-4. **커밋** — `feat(refs): token backfill batch (<ids>)`. 브랜치는 `feat/design-tokens` (또는 후속).
-
-## 로직 vs LLM
-- 로직: token-status(체크리스트) · extract-tokens(drift) · build-registry · 정합성 게이트.
-- LLM: 역할/variant 배정 · 산문 표 → 토큰 구조화 · drift canonical 판정 · note 작성.
-
-## 트래킹 (체크리스트)
-**`web/scripts/token-status.mjs`** 가 live 체크리스트다(파일이 truth라 drift 없음):
-- `node scripts/token-status.mjs` → done N/200 · pending · needs-attention(ungrounded)
-- `--md` → 마크다운 체크리스트(`- [x]`/`- [ ]`) 문서로 떨굴 때
-- 매 배치 후 done 카운트가 +배치크기 되는지 확인. needs-attention 0 유지.
-
-## 하지 말 것
-- ❌ 산문에 없는 hex를 토큰에 넣기(게이트 실패). ❌ 산문 전면 토큰참조(`{token}`) 치환(렌더러 이슈).
-- ❌ token-status 안 보고 임의 ref 선정(중복/누락). ❌ 배치 후 build-registry/vitest 생략.
-- ❌ 신규 ref를 여기서 처리(그건 omd-add-reference Phase 4.5 — 라이브 실측 토큰).

package/.opencode/oh-my-design/.claude/skills/skill-rules.json

@@ -1,84 +0,0 @@
-{
-  "$schema": "./skill-rules.schema.json",
-  "version": "0.2.0",
-  "description": "omd v0.2 agent layer — skill registry. Lists skills available for orchestrated multi-agent workflows. Consumed by omd-orchestrator routing.",
-  "skills": [
-    {
-      "id": "omd-orchestrator",
-      "path": ".claude/skills/omd-orchestrator/SKILL.md",
-      "agent": ".claude/agents/omd-orchestrator.md",
-      "role": "supervisor",
-      "user_invocable": true,
-      "depends_on": [
-        "omd-kr-writer",
-        "omd-locale-adapter",
-        "omd-designer-review",
-        "omd-final-qa",
-        "omd-codex-image"
-      ]
-    },
-    {
-      "id": "omd-kr-writer",
-      "path": ".claude/skills/omd-kr-writer/SKILL.md",
-      "agent": ".claude/agents/omd-kr-writer.md",
-      "role": "writer",
-      "user_invocable": true,
-      "args": {
-        "preset_id": {
-          "type": "enum",
-          "default": "toss-tech-design",
-          "values": [
-            "toss-tech-design",
-            "karrot-neighborly",
-            "brunch-maker-popular",
-            "biz-formal-report",
-            "academic-paper",
-            "journalism-broadsheet"
-          ],
-          "spec": "data/research/2026-05-18-kr-style-presets.md"
-        }
-      }
-    },
-    {
-      "id": "omd-locale-adapter",
-      "path": ".claude/skills/omd-locale-adapter/SKILL.md",
-      "agent": ".claude/agents/omd-locale-adapter.md",
-      "role": "localizer",
-      "user_invocable": true,
-      "supports_locales": ["en", "ja", "zh-tw"],
-      "source_locale": "ko"
-    },
-    {
-      "id": "omd-designer-review",
-      "path": ".claude/skills/omd-designer-review/SKILL.md",
-      "agent": ".claude/agents/omd-designer-review.md",
-      "role": "visual-critic",
-      "user_invocable": true,
-      "read_only": true,
-      "revision_cap": 2
-    },
-    {
-      "id": "omd-final-qa",
-      "path": ".claude/skills/omd-final-qa/SKILL.md",
-      "agent": ".claude/agents/omd-final-qa.md",
-      "role": "final-critic",
-      "user_invocable": true,
-      "read_only": true,
-      "revision_cap": 2
-    },
-    {
-      "id": "omd-codex-image",
-      "path": ".claude/skills/omd-codex-image/SKILL.md",
-      "agent": ".claude/agents/omd-codex-image.md",
-      "role": "image-materializer",
-      "user_invocable": true,
-      "channels": ["codex", "claude-code", "opencode"]
-    }
-  ],
-  "orchestration": {
-    "supervisor": "omd-orchestrator",
-    "pattern": "anthropic-orchestrator-workers + langgraph-supervisor-revision-cap",
-    "max_revision_rounds_per_gate": 2,
-    "research_ref": "data/research/2026-05-18-agent-landscape.md"
-  }
-}

package/.opencode/oh-my-design/.github/ISSUE_TEMPLATE/agent-fidelity.md

@@ -1,59 +0,0 @@
----
-name: Agent fidelity report
-about: Report a real session of `omd:init` (or other omd:* skills) running in your agent. These reports drive the v0.2 roadmap.
-title: '[fidelity] '
-labels: agent-fidelity
----
-
-## Setup
-
-- **Agent + version**: <!-- e.g. Claude Code 1.x.x / Codex CLI / OpenCode 0.x.x / Cursor -->
-- **OS**: <!-- macOS 14 / Ubuntu 22.04 / Windows 11 / WSL2 -->
-- **`oh-my-design-cli` version**: `npx oh-my-design-cli --version` →
-- **Skills installed via**: <!-- `omd install-skills` / manual copy / pre-existing -->
-
-## What you ran
-
-```
-# the user prompt or commands you gave the agent
-```
-
-## What omd:init produced
-
-Attach or paste the relevant pieces. Don't include anything sensitive.
-
-- `.omd/init-context.json`:
-  ```json
-  ```
-- Resulting `DESIGN.md` — section that looks wrong (or full file if small):
-  ```markdown
-  ```
-
-## What you expected vs got
-
-<!-- 1-3 bullets. -->
-
-## 7-rule self-assessment
-
-Tick each that the output passes (skill enforces these in Phase 5B):
-
-- [ ] **R1** — Section structure 1:1 with the reference (same H2/H3 in same order)
-- [ ] **R2** — Token values changed only where `delta_set` authorizes; rest byte-for-byte
-- [ ] **R3** — Voice fingerprint preserved (sentence length / register / metaphor density)
-- [ ] **R4** — Domain swap scoped to concrete nouns (verbs/adjectives/framing untouched)
-- [ ] **R5** — No new philosophies added (no new bullets/principles outside the reference)
-- [ ] **R6** — Unresolved deltas (if any) marked with `<!-- omd:unresolved: ... -->`
-- [ ] **R7** — Voice hints from `delta_set.voiceHints` reflected in §10
-- [ ] **R8** — §11–13 (Brand Narrative / Principles / Personas) either filled with project-specific facts collected in Phase 4.5, OR left as `[FILL IN: ...]` placeholders with `omd:limitation` comments
-
-## Phase 4.5 dialog (NEW in v0.1.x)
-
-- Did the agent ask you for project facts (founding date / thesis / tagline / personas) before writing §11–13?
-  - [ ] Yes — collected facts and used them
-  - [ ] Yes — I said "skip" and got `[FILL IN]` placeholders
-  - [ ] No — agent skipped Phase 4.5 entirely
-  - [ ] N/A — used a reference without §11–13
-
-## Anything else
-
-<!-- Anything surprising, confusing, or that you wish the skill had asked. -->

package/.opencode/oh-my-design/.github/ISSUE_TEMPLATE/bug-report.md

@@ -1,36 +0,0 @@
----
-name: Bug report
-about: A CLI command, sync/init flow, or generated file behaves incorrectly.
-title: '[bug] '
-labels: bug
----
-
-## What you ran
-
-```bash
-# exact command(s)
-```
-
-## What happened
-
-<!-- output or behavior -->
-
-## What you expected
-
-<!-- expected output or behavior -->
-
-## Environment
-
-- **`oh-my-design-cli` version**: `npx oh-my-design-cli --version` →
-- **Node**: `node --version` →
-- **OS**: <!-- macOS 14 / Ubuntu 22.04 / Windows 11 / WSL2 -->
-
-## Reproduction
-
-1.
-2.
-3.
-
-## Logs / artifacts
-
-<!-- Paste relevant output. Attach .omd/sync.lock.json or DESIGN.md if relevant. -->

package/.opencode/oh-my-design/.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +0,0 @@
-blank_issues_enabled: false
-contact_links:
-  - name: Workflow & verification map
-    url: https://github.com/kwakseongjae/oh-my-design/blob/main/test/scenarios/WORKFLOWS.md
-    about: Before reporting, check whether the workflow you ran is mapped here. Each workflow links to the tests/smokes that cover it.
-  - name: Reference list
-    url: https://github.com/kwakseongjae/oh-my-design/tree/main/references
-    about: Full list of bundled references (also accessible via `omd reference list`).

package/.opencode/oh-my-design/.github/ISSUE_TEMPLATE/feature-request.md

@@ -1,26 +0,0 @@
----
-name: Feature request
-about: Propose a new CLI command, skill, vocabulary keyword, or recommendation behavior.
-title: '[feat] '
-labels: enhancement
----
-
-## What you want to do
-
-<!-- Concretely. What command would you run? What output would you expect? -->
-
-## Why current options don't work
-
-<!-- What did you try? What was missing? -->
-
-## Proposed shape
-
-<!-- Optional: a sketch of the API or behavior. -->
-
-```bash
-# example
-```
-
-## Out of scope
-
-<!-- Optional: anything explicitly NOT part of this request, to keep the scope tight. -->

package/.opencode/oh-my-design/.github/PULL_REQUEST_TEMPLATE.md

@@ -1,134 +0,0 @@
-<!--
-Thanks for contributing to oh-my-design!
-Fill the sections that apply. Delete the rest.
-The type selector at top helps reviewers skim — please check one.
--->
-
-## Type
-
-- [ ] **New reference** — `references/<brand>/DESIGN.md` for a brand not yet covered
-- [ ] **Philosophy Layer** — OmD v0.1 sections 10–15 added to an existing reference
-- [ ] **Reference update** — correcting facts, tokens, or screenshots in an existing reference
-- [ ] **Spec change** — modifying `spec/omd-*.md`
-- [ ] **Bug fix** — fixing a regression or incorrect behavior
-- [ ] **Feature / enhancement** — adding or improving functionality
-- [ ] **Chore / infra** — CI, tooling, build config, dependencies, cleanup
-- [ ] **Docs** — README, contributing guide, spec clarifications
-- [ ] **Other** — please describe below
-
-## Summary
-
-<!-- 1–3 sentences. What does this PR do, and why? -->
-
-## Test plan / screenshots
-
-<!--
-- For code changes: what did you test? Paste commands or list flows.
-- For UI changes: screenshots or short screen recording.
-- For content changes: N/A is OK.
--->
-
----
-
-<!--
-Per-type checklists below. Fill the one that matches. Delete the rest.
--->
-
-### New Reference
-
-**Brand:** <!-- e.g. Toss, Stripe -->  
-**Category:** <!-- AI/LLM, Fintech, Dev Tools, Consumer Tech, etc. -->  
-**Country:** <!-- for the builder's country filter -->  
-**Official design / brand page (if public):** <!-- URL, or "N/A" -->
-
-Sections 1–9 (Google Stitch base — **required**):
-
-- [ ] 1. Visual Theme & Atmosphere — 2–3 paragraphs + Key Characteristics
-- [ ] 2. Color Palette & Roles — **descriptive name + exact hex** for every color
-- [ ] 3. Typography Rules — font stack, hierarchy table, principles
-- [ ] 4. Component Stylings — buttons, cards, inputs, nav, overlays
-- [ ] 5. Layout Principles — spacing scale, grid, radius scale, whitespace philosophy
-- [ ] 6. Depth & Elevation — shadow system with values
-- [ ] 7. Do's and Don'ts — explicit hard constraints
-- [ ] 8. Responsive Behavior — breakpoints, touch targets, image rules
-- [ ] 9. Agent Prompt Guide — quick color ref, example prompts, iteration guide
-
-Sections 10–15 (OmD v0.1 Philosophy Layer — recommended, skip if out of scope).
-
-**Sources** — list URLs used to verify tokens, type stack, and brand philosophy. Reviewers spot-check.
-
----
-
-### Philosophy Layer
-
-**Brand being upgraded:** <!-- e.g. Line, Anthropic -->
-
-- [ ] YAML frontmatter has `omd: 0.1` and `brand: <name>`
-- [ ] Section 10 — Voice & Tone (voice prose + tone table + forbidden phrases)
-- [ ] Section 11 — Brand Narrative (under 200 words)
-- [ ] Section 12 — Principles (5–10 first-principles rules)
-- [ ] Section 13 — Personas (2–4 concrete sketches with name, context, quote)
-- [ ] Section 14 — States (empty / loading / error / skeleton / success)
-- [ ] Section 15 — Motion & Easing (named durations + easings + ≥1 signature motion)
-
-**Sources for philosophy claims** — interviews, blog posts, press kits, founder writing. Personas and narrative must trace back to sources; reviewers reject invented material.
-
----
-
-### Spec change
-
-**Target version:** <!-- v0.1.1 (patch), v0.2 (minor), v1.0 (major) -->
-
-- [ ] Patch or minor bump (follow versioning policy in `spec/omd-v0.1.md` §6)
-- [ ] Major bump — discussion issue opened first: <!-- link -->
-- [ ] Migration guide for existing files (if breaking)
-- [ ] JSON Schema reflects the change (if section names changed)
-
----
-
-### Bug fix
-
-- [ ] Steps to reproduce are in the PR description
-- [ ] Root cause identified (not just the symptom)
-- [ ] Regression test added where practical
-- [ ] `npm test` passes
-- [ ] Manually verified fix (describe in Test plan)
-
----
-
-### Feature / enhancement
-
-- [ ] `npm test` passes; new tests added for new behavior
-- [ ] Builder runs (`npm run dev` in `web/`) and the feature works end-to-end
-- [ ] Screenshots or recording for UI-visible changes
-- [ ] No new runtime dependencies, or justification in Summary
-- [ ] No secrets / keys / `.env` accidentally committed
-- [ ] If this touches `export-panel.tsx`, `generate-css.ts`, or `applyOverridesToMd`: verified at least one existing reference still exports a valid DESIGN.md
-
----
-
-### Chore / infra
-
-- [ ] No behavior change to builder output (confirmed by diffing an export)
-- [ ] CI still green
-
----
-
-### Docs
-
-- [ ] Links resolve
-- [ ] README change applied to all 4 language variants (`.md`, `.ko.md`, `.ja.md`, `.zh-TW.md`) — or a note on why not
-- [ ] Spelling / grammar pass
-
----
-
-## Final checklist (all PRs)
-
-- [ ] PR title is descriptive (e.g. `Add Line DESIGN.md v0.1`, not `update`)
-- [ ] Commit history is clean (squash fixup commits if noisy)
-- [ ] I'm OK with this PR being MIT-licensed per repo license
-- [ ] If this adds content about a brand I don't work at, it is based on public sources only
-
-<!--
-Anti-slop policy: PRs that claim a brand uses Inter/Roboto/Arial without citation, or include invented personas/narrative, will be sent back for sources. See spec/omd-v0.1.md for the full rationale.
--->

package/.opencode/oh-my-design/.github/workflows/release.yml

@@ -1,55 +0,0 @@
-# npm 자동 배포 — vX.Y.Z 태그 푸시가 트리거.
-#
-# 릴리스 절차 (로컬):
-#   1. package.json version 범프 + CHANGELOG 항목 → main 머지
-#   2. git tag v1.7.2 && git push origin v1.7.2
-#   3. 이 워크플로가 테스트 → 빌드 → npm publish (provenance 포함)
-#
-# 필요 시크릿: NPM_TOKEN (npmjs.com granular token, oh-my-design-cli read+write)
-# 주의: npm 계정 2FA 설정이 "Require 2FA and disallow tokens"면 publish가
-# EOTP로 실패한다 — "2FA for authorization only" 또는 토큰 허용으로 둘 것.
-
-name: Release to npm
-
-on:
-  push:
-    tags:
-      - "v*.*.*"
-
-permissions:
-  contents: read
-  id-token: write # npm provenance 서명용
-
-concurrency:
-  group: release
-  cancel-in-progress: false
-
-jobs:
-  publish:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v5
-
-      - uses: actions/setup-node@v5
-        with:
-          node-version: 22
-          registry-url: "https://registry.npmjs.org"
-
-      - name: Verify tag matches package.json version
-        run: |
-          PKG_VERSION=$(node -p "require('./package.json').version")
-          TAG_VERSION="${GITHUB_REF_NAME#v}"
-          if [ "$PKG_VERSION" != "$TAG_VERSION" ]; then
-            echo "::error::tag $GITHUB_REF_NAME != package.json $PKG_VERSION"
-            exit 1
-          fi
-
-      - run: npm ci
-
-      - run: npm test
-
-      # prepublishOnly가 build + gen-llms-full + release-hygiene(pack)을 다시 돌린다
-      - name: Publish
-        run: npm publish --provenance --access public
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

package/.opencode/oh-my-design/.husky/pre-commit

@@ -1,23 +0,0 @@
-#!/usr/bin/env bash
-# Catalog-integrity gate. Runs the vitest suite when any of the data-plane
-# paths change. Otherwise skips silently so unrelated commits stay fast.
-#
-# Bypass (emergencies only): `git commit --no-verify`.
-
-set -euo pipefail
-
-# --- Release-hygiene gate: block experiment byproducts (v1/v2 .bak, _source,
-# contact sheets, logs, scratch dirs) from entering a commit. See
-# scripts/check-release-hygiene.sh and the omd-release-hygiene skill. ---
-if [ -x scripts/check-release-hygiene.sh ]; then
-  bash scripts/check-release-hygiene.sh staged
-fi
-
-changed=$(git diff --cached --name-only)
-
-if echo "$changed" | grep -qE '^(references/|data/reference-fingerprints\.json|\.claude/data/reference-fingerprints\.json|\.codex/data/reference-fingerprints\.json|web/src/data/registry\.generated\.ts|web/scripts/build-registry\.mjs|web/scripts/migrate-frontmatters\.mjs|web/__tests__/catalog-integrity\.test\.ts|design-md/)'; then
-  echo "[husky] catalog-integrity gate: running vitest…"
-  (cd web && npm run build-registry && npm test -- --run __tests__/catalog-integrity.test.ts)
-else
-  echo "[husky] catalog-integrity gate: no data-plane changes, skipping."
-fi

package/.opencode/oh-my-design/.mcp.json

@@ -1,12 +0,0 @@
-{
-  "mcpServers": {
-    "playwright": {
-      "type": "stdio",
-      "command": "npx",
-      "args": [
-        "@playwright/mcp@latest"
-      ],
-      "env": {}
-    }
-  }
-}