xtrm-tools 0.7.2 → 0.7.4

package/.xtrm/skills/optional/research-methods/brainstorming/visual-companion.md

@@ -0,0 +1,287 @@
+# Visual Companion Guide
+
+Browser-based visual brainstorming companion for showing mockups, diagrams, and options.
+
+## When to Use
+
+Decide per-question, not per-session. The test: **would the user understand this better by seeing it than reading it?**
+
+**Use the browser** when the content itself is visual:
+
+- **UI mockups** — wireframes, layouts, navigation structures, component designs
+- **Architecture diagrams** — system components, data flow, relationship maps
+- **Side-by-side visual comparisons** — comparing two layouts, two color schemes, two design directions
+- **Design polish** — when the question is about look and feel, spacing, visual hierarchy
+- **Spatial relationships** — state machines, flowcharts, entity relationships rendered as diagrams
+
+**Use the terminal** when the content is text or tabular:
+
+- **Requirements and scope questions** — "what does X mean?", "which features are in scope?"
+- **Conceptual A/B/C choices** — picking between approaches described in words
+- **Tradeoff lists** — pros/cons, comparison tables
+- **Technical decisions** — API design, data modeling, architectural approach selection
+- **Clarifying questions** — anything where the answer is words, not a visual preference
+
+A question *about* a UI topic is not automatically a visual question. "What kind of wizard do you want?" is conceptual — use the terminal. "Which of these wizard layouts feels right?" is visual — use the browser.
+
+## How It Works
+
+The server watches a directory for HTML files and serves the newest one to the browser. You write HTML content to `screen_dir`, the user sees it in their browser and can click to select options. Selections are recorded to `state_dir/events` that you read on your next turn.
+
+**Content fragments vs full documents:** If your HTML file starts with `<!DOCTYPE` or `<html`, the server serves it as-is (just injects the helper script). Otherwise, the server automatically wraps your content in the frame template — adding the header, CSS theme, selection indicator, and all interactive infrastructure. **Write content fragments by default.** Only write full documents when you need complete control over the page.
+
+## Starting a Session
+
+```bash
+# Start server with persistence (mockups saved to project)
+scripts/start-server.sh --project-dir /path/to/project
+
+# Returns: {"type":"server-started","port":52341,"url":"http://localhost:52341",
+#           "screen_dir":"/path/to/project/.superpowers/brainstorm/12345-1706000000/content",
+#           "state_dir":"/path/to/project/.superpowers/brainstorm/12345-1706000000/state"}
+```
+
+Save `screen_dir` and `state_dir` from the response. Tell user to open the URL.
+
+**Finding connection info:** The server writes its startup JSON to `$STATE_DIR/server-info`. If you launched the server in the background and didn't capture stdout, read that file to get the URL and port. When using `--project-dir`, check `<project>/.superpowers/brainstorm/` for the session directory.
+
+**Note:** Pass the project root as `--project-dir` so mockups persist in `.superpowers/brainstorm/` and survive server restarts. Without it, files go to `/tmp` and get cleaned up. Remind the user to add `.superpowers/` to `.gitignore` if it's not already there.
+
+**Launching the server by platform:**
+
+**Claude Code (macOS / Linux):**
+```bash
+# Default mode works — the script backgrounds the server itself
+scripts/start-server.sh --project-dir /path/to/project
+```
+
+**Claude Code (Windows):**
+```bash
+# Windows auto-detects and uses foreground mode, which blocks the tool call.
+# Use run_in_background: true on the Bash tool call so the server survives
+# across conversation turns.
+scripts/start-server.sh --project-dir /path/to/project
+```
+When calling this via the Bash tool, set `run_in_background: true`. Then read `$STATE_DIR/server-info` on the next turn to get the URL and port.
+
+**Codex:**
+```bash
+# Codex reaps background processes. The script auto-detects CODEX_CI and
+# switches to foreground mode. Run it normally — no extra flags needed.
+scripts/start-server.sh --project-dir /path/to/project
+```
+
+**Gemini CLI:**
+```bash
+# Use --foreground and set is_background: true on your shell tool call
+# so the process survives across turns
+scripts/start-server.sh --project-dir /path/to/project --foreground
+```
+
+**Other environments:** The server must keep running in the background across conversation turns. If your environment reaps detached processes, use `--foreground` and launch the command with your platform's background execution mechanism.
+
+If the URL is unreachable from your browser (common in remote/containerized setups), bind a non-loopback host:
+
+```bash
+scripts/start-server.sh \
+  --project-dir /path/to/project \
+  --host 0.0.0.0 \
+  --url-host localhost
+```
+
+Use `--url-host` to control what hostname is printed in the returned URL JSON.
+
+## The Loop
+
+1. **Check server is alive**, then **write HTML** to a new file in `screen_dir`:
+   - Before each write, check that `$STATE_DIR/server-info` exists. If it doesn't (or `$STATE_DIR/server-stopped` exists), the server has shut down — restart it with `start-server.sh` before continuing. The server auto-exits after 30 minutes of inactivity.
+   - Use semantic filenames: `platform.html`, `visual-style.html`, `layout.html`
+   - **Never reuse filenames** — each screen gets a fresh file
+   - Use Write tool — **never use cat/heredoc** (dumps noise into terminal)
+   - Server automatically serves the newest file
+
+2. **Tell user what to expect and end your turn:**
+   - Remind them of the URL (every step, not just first)
+   - Give a brief text summary of what's on screen (e.g., "Showing 3 layout options for the homepage")
+   - Ask them to respond in the terminal: "Take a look and let me know what you think. Click to select an option if you'd like."
+
+3. **On your next turn** — after the user responds in the terminal:
+   - Read `$STATE_DIR/events` if it exists — this contains the user's browser interactions (clicks, selections) as JSON lines
+   - Merge with the user's terminal text to get the full picture
+   - The terminal message is the primary feedback; `state_dir/events` provides structured interaction data
+
+4. **Iterate or advance** — if feedback changes current screen, write a new file (e.g., `layout-v2.html`). Only move to the next question when the current step is validated.
+
+5. **Unload when returning to terminal** — when the next step doesn't need the browser (e.g., a clarifying question, a tradeoff discussion), push a waiting screen to clear the stale content:
+
+   ```html
+   <!-- filename: waiting.html (or waiting-2.html, etc.) -->
+   <div style="display:flex;align-items:center;justify-content:center;min-height:60vh">
+     <p class="subtitle">Continuing in terminal...</p>
+   </div>
+   ```
+
+   This prevents the user from staring at a resolved choice while the conversation has moved on. When the next visual question comes up, push a new content file as usual.
+
+6. Repeat until done.
+
+## Writing Content Fragments
+
+Write just the content that goes inside the page. The server wraps it in the frame template automatically (header, theme CSS, selection indicator, and all interactive infrastructure).
+
+**Minimal example:**
+
+```html
+<h2>Which layout works better?</h2>
+<p class="subtitle">Consider readability and visual hierarchy</p>
+
+<div class="options">
+  <div class="option" data-choice="a" onclick="toggleSelect(this)">
+    <div class="letter">A</div>
+    <div class="content">
+      <h3>Single Column</h3>
+      <p>Clean, focused reading experience</p>
+    </div>
+  </div>
+  <div class="option" data-choice="b" onclick="toggleSelect(this)">
+    <div class="letter">B</div>
+    <div class="content">
+      <h3>Two Column</h3>
+      <p>Sidebar navigation with main content</p>
+    </div>
+  </div>
+</div>
+```
+
+That's it. No `<html>`, no CSS, no `<script>` tags needed. The server provides all of that.
+
+## CSS Classes Available
+
+The frame template provides these CSS classes for your content:
+
+### Options (A/B/C choices)
+
+```html
+<div class="options">
+  <div class="option" data-choice="a" onclick="toggleSelect(this)">
+    <div class="letter">A</div>
+    <div class="content">
+      <h3>Title</h3>
+      <p>Description</p>
+    </div>
+  </div>
+</div>
+```
+
+**Multi-select:** Add `data-multiselect` to the container to let users select multiple options. Each click toggles the item. The indicator bar shows the count.
+
+```html
+<div class="options" data-multiselect>
+  <!-- same option markup — users can select/deselect multiple -->
+</div>
+```
+
+### Cards (visual designs)
+
+```html
+<div class="cards">
+  <div class="card" data-choice="design1" onclick="toggleSelect(this)">
+    <div class="card-image"><!-- mockup content --></div>
+    <div class="card-body">
+      <h3>Name</h3>
+      <p>Description</p>
+    </div>
+  </div>
+</div>
+```
+
+### Mockup container
+
+```html
+<div class="mockup">
+  <div class="mockup-header">Preview: Dashboard Layout</div>
+  <div class="mockup-body"><!-- your mockup HTML --></div>
+</div>
+```
+
+### Split view (side-by-side)
+
+```html
+<div class="split">
+  <div class="mockup"><!-- left --></div>
+  <div class="mockup"><!-- right --></div>
+</div>
+```
+
+### Pros/Cons
+
+```html
+<div class="pros-cons">
+  <div class="pros"><h4>Pros</h4><ul><li>Benefit</li></ul></div>
+  <div class="cons"><h4>Cons</h4><ul><li>Drawback</li></ul></div>
+</div>
+```
+
+### Mock elements (wireframe building blocks)
+
+```html
+<div class="mock-nav">Logo | Home | About | Contact</div>
+<div style="display: flex;">
+  <div class="mock-sidebar">Navigation</div>
+  <div class="mock-content">Main content area</div>
+</div>
+<button class="mock-button">Action Button</button>
+<input class="mock-input" placeholder="Input field">
+<div class="placeholder">Placeholder area</div>
+```
+
+### Typography and sections
+
+- `h2` — page title
+- `h3` — section heading
+- `.subtitle` — secondary text below title
+- `.section` — content block with bottom margin
+- `.label` — small uppercase label text
+
+## Browser Events Format
+
+When the user clicks options in the browser, their interactions are recorded to `$STATE_DIR/events` (one JSON object per line). The file is cleared automatically when you push a new screen.
+
+```jsonl
+{"type":"click","choice":"a","text":"Option A - Simple Layout","timestamp":1706000101}
+{"type":"click","choice":"c","text":"Option C - Complex Grid","timestamp":1706000108}
+{"type":"click","choice":"b","text":"Option B - Hybrid","timestamp":1706000115}
+```
+
+The full event stream shows the user's exploration path — they may click multiple options before settling. The last `choice` event is typically the final selection, but the pattern of clicks can reveal hesitation or preferences worth asking about.
+
+If `$STATE_DIR/events` doesn't exist, the user didn't interact with the browser — use only their terminal text.
+
+## Design Tips
+
+- **Scale fidelity to the question** — wireframes for layout, polish for polish questions
+- **Explain the question on each page** — "Which layout feels more professional?" not just "Pick one"
+- **Iterate before advancing** — if feedback changes current screen, write a new version
+- **2-4 options max** per screen
+- **Use real content when it matters** — for a photography portfolio, use actual images (Unsplash). Placeholder content obscures design issues.
+- **Keep mockups simple** — focus on layout and structure, not pixel-perfect design
+
+## File Naming
+
+- Use semantic names: `platform.html`, `visual-style.html`, `layout.html`
+- Never reuse filenames — each screen must be a new file
+- For iterations: append version suffix like `layout-v2.html`, `layout-v3.html`
+- Server serves newest file by modification time
+
+## Cleaning Up
+
+```bash
+scripts/stop-server.sh $SESSION_DIR
+```
+
+If the session used `--project-dir`, mockup files persist in `.superpowers/brainstorm/` for later reference. Only `/tmp` sessions get deleted on stop.
+
+## Reference
+
+- Frame template (CSS reference): `scripts/frame-template.html`
+- Helper script (client-side): `scripts/helper.js`

package/.xtrm/skills/optional/research-methods/deep-research/SKILL.md

@@ -0,0 +1,192 @@
+---
+name: deep-research
+description: |
+  Comprehensive research assistant that synthesizes information from multiple sources with citations.
+  Use when: conducting in-depth research, gathering sources, writing research summaries, analyzing topics
+  from multiple perspectives, or when user mentions research, investigation, or needs synthesized analysis
+  with citations.
+license: MIT
+metadata:
+  author: awesome-llm-apps
+  version: "1.0.0"
+---
+
+# Deep Research
+
+You are an expert researcher who provides thorough, well-cited analysis by synthesizing information from multiple perspectives.
+
+## When to Apply
+
+Use this skill when:
+- Conducting in-depth research on a topic
+- Synthesizing information from multiple sources
+- Creating research summaries with proper citations
+- Analyzing different viewpoints and perspectives
+- Identifying key findings and trends
+- Evaluating the quality and credibility of sources
+
+## Research Process
+
+Follow this systematic approach:
+
+### 1. **Clarify the Research Question**
+- What exactly needs to be researched?
+- What level of detail is required?
+- Are there specific angles to prioritize?
+- What is the purpose of the research?
+
+### 2. **Identify Key Aspects**
+- Break the topic into subtopics or dimensions
+- List main questions to answer
+- Note important context or background needed
+
+### 3. **Gather Information**
+- Consider multiple perspectives
+- Look for primary and secondary sources
+- Check publication dates and currency
+- Evaluate source credibility
+
+### 4. **Synthesize Findings**
+- Identify patterns and themes
+- Note areas of consensus and disagreement
+- Highlight key insights
+- Connect related information
+
+### 5. **Document Sources**
+- Use numbered citations [1], [2], etc.
+- List full sources at the end
+- Note if information is uncertain or contested
+- Indicate confidence levels where appropriate
+
+## Output Format
+
+Structure your research as:
+
+```markdown
+## Executive Summary
+[2-3 sentence overview of key findings]
+
+## Key Findings
+- **[Finding 1]**: [Brief explanation] [1]
+- **[Finding 2]**: [Brief explanation] [2]
+- **[Finding 3]**: [Brief explanation] [3]
+
+## Detailed Analysis
+
+### [Subtopic 1]
+[In-depth analysis with citations]
+
+### [Subtopic 2]
+[In-depth analysis with citations]
+
+## Areas of Consensus
+[What sources agree on]
+
+## Areas of Debate
+[Where sources disagree or uncertainty exists]
+
+## Sources
+[1] [Full citation with credibility note]
+[2] [Full citation with credibility note]
+
+## Gaps and Further Research
+[What's still unknown or needs investigation]
+```
+
+## Source Evaluation Criteria
+
+When citing sources, note:
+
+- **Peer-reviewed journals** - Highest credibility
+- **Official reports/statistics** - Authoritative data
+- **News from reputable outlets** - Timely, fact-checked
+- **Expert commentary** - Qualified opinions
+- **General websites** - verify independently
+
+## Example
+
+**User Request:** "Research the benefits and risks of intermittent fasting"
+
+**Response:**
+
+## Executive Summary
+
+Intermittent fasting (IF) shows promising benefits for weight loss and metabolic health based on current research, though long-term effects remain under study. Evidence supports its safety for most healthy adults, with certain populations requiring medical supervision [1][2].
+
+## Key Findings
+
+- **Weight Loss**: IF produces similar weight loss to calorie restriction (5-8% body weight over 12 weeks), with potentially better adherence [1]
+- **Metabolic Health**: May improve insulin sensitivity by 20-31% and reduce inflammation markers [2]
+- **Longevity**: Animal studies show promise; human long-term data is limited [3]
+- **Safety**: Not recommended for pregnant women, diabetics without supervision, or those with eating disorder history [4]
+
+## Detailed Analysis
+
+### Weight Management
+Studies comparing IF to traditional calorie restriction show similar weight loss outcomes. The main advantage appears to be adherence - many people find time-restricted eating easier to maintain than calorie counting [1]. Typical results show 5-8% body weight loss over 12-16 weeks.
+
+Common IF protocols:
+- **16:8** - 16 hours fasting, 8-hour eating window
+- **5:2** - Normal eating 5 days, restricted calories 2 days
+- **Alternate day** - Alternating between fasting and eating days
+
+### Metabolic Effects
+Research indicates improvements in several biomarkers [2]:
+- Fasting insulin levels decreased 20-31%
+- Blood pressure reductions (3-8 mmHg systolic)
+- Inflammatory marker (CRP) reductions
+- Improved lipid profiles in some studies
+
+However, individual responses vary significantly. Some people show dramatic improvements while others see minimal changes.
+
+### Potential Mechanisms
+Several explanations for observed benefits:
+1. **Caloric restriction** - IF naturally reduces total calories
+2. **Circadian alignment** - Eating during daytime hours aligns with metabolism
+3. **Autophagy** - Cellular cleanup processes activated during fasting
+4. **Hormetic stress** - Mild stress that improves adaptation
+
+### Safety Considerations
+While generally safe for healthy adults, certain groups should avoid IF or proceed with medical supervision [4]:
+- Pregnant or breastfeeding women
+- People with diabetes (risk of hypoglycemia)
+- History of eating disorders
+- Children and adolescents
+- Those taking medications requiring food
+
+Common side effects during adaptation (1-2 weeks):
+- Hunger and irritability
+- Headaches
+- Fatigue
+- Difficulty concentrating
+
+## Areas of Consensus
+
+- IF is as effective as traditional diets for weight loss
+- Short-term safety is established for healthy adults
+- Individual results vary considerably
+- Not a magic solution - overall diet quality matters
+
+## Areas of Debate
+
+- **Optimal fasting window**: Research shows benefits across different protocols
+- **Long-term sustainability**: Most studies are 8-24 weeks; need multi-year data
+- **Superiority to other diets**: Unclear if benefits exceed other healthy eating patterns
+- **Muscle preservation**: Some concern about muscle loss, but studies show mixed results
+
+## Sources
+
+[1] Varady KA, et al. "Clinical application of intermittent fasting for weight loss." *Nature Reviews Endocrinology*, 2022. (Systematic review, high credibility)
+
+[2] de Cabo R, Mattson MP. "Effects of Intermittent Fasting on Health, Aging, and Disease." *New England Journal of Medicine*, 2019. (Peer-reviewed, authoritative review)
+
+[3] Longo VD, Panda S. "Fasting, Circadian Rhythms, and Time-Restricted Feeding in Healthy Lifespan." *Cell Metabolism*, 2016. (Mechanistic research, preliminary human data)
+
+[4] Academy of Nutrition and Dietetics. "Position on Intermittent Fasting." 2022. (Professional organization guidelines)
+
+## Gaps and Further Research
+
+- **Long-term studies** (5+ years) needed for sustained effects
+- **Different populations** - effects across ages, sexes, ethnicities
+- **Optimization** - best fasting windows, meal timing, macronutrient composition
+- **Clinical applications** - specific diseases or conditions that benefit most

package/.xtrm/skills/optional/research-methods/fact-checker/SKILL.md

@@ -0,0 +1,182 @@
+---
+name: fact-checker
+description: |
+  Systematic fact verification and misinformation identification using evidence-based analysis.
+  Use when: verifying claims, checking facts, identifying misinformation, evaluating source credibility,
+  or when user asks to "fact check", "verify", "is this true", or mentions claims that need validation.
+license: MIT
+metadata:
+  author: awesome-llm-apps
+  version: "1.0.0"
+---
+
+# Fact Checker
+
+You are an expert fact-checker who evaluates claims systematically using evidence-based analysis.
+
+## When to Apply
+
+Use this skill when:
+- Verifying specific claims or statements
+- Identifying potential misinformation or disinformation
+- Checking statistics and data accuracy
+- Evaluating source credibility
+- Separating fact from opinion or interpretation
+- Analyzing viral claims or rumors
+
+## Verification Process
+
+Follow this systematic approach:
+
+### 1. **Identify the Claim**
+- Extract the specific factual assertion
+- Distinguish fact from opinion
+- Note any implicit claims
+- Identify measurable aspects
+
+### 2. **Determine Required Evidence**
+- What would prove this claim?
+- What would disprove it?
+- What sources would be authoritative?
+- Can this be verified or is it opinion?
+
+### 3. **Evaluate Available Evidence**
+- Check authoritative sources
+- Look for primary data
+- Consider source credibility
+- Note publication dates
+- Check for context
+
+### 4. **Rate the Claim**
+- Assess accuracy based on evidence
+- Note confidence level
+- Explain reasoning clearly
+- Highlight missing context if relevant
+
+### 5. **Provide Context**
+- Why does this matter?
+- Common misconceptions
+- Related facts
+- Proper interpretation
+
+## Rating Scale
+
+Use these ratings:
+
+- **✅ TRUE** - Claim is accurate and supported by reliable evidence
+- **⚠️ MOSTLY TRUE** - Claim is accurate but missing important context or minor details wrong
+- **🔶 MIXED** - Claim contains both true and false elements
+- **❌ MOSTLY FALSE** - Claim is misleading or largely inaccurate
+- **🚫 FALSE** - Claim is demonstrably wrong
+- **❓ UNVERIFIABLE** - Cannot be confirmed or denied with available evidence
+
+## Source Quality Hierarchy
+
+Rate sources by credibility:
+
+1. **Peer-reviewed scientific studies** - Highest credibility
+2. **Official government statistics** - Authoritative data
+3. **Reputable news organizations** - Fact-checked reporting
+4. **Expert statements in field** - Qualified opinions
+5. **General news sites** - Verify with other sources
+6. **Social media/blogs** - Lowest credibility, verify independently
+
+## Output Format
+
+```markdown
+## Claim
+[Exact statement being verified]
+
+## Verdict: [RATING]
+
+## Analysis
+[Explanation of why this rating]
+
+**Evidence:**
+- [Key supporting or refuting evidence]
+- [Secondary evidence]
+
+**Context:**
+- [Important context or nuance]
+- [Why this matters]
+
+**Source Quality:**
+- [Evaluation of sources used]
+
+## Correct Information
+[If claim is false/misleading, provide accurate version]
+
+## Sources
+[Numbered list of sources with credibility notes]
+```
+
+## Common Patterns to Watch For
+
+### Statistical Manipulation
+- Cherry-picking data
+- Misleading graphs or scales
+- Correlation vs causation
+- Inappropriate comparisons
+
+### Context Removal
+- Quote mining (taking statements out of context
+- Omitting important qualifiers
+- Ignoring timeframes or conditions
+- Removing statistical caveats
+
+### False Equivalences
+- Comparing incomparable things
+- Treating all sources as equally valid
+- Both-sidesing settled science
+
+### Logical Fallacies
+- Ad hominem attacks
+- Appeal to authority (improper)
+- False dichotomies
+- Slippery slope arguments
+
+## Example
+
+**User Request:** "Fact check: Humans only use 10% of their brain"
+
+**Response:**
+
+## Claim
+"Humans only use 10% of their brain"
+
+## Verdict: 🚫 FALSE
+
+## Analysis
+
+This is a persistent myth with no scientific basis. Neurological research consistently shows that humans use virtually all parts of their brain, though not all at the same time.
+
+**Evidence:**
+- Brain imaging (fMRI, PET scans) shows activity throughout the brain during even simple tasks [1]
+- Brain damage to any area causes functional impairment, indicating all regions serve purposes [2]
+- Metabolic studies show the brain uses ~20% of body's energy despite being ~2% of body weight - wouldn't occur if 90% were unused [3]
+- Evolutionary perspective: maintaining unused brain tissue would be wasteful
+
+**Context:**
+- The myth may originate from early neurological studies or misunderstanding of brain plasticity
+- Not all neurons fire simultaneously (which would cause seizure)
+- Different regions activate for different tasks
+- We don't consciously control all brain functions (breathing, heartbeat, etc.)
+
+**Source Quality:**
+- Neuroscience consensus supported by decades of research
+- Brain imaging studies provide direct evidence
+- Myth persists in popular culture despite scientific consensus
+
+## Correct Information
+
+Humans use virtually all of their brain. Different regions activate for different tasks, and brain imaging shows activity distributed throughout the brain during both active tasks and rest. The brain's high energy consumption (20% of body's energy for 2% of body weight) demonstrates intensive usage.
+
+While we don't have conscious access to all brain functions (autonomic processes like heartbeat, many memory processes), this doesn't mean those regions are "unused" - they're actively maintaining vital functions.
+
+## Sources
+
+[1] Herculano-Houzel, S. (2012). "The remarkable, yet not extraordinary, human brain." *Proceedings of the National Academy of Sciences*, 109(Supplement 1), 10661-10668. (Peer-reviewed, authoritative neuroscience)
+
+[2] Boyd, R. (2008). "Do People Only Use 10 Percent of Their Brains?" *Scientific American*. (Science journalism, expert sources)
+
+[3] Raichle, M.E., & Gusnard, D.A. (2002). "Appraising the brain's energy budget." *Proceedings of the National Academy of Sciences*, 99(16), 10237-10239. (Peer-reviewed, metabolic research)

package/.xtrm/skills/optional/security-ops/PACK.json

@@ -0,0 +1,9 @@
+{
+  "schemaVersion": "1",
+  "name": "security-ops",
+  "version": "1.0.0",
+  "description": "Security auditing and DevSecOps skills",
+  "skills": [
+    "security-auditor"
+  ]
+}