@su-record/vibe 2.9.23 → 2.9.24

package/commands/vibe.contract.md

@@ -1,105 +1,105 @@
----
-description: API contract drift detection — extract contracts from SPEC, compare to implementation, fail on drift
-argument-hint: "extract | check | diff [feature-name]"
----
-
-# /vibe.contract
-
-**API Contract Drift Detection** — when implementation diverges from the SPEC's API contract, catch it immediately.
-
-> The SPEC is the source of truth. If the implementation silently leaves the SPEC, tests can pass while the contract breaks.
-
-## Usage
-
-```
-/vibe.contract extract <feature>       # SPEC → contract record at .claude/vibe/contracts/<feature>.md
-/vibe.contract check <feature>         # contract vs implementation, drift report
-/vibe.contract diff <feature>          # changed fields since last check
-```
-
-## What counts as an "API contract"
-
-A contract = any **interface shape** that external consumers (clients, other services) depend on:
-
-- HTTP endpoint: method + path + request schema + response schema + status codes
-- GraphQL: query/mutation name + args + return shape
-- Event/message: topic + payload schema
-- Exported TypeScript function signature (when explicitly marked as public API)
-
-## Process
-
-Load skill `vibe-contract` with subcommand: `$ARGUMENTS`
-
-**Core steps**:
-
-1. **extract**: parse SPEC sections like `## API` / `## Endpoints` / `## Interface` and persist as a structured contract record
-2. **check**: locate matching endpoints in the implementation, compare signature/schema, report drift as P1 findings
-3. **diff**: compare against the previous snapshot, surface only **changed fields** (noise minimized)
-
-## Drift severity
-
-| Drift type | Severity | Example |
-|---|---|---|
-| Missing endpoint | P1 | SPEC says `GET /users/:id`, implementation has none |
-| Missing required field in response | P1 | SPEC response includes `email`, implementation drops it |
-| Type change (breaking) | P1 | `userId: number` → `userId: string` |
-| Added required request field | P1 | breaks existing clients |
-| Added optional field | P3 | extension is allowed |
-| Status code added | P2 | client must handle a new case |
-| Status code removed | P1 | expected response disappeared |
-
-**On any P1 drift**: treat as failure regardless of `/vibe.verify` outcome — tests can pass while the contract breaks.
-
-## Storage Format
-
-```
-.claude/vibe/contracts/
-  <feature>.md           # extracted contract (SSOT)
-  <feature>.snapshot.md  # implementation snapshot at last check (for diff)
-```
-
-### Contract schema (frontmatter)
-
-```yaml
----
-feature: string
-extracted-from: path/to/spec.md
-extracted-at: ISO timestamp
-endpoints:
-  - method: GET | POST | PUT | DELETE | PATCH
-    path: /users/:id
-    request:
-      params: { id: string }
-      body: null
-    response:
-      200: { id: string, email: string, ... }
-      404: { error: string }
-      required: [id, email]
-  - ...
----
-```
-
-## Integration with /vibe.verify
-
-After `/vibe.verify <feature>` scenarios pass, auto-chain:
-
-```
-scenarios pass → /vibe.contract check <feature>
-  ├─ no drift → ✅ complete
-  └─ drift found → ❌ report + auto /vibe.regress register (tag: integration)
-```
-
-## Integration with /vibe.spec
-
-Right after `/vibe.spec` finishes writing the SPEC, auto-invoke `/vibe.contract extract`. The resulting contract becomes the reference for the subsequent `/vibe.run`.
-
-## Done Criteria
-
-- [ ] `extract` exits cleanly when SPEC has no API section (not every feature has one)
-- [ ] `check` is silent when no drift; otherwise prints findings grouped by severity
-- [ ] Every P1 drift triggers `/vibe.regress register --from-contract`
-- [ ] `diff` says "first run" when no prior snapshot exists
-
----
-
-ARGUMENTS: $ARGUMENTS
+---
+description: API contract drift detection — extract contracts from SPEC, compare to implementation, fail on drift
+argument-hint: "extract | check | diff [feature-name]"
+---
+
+# /vibe.contract
+
+**API Contract Drift Detection** — when implementation diverges from the SPEC's API contract, catch it immediately.
+
+> The SPEC is the source of truth. If the implementation silently leaves the SPEC, tests can pass while the contract breaks.
+
+## Usage
+
+```
+/vibe.contract extract <feature>       # SPEC → contract record at .claude/vibe/contracts/<feature>.md
+/vibe.contract check <feature>         # contract vs implementation, drift report
+/vibe.contract diff <feature>          # changed fields since last check
+```
+
+## What counts as an "API contract"
+
+A contract = any **interface shape** that external consumers (clients, other services) depend on:
+
+- HTTP endpoint: method + path + request schema + response schema + status codes
+- GraphQL: query/mutation name + args + return shape
+- Event/message: topic + payload schema
+- Exported TypeScript function signature (when explicitly marked as public API)
+
+## Process
+
+Load skill `vibe-contract` with subcommand: `$ARGUMENTS`
+
+**Core steps**:
+
+1. **extract**: parse SPEC sections like `## API` / `## Endpoints` / `## Interface` and persist as a structured contract record
+2. **check**: locate matching endpoints in the implementation, compare signature/schema, report drift as P1 findings
+3. **diff**: compare against the previous snapshot, surface only **changed fields** (noise minimized)
+
+## Drift severity
+
+| Drift type | Severity | Example |
+|---|---|---|
+| Missing endpoint | P1 | SPEC says `GET /users/:id`, implementation has none |
+| Missing required field in response | P1 | SPEC response includes `email`, implementation drops it |
+| Type change (breaking) | P1 | `userId: number` → `userId: string` |
+| Added required request field | P1 | breaks existing clients |
+| Added optional field | P3 | extension is allowed |
+| Status code added | P2 | client must handle a new case |
+| Status code removed | P1 | expected response disappeared |
+
+**On any P1 drift**: treat as failure regardless of `/vibe.verify` outcome — tests can pass while the contract breaks.
+
+## Storage Format
+
+```
+.claude/vibe/contracts/
+  <feature>.md           # extracted contract (SSOT)
+  <feature>.snapshot.md  # implementation snapshot at last check (for diff)
+```
+
+### Contract schema (frontmatter)
+
+```yaml
+---
+feature: string
+extracted-from: path/to/spec.md
+extracted-at: ISO timestamp
+endpoints:
+  - method: GET | POST | PUT | DELETE | PATCH
+    path: /users/:id
+    request:
+      params: { id: string }
+      body: null
+    response:
+      200: { id: string, email: string, ... }
+      404: { error: string }
+      required: [id, email]
+  - ...
+---
+```
+
+## Integration with /vibe.verify
+
+After `/vibe.verify <feature>` scenarios pass, auto-chain:
+
+```
+scenarios pass → /vibe.contract check <feature>
+  ├─ no drift → ✅ complete
+  └─ drift found → ❌ report + auto /vibe.regress register (tag: integration)
+```
+
+## Integration with /vibe.spec
+
+Right after `/vibe.spec` finishes writing the SPEC, auto-invoke `/vibe.contract extract`. The resulting contract becomes the reference for the subsequent `/vibe.run`.
+
+## Done Criteria
+
+- [ ] `extract` exits cleanly when SPEC has no API section (not every feature has one)
+- [ ] `check` is silent when no drift; otherwise prints findings grouped by severity
+- [ ] Every P1 drift triggers `/vibe.regress register --from-contract`
+- [ ] `diff` says "first run" when no prior snapshot exists
+
+---
+
+ARGUMENTS: $ARGUMENTS

package/commands/vibe.docs.md

@@ -1,33 +1,33 @@
----
-description: Generate project documentation — README, architecture docs, user guide, release notes, agent instructions
-argument-hint: "readme, guide, arch, release, or agent"
----
-
-# /vibe.docs
-
-Generate or update project documentation by analyzing the actual codebase.
-
-## Usage
-
-```
-/vibe.docs readme     # README.md 생성/갱신
-/vibe.docs guide      # 사용자 가이드 (docs/GUIDE.md)
-/vibe.docs arch       # 아키텍처 문서 + Mermaid 다이어그램 (docs/ARCHITECTURE.md)
-/vibe.docs release    # 릴리즈 노트 (git history 기반)
-/vibe.docs agent      # CLAUDE.md / AGENTS.md 생성·동기화 (claude-md-guide + agents-md 검증 필수)
-```
-
-## Pipeline Position
-
-```
-/vibe.spec    → Design (what to build)
-/vibe.run     → Implement (build it)
-/vibe.trace   → Verify (prove it works)
-/vibe.docs    → Document (explain it)
-```
-
----
-
-Load skill `vibe-docs` — subcommand에 따라 해당 섹션 실행
-
-ARGUMENTS: $ARGUMENTS
+---
+description: Generate project documentation — README, architecture docs, user guide, release notes, agent instructions
+argument-hint: "readme, guide, arch, release, or agent"
+---
+
+# /vibe.docs
+
+Generate or update project documentation by analyzing the actual codebase.
+
+## Usage
+
+```
+/vibe.docs readme     # README.md 생성/갱신
+/vibe.docs guide      # 사용자 가이드 (docs/GUIDE.md)
+/vibe.docs arch       # 아키텍처 문서 + Mermaid 다이어그램 (docs/ARCHITECTURE.md)
+/vibe.docs release    # 릴리즈 노트 (git history 기반)
+/vibe.docs agent      # CLAUDE.md / AGENTS.md 생성·동기화 (claude-md-guide + agents-md 검증 필수)
+```
+
+## Pipeline Position
+
+```
+/vibe.spec    → Design (what to build)
+/vibe.run     → Implement (build it)
+/vibe.trace   → Verify (prove it works)
+/vibe.docs    → Document (explain it)
+```
+
+---
+
+Load skill `vibe-docs` — subcommand에 따라 해당 섹션 실행
+
+ARGUMENTS: $ARGUMENTS

package/commands/vibe.event.md

@@ -1,163 +1,163 @@
----
-description: Community event automation — D-Day based proactive task execution
-argument-hint: "MDC 12차 3/30" or "webinar AI에이전트 4/15" or "DWK 5차 5/20"
----
-
-# /vibe.event
-
-Automate community event planning with D-Day based proactive execution.
-
-## Usage
-
-```
-/vibe.event "MDC 12차 3/30"                    # Parse: type=MDC, edition=12, date=3/30
-/vibe.event "webinar AI에이전트 4/15"            # Parse: type=webinar, topic=AI에이전트, date=4/15
-/vibe.event "DWK 5차 5/20 오프라인"              # Parse: type=DWK, edition=5, date=5/20, format=offline
-/vibe.event status                              # Show current event status
-/vibe.event dashboard                           # Open dashboard (localhost:8080)
-```
-
-## Execution Flow
-
-```
-1. PARSE input
-   ├── Event type: MDC / webinar / DWK
-   ├── Edition number (optional)
-   ├── Date (required)
-   ├── Topic (optional, can be set later)
-   └── Format: offline/online (DWK only, default=offline)
-
-2. CALCULATE D-Day
-   └── today - event_date = D-{n}
-
-3. LOAD or CREATE state
-   ├── Check .event_state.json
-   └── Create if new event
-
-4. DETERMINE current phase
-   ├── MDC: 11 steps (D-60 → D+2)
-   ├── Webinar: 5 steps (planning → D+1)
-   └── DWK: 9 steps (D-30 → D+3)
-
-5. AUTO-EXECUTE pending deliverables
-   ├── Content drafts → event-content agent
-   ├── Image generation → event-image agent
-   ├── SMS/email drafts → event-comms agent
-   ├── Ops materials → event-ops agent
-   └── Speaker research → event-speaker agent
-
-6. REQUEST confirmation for send actions
-   ├── SMS actual send
-   ├── Email actual send
-   └── Notion real registration
-
-7. SAVE state
-   └── Update .event_state.json
-```
-
-## Input Parsing Rules
-
-| Input | Parsed Result |
-|-------|---------------|
-| `MDC 12차 3/30` | type=MDC, edition=12, date=2026-03-30 |
-| `webinar AI에이전트` | type=webinar, topic=AI에이전트, date=TBD (ask) |
-| `DWK 5차 5/20 오프라인` | type=DWK, edition=5, date=2026-05-20, format=offline |
-| `status` | Show .event_state.json summary |
-| `dashboard` | Run `python output/serve.py` |
-
-## Phase-by-Phase Agent Dispatch
-
-### MDC Phases
-
-| Phase | Agents Triggered | Outputs |
-|-------|-----------------|---------|
-| D-60 | event-speaker | 3 topic suggestions + speaker research |
-| D-45 | event-speaker | DM + email outreach drafts |
-| D-40 | event-comms | Topic confirmation request email |
-| D-28 | event-content, event-image, event-comms | Intro + 2 images + 3 SMS + 1 email |
-| D-30 | event-content, event-comms | LinkedIn/Threads promo + SMS send(✅) |
-| D-14 | event-content | LinkedIn/Threads reminder |
-| D-3 | event-comms | BCC email + SMS send(✅) |
-| D-1 | event-ops | Nametags + checklist + PPTX + SMS(✅) |
-| D-Day | event-comms | Day-of SMS(✅) |
-| D+1 | event-content, event-ops | Review posts + settlement |
-| D+2 | — | Site update (manual) |
-
-### Webinar Phases
-
-| Phase | Agents Triggered | Outputs |
-|-------|-----------------|---------|
-| Planning | event-content, event-image, event-comms | Intro + 3 images + SMS + email |
-| Planning | event-content | LinkedIn/Threads promo |
-| D-4 | event-comms | Zoom(manual) + BCC email + SMS(✅) |
-| D-Day | event-comms, event-ops | SMS(✅) + slides |
-| D+1 | event-content | Review posts |
-
-### DWK Phases
-
-| Phase | Agents Triggered | Outputs |
-|-------|-----------------|---------|
-| D-30 | event-speaker | 3 topics + speaker research |
-| D-25 | event-speaker | DM + email outreach |
-| D-20 | event-comms | Topic confirmation email |
-| D-16 | event-content, event-image, event-comms | Intro + 2 images + SMS + email |
-| D-15 | event-content | LinkedIn/Threads promo |
-| D-3 | event-comms | BCC email + SMS(✅) |
-| D-1 | event-ops | Slido plan + PPTX + SNS remind(✅) |
-| D-Day | event-comms, event-ops | SMS(✅) + nametags(offline) |
-| D+3 | event-content, event-ops | Review + settlement |
-
-## State File Format
-
-```json
-{
-  "event_id": "MDC-12",
-  "type": "MDC",
-  "edition": 12,
-  "date": "2026-03-30",
-  "title": "마케팅데이터커넥트 12회",
-  "topic": "마케팅 자동화",
-  "format": "offline",
-  "speakers": [
-    {
-      "name": "김영수",
-      "company": "Company X",
-      "topic": "마케팅 데이터 파이프라인"
-    }
-  ],
-  "current_step": "D-28",
-  "completed_steps": ["D-60", "D-45", "D-40"],
-  "outputs": {
-    "D-28": ["intro.md", "thumbnail_500x500.png", "sms_notification.txt"]
-  },
-  "confirmations_pending": []
-}
-```
-
-## Dashboard
-
-```bash
-# Start dashboard
-python output/serve.py
-# Opens http://localhost:8080
-
-# Features:
-# - Timeline view with D-Day progress
-# - Generate buttons per step
-# - File preview links
-# - API status (Gemini/Aligo key validity)
-# - Dark theme with community color coding
-```
-
-## Safety Rules
-
-```
-CRITICAL — These are absolute prohibitions:
-1. NEVER send SMS/email without explicit user confirmation
-2. ALWAYS use BCC for email (never expose attendee emails)
-3. NEVER use emoji in SMS (EUC-KR incompatible)
-4. NEVER delete files (move only)
-5. ALWAYS test SMS with testmode_yn=Y before real send
-6. NEVER register to Notion without dry_run first
-7. NEVER commit .env files
-```
+---
+description: Community event automation — D-Day based proactive task execution
+argument-hint: "MDC 12차 3/30" or "webinar AI에이전트 4/15" or "DWK 5차 5/20"
+---
+
+# /vibe.event
+
+Automate community event planning with D-Day based proactive execution.
+
+## Usage
+
+```
+/vibe.event "MDC 12차 3/30"                    # Parse: type=MDC, edition=12, date=3/30
+/vibe.event "webinar AI에이전트 4/15"            # Parse: type=webinar, topic=AI에이전트, date=4/15
+/vibe.event "DWK 5차 5/20 오프라인"              # Parse: type=DWK, edition=5, date=5/20, format=offline
+/vibe.event status                              # Show current event status
+/vibe.event dashboard                           # Open dashboard (localhost:8080)
+```
+
+## Execution Flow
+
+```
+1. PARSE input
+   ├── Event type: MDC / webinar / DWK
+   ├── Edition number (optional)
+   ├── Date (required)
+   ├── Topic (optional, can be set later)
+   └── Format: offline/online (DWK only, default=offline)
+
+2. CALCULATE D-Day
+   └── today - event_date = D-{n}
+
+3. LOAD or CREATE state
+   ├── Check .event_state.json
+   └── Create if new event
+
+4. DETERMINE current phase
+   ├── MDC: 11 steps (D-60 → D+2)
+   ├── Webinar: 5 steps (planning → D+1)
+   └── DWK: 9 steps (D-30 → D+3)
+
+5. AUTO-EXECUTE pending deliverables
+   ├── Content drafts → event-content agent
+   ├── Image generation → event-image agent
+   ├── SMS/email drafts → event-comms agent
+   ├── Ops materials → event-ops agent
+   └── Speaker research → event-speaker agent
+
+6. REQUEST confirmation for send actions
+   ├── SMS actual send
+   ├── Email actual send
+   └── Notion real registration
+
+7. SAVE state
+   └── Update .event_state.json
+```
+
+## Input Parsing Rules
+
+| Input | Parsed Result |
+|-------|---------------|
+| `MDC 12차 3/30` | type=MDC, edition=12, date=2026-03-30 |
+| `webinar AI에이전트` | type=webinar, topic=AI에이전트, date=TBD (ask) |
+| `DWK 5차 5/20 오프라인` | type=DWK, edition=5, date=2026-05-20, format=offline |
+| `status` | Show .event_state.json summary |
+| `dashboard` | Run `python output/serve.py` |
+
+## Phase-by-Phase Agent Dispatch
+
+### MDC Phases
+
+| Phase | Agents Triggered | Outputs |
+|-------|-----------------|---------|
+| D-60 | event-speaker | 3 topic suggestions + speaker research |
+| D-45 | event-speaker | DM + email outreach drafts |
+| D-40 | event-comms | Topic confirmation request email |
+| D-28 | event-content, event-image, event-comms | Intro + 2 images + 3 SMS + 1 email |
+| D-30 | event-content, event-comms | LinkedIn/Threads promo + SMS send(✅) |
+| D-14 | event-content | LinkedIn/Threads reminder |
+| D-3 | event-comms | BCC email + SMS send(✅) |
+| D-1 | event-ops | Nametags + checklist + PPTX + SMS(✅) |
+| D-Day | event-comms | Day-of SMS(✅) |
+| D+1 | event-content, event-ops | Review posts + settlement |
+| D+2 | — | Site update (manual) |
+
+### Webinar Phases
+
+| Phase | Agents Triggered | Outputs |
+|-------|-----------------|---------|
+| Planning | event-content, event-image, event-comms | Intro + 3 images + SMS + email |
+| Planning | event-content | LinkedIn/Threads promo |
+| D-4 | event-comms | Zoom(manual) + BCC email + SMS(✅) |
+| D-Day | event-comms, event-ops | SMS(✅) + slides |
+| D+1 | event-content | Review posts |
+
+### DWK Phases
+
+| Phase | Agents Triggered | Outputs |
+|-------|-----------------|---------|
+| D-30 | event-speaker | 3 topics + speaker research |
+| D-25 | event-speaker | DM + email outreach |
+| D-20 | event-comms | Topic confirmation email |
+| D-16 | event-content, event-image, event-comms | Intro + 2 images + SMS + email |
+| D-15 | event-content | LinkedIn/Threads promo |
+| D-3 | event-comms | BCC email + SMS(✅) |
+| D-1 | event-ops | Slido plan + PPTX + SNS remind(✅) |
+| D-Day | event-comms, event-ops | SMS(✅) + nametags(offline) |
+| D+3 | event-content, event-ops | Review + settlement |
+
+## State File Format
+
+```json
+{
+  "event_id": "MDC-12",
+  "type": "MDC",
+  "edition": 12,
+  "date": "2026-03-30",
+  "title": "마케팅데이터커넥트 12회",
+  "topic": "마케팅 자동화",
+  "format": "offline",
+  "speakers": [
+    {
+      "name": "김영수",
+      "company": "Company X",
+      "topic": "마케팅 데이터 파이프라인"
+    }
+  ],
+  "current_step": "D-28",
+  "completed_steps": ["D-60", "D-45", "D-40"],
+  "outputs": {
+    "D-28": ["intro.md", "thumbnail_500x500.png", "sms_notification.txt"]
+  },
+  "confirmations_pending": []
+}
+```
+
+## Dashboard
+
+```bash
+# Start dashboard
+python output/serve.py
+# Opens http://localhost:8080
+
+# Features:
+# - Timeline view with D-Day progress
+# - Generate buttons per step
+# - File preview links
+# - API status (Gemini/Aligo key validity)
+# - Dark theme with community color coding
+```
+
+## Safety Rules
+
+```
+CRITICAL — These are absolute prohibitions:
+1. NEVER send SMS/email without explicit user confirmation
+2. ALWAYS use BCC for email (never expose attendee emails)
+3. NEVER use emoji in SMS (EUC-KR incompatible)
+4. NEVER delete files (move only)
+5. ALWAYS test SMS with testmode_yn=Y before real send
+6. NEVER register to Notion without dry_run first
+7. NEVER commit .env files
+```