bob-pr-reviewer 0.0.5

package/README.md

@@ -0,0 +1,576 @@
+# bob-pr-reviewer `v0.0.5`
+
+An MCP (Model Context Protocol) server that gives AI assistants in VS Code the ability to **read GitHub Enterprise pull requests**, **fetch Jira ticket requirements**, and **post structured review comments** — all via natural language.
+
+**No clone required. No build step. No manual server startup.**  
+VS Code launches this automatically via `npx` — just configure once and it works everywhere.
+
+---
+
+## Table of Contents
+
+- [How It Works](#how-it-works)
+- [Quick Start (5 minutes)](#quick-start-5-minutes)
+- [Tools Available](#tools-available)
+- [Usage Examples](#usage-examples)
+- [What to Expect in VS Code](#what-to-expect-in-vs-code)
+- [What to Expect on GitHub](#what-to-expect-on-github)
+- [Project Structure](#project-structure)
+- [For Contributors / Local Development](#for-contributors--local-development)
+- [Publishing a New Version](#publishing-a-new-version)
+- [Troubleshooting](#troubleshooting)
+- [Security Notes](#security-notes)
+
+---
+
+## How It Works
+
+```
+You:    "@bob-pr-reviewer Review PR #1758 in sec-ci/notification and check it against the Jira ticket"
+           │
+           ▼
+     VS Code AI Assistant (IBM Bob / GitHub Copilot Chat / Cline)
+           │  sees MCP tools available, decides which to call
+           ▼
+     bob-pr-reviewer (auto-launched by VS Code via npx — no clone needed)
+           │  calls GitHub Enterprise API + Jira API in parallel
+           ▼
+     GitHub Enterprise (github.ibm.com)  +  Jira (jsw.ibm.com)
+           │  returns PR diff + Jira requirements
+           ▼
+     AI analyzes code vs requirements → posts structured comment to PR
+```
+
+VS Code spawns this MCP server as a subprocess automatically using `npx`. The package is downloaded and cached on first use — you never need to clone this repo or run a build command.
+
+---
+
+## Quick Start (5 minutes)
+
+> **Full step-by-step instructions:** see [SETUP.md](./SETUP.md)
+
+### Step 1 — Get your tokens
+
+| Token | Where to get it |
+|-------|----------------|
+| GitHub Enterprise PAT | `https://github.ibm.com/settings/tokens` → scope: **`repo`** |
+| Jira Personal Access Token | `https://jsw.ibm.com/secure/ViewProfile.jspa` → Personal Access Tokens |
+
+### Step 2 — Set your tokens
+
+Add to your `~/.zshrc` (or `~/.bashrc`):
+
+```bash
+export GITHUB_TOKEN=ghp_yourGitHubTokenHere
+export JIRA_ISV_PERSONAL_ACCESS_TOKEN=yourJiraTokenHere
+```
+
+Then reload: `source ~/.zshrc` and **restart VS Code completely**.
+
+### Step 3 — Add to VS Code User Settings
+
+Open VS Code global settings JSON (`Cmd+Shift+P` → **"Open User Settings (JSON)"**) and add:
+
+```json
+{
+  "mcp": {
+    "servers": {
+      "bob-pr-reviewer": {
+        "type": "stdio",
+        "command": "npx",
+        "args": ["-y", "bob-pr-reviewer"],
+        "env": {
+          "GITHUB_TOKEN": "${env:GITHUB_TOKEN}",
+          "GITHUB_BASE_URL": "https://github.ibm.com/api/v3",
+          "JIRA_ISV_PERSONAL_ACCESS_TOKEN": "${env:JIRA_ISV_PERSONAL_ACCESS_TOKEN}",
+          "JIRA_BASE_URL": "https://jsw.ibm.com"
+        }
+      }
+    }
+  }
+}
+```
+
+> ⚠️ This goes in **User Settings (JSON)** — not in `.vscode/settings.json` or `.vscode/mcp.json` in your project. User Settings apply globally across all projects.
+
+### Step 4 — Reload VS Code
+
+`Cmd+Shift+P` → **"Developer: Reload Window"**
+
+That's it. The server starts automatically. Open any project and the tools are available.
+
+---
+
+## Slash Commands (Recommended)
+
+MCP prompts appear as **slash commands** with autocomplete in IBM Bob and other MCP-compatible AI clients. Type `/bob-pr-reviewer` to see all available commands.
+
+> 💡 The `bob-pr-reviewer:` prefix ensures these commands never clash with slash commands from other MCP servers you may have loaded.
+
+| Slash command | Description | Arguments |
+|---|---|---|
+| `/bob-pr-reviewer:check-setup` | Run prerequisites check | none |
+| `/bob-pr-reviewer:review-pr` | Full code review with inline comments | `repo`, `pr_number` |
+| `/bob-pr-reviewer:review-pr-vs-jira` | Review PR against its Jira ticket | `repo`, `pr_number`, `ticket_key` (optional) |
+| `/bob-pr-reviewer:get-pr-info` | Fetch PR metadata | `repo`, `pr_number` |
+| `/bob-pr-reviewer:get-jira-ticket` | Fetch Jira ticket requirements | `ticket_key` |
+| `/bob-pr-reviewer:post-comment` | Post a general comment on a PR | `repo`, `pr_number`, `comment` |
+
+**How to use:**
+1. Type `/bob-pr-reviewer:` in the IBM Bob chat — autocomplete shows all commands
+2. Select a command — the AI prompts you for any required arguments
+3. The AI fills in the message and calls the appropriate tools automatically
+
+---
+
+## Tools Available
+
+| Tool | Description |
+|------|-------------|
+| `check_setup` | Re-run all prerequisites checks and show status |
+| `validate_token` | Verify your GitHub token is working |
+| `get_pr_info` | Fetch PR title, author, branches, commit SHA, description |
+| `fetch_pr_diff` | Fetch all changed files + unified diffs |
+| `post_review` | Post a review with inline comments at diff positions |
+| `post_comment` | Post a general (non-inline) PR comment |
+| `get_jira_ticket` | Fetch a Jira ticket's summary, description, acceptance criteria |
+| `check_pr_vs_jira` | Auto-detect Jira ticket from PR, fetch requirements, return analysis context |
+| `post_jira_analysis` | Post the Jira vs PR analysis as a structured comment (called automatically after `check_pr_vs_jira`) |
+
+### Tool call chain for Jira-aware review
+
+```
+check_pr_vs_jira
+    ├── fetches PR info + diff from GitHub
+    ├── auto-detects Jira ticket key from PR title/branch/description
+    ├── fetches Jira requirements
+    └── returns structured context to AI
+         │
+         ▼ (AI analyzes, then MUST call:)
+post_jira_analysis
+    ├── receives verdict, coverage list, gaps list, summary from AI
+    └── posts formatted Markdown comment to the PR on GitHub
+```
+
+---
+
+## Usage Examples
+
+> 💡 **Prefer slash commands** — type `/bob-pr-reviewer:` for autocomplete. Use the `@bob-pr-reviewer` prefix in free-text prompts when you need more control or have multiple MCP servers loaded.
+
+### Jira-aware review (recommended)
+
+**Slash command (autocomplete):**
+```
+/bob-pr-reviewer:review-pr-vs-jira
+```
+
+**Or free-text prompt:**
+```
+@bob-pr-reviewer Check PR #1758 in sec-ci/notification against its Jira ticket and post the analysis
+```
+
+If the PR title/branch/description contains a Jira key (e.g. `VDEV-47721`), it's detected automatically. If not, provide it explicitly:
+
+```
+@bob-pr-reviewer Check PR #1758 in sec-ci/notification against Jira ticket VDEV-47721
+```
+
+### Basic PR review with inline comments
+
+**Slash command:**
+```
+/bob-pr-reviewer:review-pr
+```
+
+**Or free-text prompt:**
+```
+@bob-pr-reviewer Review PR #1758 in sec-ci/notification and post your findings as inline comments
+```
+
+### Fetch PR info only
+
+**Slash command:**
+```
+/bob-pr-reviewer:get-pr-info
+```
+
+**Or free-text prompt:**
+```
+@bob-pr-reviewer Get the details for PR #1758 in sec-ci/notification
+```
+
+### Fetch a Jira ticket
+
+**Slash command:**
+```
+/bob-pr-reviewer:get-jira-ticket
+```
+
+**Or free-text prompt:**
+```
+@bob-pr-reviewer Get the requirements for Jira ticket VDEV-47721
+```
+
+### Post a quick comment
+
+**Slash command:**
+```
+/bob-pr-reviewer:post-comment
+```
+
+**Or free-text prompt:**
+```
+@bob-pr-reviewer Post a comment on PR #1758 in sec-ci/notification: "LGTM! Nice work."
+```
+
+### Verify setup
+
+**Slash command:**
+```
+/bob-pr-reviewer:check-setup
+```
+
+**Or free-text prompt:**
+```
+@bob-pr-reviewer Run check_setup
+```
+
+---
+
+## What to Expect in VS Code
+
+### On first use
+
+When VS Code first launches the server, `npx` downloads and caches the package automatically. You'll see a brief pause — subsequent launches are instant.
+
+To verify the server is running:
+1. Open the **Output** panel: `View → Output`
+2. Select **MCP** from the dropdown
+3. You should see output like this (shown as "errors" in VS Code's panel — this is normal, all MCP server logs go to stderr):
+
+```
+[bob-pr-reviewer] Starting up... GitHub: https://github.ibm.com/api/v3 | Jira: https://jsw.ibm.com
+[bob-pr-reviewer] Prerequisites check:
+  ✓ Node.js version: Node.js 18.19.0 (requires >= 18.x)
+  ✓ GITHUB_TOKEN environment variable: GITHUB_TOKEN is set (length: 40)
+  ✓ GitHub token validity: Token is valid — authenticated as: your-username
+  ✓ GitHub API reachability: https://github.ibm.com/api/v3 is reachable
+  ✓ JIRA_ISV_PERSONAL_ACCESS_TOKEN environment variable: set (length: 38)
+  ✓ Jira token validity: Token is valid — authenticated as: Your Name
+[bob-pr-reviewer] ✅ All checks passed — registering all tools
+[bob-pr-reviewer] MCP server ready (stdio transport)
+```
+
+> **Note:** VS Code's MCP output panel labels all server log messages as "errors" — this is cosmetic. If you see the `✅ All checks passed` line, the server is healthy and working correctly.
+
+If any check fails, the server runs in **degraded mode** — only the `check_setup` tool is available, and it will tell you exactly what to fix.
+
+### Checking setup status
+
+At any time, use the slash command:
+```
+/bob-pr-reviewer:check-setup
+```
+
+Or ask in free-text:
+```
+@bob-pr-reviewer Run check_setup
+```
+
+The AI will call `check_setup` and show you the current status of all prerequisites.
+
+---
+
+## What to Expect on GitHub
+
+### After `check_pr_vs_jira` + `post_jira_analysis`
+
+A structured comment is automatically posted to the PR on `github.ibm.com`. It looks like this:
+
+---
+
+**🤖 Requirements Check: [VDEV-47721](https://jsw.ibm.com/browse/VDEV-47721)**
+
+**Jira:** Domain auth APIs rate limit  
+**Verdict:** ⚠️ Partial Match
+
+**Requirements Coverage**
+- ✅ Rate limiting logic implemented in `NotificationConfigResource.java`
+- ✅ New `RateLimitConfig` class added with configurable thresholds
+- ⚠️ Error response format differs from acceptance criteria (returns 429 but missing `Retry-After` header)
+
+**Gaps / Concerns**
+- Missing `Retry-After` header in 429 responses per RFC 6585
+- No unit tests for the rate limit boundary conditions
+- Config reload behavior under concurrent requests not tested
+
+**Summary**
+The PR implements the core rate limiting feature described in VDEV-47721 and correctly gates domain auth API calls per tenant. However, the HTTP 429 response is missing the `Retry-After` header required by the acceptance criteria, and test coverage for edge cases is absent.
+
+---
+_Automated check by bob-pr-reviewer • [VDEV-47721](https://jsw.ibm.com/browse/VDEV-47721)_
+
+---
+
+### After `post_review` (inline comments)
+
+If you ask for a full code review with inline comments, the AI calls `post_review` which posts a GitHub review with:
+- An overall summary
+- Inline comments at specific diff positions (shown in the **Files changed** tab)
+- A review state: `COMMENT`, `APPROVE`, or `REQUEST_CHANGES`
+
+---
+
+## Project Structure
+
+```
+bob-pr-reviewer/
+├── src/
+│   ├── index.ts            # MCP server entry point — tool registration, startup flow
+│   ├── github-client.ts    # GitHub Enterprise REST API client
+│   ├── jira-client.ts      # Jira REST API v2 client (PAT auth, ADF parsing)
+│   ├── prerequisites.ts    # Startup validator (Node, tokens, APIs)
+│   └── tools.ts            # MCP tool schema definitions (reference)
+├── dist/                   # Compiled JavaScript — included in npm package
+├── .vscode/
+│   └── mcp.json            # VS Code built-in MCP config for local dev (uses local dist/)
+├── .bob/
+│   └── mcp.json            # IBM Bob extension MCP config for local dev (uses local dist/)
+├── .env.example            # Template showing required variables
+├── package.json            # includes "bin" field for npx support
+├── tsconfig.json
+├── SETUP.md                # Detailed installation guide for end users
+├── PROMPT_TEMPLATE.md      # Reusable prompt template for building new MCP servers
+└── README.md
+```
+
+### Key files explained
+
+**`src/index.ts`** — The main server. Loads `.env`, runs prerequisites, registers tools. Two modes:
+- **Healthy**: all 9 tools registered
+- **Degraded**: only `check_setup` registered (with fix instructions)
+
+**`src/github-client.ts`** — Wraps GitHub Enterprise REST API v3. Methods: `getPrInfo()`, `getPrFiles()`, `postReview()`, `postComment()`, `validateToken()`.
+
+**`src/jira-client.ts`** — Wraps Jira REST API v2 with Bearer token auth. Handles Atlassian Document Format (ADF) → plain text conversion. Tries 6 custom field IDs to find Acceptance Criteria. Static `extractTicketKey()` regex for auto-detection.
+
+**`src/prerequisites.ts`** — Runs checks at startup: Node.js version, `GITHUB_TOKEN` set, GitHub token valid (live API call), GitHub API reachable, `JIRA_ISV_PERSONAL_ACCESS_TOKEN` set, Jira token valid (live API call). Each failed check includes step-by-step fix instructions.
+
+**`.vscode/mcp.json`** — Used by VS Code's built-in MCP support when this repo is open. Points to `dist/index.js` (local build) so changes are picked up immediately without publishing.
+
+**`.bob/mcp.json`** — Used by the IBM Bob extension when this repo is open. Same purpose as `.vscode/mcp.json` but in Bob's format (`mcpServers` key). Both files override the global User Settings entry only while this project is open.
+
+---
+
+## For Contributors / Local Development
+
+If you want to modify the server or contribute:
+
+```bash
+git clone git@github.ibm.com:himanshu-sao-ibm/bob-pr-reviewer.git
+cd bob-pr-reviewer
+npm install
+npm run build
+```
+
+Both `.vscode/mcp.json` and `.bob/mcp.json` in this repo point directly to the local build output (`dist/index.js`) so your changes are picked up immediately — no publishing needed. They override the global User Settings entry **only when this project is open in VS Code**. All other projects continue to use the published npm version.
+
+> **How precedence works:** Project-level MCP configs (`.vscode/mcp.json` for VS Code built-in, `.bob/mcp.json` for IBM Bob) take precedence over User Settings when the project is open. Both use the same server name (`bob-pr-reviewer`) — no conflicts, no duplicate servers.
+
+**`.vscode/mcp.json`** (VS Code built-in MCP):
+```json
+{
+  "servers": {
+    "bob-pr-reviewer": {
+      "type": "stdio",
+      "command": "node",
+      "args": ["dist/index.js"],
+      "env": {
+        "GITHUB_TOKEN": "${env:GITHUB_TOKEN}",
+        "GITHUB_BASE_URL": "https://github.ibm.com/api/v3",
+        "JIRA_ISV_PERSONAL_ACCESS_TOKEN": "${env:JIRA_ISV_PERSONAL_ACCESS_TOKEN}",
+        "JIRA_BASE_URL": "https://jsw.ibm.com"
+      }
+    }
+  }
+}
+```
+
+**`.bob/mcp.json`** (IBM Bob extension):
+```json
+{
+  "mcpServers": {
+    "bob-pr-reviewer": {
+      "type": "stdio",
+      "command": "node",
+      "args": ["dist/index.js"],
+      "env": {
+        "GITHUB_TOKEN": "${env:GITHUB_TOKEN}",
+        "GITHUB_BASE_URL": "https://github.ibm.com/api/v3",
+        "JIRA_ISV_PERSONAL_ACCESS_TOKEN": "${env:JIRA_ISV_PERSONAL_ACCESS_TOKEN}",
+        "JIRA_BASE_URL": "https://jsw.ibm.com"
+      }
+    }
+  }
+}
+```
+
+After making code changes, rebuild and reload:
+
+```bash
+npm run build
+# Then in VS Code: Cmd+Shift+P → "Developer: Reload Window"
+```
+
+---
+
+## Publishing a New Version
+
+> **Who does this:** Only the maintainer (`himanshu-sao-ibm`) needs to do this when releasing updates. Teammates never need to run these steps.
+
+### First-time setup (one-time only)
+
+1. Create an account at [npmjs.com](https://www.npmjs.com) if you don't have one
+2. Log in from your terminal:
+   ```bash
+   npm login
+   ```
+   Enter your npm username, password, and email when prompted.
+
+   > **2FA / Granular Access Token:** If your npm account has 2FA enabled, you have two options:
+   > - Pass your OTP at publish time: `./publish.sh --otp=123456`
+   > - Or create a **Granular Access Token** on npmjs.com with "Read and write" + bypass 2FA, then set it:
+   >   ```bash
+   >   npm set //registry.npmjs.org/:_authToken YOUR_TOKEN
+   >   ```
+
+### Publishing an update (using `publish.sh`)
+
+A [`publish.sh`](./publish.sh) script is included that handles build + version bump + publish in one step:
+
+```bash
+# Make executable (one-time)
+chmod +x publish.sh
+
+# Patch release — bug fixes (0.0.5 → 0.0.6)
+./publish.sh
+
+# Minor release — new features, backwards compatible (0.0.5 → 0.1.0)
+./publish.sh minor
+
+# Major release — breaking changes (0.0.5 → 1.0.0)
+./publish.sh major
+
+# Publish current version as-is (no version bump)
+./publish.sh --no-bump
+
+# With 2FA OTP (if your npm account requires it)
+./publish.sh minor --otp=123456
+```
+
+The script will:
+1. Verify you are logged in to npm
+2. Run `npm run build` (TypeScript → `dist/`)
+3. Bump the version in `package.json`
+4. Run `npm publish`
+5. Print the package URL and next steps for users
+
+### Manual publish (without the script)
+
+```bash
+# 1. Make your code changes in src/
+
+# 2. Build the compiled output
+npm run build
+
+# 3. Bump the version (choose one):
+npm version patch   # 0.0.5 → 0.0.6  (bug fixes)
+npm version minor   # 0.0.5 → 0.1.0  (new features, backwards compatible)
+npm version major   # 0.0.5 → 1.0.0  (breaking changes)
+
+# 4. Publish to npm
+npm publish
+# With 2FA OTP:
+npm publish --otp=123456
+```
+
+`npm version` automatically updates `package.json`. `npm publish` uploads only the `dist/` folder (as defined in `"files"` in `package.json`).
+
+### Verify the publish succeeded
+
+```bash
+npm view bob-pr-reviewer version
+# Should show the new version number
+```
+
+Or check: `https://www.npmjs.com/package/bob-pr-reviewer`
+
+### After publishing — users get the update automatically
+
+Users running `npx -y bob-pr-reviewer` will get the new version automatically on next VS Code launch. If they want to force a refresh of a cached version:
+
+```bash
+npx clear-npx-cache
+# Then: Cmd+Shift+P → "Developer: Reload Window"
+```
+
+---
+
+## Troubleshooting
+
+### Server doesn't appear in VS Code
+
+1. Check the MCP output panel: `View → Output → MCP`
+2. Make sure you added the config to **User Settings (JSON)** (global), not workspace settings
+3. Reload VS Code: `Cmd+Shift+P` → "Developer: Reload Window"
+4. Verify `npx bob-pr-reviewer` works in your terminal
+
+### All MCP logs show as "errors" in VS Code
+
+This is normal and expected. VS Code's MCP output panel labels all stderr output as errors regardless of content. MCP servers must use stderr for logging (stdout is reserved for the JSON-RPC protocol). If you see `✅ All checks passed`, the server is working correctly.
+
+### "GITHUB_TOKEN is not set"
+
+The token isn't reaching the server. Make sure you:
+1. Added `export GITHUB_TOKEN=...` to `~/.zshrc`
+2. Ran `source ~/.zshrc`
+3. **Fully restarted VS Code** (quit and reopen — not just reload window)
+
+### "GitHub API error 401: Bad credentials"
+
+Your token is invalid or expired. Generate a new one at `https://github.ibm.com/settings/tokens` with `repo` scope.
+
+### "Cannot reach github.ibm.com"
+
+You're not on IBM VPN. Connect to VPN and reload VS Code.
+
+### "No Jira ticket key found in PR"
+
+The PR title/branch/description doesn't contain a recognizable Jira key pattern (e.g. `ABC-1234`). Provide it explicitly:
+```
+Check PR #1758 in sec-ci/notification against Jira ticket VDEV-47721
+```
+
+### Inline comments fail with position errors
+
+The `position` field in `post_review` refers to the **line position in the unified diff** (1-based), not the actual file line number. The AI calculates these from the diff returned by `fetch_pr_diff`. If positions are wrong, ask the AI to re-fetch the diff and recount.
+
+### Degraded mode — only `check_setup` available
+
+Ask the AI: `@bob-pr-reviewer Run check_setup` — it will show exactly which check failed and how to fix it.
+
+---
+
+## Security Notes
+
+- **Never commit your `.env` file** — it's in `.gitignore`
+- Tokens are passed via environment variables and never sent to the AI model
+- The MCP server only has access to repos your GitHub token can access
+- The server runs locally — no data leaves your machine except to `github.ibm.com` and `jsw.ibm.com`
+
+---
+
+## License
+
+ISC

package/dist/github-client.d.ts

@@ -0,0 +1,73 @@
+/**
+ * GitHub Enterprise API client for bob-pr-reviewer MCP server.
+ * Handles all communication with the GitHub Enterprise REST API.
+ */
+export interface PrInfo {
+    number: number;
+    title: string;
+    author: string;
+    state: string;
+    baseBranch: string;
+    headBranch: string;
+    description: string;
+    commitSha: string;
+    url: string;
+    createdAt: string;
+    updatedAt: string;
+}
+export interface PrFile {
+    filename: string;
+    status: string;
+    additions: number;
+    deletions: number;
+    patch: string;
+}
+export interface ReviewComment {
+    path: string;
+    position: number;
+    body: string;
+}
+export interface PostReviewRequest {
+    repo: string;
+    prNumber: number;
+    commitSha: string;
+    summary: string;
+    event: 'COMMENT' | 'APPROVE' | 'REQUEST_CHANGES';
+    comments: ReviewComment[];
+}
+export interface PostReviewResult {
+    reviewId: number;
+    htmlUrl: string;
+    state: string;
+}
+export declare class GitHubClient {
+    private baseUrl;
+    private token;
+    constructor(baseUrl: string, token: string);
+    private get headers();
+    private request;
+    /**
+     * Get PR metadata: title, author, branches, description, commit SHA
+     */
+    getPrInfo(repo: string, prNumber: number): Promise<PrInfo>;
+    /**
+     * Get all changed files and their diffs for a PR
+     */
+    getPrFiles(repo: string, prNumber: number): Promise<PrFile[]>;
+    /**
+     * Post a review with optional inline comments to a PR
+     */
+    postReview(req: PostReviewRequest): Promise<PostReviewResult>;
+    /**
+     * Post a general (non-inline) comment on a PR
+     */
+    postComment(repo: string, prNumber: number, body: string): Promise<{
+        commentId: number;
+        htmlUrl: string;
+    }>;
+    /**
+     * Validate that the token works and return the authenticated user
+     */
+    validateToken(): Promise<string>;
+}
+//# sourceMappingURL=github-client.d.ts.map

package/dist/github-client.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"github-client.d.ts","sourceRoot":"","sources":["../src/github-client.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,MAAM,WAAW,MAAM;IACrB,MAAM,EAAE,MAAM,CAAC;IACf,KAAK,EAAE,MAAM,CAAC;IACd,MAAM,EAAE,MAAM,CAAC;IACf,KAAK,EAAE,MAAM,CAAC;IACd,UAAU,EAAE,MAAM,CAAC;IACnB,UAAU,EAAE,MAAM,CAAC;IACnB,WAAW,EAAE,MAAM,CAAC;IACpB,SAAS,EAAE,MAAM,CAAC;IAClB,GAAG,EAAE,MAAM,CAAC;IACZ,SAAS,EAAE,MAAM,CAAC;IAClB,SAAS,EAAE,MAAM,CAAC;CACnB;AAED,MAAM,WAAW,MAAM;IACrB,QAAQ,EAAE,MAAM,CAAC;IACjB,MAAM,EAAE,MAAM,CAAC;IACf,SAAS,EAAE,MAAM,CAAC;IAClB,SAAS,EAAE,MAAM,CAAC;IAClB,KAAK,EAAE,MAAM,CAAC;CACf;AAED,MAAM,WAAW,aAAa;IAC5B,IAAI,EAAE,MAAM,CAAC;IACb,QAAQ,EAAE,MAAM,CAAC;IACjB,IAAI,EAAE,MAAM,CAAC;CACd;AAED,MAAM,WAAW,iBAAiB;IAChC,IAAI,EAAE,MAAM,CAAC;IACb,QAAQ,EAAE,MAAM,CAAC;IACjB,SAAS,EAAE,MAAM,CAAC;IAClB,OAAO,EAAE,MAAM,CAAC;IAChB,KAAK,EAAE,SAAS,GAAG,SAAS,GAAG,iBAAiB,CAAC;IACjD,QAAQ,EAAE,aAAa,EAAE,CAAC;CAC3B;AAED,MAAM,WAAW,gBAAgB;IAC/B,QAAQ,EAAE,MAAM,CAAC;IACjB,OAAO,EAAE,MAAM,CAAC;IAChB,KAAK,EAAE,MAAM,CAAC;CACf;AAED,qBAAa,YAAY;IACvB,OAAO,CAAC,OAAO,CAAS;IACxB,OAAO,CAAC,KAAK,CAAS;gBAEV,OAAO,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM;IAM1C,OAAO,KAAK,OAAO,GAOlB;YAEa,OAAO;IA0BrB;;OAEG;IACG,SAAS,CAAC,IAAI,EAAE,MAAM,EAAE,QAAQ,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,CAAC;IAkBhE;;OAEG;IACG,UAAU,CAAC,IAAI,EAAE,MAAM,EAAE,QAAQ,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,EAAE,CAAC;IAYnE;;OAEG;IACG,UAAU,CAAC,GAAG,EAAE,iBAAiB,GAAG,OAAO,CAAC,gBAAgB,CAAC;IA2BnE;;OAEG;IACG,WAAW,CAAC,IAAI,EAAE,MAAM,EAAE,QAAQ,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,GAAG,OAAO,CAAC;QAAE,SAAS,EAAE,MAAM,CAAC;QAAC,OAAO,EAAE,MAAM,CAAA;KAAE,CAAC;IAehH;;OAEG;IACG,aAAa,IAAI,OAAO,CAAC,MAAM,CAAC;CAIvC"}