viepilot 2.23.0 → 2.41.0

package/docs/brainstorm/session-2026-04-20.md

@@ -0,0 +1,261 @@
+# Brainstorm Session — 2026-04-20
+
+## Topic
+**ViePilot Skill Registry System** — Third-party skill installation + scan-skills command + workflow skill integration (brainstorm / crystallize / vp-auto gates)
+
+## Status
+In Progress
+
+---
+
+## Problem Statement
+
+ViePilot hiện tại chỉ dùng built-in `vp-*` skills. Khi user muốn xây dựng UI-Direction phức tạp hơn (ví dụ dùng design system cụ thể, component library, hay frontend framework chuyên biệt), không có cơ chế nào để bổ sung context chuyên sâu từ external skills.
+
+Vấn đề cụ thể:
+1. Không có cách cài thêm skills từ bên thứ 3 (npm, GitHub, local)
+2. ViePilot không biết skills nào đang có sẵn trên máy
+3. Workflow (brainstorm / crystallize / vp-auto) không thể tận dụng skill context ngoài vp-* namespace
+4. Quyết định "dùng skill nào" không có điểm lock — vp-auto phải hỏi lại hoặc đoán
+
+---
+
+## Proposed Solution: Skill Registry System
+
+### Core Concept
+
+Ba tầng hoạt động:
+
+```
+[Install]  vp-tools install-skill <source>  → cài skill vào adapter dirs
+[Discover] vp-tools scan-skills             → quét + index toàn bộ skills
+[Apply]    brainstorm → crystallize → auto  → dùng skills theo pipeline
+```
+
+### Tầng 1 — Installation (multi-channel)
+
+`vp-tools install-skill <source>` hỗ trợ:
+
+| Channel | Syntax | Example |
+|---------|--------|---------|
+| npm | `npm:package-name` hoặc bare name | `vp-tools install-skill @vp-skills/frontend-design` |
+| GitHub | `github:org/repo` | `vp-tools install-skill github:myorg/vp-skill-tailwind` |
+| Local | `./path` hoặc absolute path | `vp-tools install-skill ./my-skill` |
+
+Sau khi install → tự động chạy `scan-skills` để cập nhật registry.
+
+Commands bổ sung:
+- `vp-tools uninstall-skill <id>` — xóa khỏi tất cả adapter dirs
+- `vp-tools list-skills` — hiển thị skills đã cài + version + source
+- `vp-tools update-skill <id>` — cập nhật từ source gốc
+
+### Tầng 2 — Scanner & Registry
+
+`vp-tools scan-skills` quét toàn bộ adapter dirs:
+- `~/.claude/skills/` (Claude Code)
+- `~/.cursor/skills/` (Cursor)
+- `~/.codex/skills/` (Codex)
+- `~/.antigravity/skills/` (Antigravity)
+
+Output: `~/.viepilot/skill-registry.json`
+
+```json
+{
+  "version": "1.0",
+  "last_scan": "2026-04-20T10:30:00Z",
+  "scan_paths": ["~/.claude/skills/", "~/.cursor/skills/"],
+  "skills": [
+    {
+      "id": "frontend-design",
+      "name": "Frontend Design",
+      "source": "npm:@vp-skills/frontend-design",
+      "version": "1.2.0",
+      "description": "...",
+      "capabilities": ["ui-generation", "component-design", "responsive-layout"],
+      "tags": ["ui", "design", "frontend", "css", "html"],
+      "best_practices": ["Mobile-first", "Design tokens", "BEM naming"],
+      "adapters": ["claude-code", "cursor"],
+      "installed_paths": {
+        "claude-code": "~/.claude/skills/frontend-design/",
+        "cursor": "~/.cursor/skills/frontend-design/"
+      }
+    }
+  ]
+}
+```
+
+### Tầng 3 — SKILL.md Extended Format
+
+Third-party skills (và vp-* skills nếu muốn) thêm 3 sections mới vào SKILL.md:
+
+```markdown
+## Capabilities
+- ui-generation
+- component-design
+- responsive-layout
+
+## Tags
+ui, design, frontend, css, html, tailwind
+
+## Best Practices
+- Use design tokens for consistency across components
+- Mobile-first: design breakpoints from 320px up
+- BEM naming convention for CSS classes
+```
+
+Scanner đọc các sections này để index. Skills không có sections mới vẫn được scan (fallback: parse description + content tự động).
+
+### Tầng 4 — Workflow Integration Pipeline
+
+#### A. Brainstorm → Silent Skill Application (UI-Direction)
+
+Khi brainstorm có UI signals (keywords: `component`, `design`, `layout`, `screen`, `UI`, v.v.):
+- Load `~/.viepilot/skill-registry.json`
+- Match skills có `capabilities` phù hợp (e.g., `ui-generation`, `component-design`)
+- **Silent apply**: tự động include best practices từ matched skills vào HTML generation
+- Record vào `notes.md`: `## skills_used` section
+
+```yaml
+## skills_used
+- id: frontend-design
+  version: 1.2.0
+  trigger: ui-generation signal
+  applied_at: brainstorm-session
+  best_practices_applied:
+    - Mobile-first
+    - Design tokens
+```
+
+Không hỏi user — chạy ngầm như Background UI Extraction.
+
+#### B. Crystallize → Skill Decision Lock Gate
+
+Bước mới trong `vp-crystallize` (sau scope lock, trước generate SPEC):
+
+1. Đọc `notes.md` → `## skills_used` của session đó
+2. Hiển thị danh sách skills đã/sẽ được dùng
+3. User confirm: required vs optional per phase/task
+4. Ghi vào `PROJECT-CONTEXT.md`:
+
+```markdown
+## Skills
+
+| Skill | Source | Required | Phases | Rationale |
+|-------|--------|----------|--------|-----------|
+| frontend-design | npm:@vp-skills/frontend-design | required | 1, 2 | UI-Direction HTML generation — design token best practices |
+| tailwind-guide | github:org/vp-tailwind | optional | 2 | Phase 2 styling layer |
+```
+
+**Lý do lock ở crystallize:** vp-auto là execution-only — nó đọc SPEC và chạy, không ra quyết định. Tất cả quyết định về "dùng skill nào" phải được lock trước khi vp-auto bắt đầu.
+
+#### C. vp-auto → Silent Skill Execution
+
+vp-auto đọc `## Skills` từ `PROJECT-CONTEXT.md`:
+- Với mỗi task, kiểm tra skills `required` trong phases tương ứng
+- Load best practices từ skill registry
+- Include context vào execution prompt — **không hỏi lại user**
+- Ghi vào task output: `skills_applied: [frontend-design@1.2.0]`
+
+---
+
+## Decisions
+
+| Decision | Options Considered | Chosen | Rationale |
+|----------|--------------------|--------|-----------|
+| Skill source channels | npm-only / all channels | All channels (npm + github + local) | Flexibility cho cả published và WIP skills |
+| Scanner scope | ViePilot-only dirs / all adapter dirs | All adapter dirs | Discover tất cả skills user đã cài qua bất kỳ tool nào |
+| Gate model | Required block / heuristic prompt / silent / hybrid | Silent auto-apply + crystallize-time lock | vp-auto không hỏi lại; quyết định từ crystallize. Nhất quán với ui-direction guard |
+| SKILL.md format | Giữ nguyên / extend / file riêng | Extend — thêm Capabilities/Tags/Best Practices | Backward compat; scanner vẫn parse skills cũ |
+| Lock storage | SPEC.md per-task / PROJECT-CONTEXT.md ## Skills / file riêng | PROJECT-CONTEXT.md ## Skills | Tương tự ## Tech Stack — project-level; dễ đọc cho vp-auto |
+| Phase 1 target | Scanner / Installer / Brainstorm integration | Scanner + registry first | Nền tảng cho mọi tính năng phía sau |
+
+---
+
+## Open Questions
+
+| ID | Question | Priority | Due |
+|----|----------|----------|-----|
+| Q1 | Có cần `vp-tools publish-skill` để user publish skill lên npm không? | low | next milestone |
+| Q2 | Skill versioning: nếu skill update, best practices thay đổi — có cần re-crystallize không? | medium | Phase 4 design |
+| Q3 | Skill conflict: 2 skills có cùng capability, workflow ưu tiên cái nào? | medium | Phase 3 design |
+| Q4 | Có cần một "official ViePilot skills registry" (marketplace) hay chỉ dựa vào npm search? | low | future |
+
+---
+
+## Phases
+
+### Phase 1 — Skill Registry Foundation
+**Goal**: `vp-tools scan-skills` + `~/.viepilot/skill-registry.json` + extended SKILL.md format spec
+
+Tasks:
+1. `lib/skill-registry.cjs` — scanner: traverse adapter dirs, parse SKILL.md (extended + legacy), build JSON
+2. `bin/viepilot.cjs` — add `scan-skills` subcommand + `list-skills` display
+3. `docs/user/features/skill-registry.md` — extended SKILL.md format spec + scanner docs
+4. `tests/unit/vp-skill-registry.test.js` — 15+ contract tests (scan, parse, index, legacy compat)
+
+Target version: **2.26.0**
+
+### Phase 2 — Third-party Skill Installation
+**Goal**: `vp-tools install-skill` (npm + github + local) + `uninstall-skill` + `update-skill`
+
+Tasks:
+1. `lib/skill-installer.cjs` — multi-channel installer (npm exec + git clone + fs copy)
+2. `bin/viepilot.cjs` — add `install-skill`, `uninstall-skill`, `update-skill` subcommands
+3. Post-install hook: auto-run `scan-skills`
+4. `tests/unit/vp-skill-installer.test.js` — 12+ tests (each channel, auto-scan trigger)
+
+Target version: **2.27.0**
+
+### Phase 3 — Brainstorm Integration (UI-Direction silent apply)
+**Goal**: brainstorm.md detects UI signals → loads registry → silently applies matched skill best practices → records `## skills_used` in notes.md
+
+Tasks:
+1. `workflows/brainstorm.md` — add skill registry load step + signal matching logic + silent apply rule
+2. `skills/vp-brainstorm/SKILL.md` — document skill integration behavior
+3. `tests/unit/brainstorm-skill-integration.test.js` — 10+ tests
+
+Target version: **2.28.0**
+
+### Phase 4 — Crystallize Skill Decision Gate
+**Goal**: crystallize.md new step → skill confirmation gate → `## Skills` in PROJECT-CONTEXT.md
+
+Tasks:
+1. `workflows/crystallize.md` — add skill gate step (read notes.md skills_used → AUQ confirm → write PROJECT-CONTEXT.md)
+2. `templates/project/PROJECT-CONTEXT.md` — add `## Skills` section template
+3. `skills/vp-crystallize/SKILL.md` — document skill gate
+4. `tests/unit/crystallize-skill-gate.test.js` — 10+ tests
+
+Target version: **2.29.0**
+
+### Phase 5 — vp-auto Silent Skill Execution
+**Goal**: autonomous.md reads `## Skills` from PROJECT-CONTEXT.md → per-task silent context injection
+
+Tasks:
+1. `workflows/autonomous.md` — add skill context load step + per-task skill injection rule
+2. `skills/vp-auto/SKILL.md` — document silent skill execution
+3. `tests/unit/autonomous-skill-execution.test.js` — 8+ tests
+
+Target version: **2.30.0**
+
+---
+
+## Background UI Extraction
+
+Waiver — session topic is a framework feature (skill registry), not a consumer app UI. No UI Direction artifacts needed.
+
+---
+
+## Project meta intake (FEAT-009)
+
+Waiver — ViePilot framework repo; profile binding already exists.
+
+---
+
+## Session Summary
+
+- **Feature**: ViePilot Skill Registry System
+- **Suggested ID**: FEAT-020
+- **Scope**: 5 phases — registry/scanner → installer → brainstorm integration → crystallize gate → vp-auto execution
+- **Key architectural decision**: Skills are **silent auto-apply** at brainstorm time; **locked at crystallize** time; **executed without re-asking** by vp-auto
+- **Backward compat**: Existing SKILL.md files still work — scanner gracefully handles missing extended sections
+- **First deliverable**: `vp-tools scan-skills` + `~/.viepilot/skill-registry.json` (Phase 1 → v2.26.0)

package/docs/skills-reference.md

@@ -525,3 +525,25 @@ Place custom `.pptx`/`.docx` files in `.viepilot/proposal-templates/` to overrid
 ```
 
 Full guide: `docs/user/features/proposal.md`
+
+---
+
+## /vp-skills
+
+**Purpose**: Agent-native global skill registry management — scan, list, install, uninstall, update, and inspect third-party skills from any project directory (ENH-062).
+
+### Commands
+| Command | Description |
+|---------|-------------|
+| `/vp-skills scan` | Refresh `~/.viepilot/skill-registry.json` by scanning all adapter dirs |
+| `/vp-skills list` | Display indexed skills table |
+| `/vp-skills install <src>` | Install from npm / `github:<user>/<repo>` / local path |
+| `/vp-skills uninstall <id>` | Remove skill from all adapter directories |
+| `/vp-skills update <id>` | Re-install from original source (`skill-meta.json`) |
+| `/vp-skills info <id>` | Show capabilities, best_practices, and adapter paths |
+
+### Notes
+- Uses installed vp-tools binary (`~/.claude/viepilot/bin/vp-tools.cjs`) — works from any project directory.
+- Fallback: `~/.cursor/viepilot/bin/vp-tools.cjs` for Cursor adapter.
+- Registry file: `~/.viepilot/skill-registry.json` — shared across all projects.
+- Confirmation AUQ prompt before destructive `uninstall` (Claude Code terminal only).

package/docs/user/features/adapters.md

@@ -8,7 +8,7 @@ ViePilot supports multiple AI coding platforms via its adapter system (FEAT-013)
 |------------|----------|------------|--------------|-------|--------------|
 | `claude-code` | Claude Code *(default)* | `~/.claude/skills/` | `~/.claude/viepilot/` | ✅ Stop, PreToolUse, … | `/vp-status` |
 | `cursor-agent` / `cursor-ide` | Cursor | `~/.cursor/skills/` | `~/.cursor/viepilot/` | — | `/vp-status` |
-| `antigravity` | Google Antigravity | `~/.antigravity/skills/` | `~/.antigravity/viepilot/` | — | `/vp-status` |
+| `antigravity` | Google Antigravity | `~/.gemini/antigravity/skills/` | `~/.gemini/antigravity/viepilot/` | — | `/vp-status` |
 | `codex` | OpenAI Codex CLI | `~/.codex/skills/` | `~/.codex/viepilot/` | — | `$vp-status` |
 | `copilot` | GitHub Copilot | `~/.config/gh-copilot/skills/` | `~/.config/gh-copilot/viepilot/` | — | `/vp-status` |
 
@@ -47,7 +47,7 @@ Skill source files use the neutral placeholder `{envToolDir}` in `execution_cont
 At install time, `{envToolDir}` is replaced with each adapter's `executionContextBase`:
 - `claude-code` → `.claude/viepilot`
 - `cursor` → `.cursor/viepilot`
-- `antigravity` → `.antigravity/viepilot`
+- `antigravity` → `.gemini/antigravity/viepilot`
 - `codex` → `.codex/viepilot`
 - `copilot` → `.config/gh-copilot/viepilot`
 

package/docs/user/features/scaffold-first.md

@@ -0,0 +1,62 @@
+# Scaffold-First Gate (BUG-020)
+
+`vp-auto` enforces a **scaffold-first** rule for framework-based projects: when a task initializes a new project, the canonical scaffold command MUST run before any framework-generated files are created manually.
+
+## How It Works
+
+1. **Detection** — vp-auto detects "project setup" tasks by keywords in the task title/objective: "set up", "initialize", "create project", "scaffold", "bootstrap", "new project"
+2. **Marker check** — checks for a framework marker file (e.g. `artisan` for Laravel, `manage.py` for Django) to determine if the project is already scaffolded
+3. **Scaffold command** — if not yet scaffolded, runs the scaffold command from either:
+   - `~/.viepilot/stacks/{stack}/SUMMARY.md` → `## Scaffold` → `init_command:` field (takes priority)
+   - The built-in heuristic table in `workflows/autonomous.md`
+4. **Block list** — refuses to create framework-native files (artisan, next.config.*, manage.py, nest-cli.json, pom.xml, etc.) without prior scaffold
+
+## Adding a Scaffold Command to a Stack
+
+In `~/.viepilot/stacks/{your-stack}/SUMMARY.md`, append:
+
+```markdown
+## Scaffold
+
+init_command: composer create-project laravel/laravel {name}
+marker_file: artisan
+```
+
+Replace `{name}` with the project directory name placeholder — vp-auto substitutes the actual project name at runtime.
+
+## Built-in Supported Stacks
+
+| Stack | Scaffold command | Marker file |
+|-------|-----------------|-------------|
+| laravel | `composer create-project laravel/laravel {name}` | `artisan` |
+| laravel-php84 | `composer create-project laravel/laravel:^11 {name}` | `artisan` |
+| nextjs | `npx create-next-app@latest {name}` | `next.config.js` |
+| nextjs-tailwind-shadcn-threejs | `npx create-next-app@latest {name} --typescript --tailwind --eslint --app` | `next.config.js` |
+| nestjs | `npx @nestjs/cli new {name}` | `nest-cli.json` |
+| rails | `rails new {name}` | `config/application.rb` |
+| django | `django-admin startproject {name} .` | `manage.py` |
+| spring-boot* | `spring init --dependencies=web,data-jpa,validation {name}` | `pom.xml` |
+| nuxt / vuejs* | `npx nuxi@latest init {name}` | `nuxt.config.ts` |
+| react | `npx create-react-app {name}` | `src/index.js` |
+| electron | `npx create-electron-app {name}` | `electron-builder.yml` |
+
+## Never-Handcraft Block List
+
+The following files must never be created manually in a project setup task without first running the scaffold command:
+
+- `artisan`, `composer.json` (Laravel)
+- `next.config.js`, `next.config.ts`, `pages/_app.*`, `app/layout.*` (Next.js)
+- `nest-cli.json`, `src/main.ts` + `tsconfig.json` combo (NestJS)
+- `manage.py`, `wsgi.py`, `asgi.py` (Django)
+- `config/application.rb`, `config/routes.rb`, `Gemfile` (Rails)
+- `pom.xml` or `build.gradle` with Spring Boot starters
+
+## Bypassing the Gate
+
+To override the gate (e.g. the project is already partially set up), add to the task file under `## Implementation Notes`:
+
+```
+scaffold_gate_waiver: project already scaffolded — artisan exists at {path}
+```
+
+Or at execution time, select "confirm project already scaffolded" at the control-point prompt.

package/docs/user/features/skill-registry.md

@@ -0,0 +1,125 @@
+# Skill Registry
+
+ViePilot can discover and index skills installed across all adapter directories. The registry powers workflow skill integration — brainstorm silently applies relevant skill best practices during UI-Direction sessions, crystallize locks skill decisions, and vp-auto executes with no re-prompting.
+
+## Commands
+
+| Command | Description |
+|---------|-------------|
+| `vp-tools scan-skills` | Scan all adapter dirs and write `~/.viepilot/skill-registry.json` |
+| `vp-tools list-skills` | Display indexed skills from the registry |
+| `vp-tools install-skill <source>` | Install a third-party skill *(Phase 91 — coming soon)* |
+
+## Extended SKILL.md Format
+
+Third-party skills (and built-in vp-* skills) can add optional metadata sections to their `SKILL.md`:
+
+```markdown
+## Capabilities
+- ui-generation
+- component-design
+- responsive-layout
+
+## Tags
+ui, design, frontend, css, html
+
+## Best Practices
+- Mobile-first: design breakpoints from 320px up
+- Use design tokens for consistency across components
+- BEM naming convention for CSS class names
+```
+
+### Section rules
+
+| Section | Format | Description |
+|---------|--------|-------------|
+| `## Capabilities` | One capability per line (`- item`) | Machine-readable ability tags used for skill matching |
+| `## Tags` | Comma-separated or one per line | Human-readable keywords for discovery |
+| `## Best Practices` | One practice per line (`- item`) | Applied silently when skill is matched in brainstorm/vp-auto |
+
+All sections are **optional** — skills without them are still indexed and available.
+
+### Backward compatibility
+
+Existing `SKILL.md` files that do not contain these sections continue to work without modification. The scanner indexes them with empty `capabilities`, `tags`, and `best_practices` arrays and marks them as `(legacy — no capabilities)` in `list-skills` output.
+
+## Scanner
+
+`vp-tools scan-skills` traverses the following adapter directories:
+
+| Adapter | Skill directory |
+|---------|----------------|
+| Claude Code | `~/.claude/skills/` |
+| Cursor | `~/.cursor/skills/` |
+| Codex | `~/.codex/skills/` |
+| Antigravity | `~/.gemini/antigravity/skills/` |
+| GitHub Copilot | `~/.config/gh-copilot/skills/` |
+
+Adapter directories that do not exist are silently skipped. The same skill found in multiple adapter directories is merged into a single registry entry with all adapters listed.
+
+## Registry Format
+
+The registry is written to `~/.viepilot/skill-registry.json`:
+
+```json
+{
+  "version": "1.0",
+  "last_scan": "2026-04-20T10:30:00.000Z",
+  "scan_paths": [
+    "/Users/you/.claude/skills",
+    "/Users/you/.cursor/skills"
+  ],
+  "skills": [
+    {
+      "id": "frontend-design",
+      "name": "frontend-design",
+      "source": null,
+      "version": null,
+      "description": "Opinionated frontend design guidance for UI-Direction sessions.",
+      "capabilities": ["ui-generation", "component-design", "responsive-layout"],
+      "tags": ["ui", "design", "frontend", "css"],
+      "best_practices": [
+        "Mobile-first: design breakpoints from 320px up",
+        "Use design tokens for consistency"
+      ],
+      "adapters": ["claude-code", "cursor"],
+      "installed_paths": {
+        "claude-code": "/Users/you/.claude/skills/frontend-design",
+        "cursor": "/Users/you/.cursor/skills/frontend-design"
+      }
+    }
+  ]
+}
+```
+
+### Schema reference
+
+| Field | Type | Description |
+|-------|------|-------------|
+| `id` | string | Directory name (unique per skill) |
+| `name` | string | Display name (defaults to `id`) |
+| `source` | string \| null | Installation source: `npm:pkg`, `github:org/repo`, `./path`, or `null` for manually placed skills |
+| `version` | string \| null | Version from `skill-meta.json` (future); `null` for legacy skills |
+| `description` | string | First non-heading paragraph from `SKILL.md` |
+| `capabilities` | string[] | From `## Capabilities` section |
+| `tags` | string[] | From `## Tags` section |
+| `best_practices` | string[] | From `## Best Practices` section |
+| `adapters` | string[] | Adapter IDs where this skill is installed |
+| `installed_paths` | object | `{ adapterId: absolutePath }` |
+
+## Workflow Integration
+
+The registry is used automatically by ViePilot workflows:
+
+### Brainstorm (UI-Direction)
+When UI signals are detected during a brainstorm session, relevant skills (matched by `capabilities`) are silently applied — their `best_practices` are included in HTML generation without prompting. Matched skills are recorded in `notes.md` under `## skills_used`.
+
+### Crystallize (skill decision lock)
+After the brainstorm scope is locked, crystallize presents the skills used and asks the user to confirm which are required vs optional per phase. The decision is written to `PROJECT-CONTEXT.md` under `## Skills`.
+
+### vp-auto (silent execution)
+vp-auto reads `## Skills` from `PROJECT-CONTEXT.md` and injects skill best practices per task — no re-asking. Decisions made at crystallize time are final.
+
+## Refreshing the Registry
+
+Run `vp-tools scan-skills` any time you install a new skill manually or after `vp-tools install-skill` (which runs it automatically). The registry is not auto-refreshed on session start.

package/lib/adapters/antigravity.cjs

@@ -6,10 +6,10 @@ const fs = require('fs');
 module.exports = {
   id: 'antigravity',
   name: 'Antigravity',
-  skillsDir:   (home) => path.join(home, '.antigravity', 'skills'),
-  viepilotDir: (home) => path.join(home, '.antigravity', 'viepilot'),
+  skillsDir:   (home) => path.join(home, '.gemini', 'antigravity', 'skills'),
+  viepilotDir: (home) => path.join(home, '.gemini', 'antigravity', 'viepilot'),
   // {envToolDir} in SKILL.md files resolves to this value at install time (ENH-035)
-  executionContextBase: '.antigravity/viepilot',
+  executionContextBase: '.gemini/antigravity/viepilot',
   // Post-install hint shown in "Next actions" after viepilot install
   postInstallHint: 'Open project and run /vp-status',
   hooks: {
@@ -29,6 +29,7 @@ module.exports = {
   ],
   isAvailable: (home) => {
     const h = home || os.homedir();
-    return fs.existsSync(path.join(h, '.antigravity'));
+    return fs.existsSync(path.join(h, '.gemini', 'antigravity'))
+      || fs.existsSync(path.join(h, '.antigravity'));
   }
 };