v0.4.1 - Colocation fix

[0.4.1] - 2026-01-20

Fixed

• Colocation in monorepos now resolves paths relative to the target package directory, so .figma.ts(x) files land next to the actual component files (affects Chakra, ZapUI, etc.)

v0.4.0 - Package-centric scanning

Changes

Features

• Package-centric scanning: Replace repo-wide scanning with package-focused approach - scans from package.json downward (single package scope)
• import_from support: Auto-derive import path from package.json name, or allow explicit override via [inputs].import_from in superconnect.toml
• Improved UX: Better init and run flow with validation and guidance

Fixes

• E2E tests: Handle Figma CLI non-zero exit on 404 errors (expected for test fixtures)
• Windows: Use pathToFileURL for dynamic imports in tests

Internal

• Deleted summarize-repo.ts (409 lines), replaced with package-scan.ts (238 lines)
• Prompts now use {{IMPORT_INSTRUCTIONS}} placeholder for configurable import guidance
• Updated README and ARCHITECTURE.md to reflect new terminology

v0.3.2 - Improved error handling & concurrency defaults

Changed

• Default concurrency reduced from 8 to 5 for better compatibility with LLM proxies
• Improved TOML comments for concurrency setting to explain its purpose and troubleshooting

Fixed

• Added comprehensive error handling for common API errors:
  • 402 billing/quota errors with links to billing dashboards
  • 408 timeout errors with retry guidance
  • 413/context length errors with model suggestions
  • 502/503 service unavailable with concurrency advice (helps LiteLLM/Bedrock users)
  • 529 overloaded (Anthropic-specific) with wait guidance
  • Content policy violations with troubleshooting tips
• Rate limit (429) errors now suggest lowering concurrency as first troubleshooting step

v0.3.1 - Rename logs directory

Changed

• Renamed intermediate results directory from superconnect/ to superconnect-logs/ for clarity
  • All pipeline artifacts (repo-summary.json, figma-components-index.json, orientation.jsonl, codegen-summaries/, etc.) now written to superconnect-logs/
  • Updated documentation, scripts, tests, and .gitignore to reflect new naming
  • No changes to config file name (superconnect.toml) or package/binary names

v0.3.0 - Agent SDK default

Changed

• Agent SDK is now the default backend — 33% faster, 6x fewer tokens vs Messages API
• Default model changed to claude-sonnet-4-5
• Default max tokens increased from 2048 to 16384

Added

• Agent SDK mode with autonomous codebase exploration (Read, Glob, Grep tools)
• --no-agent-sdk flag to use Messages API instead
• Expanded E2E test coverage (7 Chakra + 6 ZapUI components with semantic assertions)

Fixed

• Validation false positives on valid Code Connect files
• Angular codegen confusion when React quickstart docs present
• Agent SDK thinking text leaking into generated code

Internal

• Migrated from Jest to node:test (faster, zero deps)
• Consolidated utilities into src/util/naming.js and src/util/fs-helpers.js
• Streamlined documentation

v0.2.10 - Windows PowerShell output visibility fix

Fixed

• Windows PowerShell output visibility: Child process output (Figma scan details, code generation progress) now displays correctly on Windows
  • Root cause: spawnSync with shell: true spawned cmd.exe as intermediary, which interfered with console output and ANSI color codes
  • Solution: Call Node.js scripts directly via process.execPath with argument arrays instead of shell command strings
  • Eliminates shell quoting/escaping issues and works identically across all platforms

v0.2.9 - Hybrid AST/regex validation

Changed

• Refactor validation layer to use hybrid AST/regex approach
  • Replace regex-based figma.*() extraction with ts-morph AST traversal for better edge case handling
  • Keep proven regex patterns for template/JSX validation
  • Improves correctness (+43%) and maintainability (+33%) with minimal performance impact

v0.2.8 - 4x faster Windows validation

Performance

• Replace npx with direct CLI invocation for Figma validation (4x faster on Windows)
  • Resolve @figma/code-connect binary path directly from node_modules
  • Use process.execPath (node) to invoke CLI instead of npx
  • Eliminates ~30s npx overhead per CLI call on Windows
  • Windows CI improved from 64s to 16s for unit tests
  • Reduce timeout from 120s to 30s (no package download overhead)

Changed

• Trigger CI unit tests on version tags in addition to branch pushes
• Improve release process documentation with pre-flight checks and error summaries
• Remove global Figma CLI pre-install from CI workflow (no longer needed)

v0.2.7 - Windows compatibility fix

Fixed

• CRITICAL: Windows compatibility for validation - add shell: true to all npx spawn calls
  • v0.2.6 used npx.cmd but still failed with EINVAL on Windows
  • Now uses shell: true which is the Node.js recommended approach for cross-platform compatibility
  • Removes platform-specific npx.cmd detection in favor of simpler, more robust solution

v0.2.6 - Windows npx compatibility fix

Fixed

• CRITICAL: Windows npx compatibility - use npx.cmd on Windows to prevent ENOENT errors
  • Previously caused 100% validation failure on Windows with "spawnSync npx ENOENT"
  • Affects all Code Connect file validation attempts
  • Now correctly detects Windows platform and uses npx.cmd

Changed

• Streamline agent documentation for clarity and reduced token usage