@tyroneross/build-loop 0.30.3

package/commands/optimize.md

@@ -0,0 +1,31 @@
+---
+name: optimize
+description: "(Advanced override — `/build-loop:run` auto-routes here; use this only to force the mode.) Run autonomous metric-driven optimization. Detects available targets or accepts a specific one."
+argument-hint: "[target]"
+---
+
+<!-- SPDX-FileCopyrightText: 2025-2026 Tyrone Ross, Jr <46267523+tyroneross@users.noreply.github.com> | SPDX-License-Identifier: Apache-2.0 -->
+
+Load the `build-loop:optimize` skill.
+
+{{#if ARGUMENTS}}
+Target: `{{ARGUMENTS}}`
+
+Run all three phases:
+1. **Setup** — configure the optimization for the specified target
+2. **Loop** — iterate: hypothesize → edit → measure → keep or revert
+3. **Review** — check for overfitting, summarize results
+
+If the target matches a known profile (`simplify`, `optimize-build`, `optimize-tests`, `optimize-bundle`, `optimize-perf`, `semantic-search-latency`), use the pre-configured settings from `profiles.md`.
+
+For custom targets, run Phase 1 (Setup) interactively.
+For latency-sensitive targets, prefer repeated sampling with warmups and a stable aggregate such as `median` or `p95` instead of a single timing sample.
+{{else}}
+No target specified.
+
+1. Run `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/optimize_loop.py --detect --workdir "$PWD"` to discover available targets
+2. Check for existing `.build-loop/optimize/experiment.json` — offer to resume if found
+3. Present available targets and let the user choose
+4. The `simplify` target is always available (reduces line count in changed files)
+5. For response-time work, initialize a custom target with `--metric-samples`, `--metric-warmups`, and `--metric-aggregate` so the loop compares stable latency numbers instead of one noisy run
+{{/if}}

package/commands/plan-verify.md

@@ -0,0 +1,39 @@
+---
+name: plan-verify
+description: "Deterministic verifier for plan markdown — grep-checkable rules (delete-with-callers, numeric-drift, route-change-evidence, package-state, missing-evidence). Run before accepting a Phase 2 plan."
+argument-hint: "<plan.md>"
+---
+
+<!-- SPDX-FileCopyrightText: 2025-2026 Tyrone Ross, Jr <46267523+tyroneross@users.noreply.github.com> | SPDX-License-Identifier: Apache-2.0 -->
+
+Load the `plan-verify` skill from `${CLAUDE_PLUGIN_ROOT}/skills/plan-verify/SKILL.md` for context.
+
+{{#if ARGUMENTS}}
+Plan file: `{{ARGUMENTS}}`
+
+Run:
+
+```bash
+python3 ${CLAUDE_PLUGIN_ROOT}/scripts/plan_verify.py {{ARGUMENTS}} --repo "$PWD" --json
+```
+
+Then:
+
+1. Report the summary (BLOCKER / WARN / INFO counts and per-rule breakdown).
+2. If exit code is 1, list each BLOCKER with claim_text + line + rule_id and stop — do NOT proceed to Phase 3.
+3. If exit code is 0, surface WARN findings as advisory and proceed.
+4. If exit code is 2, treat as verifier outage and surface to the user.
+
+For non-deterministic checks (alternatives considered, MECE scope, marker adequacy),
+follow up by dispatching the `plan-critic` agent with the same plan + this script's JSON output.
+{{else}}
+No plan file specified.
+
+Usage: `/plan-verify <path-to-plan.md>`
+
+Example: `/plan-verify .build-loop/plan.md`
+
+The verifier exits 0 if there are no BLOCKERs, 1 if BLOCKERs are present, 2 on verifier error.
+
+To inspect rules, read `${CLAUDE_PLUGIN_ROOT}/skills/plan-verify/SKILL.md`.
+{{/if}}

package/commands/promote-experiment.md

@@ -0,0 +1,129 @@
+---
+name: build-loop:promote-experiment
+description: Promote an auto-promoted experimental skill or agent from project-local `.build-loop/skills/active/` into the build-loop plugin repo, making it available across every project. Requires user confirmation and opens a PR on the plugin repo for review.
+argument-hint: <artifact-name>
+---
+
+<!-- SPDX-FileCopyrightText: 2025-2026 Tyrone Ross, Jr <46267523+tyroneross@users.noreply.github.com> | SPDX-License-Identifier: Apache-2.0 -->
+
+# /build-loop:promote-experiment <name>
+
+Promote a proven experimental artifact into the build-loop plugin itself. This is the manual, user-approved counterpart to Phase 6 Learn's auto-promote — which stays local to the project. Cross-project promotion modifies the plugin repo and affects every user, so it is never automatic.
+
+## Prerequisites
+
+1. The artifact must exist at `.build-loop/skills/active/<name>/SKILL.md` (already auto-promoted within the project), OR at `.build-loop/skills/experimental/<name>/SKILL.md` (user is fast-tracking without waiting for A/B completion — require explicit confirmation).
+
+2. The build-loop plugin repo must be writable. Check:
+   ```bash
+   BUILD_LOOP_REPO="${CLAUDE_PLUGIN_ROOT:-$HOME/Desktop/git-folder/build-loop}"
+   [ -d "$BUILD_LOOP_REPO/.git" ] && [ -w "$BUILD_LOOP_REPO/skills" ]
+   ```
+   If false, abort with "build-loop plugin repo not writable at $BUILD_LOOP_REPO".
+
+3. The user must supply `<name>` as an argument. If missing, list current candidates:
+   ```bash
+   ls .build-loop/skills/active/ 2>/dev/null
+   ls .build-loop/skills/experimental/ 2>/dev/null
+   ```
+
+## Steps
+
+### 1. Read the evidence
+
+Collect:
+- The artifact's SKILL.md content
+- Its experiments jsonl (`.build-loop/experiments/<name>.jsonl`)
+- All `applied` entries across this project (and, if a global index exists at `~/.build-loop/experiments/<name>.jsonl`, append those too)
+- Any `auto_promote` or `extend_sample` decisions from `.build-loop/experiments/decisions.jsonl`
+
+Compute:
+- Total applied runs (across projects)
+- Aggregate win rate vs baseline
+- Any regression signals (reversed auto-promotes, discard attempts)
+
+### 2. Synthesize a promotion dossier
+
+Build a markdown summary for the user:
+
+```markdown
+## Promotion dossier: <name>
+
+**Type**: skill | agent
+**Auto-promoted in this project**: <date>, after N runs
+**Cross-project evidence**: P projects, Q applied runs, R wins, S regressions
+**Aggregate metric delta**: +X% vs baseline (target was +Y%)
+**SKILL.md length**: N lines
+**Dependencies declared**: (none | list)
+**Last modified**: <date>
+
+**What the skill does** (from description frontmatter):
+<one line>
+
+**Recommended promotion target**:
+- Name on promote: build-loop:<name>  (or rename to: build-loop:<suggested-name>)
+- Target path: skills/<name>/SKILL.md in the plugin repo
+- Triggers on: <extracted trigger phrases>
+```
+
+### 3. Ask the user
+
+Use `AskUserQuestion`:
+
+```
+Question: "Promote '<name>' into the build-loop plugin repo?"
+Header: "Promote"
+Options:
+  - "Promote as drafted" — copy SKILL.md verbatim, open PR
+  - "Promote with rename" — user provides new name, then copy + PR
+  - "Review first" — output the dossier but do not copy (user decides after reading)
+  - Cancel (implicit via AskUserQuestion "Other")
+```
+
+### 4. Execute
+
+If user approved promotion:
+
+1. Determine target path: `$BUILD_LOOP_REPO/skills/<final-name>/SKILL.md` (plus any references/ subdirectory from source).
+2. If target already exists:
+   - Abort and ask user to choose a new name, OR confirm overwrite.
+3. Create a feature branch on the plugin repo: `feat/promote-<name>-from-<project-slug>`.
+4. Copy files. Edit frontmatter: remove `experimental: true`, `promoted_at`, `promoted_from_project`; add `promoted_at: <ISO>`, `promoted_from_project: <project-name>`, `original_baseline: <N>`, `aggregate_delta: <percent>`.
+5. Update the plugin's `skills/build-loop/SKILL.md` capability routing table to reference the new skill if it fits an existing row, OR add a new row (ask the user which).
+6. Commit:
+   ```
+   feat(skills): promote <name> from Phase 6 Learn
+
+   Originated as auto-drafted experimental skill in <project>.
+   Aggregate track record: P projects, Q runs, +X% vs baseline
+   (target was +Y%). SKILL.md copied verbatim with promotion
+   metadata added to frontmatter.
+
+   Evidence log: .build-loop/experiments/<name>.jsonl (N entries)
+   Signed off by Opus 4.7 on <auto-promote date>.
+   ```
+7. Push the branch and open a PR with the promotion dossier as the body.
+
+### 5. Record in project
+
+Append to `.build-loop/experiments/decisions.jsonl`:
+
+```jsonl
+{"event": "cross_project_promote", "date": "ISO", "name": "<name>", "plugin_pr_url": "<url>", "aggregate_evidence": { runs, projects, delta }}
+```
+
+Do not delete the local artifact — it stays in `.build-loop/skills/active/<name>/`. The plugin version will shadow it once installed; the local copy is retained as the historical source.
+
+## Safety rails
+
+- **Never auto-invoke**. Phase 6 Learn auto-promote stops at the project boundary. This command is the only path to the plugin repo.
+- **Require user confirmation**. AskUserQuestion is mandatory.
+- **Always open a PR**, never commit to main directly. Plugin maintainers review before merge.
+- **Preserve provenance**. Frontmatter records the source project, baseline, and delta. If the promoted skill regresses in a cross-project context, the track record makes rollback decisions clear.
+- **Never overwrite without confirmation**. If a skill with the same name exists, abort and let the user rename or approve overwrite.
+
+## Related
+
+- Phase 6 Learn auto-promote (project-local): `skills/self-improve/SKILL.md`
+- User removal override: `.build-loop/skills/.demoted` file or `rm -rf .build-loop/skills/active/<name>/`
+- Global cross-project evidence index: `~/.build-loop/experiments/<name>.jsonl` (appended on every applied run across projects)

package/commands/research.md

@@ -0,0 +1,22 @@
+---
+name: research
+description: "(Advanced override — `/build-loop:run` auto-routes here; use this only to force the mode.) Generate a repo-grounded research packet without committing to build. Pre-decision analysis."
+argument-hint: "[topic]"
+---
+
+<!-- SPDX-FileCopyrightText: 2025-2026 Tyrone Ross, Jr <46267523+tyroneross@users.noreply.github.com> | SPDX-License-Identifier: Apache-2.0 -->
+
+Load the `build-loop:research` skill.
+
+{{#if ARGUMENTS}}
+Topic: `{{ARGUMENTS}}`
+
+Run the research packet workflow:
+1. Scan the repo for context relevant to the topic
+2. Classify the task type
+3. Generate a structured research packet (Bottom line, What I found, Best path, Why, Risks, Confidence, Next action)
+4. Archive to `.build-loop/research/`
+5. Present the packet — user decides next step: build, optimize, or shelve
+{{else}}
+No topic specified. Ask the user what they want to research or evaluate.
+{{/if}}

package/commands/run.md

@@ -0,0 +1,12 @@
+---
+description: "The single entry for any coding task — build, fix, refactor, optimize, research, or test. Auto-routes to the right mode; you don't pick."
+argument-hint: "[--parallel] [goal description]"
+---
+
+<!-- SPDX-FileCopyrightText: 2025-2026 Tyrone Ross, Jr <46267523+tyroneross@users.noreply.github.com> | SPDX-License-Identifier: Apache-2.0 -->
+
+{{#if ARGUMENTS}}
+Load the `build-loop:build-loop` skill. Goal: `{{ARGUMENTS}}`
+{{else}}
+Load the `build-loop:build-loop` skill. Ask the user what they're building or changing.
+{{/if}}

package/commands/self-review.md

@@ -0,0 +1,51 @@
+---
+description: "Periodic self-review: mine recent build activity for issues and efficiency signals, optionally apply SAFE improvements. Use --install/--uninstall/--status to manage the launchd schedule."
+argument-hint: "[light|deep] [--install|--uninstall|--status]"
+---
+
+<!-- SPDX-FileCopyrightText: 2025-2026 Tyrone Ross, Jr <46267523+tyroneross@users.noreply.github.com> | SPDX-License-Identifier: Apache-2.0 -->
+
+{{#if ARGUMENTS}}
+{{#contains ARGUMENTS "--install"}}
+Run `python3 scripts/install_self_review.py install --json` in the current repo and report the result.
+{{else}}
+{{#contains ARGUMENTS "--uninstall"}}
+Run `python3 scripts/install_self_review.py uninstall --json` in the current repo and report the result.
+{{else}}
+{{#contains ARGUMENTS "--status"}}
+Run `python3 scripts/install_self_review.py status --json` in the current repo and report loaded/not-loaded state for both scheduled jobs.
+{{else}}
+Determine mode from ARGUMENTS: if it contains "deep" use `deep`, otherwise use `light`.
+Determine mode from ARGUMENTS: if it contains "deep" use `deep`, otherwise use `light`.
+Run `python3 scripts/self_review/__main__.py --mode <mode> --workdir . --json` and display the digest path and queued proposal count. If mode is deep, also describe the queued proposals and their classify_hint values.
+{{/contains}}
+{{/contains}}
+{{/contains}}
+{{else}}
+Run `python3 scripts/self_review/__main__.py --mode light --workdir . --json` and display the digest path and queued proposal count.
+{{/if}}
+
+---
+
+## Reference
+
+**Manual trigger (light — daily digest, no apply)**
+```
+/build-loop:self-review light
+```
+
+**Manual trigger (deep — full review; routes SAFE proposals through /build-loop:run)**
+```
+/build-loop:self-review deep
+```
+
+**Launchd schedule management**
+```
+/build-loop:self-review --install    # install both launchd jobs (reads .build-loop/config.json)
+/build-loop:self-review --status     # check loaded/not-loaded
+/build-loop:self-review --uninstall  # remove jobs and plists
+```
+
+Scheduled runs are fully autonomous: the deep job (Sunday 03:00 by default) runs the gatherer, then calls `claude -p` with the apply prompt to route SAFE proposals through `/build-loop:run`, which applies + commits + collapses. Push behavior is governed by `selfReview.autonomy` in `.build-loop/config.json` (`apply_push` / `apply_local` / `propose`). RISKY and DECISION proposals are never applied autonomously — they stay queued for manual review.
+
+See `skills/build-loop/references/self-review.md` for the full config schema, graceful-degradation notes, and the APPLY PROMPT.

package/commands/start-prd.md

@@ -0,0 +1,57 @@
+---
+name: start-prd
+description: "Start a living PRD for the current project by answering 3-5 strategic questions. Loads the prd-builder skill if installed."
+argument-hint: "[appname]"
+---
+
+<!-- SPDX-FileCopyrightText: 2025-2026 Tyrone Ross, Jr <46267523+tyroneross@users.noreply.github.com> | SPDX-License-Identifier: Apache-2.0 -->
+
+Load the `prd-builder` skill from RossLabs-AI-Toolkit if available. If unavailable, fall back to the inline guidance below.
+
+{{#if ARGUMENTS}}
+App name: `{{ARGUMENTS}}`
+
+Run the prd-builder workflow for this app:
+1. Confirm the skill applies (check trigger conditions).
+2. Ask Q1-3 in a single message, formatted as draft inferences (not blank prompts) based on whatever you know about the project from the codebase + memory.
+3. Wait for the user to redirect or confirm.
+4. Optionally ask Q4-5 if Q1-3 leave specific gaps the user wants pinned down.
+5. Draft the PRD at `docs/prd-{{ARGUMENTS}}.md` per the prd-builder Output Specification.
+6. Run the Fidelity check; deepen any section that fails prediction.
+7. Add a project-level pointer in `CLAUDE.md` (or `.claude/CLAUDE.md`): *"For non-trivial changes, read `docs/prd-{{ARGUMENTS}}.md` and apply its LLM Navigation Map."*
+8. (If applicable) bidirectionally link to existing research packets, audit docs, or operationalization documents.
+{{else}}
+No app name provided. Either:
+- Provide an appname argument: `/build-loop:start-prd myapp` → drafts `docs/prd-myapp.md`
+- Or ask the user what app this PRD is for, then proceed with the workflow above.
+{{/if}}
+
+## Fallback when prd-builder skill is not installed
+
+If the `prd-builder` skill is unavailable in this session, walk the user through the 3 core questions inline:
+
+**Q1 — Who and when (persona + trigger):** Describe the primary user (role, life stage, what they already use that this competes with). List 1-3 trigger moments that make them open the app. List 3-7 explicit "is NOT" exclusions.
+
+**Q2 — Outcome (the measurable change):** Pick ONE measurable change after N weeks/months of usage. Number, behavior, or self-perception.
+
+**Q3 — Stance (the philosophy):** Three sentences:
+1. Privacy/Data: "We will/won't [send/store/share] X because Y."
+2. Complexity: "Regular users will/won't see [advanced feature class] because Y."
+3. Cost: "App is [free/freemium/paid/subscription/...] because Y."
+
+Then draft a markdown PRD at `docs/prd-{{ARGUMENTS}}.md` with:
+- Frontmatter (name, status, revision, last_updated, load_when, evolves_when, core_principles)
+- Body sections: How to use this PRD, LLM Navigation Map, Section Index, Fidelity check, Intent, North Star, Persona, Outcome, Methodology, Stance, Non-goals (illustrative), Roadmap stance, One-line summary, Open questions, Pivot log, Document maintenance.
+
+Cite `~/dev/git-folder/RossLabs-AI-Toolkit/skills/prd-builder/SKILL.md` for the full output spec.
+
+After drafting, run the Fidelity check by predicting answers to:
+- Should the next major release prioritize speed or accuracy?
+- Should new features add complexity or simplify existing ones?
+- Should the home screen show many metrics or one north-star indicator?
+- Should we accept a feature request from a vocal user who doesn't fit the persona?
+- When should the app degrade gracefully vs fail loudly?
+- When should we move work from on-device to cloud (or vice versa)?
+- Should onboarding be opinionated or open?
+
+If you can predict each cleanly with PRD section citations, the PRD passes. If not, deepen the failing section.

package/commands/test.md

@@ -0,0 +1,34 @@
+---
+description: "(Advanced override — `/build-loop:run` auto-routes here on 'test plugin'/'validate plugin' language; use this to force the mode.) Run build-loop's plugin-tests static-analysis suite against the current repo (skill resolution, manifest, MCP, triggers, bridges, agent surfaces, cache pruning)"
+allowed-tools: Bash, Read
+argument-hint: "[--strict] [<test-name>]"
+---
+
+<!-- SPDX-FileCopyrightText: 2025-2026 Tyrone Ross, Jr <46267523+tyroneross@users.noreply.github.com> | SPDX-License-Identifier: Apache-2.0 -->
+
+Load the `build-loop:plugin-tests` skill.
+
+{{#if ARGUMENTS}}
+Args: `{{ARGUMENTS}}`
+
+If `<test-name>` is one of `skill-resolution`, `plugin-manifest`, `mcp-registration`, `trigger-phrases`, `bridge-preflight`, `agent-surface-policy`, `cache-prune`, run only that single script. Otherwise treat the args as flags for the runner.
+
+Example:
+- `/build-loop:test skill-resolution` — run only the namesake-collision test
+- `/build-loop:test --strict` — exit non-zero on any soft warning (CI gate)
+{{else}}
+Run the full plugin-test suite from the repo root:
+
+```bash
+for t in scripts/test_skill_resolution.py scripts/test_plugin_manifest.py \
+         scripts/test_mcp_registration.py scripts/test_trigger_phrases.py \
+         scripts/test_bridge_preflight.py scripts/test_agent_surface_policy.py \
+         scripts/test_prune_plugin_cache.py scripts/test_prune_codex_plugin_cache.py; do
+  echo "=== $(basename $t) ==="
+  python3 "$t" || EXIT=1
+done
+exit ${EXIT:-0}
+```
+
+Surface failures with the script name + test name + the assertion message. On any failure, suggest the fix path documented in the test's docstring.
+{{/if}}

package/dist/src/assessment-orchestrator.d.ts

@@ -0,0 +1,78 @@
+/**
+ * Assessment Orchestrator
+ *
+ * Coordinates parallel domain-specific assessments for comprehensive debugging.
+ * Detects which domains are involved based on symptom keywords and launches
+ * appropriate assessors in parallel.
+ */
+import type { DomainAssessment, OrchestrationResult } from './types';
+export type Domain = 'database' | 'frontend' | 'api' | 'performance';
+export type DomainPriority = 'high' | 'medium' | 'low';
+export interface DomainDetection {
+    domain: Domain;
+    priority: DomainPriority;
+    matchCount: number;
+    matchedKeywords: string[];
+}
+export interface OrchestrationConfig {
+    minMatchThreshold?: number;
+    maxParallelDomains?: number;
+    includeLowPriority?: boolean;
+    domainWeights?: Partial<Record<Domain, number>>;
+}
+/**
+ * Detect which domains are potentially involved based on symptom keywords
+ */
+export declare function detectDomains(symptom: string, config?: OrchestrationConfig): DomainDetection[];
+/**
+ * Select which domains should be assessed based on detection results
+ */
+export declare function selectDomainsForAssessment(detections: DomainDetection[], config?: OrchestrationConfig): Domain[];
+/**
+ * Format domain detection results for the orchestrator agent
+ */
+export declare function formatDetectionForAgent(detections: DomainDetection[]): string;
+/**
+ * Generate prompts for each domain assessor agent
+ */
+export declare function generateAssessorPrompts(symptom: string, domains: Domain[]): Record<Domain, string>;
+/**
+ * Parse assessment JSON from agent response
+ */
+export declare function parseAssessmentResponse(response: string, domain: Domain): DomainAssessment | null;
+/**
+ * Rank assessments by confidence and evidence
+ */
+export declare function rankAssessments(assessments: DomainAssessment[]): DomainAssessment[];
+/**
+ * Generate priority ranking for orchestration result
+ */
+export declare function generatePriorityRanking(rankedAssessments: DomainAssessment[]): Array<{
+    rank: number;
+    domain: Domain;
+    action: string;
+}>;
+/**
+ * Generate recommended sequence of actions
+ */
+export declare function generateRecommendedSequence(rankedAssessments: DomainAssessment[]): string[];
+/**
+ * Create the final orchestration result
+ */
+export declare function createOrchestrationResult(symptom: string, assessments: DomainAssessment[]): OrchestrationResult;
+/**
+ * Format orchestration result for display
+ */
+export declare function formatOrchestrationResult(result: OrchestrationResult): string;
+/**
+ * Main orchestration entry point
+ * Note: This prepares the orchestration but doesn't spawn agents directly.
+ * The actual agent spawning is done by Claude Code using the Task tool.
+ */
+export declare function prepareOrchestration(symptom: string, config?: OrchestrationConfig): {
+    detections: DomainDetection[];
+    selectedDomains: Domain[];
+    prompts: Record<Domain, string>;
+    shouldUseOrchestrator: boolean;
+};
+//# sourceMappingURL=assessment-orchestrator.d.ts.map

package/dist/src/assessment-orchestrator.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"assessment-orchestrator.d.ts","sourceRoot":"","sources":["../../src/assessment-orchestrator.ts"],"names":[],"mappings":"AAEA;;;;;;GAMG;AAEH,OAAO,KAAK,EAAE,gBAAgB,EAAE,mBAAmB,EAAE,MAAM,SAAS,CAAC;AAkCrE,MAAM,MAAM,MAAM,GAAG,UAAU,GAAG,UAAU,GAAG,KAAK,GAAG,aAAa,CAAC;AACrE,MAAM,MAAM,cAAc,GAAG,MAAM,GAAG,QAAQ,GAAG,KAAK,CAAC;AAEvD,MAAM,WAAW,eAAe;IAC9B,MAAM,EAAE,MAAM,CAAC;IACf,QAAQ,EAAE,cAAc,CAAC;IACzB,UAAU,EAAE,MAAM,CAAC;IACnB,eAAe,EAAE,MAAM,EAAE,CAAC;CAC3B;AAED,MAAM,WAAW,mBAAmB;IAElC,iBAAiB,CAAC,EAAE,MAAM,CAAC;IAE3B,kBAAkB,CAAC,EAAE,MAAM,CAAC;IAE5B,kBAAkB,CAAC,EAAE,OAAO,CAAC;IAE7B,aAAa,CAAC,EAAE,OAAO,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,CAAC;CACjD;AASD;;GAEG;AACH,wBAAgB,aAAa,CAC3B,OAAO,EAAE,MAAM,EACf,MAAM,GAAE,mBAAwB,GAC/B,eAAe,EAAE,CA0CnB;AAED;;GAEG;AACH,wBAAgB,0BAA0B,CACxC,UAAU,EAAE,eAAe,EAAE,EAC7B,MAAM,GAAE,mBAAwB,GAC/B,MAAM,EAAE,CAoBV;AAED;;GAEG;AACH,wBAAgB,uBAAuB,CAAC,UAAU,EAAE,eAAe,EAAE,GAAG,MAAM,CAe7E;AAED;;GAEG;AACH,wBAAgB,uBAAuB,CACrC,OAAO,EAAE,MAAM,EACf,OAAO,EAAE,MAAM,EAAE,GAChB,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAkBxB;AAED;;GAEG;AACH,wBAAgB,uBAAuB,CACrC,QAAQ,EAAE,MAAM,EAChB,MAAM,EAAE,MAAM,GACb,gBAAgB,GAAG,IAAI,CA2BzB;AAED;;GAEG;AACH,wBAAgB,eAAe,CAC7B,WAAW,EAAE,gBAAgB,EAAE,GAC9B,gBAAgB,EAAE,CAmBpB;AAED;;GAEG;AACH,wBAAgB,uBAAuB,CACrC,iBAAiB,EAAE,gBAAgB,EAAE,GACpC,KAAK,CAAC;IAAE,IAAI,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,MAAM,CAAA;CAAE,CAAC,CAMzD;AAED;;GAEG;AACH,wBAAgB,2BAA2B,CACzC,iBAAiB,EAAE,gBAAgB,EAAE,GACpC,MAAM,EAAE,CAcV;AAED;;GAEG;AACH,wBAAgB,yBAAyB,CACvC,OAAO,EAAE,MAAM,EACf,WAAW,EAAE,gBAAgB,EAAE,GAC9B,mBAAmB,CAcrB;AAED;;GAEG;AACH,wBAAgB,yBAAyB,CAAC,MAAM,EAAE,mBAAmB,GAAG,MAAM,CAoC7E;AAED;;;;GAIG;AACH,wBAAgB,oBAAoB,CAClC,OAAO,EAAE,MAAM,EACf,MAAM,GAAE,mBAAwB,GAC/B;IACD,UAAU,EAAE,eAAe,EAAE,CAAC;IAC9B,eAAe,EAAE,MAAM,EAAE,CAAC;IAC1B,OAAO,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAChC,qBAAqB,EAAE,OAAO,CAAC;CAChC,CAeA"}