agentic-qe 3.8.1 → 3.8.3

package/assets/skills/compatibility-testing/SKILL.md

@@ -47,57 +47,6 @@ When validating cross-browser/platform compatibility:
 - Launching in new markets
 - Responsive design validation
 
-### Browser Matrix
-| Browser | Versions | Priority |
-|---------|----------|----------|
-| **Chrome** | Latest, N-1 | High |
-| **Firefox** | Latest, N-1 | High |
-| **Safari** | Latest, N-1 | High |
-| **Edge** | Latest | Medium |
-| **Mobile Safari** | iOS latest | High |
-| **Mobile Chrome** | Android latest | High |
-
-### Screen Breakpoints
-| Category | Width Range |
-|----------|-------------|
-| **Mobile** | 320px - 480px |
-| **Tablet** | 481px - 768px |
-| **Desktop** | 769px - 1920px+ |
-
----
-
-## Responsive Design Testing
-
-```javascript
-import { test, expect } from '@playwright/test';
-
-const devices = [
-  { name: 'iPhone 12', width: 390, height: 844 },
-  { name: 'iPad', width: 768, height: 1024 },
-  { name: 'Desktop', width: 1920, height: 1080 }
-];
-
-for (const device of devices) {
-  test(`layout on ${device.name}`, async ({ page }) => {
-    await page.setViewportSize({
-      width: device.width,
-      height: device.height
-    });
-
-    await page.goto('https://example.com');
-
-    const nav = await page.locator('nav');
-    if (device.width < 768) {
-      // Mobile: hamburger menu
-      expect(await nav.locator('.hamburger')).toBeVisible();
-    } else {
-      // Desktop: full menu
-      expect(await nav.locator('.menu-items')).toBeVisible();
-    }
-  });
-}
-```
-
 ---
 
 ## Cross-Browser with Playwright
@@ -202,8 +151,6 @@ const compatFleet = await FleetManager.coordinate({
 
 ## Remember
 
-**Test where users are, not where you develop.** Developers use latest Chrome on high-end machines. Users access from older browsers, low-end devices, and slow networks.
-
 **Cover 95%+ of your user base.** Use analytics to identify actual browser/device usage. Don't waste time on browsers nobody uses.
 
-**With Agents:** Agents orchestrate parallel cross-browser testing across cloud platforms, reducing 10 hours of manual testing to 15 minutes. `qe-visual-tester` catches visual inconsistencies across platforms automatically.
+**With Agents:** Agents orchestrate parallel cross-browser testing across cloud platforms. `qe-visual-tester` catches visual inconsistencies across platforms automatically.

package/assets/skills/compliance-testing/SKILL.md

@@ -11,7 +11,6 @@ last_optimized: 2025-12-02
 dependencies: []
 quick_reference_card: true
 tags: [compliance, gdpr, hipaa, pci-dss, ccpa, soc2, privacy, audit]
-
 # ADR-056 Validation Stack Configuration
 trust_tier: 3
 validation:
@@ -230,3 +229,11 @@ const complianceFleet = await FleetManager.coordinate({
 **Audit trail everything.** Every access to sensitive data, every consent, every deletion must be logged with timestamps and user IDs.
 
 **With Agents:** Agents validate compliance requirements continuously, detect violations early, and generate audit-ready reports. Catch compliance issues in development, not in audits.
+
+## Gotchas
+
+- Agent checks GDPR consent flow but misses data retention — always verify deletion/anonymization actually works
+- Compliance reports with "100% compliant" are suspicious — no real system is fully compliant, verify each claim
+- Agent may test US regulations only — explicitly specify jurisdiction (EU, CA, etc.) for correct requirements
+- PII in test data is itself a compliance violation — never use production PII, use synthetic generators
+- Audit trail gaps are invisible until audit time — verify logging exists for EVERY data access, not just writes

package/assets/skills/compliance-testing/config.json

@@ -0,0 +1,13 @@
+{
+  "$schema": "./config-schema.json",
+  "_description": "Compliance Testing configuration. Auto-created on first run. Edit to customize.",
+  "regulations": [],
+  "scope": null,
+  "options": {
+    "dataClassification": null,
+    "retentionPolicyDays": null,
+    "auditLogRequired": true,
+    "piiScanEnabled": true
+  },
+  "_setupPrompt": "If regulations is empty, ask: 'Which regulations apply to this project? (gdpr/ccpa/hipaa/soc2/pci-dss — comma-separated)'. If scope is null, ask: 'What is the compliance scope? (full-app/api-only/data-layer/specific-module)'."
+}

package/assets/skills/consultancy-practices/SKILL.md

@@ -14,7 +14,6 @@ tags: [consulting, advisory, client-engagement, quality-assessment, transformati
 trust_tier: 1
 validation:
   schema_path: schemas/output.json
-
 ---
 
 # Consultancy Practices
@@ -41,28 +40,9 @@ When consulting on quality:
 
 ## Quick Reference Card
 
-### The Consulting Process
-
-| Phase | Duration | Goal | Deliverable |
-|-------|----------|------|-------------|
-| **Discovery** | Week 1-2 | Understand context | Interview notes, observations |
-| **Analysis** | Week 2-3 | Identify root causes | Impact/effort matrix |
-| **Recommendations** | Week 3-4 | Present findings | Report with roadmap |
-| **Implementation** | Month 2-6+ | Execute changes | Working system, trained team |
-| **Transition** | Final month | Ensure self-sufficiency | Handover docs |
-
-### Impact/Effort Matrix
-
-| Priority | What | Action |
-|----------|------|--------|
-| High Impact, Low Effort | Quick wins | Do first |
-| High Impact, High Effort | Major initiatives | Plan carefully |
-| Low Impact, Low Effort | Nice-to-haves | If time permits |
-| Low Impact, High Effort | Distractions | Skip |
-
 ---
 
-## Common Patterns
+## Common Patterns (What Clients Say vs. What They Mean)
 
 ### "We Need Test Automation"
 
@@ -111,18 +91,6 @@ When consulting on quality:
 
 ---
 
-## Anti-Patterns
-
-| Anti-Pattern | Problem | Better |
-|--------------|---------|--------|
-| **Cookie-Cutter** | Same solution everywhere | Context-specific recommendations |
-| **Tool Pusher** | Recommend expensive tools | Tools that solve actual problems |
-| **Process Nazi** | Impose rigid process | Lightweight, fits their culture |
-| **Permanent Fixture** | Never leave, create dependency | Work toward them not needing you |
-| **Blame Game** | Point fingers at people | Fix systems, not blame people |
-
----
-
 ## Difficult Situations
 
 **"We already tried that"**

package/assets/skills/context-driven-testing/SKILL.md

@@ -13,7 +13,6 @@ quick_reference_card: true
 tags: [context-driven, rst, exploratory, heuristics, oracles, skilled-testing]
 trust_tier: 0
 validation:
-
 ---
 
 # Context-Driven Testing
@@ -46,23 +45,6 @@ When making testing decisions or adapting approaches:
 - Adapting approach to specific constraints
 - Exploratory testing sessions
 
-### Seven Context-Driven Principles
-1. Value of any practice depends on its context
-2. Good practices in context, no universal best practices
-3. People working together are most important
-4. Projects unfold in unpredictable ways
-5. Product is a solution - if problem not solved, product fails
-6. Good testing is challenging intellectual work
-7. Judgment and skill determine right things at right times
-
-### Context Factors
-| Factor | Questions |
-|--------|-----------|
-| **Project** | Business goal? User needs? Failure impact? |
-| **Constraints** | Timeline? Budget? Team skills? Legacy? |
-| **Risk** | Safety-critical? Regulated? High volume? |
-| **Technical** | Stack quirks? Integrations? Observability? |
-
 ### RST Heuristics
 | Heuristic | Application |
 |-----------|-------------|
@@ -98,26 +80,6 @@ When making testing decisions or adapting approaches:
 
 ---
 
-## Investigation vs. Checking
-
-| Checking | Testing (Investigation) |
-|----------|------------------------|
-| Did API return 200? | Does API meet user needs? |
-| Does button work? | What happens under load? |
-| Match the spec? | Does it solve the problem? |
-
----
-
-## Red Flags: Not Context-Driven
-
-- Follow process "because that's how it's done"
-- Can't explain *why* you're doing something
-- Measure test cases executed, not problems found
-- Test plan could apply to any project
-- Stop thinking once you have a script
-
----
-
 ## Agent-Assisted Context-Driven Testing
 
 ```typescript
@@ -192,8 +154,4 @@ const contextFleet = await FleetManager.coordinate({
 
 ## Remember
 
-**Context drives decisions.** No universal best practices. Skilled testers make informed decisions based on specific goals, constraints, and risks.
-
-You're not a test script executor. You're a skilled investigator helping teams build better products.
-
 **With Agents:** Agents analyze context, adapt strategies, and learn what works in your situation. Use agents to scale context-driven thinking while maintaining human judgment for critical decisions.

package/assets/skills/contract-testing/SKILL.md

@@ -213,6 +213,10 @@ const contractFleet = await FleetManager.coordinate({
 
 ---
 
+## Agent CLI & Advanced Patterns
+
+For v3 agent-specific commands (`aqe contract ...`), GraphQL contracts, event contracts, and Pact Broker integration, see [references/agent-commands.md](references/agent-commands.md).
+
 ## Related Skills
 - [api-testing-patterns](../api-testing-patterns/) - API testing strategies
 - [shift-left-testing](../shift-left-testing/) - Early contract validation
@@ -225,3 +229,11 @@ const contractFleet = await FleetManager.coordinate({
 **Consumers own the contract.** They define what they need; providers must fulfill it. Breaking changes require major version bumps and coordination. CI/CD blocks deploys that break contracts. Use Pact for consumer-driven, OpenAPI for API-first.
 
 **With Agents:** Agents validate contracts, detect breaking changes with semver recommendations, and generate migration guides. Use agents to maintain contract compliance at scale.
+
+## Gotchas
+
+- Pact broker URL must be configured before running — agent will generate tests that silently skip verification without it
+- Consumer tests pass locally but fail in CI when provider states aren't set up — always verify both sides
+- Adding a required field to a response is a BREAKING change even though provider tests pass — consumer didn't expect it
+- Agent may generate contracts from API docs instead of actual consumer usage — contracts must reflect real consumer needs
+- GraphQL contract testing requires schema stitching awareness — fragments may reference types from other services

package/assets/skills/contract-testing/config.json

@@ -0,0 +1,13 @@
+{
+  "$schema": "./config-schema.json",
+  "_description": "Contract Testing configuration. Auto-created on first run. Edit to customize.",
+  "broker_url": null,
+  "consumer_name": null,
+  "provider_name": null,
+  "options": {
+    "publishVerificationResults": true,
+    "enablePending": true,
+    "includeWipPactsSince": null
+  },
+  "_setupPrompt": "If broker_url is null, ask: 'What is your Pact Broker URL? (or \"local\" for file-based)'. If consumer_name is null, ask: 'What is the consumer service name?'. If provider_name is null, ask: 'What is the provider service name?'"
+}

package/assets/skills/contract-testing/references/agent-commands.md

@@ -0,0 +1,103 @@
+# Contract Testing — Agent CLI Commands & Advanced Patterns
+
+Merged from `qe-contract-testing`. Use these when working with v3 agent-specific contract capabilities.
+
+## AQE CLI Commands
+
+```bash
+# Generate contract from API spec
+aqe contract generate --api openapi.yaml --output contracts/
+
+# Verify provider against contracts
+aqe contract verify --provider http://localhost:3000 --contracts contracts/
+
+# Check breaking changes between versions
+aqe contract breaking --old api-v1.yaml --new api-v2.yaml
+
+# Test GraphQL schema
+aqe contract graphql --schema schema.graphql --operations queries/
+```
+
+## Agent Workflow
+
+```typescript
+// Contract generation
+Task("Generate API contracts", `
+  Analyze the REST API and generate consumer contracts:
+  - Parse OpenAPI specification
+  - Identify critical endpoints
+  - Generate Pact contracts
+  - Include example requests/responses
+  Output to contracts/ directory.
+`, "qe-api-contract")
+
+// Breaking change detection
+Task("Check API compatibility", `
+  Compare API v2.0 against v1.0:
+  - Detect removed endpoints
+  - Check parameter changes
+  - Verify response schema changes
+  - Identify deprecations
+  Report breaking vs non-breaking changes.
+`, "qe-api-compatibility")
+```
+
+## GraphQL Contract Testing
+
+```typescript
+await graphqlTester.testContracts({
+  schema: 'schema.graphql',
+  operations: 'queries/**/*.graphql',
+  validation: {
+    queryValidity: true,
+    responseShapes: true,
+    nullability: true,
+    deprecations: true
+  }
+});
+```
+
+## Event Contract Testing
+
+```typescript
+await contractTester.eventContracts({
+  schema: 'events/schemas/',
+  events: {
+    'user.created': {
+      schema: 'UserCreatedEvent.json',
+      examples: ['examples/user-created.json']
+    },
+    'order.completed': {
+      schema: 'OrderCompletedEvent.json',
+      examples: ['examples/order-completed.json']
+    }
+  },
+  compatibility: 'backward'
+});
+```
+
+## Contract Report Interface
+
+```typescript
+interface ContractReport {
+  summary: { contracts: number; passed: number; failed: number; warnings: number };
+  consumers: { name: string; contracts: ContractResult[]; compatibility: 'compatible' | 'breaking' | 'unknown' }[];
+  breakingChanges: { type: string; location: string; description: string; impact: 'high' | 'medium' | 'low'; migration: string }[];
+  deprecations: { item: string; deprecatedIn: string; removeIn: string; replacement: string }[];
+}
+```
+
+## Pact Broker Integration
+
+```typescript
+await contractTester.withBroker({
+  brokerUrl: 'https://pact-broker.example.com',
+  auth: { token: process.env.PACT_TOKEN },
+  operations: { publish: true, canIDeploy: true, webhooks: true }
+});
+```
+
+## Coordination
+
+**Primary Agents**: qe-api-contract, qe-api-compatibility, qe-graphql-tester
+**Coordinator**: qe-contract-coordinator

package/assets/skills/contract-testing/references/provider-states.md

@@ -0,0 +1,45 @@
+# Provider States Reference
+
+Provider states define the preconditions that must exist on the provider for a contract interaction to succeed.
+
+## Pattern: State Setup
+```javascript
+// provider-states.js
+const states = {
+  'a user exists': async () => {
+    await db.users.create({ id: 1, name: 'Test User', email: 'test@example.com' });
+  },
+  'no users exist': async () => {
+    await db.users.deleteAll();
+  },
+  'user 1 has 3 orders': async () => {
+    await db.users.create({ id: 1, name: 'Test User' });
+    await db.orders.bulkCreate([
+      { userId: 1, status: 'shipped' },
+      { userId: 1, status: 'pending' },
+      { userId: 1, status: 'delivered' }
+    ]);
+  }
+};
+```
+
+## Common Mistakes
+1. **State not cleaned up** — use transactions or truncate after each test
+2. **Hardcoded IDs** — use factories or fixtures that generate consistent IDs
+3. **Missing state** — provider test passes without state setup (no data = no error)
+4. **Overly specific states** — "user John with email john@..." couples to consumer
+
+## Pact Broker Webhook Setup
+```bash
+# Verify provider when consumer publishes new contract
+curl -X POST ${PACT_BROKER_URL}/webhooks \
+  -H "Content-Type: application/json" \
+  -d '{
+    "events": [{ "name": "contract_content_changed" }],
+    "request": {
+      "method": "POST",
+      "url": "${CI_TRIGGER_URL}",
+      "body": { "pact_url": "${pactbroker.pactUrl}" }
+    }
+  }'
+```

package/assets/skills/coverage-drop-investigator/SKILL.md

@@ -0,0 +1,90 @@
+---
+name: coverage-drop-investigator
+description: "Use when test coverage has dropped and you need to find which changes caused it and what tests to add. Traces coverage regressions to specific commits and files."
+user-invocable: true
+---
+
+# Coverage Drop Investigator
+
+Runbook-style skill for investigating coverage regressions. Identifies which changes caused coverage to drop and recommends targeted tests.
+
+## Activation
+
+```
+/coverage-drop-investigator
+```
+
+## Investigation Flow
+
+### Step 1: Measure Current Coverage
+
+```bash
+# Generate coverage report
+npx jest --coverage --coverageReporters=json-summary
+
+# View summary
+cat coverage/coverage-summary.json | jq '.total'
+```
+
+### Step 2: Find When Coverage Dropped
+
+```bash
+# Compare coverage with main branch
+git stash && npx jest --coverage --coverageReporters=json-summary
+mv coverage/coverage-summary.json coverage/baseline.json
+git stash pop && npx jest --coverage --coverageReporters=json-summary
+
+# Compare
+jq -s '.[0].total.statements.pct as $baseline | .[1].total.statements.pct as $current | {baseline: $baseline, current: $current, delta: ($current - $baseline)}' coverage/baseline.json coverage/coverage-summary.json
+```
+
+### Step 3: Identify Uncovered Files
+
+```bash
+# Find files with lowest coverage
+cat coverage/coverage-summary.json | jq 'to_entries | map(select(.key != "total")) | sort_by(.value.statements.pct) | .[0:10] | .[] | {file: .key, statements: .value.statements.pct, branches: .value.branches.pct}'
+```
+
+### Step 4: Map to Recent Changes
+
+```bash
+# Find recently changed files with low coverage
+git diff --name-only main...HEAD | while read file; do
+  jq --arg f "$file" '.[$f] // empty | {file: $f, statements: .statements.pct}' coverage/coverage-summary.json
+done
+```
+
+### Step 5: Recommend Tests
+
+For each uncovered file, identify:
+1. **Uncovered functions** — need new test cases
+2. **Uncovered branches** — need conditional test cases (if/else paths)
+3. **Uncovered lines** — may indicate dead code or missing edge cases
+
+### Step 6: Report
+
+```markdown
+## Coverage Drop Report
+- **Current**: {{current_pct}}%
+- **Baseline (main)**: {{baseline_pct}}%
+- **Delta**: {{delta}}%
+- **Files causing drop**:
+  | File | Coverage | Changed Lines | Tests Needed |
+  |------|----------|--------------|-------------|
+  | {{file}} | {{pct}}% | {{lines}} | {{count}} |
+- **Recommended action**: {{write_tests / accept_drop / mark_as_excluded}}
+```
+
+## Composition
+
+After investigation:
+- **`/qe-test-generation`** — generate tests for uncovered files
+- **`/mutation-testing`** — verify existing tests actually catch bugs
+- **`/coverage-guard`** — prevent future drops
+
+## Gotchas
+
+- Coverage can drop because NEW code was added without tests, not because tests were removed
+- 100% coverage is not always the goal — focus on critical paths, not getters/setters
+- Branch coverage drops are more concerning than line coverage drops — branches indicate logic paths
+- Coverage tools may count generated code or type definitions — exclude with coveragePathIgnorePatterns

package/assets/skills/coverage-guard/SKILL.md

@@ -0,0 +1,82 @@
+---
+name: coverage-guard
+description: "Use when you want to prevent coverage regressions during development. Activate with /coverage-guard to warn when coverage drops below threshold after code changes."
+user-invocable: true
+---
+
+# Coverage Guard Mode
+
+When activated, checks coverage after test runs and warns if it drops below the configured threshold.
+
+## What It Does
+
+After any test execution (via Bash tool), compares coverage to the threshold in config.json. Warns (doesn't block) if coverage decreased.
+
+## Activation
+
+```
+/coverage-guard
+```
+
+## Configuration
+
+Edit `config.json` in this skill directory to set thresholds:
+
+```json
+{
+  "thresholds": {
+    "statements": 80,
+    "branches": 70,
+    "functions": 75,
+    "lines": 80
+  },
+  "coverageCommand": "npx jest --coverage --coverageReporters=json-summary",
+  "coverageFile": "coverage/coverage-summary.json"
+}
+```
+
+## Hook Configuration
+
+```json
+{
+  "hooks": {
+    "PostToolUse": [
+      {
+        "matcher": "Bash",
+        "hook": ".claude/skills/coverage-guard/scripts/check-coverage.sh",
+        "condition": "command contains 'jest' OR command contains 'vitest' OR command contains 'npm test'"
+      }
+    ]
+  }
+}
+```
+
+## Enforcement Logic
+
+```bash
+#!/bin/bash
+# check-coverage.sh
+COVERAGE_FILE="coverage/coverage-summary.json"
+THRESHOLD=80
+
+if [ -f "$COVERAGE_FILE" ]; then
+  STATEMENTS=$(jq '.total.statements.pct' "$COVERAGE_FILE")
+  BRANCHES=$(jq '.total.branches.pct' "$COVERAGE_FILE")
+
+  if (( $(echo "$STATEMENTS < $THRESHOLD" | bc -l) )); then
+    echo "WARNING: Statement coverage ($STATEMENTS%) below threshold ($THRESHOLD%)"
+    echo "Coverage dropped — check which files lost coverage."
+  fi
+
+  if (( $(echo "$BRANCHES < 70" | bc -l) )); then
+    echo "WARNING: Branch coverage ($BRANCHES%) below 70%"
+  fi
+fi
+```
+
+## Gotchas
+
+- Coverage check runs AFTER the test command — if tests crash, no coverage report is generated
+- Coverage-summary.json must be configured as a reporter — default Jest config may not include it
+- Threshold comparisons use floating point — `79.999%` will trigger below `80%` threshold
+- Branch coverage is typically 10-15% lower than line coverage — set thresholds accordingly

package/assets/skills/coverage-guard/scripts/check-coverage.sh

@@ -0,0 +1,42 @@
+#!/bin/bash
+# check-coverage.sh — Coverage Guard hook
+# Checks coverage after test runs and warns if below threshold.
+# Called by PostToolUse hook on Bash commands containing jest/vitest/npm test
+
+COVERAGE_FILE="coverage/coverage-summary.json"
+THRESHOLD=${COVERAGE_THRESHOLD:-80}
+BRANCH_THRESHOLD=${BRANCH_COVERAGE_THRESHOLD:-70}
+
+if [ ! -f "$COVERAGE_FILE" ]; then
+  # No coverage report generated — skip silently
+  exit 0
+fi
+
+# Extract coverage percentages
+STATEMENTS=$(node -e "console.log(require('./$COVERAGE_FILE').total.statements.pct)" 2>/dev/null)
+BRANCHES=$(node -e "console.log(require('./$COVERAGE_FILE').total.branches.pct)" 2>/dev/null)
+FUNCTIONS=$(node -e "console.log(require('./$COVERAGE_FILE').total.functions.pct)" 2>/dev/null)
+
+if [ -z "$STATEMENTS" ]; then
+  exit 0
+fi
+
+EXIT_CODE=0
+
+# Check statement coverage
+if [ "$(echo "$STATEMENTS < $THRESHOLD" | bc -l 2>/dev/null)" = "1" ]; then
+  echo "WARNING: Statement coverage (${STATEMENTS}%) below threshold (${THRESHOLD}%)"
+  EXIT_CODE=1
+fi
+
+# Check branch coverage
+if [ -n "$BRANCHES" ] && [ "$(echo "$BRANCHES < $BRANCH_THRESHOLD" | bc -l 2>/dev/null)" = "1" ]; then
+  echo "WARNING: Branch coverage (${BRANCHES}%) below threshold (${BRANCH_THRESHOLD}%)"
+  EXIT_CODE=1
+fi
+
+if [ $EXIT_CODE -eq 0 ]; then
+  echo "Coverage OK: statements=${STATEMENTS}%, branches=${BRANCHES}%, functions=${FUNCTIONS}%"
+fi
+
+exit $EXIT_CODE

package/assets/skills/database-testing/SKILL.md

@@ -58,14 +58,6 @@ When testing database operations:
 | **Transaction** | ACID properties | Concurrent access |
 | **Performance** | Query speed | Optimization |
 
-### ACID Properties
-| Property | Test Focus |
-|----------|------------|
-| **Atomicity** | All or nothing (rollback on error) |
-| **Consistency** | Constraints always valid |
-| **Isolation** | Concurrent transactions don't interfere |
-| **Durability** | Committed data persists |
-
 ---
 
 ## Schema Testing
@@ -242,8 +234,6 @@ const dbFleet = await FleetManager.coordinate({
 
 ## Remember
 
-**Database bugs are catastrophic.** Data loss is unrecoverable. Corruption spreads silently. Performance issues compound.
-
 **Test migrations before production:** Forward works, rollback works, data preserved, performance acceptable. Never deploy untested migrations.
 
 **With Agents:** `qe-test-data-architect` generates realistic test data with referential integrity. `qe-test-executor` validates migrations automatically in CI/CD.

package/assets/skills/debug-loop/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: debug-loop
-description: Hypothesis-driven autonomous debugging with real command validation
+description: "Use when debugging a failing test or runtime error with hypothesis-driven investigation, autonomous command validation, and systematic root cause elimination."
 trust_tier: 0
 domain: debugging
 ---