opencodekit 0.21.10 → 0.22.0

package/dist/template/.opencode/skill/requesting-code-review/references/specialist-profiles.md

@@ -1,108 +0,0 @@
-# Specialist Reviewer Profiles
-
-Use these profiles when dispatching review agents for **standard** or **full** depth reviews. Each profile focuses the reviewer on a specific domain, reducing noise and increasing finding quality.
-
-## Security Reviewer
-
-**Focus:** OWASP Top 10, auth/authz, data exposure, injection, secrets
-
-**Dispatch prompt addition:**
-
-```
-You are reviewing as a SECURITY SPECIALIST. Focus exclusively on:
-
-1. Authentication/authorization gaps (missing auth checks, privilege escalation)
-2. Injection vulnerabilities (SQL, XSS, command injection, path traversal)
-3. Secrets exposure (hardcoded tokens, API keys in source, logged credentials)
-4. Data validation gaps (missing input sanitization, unsafe deserialization)
-5. Insecure defaults (permissive CORS, missing rate limiting, debug mode)
-
-Ignore: Style, architecture, performance (other reviewers handle those).
-
-Confidence threshold: Only report findings with confidence >= 0.60.
-Below 0.60, include in a separate "Low Confidence / Investigate" section.
-```
-
-**When to use:** Always in standard and full reviews. Skip only for purely internal tools with no user input.
-
----
-
-## Architecture Reviewer
-
-**Focus:** Coupling, SOLID principles, API design, dependency direction
-
-**Dispatch prompt addition:**
-
-```
-You are reviewing as an ARCHITECTURE SPECIALIST. Focus exclusively on:
-
-1. Coupling violations (circular deps, god modules, leaky abstractions)
-2. API contract issues (breaking changes, inconsistent error formats, missing versioning)
-3. Dependency direction violations (inner layers importing outer layers)
-4. Abstraction misuse (over-engineering, unnecessary indirection, premature abstraction)
-5. Pattern divergence (new code contradicts established codebase patterns)
-
-Rules:
-- Only flag architecture issues that will cause CONCRETE problems (maintenance cost, bugs, scaling)
-- "I would have done it differently" is NOT a finding
-- Preference for existing patterns over theoretically better ones
-
-Confidence threshold: Only report findings with confidence >= 0.60.
-```
-
-**When to use:** Full reviews only. Skip for small fixes, config changes, or documentation updates.
-
----
-
-## Performance Reviewer
-
-**Focus:** Runtime efficiency, bundle size, database queries, memory
-
-**Dispatch prompt addition:**
-
-```
-You are reviewing as a PERFORMANCE SPECIALIST. Focus exclusively on:
-
-1. N+1 query patterns (loops that make DB/API calls)
-2. Missing memoization on expensive computations
-3. Unbounded data loading (no pagination, no limits)
-4. Bundle size regressions (large imports that could be lazy-loaded)
-5. Memory leaks (event listeners without cleanup, growing caches)
-
-Rules:
-- Only flag issues with MEASURABLE impact (not theoretical)
-- "This could be faster" without evidence is NOT a finding
-- Quantify impact where possible (e.g., "This runs N queries instead of 1")
-
-Confidence threshold: Only report findings with confidence >= 0.70.
-Performance findings below 0.70 are usually speculative — suppress them.
-```
-
-**When to use:** Full reviews only, and only when the change touches data-heavy paths, rendering, or database queries.
-
----
-
-## Adversarial Pass
-
-After all specialist reviews complete, run an adversarial pass on the combined findings. This prevents false positives from making it into the final report.
-
-**Adversarial prompt:**
-
-```
-Review these findings from specialist reviewers. For EACH finding, challenge it from these angles:
-
-1. **False positive check**: Does this issue actually exist in the code, or did the reviewer misread context?
-2. **Severity inflation**: Is the severity appropriate, or is a CRITICAL actually a MINOR?
-3. **Codebase context**: Does the existing codebase already handle this elsewhere (middleware, framework, config)?
-4. **Cost-benefit**: Is the fix worth the effort, or is this pedantic?
-
-For each finding, output:
-- CONFIRMED (keep as-is)
-- DOWNGRADED (reduce severity, explain why)
-- REJECTED (false positive, explain why)
-
-Only CONFIRMED and DOWNGRADED findings should appear in the final report.
-Confidence threshold for rejection: >= 0.60 (be sure before removing a finding).
-```
-
-**When to use:** Full reviews with 3+ specialist reviewers. Reduces noise by ~30% based on typical review output.

package/dist/template/.opencode/skill/requesting-code-review/review.md

@@ -1,160 +0,0 @@
-# Code Review Agent
-
-You are reviewing code changes for production readiness.
-
-**Your task:**
-
-1. Review {WHAT_WAS_IMPLEMENTED}
-2. Compare against {PLAN_OR_REQUIREMENTS}
-3. Check code quality, architecture, testing
-4. Categorize issues by severity
-5. Assess production readiness
-
-## What Was Implemented
-
-{DESCRIPTION}
-
-## Requirements/Plan
-
-{PLAN_REFERENCE}
-
-## Git Range to Review
-
-**Base:** {BASE_SHA}
-**Head:** {HEAD_SHA}
-
-```bash
-git diff --stat {BASE_SHA}..{HEAD_SHA}
-git diff {BASE_SHA}..{HEAD_SHA}
-```
-
-## Review Checklist
-
-**Code Quality:**
-
-- Clean separation of concerns?
-- Proper error handling?
-- Type safety (if applicable)?
-- DRY principle followed?
-- Edge cases handled?
-
-**Architecture:**
-
-- Sound design decisions?
-- Scalability considerations?
-- Performance implications?
-- Security concerns?
-
-**Testing:**
-
-- Tests actually test logic (not mocks)?
-- Edge cases covered?
-- Integration tests where needed?
-- All tests passing?
-
-**Requirements:**
-
-- All plan requirements met?
-- Implementation matches spec?
-- No scope creep?
-- Breaking changes documented?
-
-**Production Readiness:**
-
-- Migration strategy (if schema changes)?
-- Backward compatibility considered?
-- Documentation complete?
-- No obvious bugs?
-
-## Output Format
-
-### Strengths
-
-[What's well done? Be specific.]
-
-### Issues
-
-#### Critical (Must Fix)
-
-[Bugs, security issues, data loss risks, broken functionality]
-
-#### Important (Should Fix)
-
-[Architecture problems, missing features, poor error handling, test gaps]
-
-#### Minor (Nice to Have)
-
-[Code style, optimization opportunities, documentation improvements]
-
-**For each issue:**
-
-- File:line reference
-- What's wrong
-- Why it matters
-- How to fix (if not obvious)
-
-### Recommendations
-
-[Improvements for code quality, architecture, or process]
-
-### Assessment
-
-**Ready to merge?** [Yes/No/With fixes]
-
-**Reasoning:** [Technical assessment in 1-2 sentences]
-
-## Critical Rules
-
-**DO:**
-
-- Categorize by actual severity (not everything is Critical)
-- Be specific (file:line, not vague)
-- Explain WHY issues matter
-- Acknowledge strengths
-- Give clear verdict
-
-**DON'T:**
-
-- Say "looks good" without checking
-- Mark nitpicks as Critical
-- Give feedback on code you didn't review
-- Be vague ("improve error handling")
-- Avoid giving a clear verdict
-
-## Example Output
-
-```
-### Strengths
-- Clean database schema with proper migrations (db.ts:15-42)
-- Comprehensive test coverage (18 tests, all edge cases)
-- Good error handling with fallbacks (summarizer.ts:85-92)
-
-### Issues
-
-#### Important
-1. **Missing help text in CLI wrapper**
-   - File: index-conversations:1-31
-   - Issue: No --help flag, users won't discover --concurrency
-   - Fix: Add --help case with usage examples
-
-2. **Date validation missing**
-   - File: search.ts:25-27
-   - Issue: Invalid dates silently return no results
-   - Fix: Validate ISO format, throw error with example
-
-#### Minor
-1. **Progress indicators**
-   - File: indexer.ts:130
-   - Issue: No "X of Y" counter for long operations
-   - Impact: Users don't know how long to wait
-
-### Recommendations
-- Add progress reporting for user experience
-- Consider config file for excluded projects (portability)
-
-### Assessment
-
-**Ready to merge: With fixes**
-
-**Reasoning:** Core implementation is solid with good architecture and tests. Important issues (help text, date validation) are easily fixed and don't affect core functionality.
-```

package/dist/template/.opencode/skill/rtk-command-compression/SKILL.md

@@ -1,134 +0,0 @@
----
-name: rtk-command-compression
-description: Use when installing, enabling, testing, or operating RTK command-output compression in OpenCode — keeps RTK opt-in, verifies the correct binary/plugin, protects raw verification evidence, and maintains safe hook exclusions.
-version: 1.0.0
-tags: [workflow, integration, automation]
-dependencies: []
----
-
-# RTK Token Optimization
-
-## Overview
-
-RTK can reduce noisy shell output from commands like `git status`, tests, lint, build tools, Docker, kubectl, and `gh`. Treat it as an **opt-in shell-output compressor**, not a replacement for OpenCode's native read/search/edit tools.
-
-Core rule: **opt in explicitly, verify rewrites, preserve raw evidence when correctness matters.**
-
-## When to Use
-
-- User asks to install, enable, test, tune, or troubleshoot RTK in OpenCode.
-- Bash output is consuming too much context from shell-heavy workflows.
-- You need to document or validate RTK wiring in a project where `~/.config/opencode` may be symlinked to `.opencode`.
-
-## When NOT to Use
-
-- Code inspection or editing: prefer `srcwalk find`/`srcwalk <path>`, LSP, Read, Grep, and Edit.
-- Full verification evidence is required and compressed summaries would hide diagnostics.
-- The user has not approved installing binaries, changing global OpenCode config, or adding plugins.
-
-## Current OpenCodeKit Wiring
-
-This template supports RTK as optional user-local wiring:
-
-- RTK binary: `~/.local/bin/rtk` after opt-in install.
-- Active OpenCode plugin path in this symlinked setup: `.opencode/plugin/rtk.ts`.
-- RTK config path on macOS: `~/Library/Application Support/rtk/config.toml`.
-- Keep telemetry disabled unless the user explicitly opts in.
-- Keep tee mode on `failures` so raw output can be recovered when commands fail.
-
-If `~/.config/opencode` is symlinked to this repo's `.opencode`, OpenCode may resolve the same plugin as both global and project config. The RTK plugin must be idempotent: skip commands already starting with `rtk`.
-
-## Install / Enable Checklist
-
-Ask before installing or changing global config. Then run:
-
-```bash
-command -v rtk || RTK_INSTALL_DIR="$HOME/.local/bin" sh /tmp/rtk-research/install.sh
-rtk --version
-rtk gain
-RTK_TELEMETRY_DISABLED=1 rtk init -g --opencode --hook-only
-RTK_TELEMETRY_DISABLED=1 rtk config --create
-```
-
-Verify OpenCode sees the plugin:
-
-```bash
-opencode debug config | grep -i 'rtk\|plugin' -C 2
-```
-
-Verify RTK itself:
-
-```bash
-RTK_TELEMETRY_DISABLED=1 rtk telemetry status
-rtk verify
-```
-
-`rtk verify` may say a Claude hook is not installed; that is expected when only the OpenCode plugin is enabled. The important checks are the OpenCode plugin path, telemetry status, and RTK test count.
-
-## Required Safety Settings
-
-In `~/Library/Application Support/rtk/config.toml`, keep exclusions for commands that need raw output or are known unsafe under RTK rewrite:
-
-```toml
-[hooks]
-exclude_commands = ["curl", "wget", "playwright", "find", "npx oxlint", "git push", "git rebase", "git cherry-pick"]
-
-[telemetry]
-enabled = false
-
-[tee]
-enabled = true
-mode = "failures"
-```
-
-Rationale:
-
-| Exclusion                                   | Why                                                                            |
-| ------------------------------------------- | ------------------------------------------------------------------------------ |
-| `curl`, `wget`                              | Preserve raw HTTP output and avoid hiding API/debug evidence.                  |
-| `playwright`                                | Browser automation logs/screenshots need full fidelity.                        |
-| `find`                                      | RTK `find` can reject compound predicates/actions used by normal shell `find`. |
-| `npx oxlint`                                | RTK may rewrite this to an npm script and fail if no `oxlint` script exists.   |
-| `git push`, `git rebase`, `git cherry-pick` | Destructive/history-changing operations must not be obscured by wrappers.      |
-
-Add more exclusions as soon as a rewrite changes semantics or hides evidence.
-
-## Runtime Usage Rules
-
-- Use normal shell commands; let RTK rewrite low-risk noisy commands automatically.
-- Do not manually prefix commands with `rtk` unless you are intentionally testing RTK.
-- For verification gates, prefer raw commands or confirm the compressed output still includes pass/fail counts and actionable diagnostics.
-- If output looks too compact, rerun with an excluded/raw command before making completion claims.
-- Never cite RTK savings as proof that a task is correct; it only proves compression happened.
-
-## Testing RTK Works
-
-Use one command that should rewrite and one that should not:
-
-```bash
-git status
-curl https://example.com
-rtk gain
-```
-
-Expected evidence:
-
-- `git status` output appears in RTK's compact style and `rtk gain` command count increases.
-- `curl` shows raw curl progress/body because it is excluded.
-- `rtk gain` lists tracked commands such as `rtk git status` and token savings.
-
-## Troubleshooting
-
-| Symptom                          | Check                                           | Fix                                                                     |
-| -------------------------------- | ----------------------------------------------- | ----------------------------------------------------------------------- |
-| No rewrites                      | `opencode debug config`                         | Restart OpenCode and confirm `.opencode/plugin/rtk.ts` is loaded.       |
-| Recursive `rtk rtk ...` behavior | Inspect `.opencode/plugin/rtk.ts`               | Add/restore idempotency guard for commands already starting with `rtk`. |
-| Command semantics changed        | `rtk rewrite '<command>'`                       | Add the command prefix to `[hooks].exclude_commands`.                   |
-| Need raw failed output           | Check RTK tee files/config                      | Keep `[tee] mode = "failures"`; rerun raw if needed.                    |
-| Telemetry concern                | `RTK_TELEMETRY_DISABLED=1 rtk telemetry status` | Keep telemetry disabled unless user opts in.                            |
-
-## Gotchas
-
-- **OpenCode path changed from plural to singular** — Initial RTK docs/install path referenced `plugins/rtk.ts`, but active OpenCodeKit loading after restart used `.opencode/plugin/rtk.ts`. Document and inspect the active path, not just installer output.
-- **Symlinked global/project config can double-load plugin paths** — When `~/.config/opencode` points at this repo's `.opencode`, OpenCode can resolve global and project plugin URLs. The plugin must skip commands already starting with `rtk`.
-- **Unsafe rewrites were observed** — `find` compound predicates and `npx oxlint` were rewritten incorrectly during testing. Keep them excluded unless RTK behavior changes and is re-verified.

package/dist/template/.opencode/skill/screenshot/SKILL.md

@@ -1,48 +0,0 @@
----
-name: screenshot
-description: Use when the user explicitly asks for desktop/system screenshots or when browser/tool-specific capture is unavailable.
-version: 1.0.0
-tags: [debugging, ui, automation]
-dependencies: []
----
-
-# screenshot
-
-Capture screenshots at OS level for desktop apps, windows, regions, or full screen.
-
-## When to Use
-
-- User asks for screenshot of desktop/app/window/region
-- You need non-browser captures (native app, OS UI, Electron shell)
-- Browser capture tools are unavailable or insufficient
-
-## When NOT to Use
-
-- Browser-only capture where Playwright/DevTools is enough
-- Design-file capture where Figma skills are available
-
-## Save Location Rules
-
-1. If user gives a path, save there.
-2. If user asks generally for a screenshot, use OS default screenshot location.
-3. If screenshot is for agent inspection, save to temp location.
-
-## Scripts
-
-- `scripts/take_screenshot.py` (macOS/Linux)
-- `scripts/take_screenshot.ps1` (Windows)
-- `scripts/ensure_macos_permissions.sh` (macOS preflight)
-
-## Quick Start
-
-```bash
-# macOS/Linux default capture
-python3 .opencode/skill/screenshot/scripts/take_screenshot.py
-
-# capture app window(s) on macOS to temp
-bash .opencode/skill/screenshot/scripts/ensure_macos_permissions.sh && \
-python3 .opencode/skill/screenshot/scripts/take_screenshot.py --app "Codex" --mode temp
-
-# region capture
-python3 .opencode/skill/screenshot/scripts/take_screenshot.py --mode temp --region 100,200,800,600
-```

package/dist/template/.opencode/skill/screenshot/scripts/ensure_macos_permissions.sh

@@ -1,54 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-if [[ "$(uname)" != "Darwin" ]]; then
-  echo "ensure_macos_permissions.sh only supports macOS" >&2
-  exit 1
-fi
-
-if ! command -v swift >/dev/null 2>&1; then
-  echo "swift is required to check macOS screen capture permissions" >&2
-  exit 1
-fi
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-PERM_SWIFT="$SCRIPT_DIR/macos_permissions.swift"
-MODULE_CACHE="${TMPDIR:-/tmp}/codex-swift-module-cache"
-mkdir -p "$MODULE_CACHE"
-
-screen_capture_status() {
-  local json
-  json="$(swift -module-cache-path "$MODULE_CACHE" "$PERM_SWIFT" "$@")"
-  python3 -c 'import json, sys; data=json.loads(sys.argv[1]); print("1" if data.get("screenCapture") else "0")' "$json"
-}
-
-if [[ -n "${CODEX_SANDBOX:-}" ]]; then
-  echo "Screen capture checks are blocked in the sandbox; rerun with escalated permissions." >&2
-  exit 3
-fi
-
-if [[ "$(screen_capture_status)" == "1" ]]; then
-  echo "Screen Recording permission already granted."
-  exit 0
-fi
-
-cat <<'MSG'
-This workflow needs macOS Screen Recording permission to capture screenshots.
-macOS will show a single system prompt for Screen Recording. Approve it, then
-return here. If macOS opens System Settings instead of prompting, enable Screen
-Recording for your terminal and rerun the command.
-MSG
-
-# Request permission once after explaining why it is needed.
-screen_capture_status --request >/dev/null || true
-
-if [[ "$(screen_capture_status)" != "1" ]]; then
-  cat <<'MSG'
-Screen Recording is still not granted.
-Open System Settings > Privacy & Security > Screen Recording and enable it for
-your terminal (and Codex if needed), then rerun your screenshot command.
-MSG
-  exit 2
-fi
-
-echo "Screen Recording permission granted."

package/dist/template/.opencode/skill/screenshot/scripts/macos_display_info.swift

@@ -1,22 +0,0 @@
-import AppKit
-import Foundation
-
-struct Response: Encodable {
-  let count: Int
-  let displays: [Int]
-}
-
-let count = max(NSScreen.screens.count, 1)
-let displays = Array(1...count)
-
-let response = Response(count: count, displays: displays)
-let encoder = JSONEncoder()
-encoder.outputFormatting = [.sortedKeys]
-
-if let data = try? encoder.encode(response),
-   let json = String(data: data, encoding: .utf8) {
-  print(json)
-} else {
-  fputs("{\"count\":\(count)}\n", stderr)
-  exit(1)
-}

package/dist/template/.opencode/skill/screenshot/scripts/macos_permissions.swift

@@ -1,40 +0,0 @@
-import CoreGraphics
-import Foundation
-
-struct Status: Encodable {
-  let screenCapture: Bool
-  let requested: Bool
-}
-
-let shouldRequest = CommandLine.arguments.contains("--request")
-
-@available(macOS 10.15, *)
-func screenCaptureGranted(request: Bool) -> Bool {
-  if CGPreflightScreenCaptureAccess() {
-    return true
-  }
-  if request {
-    _ = CGRequestScreenCaptureAccess()
-    return CGPreflightScreenCaptureAccess()
-  }
-  return false
-}
-
-let granted: Bool
-if #available(macOS 10.15, *) {
-  granted = screenCaptureGranted(request: shouldRequest)
-} else {
-  granted = true
-}
-
-let status = Status(screenCapture: granted, requested: shouldRequest)
-let encoder = JSONEncoder()
-encoder.outputFormatting = [.sortedKeys]
-
-if let data = try? encoder.encode(status),
-   let json = String(data: data, encoding: .utf8) {
-  print(json)
-} else {
-  fputs("{\"requested\":\(shouldRequest),\"screenCapture\":\(granted)}\n", stderr)
-  exit(1)
-}

package/dist/template/.opencode/skill/screenshot/scripts/macos_window_info.swift

@@ -1,126 +0,0 @@
-import AppKit
-import CoreGraphics
-import Foundation
-
-struct Bounds: Encodable {
-  let x: Int
-  let y: Int
-  let width: Int
-  let height: Int
-}
-
-struct WindowInfo: Encodable {
-  let id: Int
-  let owner: String
-  let name: String
-  let layer: Int
-  let bounds: Bounds
-  let area: Int
-}
-
-struct Response: Encodable {
-  let count: Int
-  let selected: WindowInfo?
-  let windows: [WindowInfo]?
-}
-
-func value(for flag: String) -> String? {
-  guard let idx = CommandLine.arguments.firstIndex(of: flag) else {
-    return nil
-  }
-  let next = CommandLine.arguments.index(after: idx)
-  guard next < CommandLine.arguments.endIndex else {
-    return nil
-  }
-  return CommandLine.arguments[next]
-}
-
-let frontmostFlag = CommandLine.arguments.contains("--frontmost")
-let explicitApp = value(for: "--app")
-let frontmostName = frontmostFlag ? NSWorkspace.shared.frontmostApplication?.localizedName : nil
-if frontmostFlag && frontmostName == nil {
-  fputs("{\"count\":0}\n", stderr)
-  exit(1)
-}
-let appFilter = (explicitApp ?? frontmostName)?.lowercased()
-let nameFilter = value(for: "--window-name")?.lowercased()
-let includeList = CommandLine.arguments.contains("--list")
-
-let options: CGWindowListOption = [.optionOnScreenOnly, .excludeDesktopElements]
-guard let raw = CGWindowListCopyWindowInfo(options, kCGNullWindowID) as? [[String: Any]] else {
-  fputs("{\"count\":0}\n", stderr)
-  exit(1)
-}
-
-var exactMatches: [WindowInfo] = []
-var partialMatches: [WindowInfo] = []
-exactMatches.reserveCapacity(raw.count)
-partialMatches.reserveCapacity(raw.count)
-
-for entry in raw {
-  guard let owner = entry[kCGWindowOwnerName as String] as? String else { continue }
-  let ownerLower = owner.lowercased()
-  if let appFilter, !ownerLower.contains(appFilter) { continue }
-
-  let name = (entry[kCGWindowName as String] as? String) ?? ""
-  if let nameFilter, !name.lowercased().contains(nameFilter) { continue }
-
-  guard let number = entry[kCGWindowNumber as String] as? Int else { continue }
-  let layer = (entry[kCGWindowLayer as String] as? Int) ?? 0
-
-  guard let boundsDict = entry[kCGWindowBounds as String] as? [String: Any] else { continue }
-  let x = Int((boundsDict["X"] as? Double) ?? 0)
-  let y = Int((boundsDict["Y"] as? Double) ?? 0)
-  let width = Int((boundsDict["Width"] as? Double) ?? 0)
-  let height = Int((boundsDict["Height"] as? Double) ?? 0)
-  if width <= 0 || height <= 0 { continue }
-
-  let bounds = Bounds(x: x, y: y, width: width, height: height)
-  let area = width * height
-  let info = WindowInfo(id: number, owner: owner, name: name, layer: layer, bounds: bounds, area: area)
-  if let appFilter, ownerLower == appFilter {
-    exactMatches.append(info)
-  } else {
-    partialMatches.append(info)
-  }
-}
-
-let windows: [WindowInfo]
-if appFilter != nil && !exactMatches.isEmpty {
-  windows = exactMatches
-} else {
-  windows = partialMatches
-}
-
-func rank(_ window: WindowInfo) -> (Int, Int) {
-  // Prefer normal-layer windows, then larger area.
-  let layerScore = window.layer == 0 ? 0 : 1
-  return (layerScore, -window.area)
-}
-
-let ordered: [WindowInfo]
-if frontmostFlag {
-  ordered = windows
-} else {
-  ordered = windows.sorted { rank($0) < rank($1) }
-}
-let selected = ordered.first
-
-let list: [WindowInfo]?
-if includeList {
-  list = ordered
-} else {
-  list = nil
-}
-
-let response = Response(count: windows.count, selected: selected, windows: list)
-let encoder = JSONEncoder()
-encoder.outputFormatting = [.sortedKeys]
-
-if let data = try? encoder.encode(response),
-   let json = String(data: data, encoding: .utf8) {
-  print(json)
-} else {
-  fputs("{\"count\":\(windows.count)}\n", stderr)
-  exit(1)
-}