@sylphx/flow 2.16.0 → 2.16.2

package/CHANGELOG.md

@@ -1,5 +1,25 @@
 # @sylphx/flow
 
+## 2.16.2 (2025-12-17)
+
+### 🐛 Bug Fixes
+
+- **commands:** tell LLM to use SlashCommand tool for /review and /continue ([6983015](https://github.com/SylphxAI/flow/commit/6983015b97e89a48e973106828672b8b3000dce8))
+
+### ♻️ Refactoring
+
+- **assets:** convert guidelines to Skills (model-invoked) ([2eb8d01](https://github.com/SylphxAI/flow/commit/2eb8d01162f00a127c5666c8afd9b63fc477ea42))
+
+### 🔧 Chores
+
+- trigger release workflow ([69d661c](https://github.com/SylphxAI/flow/commit/69d661c582157650df855a3a31e21ad6a8b3e7bf))
+
+## 2.16.1 (2025-12-17)
+
+### ♻️ Refactoring
+
+- **commands:** simplify /continue and /review - think, don't checklist ([754eec1](https://github.com/SylphxAI/flow/commit/754eec1211719fc68f25ce47510e5797a33e1469))
+
 ## 2.16.0 (2025-12-17)
 
 ### ✨ Features

package/assets/{slash-commands/guideline-account-security.md → skills/account-security/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-account-security
-description: Guideline: account security - sessions, MFA, devices, security events
-agent: coder
+name: account-security
+description: Account security - MFA, sessions, recovery. Use when protecting user accounts.
 ---
 
 # Account Security Guideline

package/assets/{slash-commands/guideline-admin.md → skills/admin/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-admin
-description: Guideline: admin - RBAC, bootstrap, audit, operational tools
-agent: coder
+name: admin
+description: Admin panel - RBAC, config, admin tools. Use when building admin UI.
 ---
 
 # Admin Guideline

package/assets/{slash-commands/guideline-auth.md → skills/auth/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-auth
-description: Guideline: authentication - sign-in, SSO, passkeys, verification
-agent: coder
+name: auth
+description: Authentication patterns - sign-in, SSO, passkeys, sessions. Use when implementing auth flows.
 ---
 
 # Auth Guideline

package/assets/{slash-commands/guideline-billing.md → skills/billing/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-billing
-description: Guideline: billing - Stripe integration, webhooks, subscription state
-agent: coder
+name: billing
+description: Billing - Stripe, webhooks, subscriptions. Use when implementing payments.
 ---
 
 # Billing Guideline

package/assets/{slash-commands/guideline-code-quality.md → skills/code-quality/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-code-quality
-description: Guideline: code quality - architecture, types, testing, maintainability
-agent: coder
+name: code-quality
+description: Code quality - patterns, testing, maintainability. Use for code review.
 ---
 
 # Code Quality Guideline

package/assets/{slash-commands/guideline-data-architecture.md → skills/data-architecture/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-data-architecture
-description: Guideline: data architecture - boundaries, consistency, state machines
-agent: coder
+name: data-architecture
+description: Data architecture - models, relationships. Use when designing data structures.
 ---
 
 # Data Architecture Guideline

package/assets/{slash-commands/guideline-database.md → skills/database/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-database
-description: Guideline: database - schema, migrations, performance, reliability
-agent: coder
+name: database
+description: Database - schema, indexes, migrations. Use when working with databases.
 ---
 
 # Database Guideline

package/assets/{slash-commands/guideline-delivery.md → skills/delivery/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-delivery
-description: Guideline: delivery - CI gates, automated verification, release safety
-agent: coder
+name: delivery
+description: Delivery - CI/CD, testing, releases. Use when improving pipelines.
 ---
 
 # Delivery Guideline

package/assets/{slash-commands/guideline-discovery.md → skills/discovery/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-discovery
-description: Guideline: discovery - competitive research, opportunities, market positioning
-agent: coder
+name: discovery
+description: Feature discovery - competitive analysis. Use when exploring features.
 ---
 
 # Discovery Guideline

package/assets/{slash-commands/guideline-growth.md → skills/growth/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-growth
-description: Guideline: growth - activation, retention, virality
-agent: coder
+name: growth
+description: Growth - onboarding, activation, retention. Use for growth features.
 ---
 
 # Growth Guideline

package/assets/{slash-commands/guideline-i18n.md → skills/i18n/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-i18n
-description: Guideline: i18n - localization, routing, translation quality
-agent: coder
+name: i18n
+description: Internationalization - localization, translations. Use when adding languages.
 ---
 
 # i18n Guideline

package/assets/{slash-commands/guideline-ledger.md → skills/ledger/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-ledger
-description: Guideline: ledger - balance systems, financial integrity, reconciliation
-agent: coder
+name: ledger
+description: Financial ledger - transactions, audit trails. Use when tracking money.
 ---
 
 # Ledger Guideline

package/assets/{slash-commands/guideline-observability.md → skills/observability/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-observability
-description: Guideline: observability - logging, tracing, alerting, debugging
-agent: coder
+name: observability
+description: Observability - logging, metrics, tracing. Use when adding monitoring.
 ---
 
 # Observability Guideline

package/assets/{slash-commands/guideline-operability.md → skills/operability/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-operability
-description: Guideline: operability - workflows, retries, DLQ, incident response
-agent: coder
+name: operability
+description: Operations - deployment, rollback, feature flags. Use for ops tooling.
 ---
 
 # Operability Guideline

package/assets/{slash-commands/guideline-performance.md → skills/performance/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-performance
-description: Guideline: performance - speed, Core Web Vitals, bottlenecks
-agent: coder
+name: performance
+description: Performance - Core Web Vitals, bundle size. Use when optimizing speed.
 ---
 
 # Performance Guideline

package/assets/{slash-commands/guideline-pricing.md → skills/pricing/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-pricing
-description: Guideline: pricing - strategy, packaging, monetization
-agent: coder
+name: pricing
+description: Pricing strategy - tiers, feature gating. Use when designing pricing.
 ---
 
 # Pricing Guideline

package/assets/{slash-commands/guideline-privacy.md → skills/privacy/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-privacy
-description: Guideline: privacy - consent, PII, data lifecycle, compliance
-agent: coder
+name: privacy
+description: Privacy and data protection - GDPR, CCPA, consent. Use when handling user data.
 ---
 
 # Privacy Guideline

package/assets/{slash-commands/guideline-pwa.md → skills/pwa/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-pwa
-description: Guideline: PWA - offline experience, installation, engagement
-agent: coder
+name: pwa
+description: PWA - service workers, offline support. Use when building PWA features.
 ---
 
 # PWA Guideline

package/assets/{slash-commands/guideline-referral.md → skills/referral/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-referral
-description: Guideline: referral - attribution, rewards, fraud prevention
-agent: coder
+name: referral
+description: Referral systems - referral programs, viral loops. Use for referrals.
 ---
 
 # Referral Guideline

package/assets/{slash-commands/guideline-security.md → skills/security/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-security
-description: Guideline: security - OWASP, headers, authentication, secrets
-agent: coder
+name: security
+description: Application security - OWASP, validation, secrets. Use when securing the app.
 ---
 
 # Security Guideline

package/assets/{slash-commands/guideline-seo.md → skills/seo/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-seo
-description: Guideline: SEO - discoverability, metadata, search rankings
-agent: coder
+name: seo
+description: SEO - meta tags, structured data. Use when optimizing for search.
 ---
 
 # SEO Guideline

package/assets/{slash-commands/guideline-storage.md → skills/storage/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-storage
-description: Guideline: storage - uploads, file handling, security
-agent: coder
+name: storage
+description: File storage - uploads, CDN, blobs. Use when handling files.
 ---
 
 # Storage Guideline

package/assets/{slash-commands/guideline-support.md → skills/support/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-support
-description: Guideline: support - help experience, communications, user satisfaction
-agent: coder
+name: support
+description: Support - help center, tickets, docs. Use when building support.
 ---
 
 # Support Guideline

package/assets/{slash-commands/guideline-trust-safety.md → skills/trust-safety/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-trust-safety
-description: Guideline: trust & safety - abuse prevention, moderation, user protection
-agent: coder
+name: trust-safety
+description: Trust and safety - abuse prevention, rate limiting. Use when fighting bad actors.
 ---
 
 # Trust Safety Guideline

package/assets/{slash-commands/guideline-uiux.md → skills/uiux/SKILL.md}

@@ -1,7 +1,6 @@
 ---
-name: guideline-uiux
-description: Guideline: UI/UX - design system, accessibility, user experience
-agent: coder
+name: uiux
+description: UI/UX - design system, accessibility. Use when building interfaces.
 ---
 
 # UI/UX Guideline

package/assets/slash-commands/continue.md

@@ -1,160 +1,91 @@
 ---
 name: continue
-description: Continue incomplete work - finish features, fix bugs, complete TODOs
+description: Continue incomplete work - find gaps, finish features, fix what's broken
 agent: coder
 ---
 
-# Continue Incomplete Work
+# Continue
 
-Scan codebase for incomplete work. Prioritize. Finish.
+Find what's incomplete. Finish it.
 
 ## Mandate
 
-* Perform a **deep, thorough scan** of incomplete work in this codebase.
-* **Delegate to multiple workers** to research different aspects in parallel; you act as the **final gate** to synthesize and verify quality.
-* **Research then Act**: understand full scope first, then **implement fixes directly**. Don't just report — finish.
-* **Single-pass delivery**: no deferrals; deliver complete implementation.
-* **Be thorough**: incomplete work hides in comments, stubs, error messages, and "temporary" solutions.
-
-## Discovery Approach
-
-### Phase 1: Code Analysis
-Scan for explicit incomplete markers:
-- `TODO`, `FIXME`, `XXX`, `HACK`, `BUG`, `@todo`
-- `NotImplementedError`, `throw new Error('not implemented')`
-- Stub implementations (hardcoded returns, empty catches, `pass`)
-- `test.skip`, `it.skip`, empty test files
-- Commented-out code, debug statements
-
-### Phase 2: Role-Based Simulation
-
-**👤 User Perspective** — Walk through every user-facing flow:
-- Onboarding: Can a new user complete setup without confusion?
-- Happy path: Does the core feature work end-to-end?
-- Error states: What happens when things go wrong? Are messages helpful?
-- Edge cases: Empty states, first-time use, account limits, expired sessions
-- Accessibility: Keyboard nav, screen readers, color contrast
-- Mobile/responsive: Does it work on all devices?
-
-**🔧 Developer Perspective** — Evaluate DX and maintainability:
-- Setup: Can someone clone and run in < 5 minutes?
-- Documentation: Are APIs documented? Examples provided?
-- Error messages: Do stack traces help identify root cause?
-- Debugging: Are there logs at appropriate levels?
-- Testing: Can tests run locally? Are mocks available?
-- Dependencies: Any outdated, deprecated, or vulnerable packages?
-
-**🛡️ Admin/Ops Perspective** — Consider operational readiness:
-- Monitoring: Can you tell if the system is healthy?
-- Logging: Is there enough info to debug production issues?
-- Configuration: Can settings be changed without code deploy?
-- Backup/Recovery: Can data be restored if something fails?
-- Security: Are admin actions audited? Permissions enforced?
-- Scaling: What happens under 10x load?
-
-### Phase 3: Scenario Simulation
-
-Run through these scenarios mentally or via code paths:
-
-| Scenario | Questions to Answer |
-|----------|---------------------|
-| New user signup | Every step works? Validation clear? Email sent? |
-| Returning user login | Session handling? Password reset works? |
-| Core action fails | Error shown? User knows what to do? Data preserved? |
-| Network offline | Graceful degradation? Retry logic? |
-| Concurrent users | Race conditions? Locks? Optimistic updates? |
-| Bad actor attempts | Input sanitized? Rate limited? Logged? |
-| Admin intervention | Can support help user? Audit trail exists? |
-
-## Execution Process
-
-1. **Parallel Discovery** (delegate to workers):
-   - Worker 1: Code markers & stubs (grep TODO, FIXME, placeholders)
-   - Worker 2: User journey simulation (trace main flows, find dead ends)
-   - Worker 3: Developer experience audit (setup, docs, error messages)
-   - Worker 4: Ops readiness check (logging, monitoring, config)
-   - Worker 5: Test coverage & edge cases (skipped tests, missing scenarios)
-
-2. **Synthesize & Prioritize**:
-   - Collect all findings
-   - Group by severity: Critical → High → Medium → Low
-   - Critical: Security issues, data loss risks, broken features
-   - High: User-facing bugs, incomplete core features
-   - Medium: Code quality, missing tests
-   - Low: Documentation, style issues
-
-3. **Implement Fixes**:
-   - Start with Critical items
-   - Complete each fix fully before moving on
-   - Run tests after each significant change
-   - Commit atomically per logical fix
-
-4. **Deep Dive with /review** (when needed):
-   If issues cluster in a specific domain, invoke `/review <domain>` for thorough analysis:
-
-   | Domain | When to Invoke |
-   |--------|----------------|
-   | `auth` | Auth flow issues, session bugs, SSO problems |
-   | `security` | Validation gaps, injection risks, secrets exposure |
-   | `billing` | Payment bugs, subscription issues, webhook failures |
-   | `performance` | Slow pages, bundle bloat, unnecessary re-renders |
-   | `database` | Schema issues, missing indexes, N+1 queries |
-   | `observability` | Missing logs, no alerts, debugging blind spots |
-   | `i18n` | Hardcoded strings, locale issues, RTL bugs |
-
-   Full domain list: auth, account-security, privacy, billing, pricing, ledger, security, trust-safety, uiux, seo, pwa, performance, i18n, database, data-architecture, storage, observability, operability, delivery, growth, referral, support, admin, discovery, code-quality
-
-5. **Loop: Re-invoke /continue**:
-   After completing fixes, **invoke `/continue` again** to:
-   - Verify fixes didn't introduce new issues
-   - Discover issues that were hidden by previous bugs
-   - Continue until no Critical/High items remain
-
-   **Exit condition**: No Critical or High severity items found.
-
-## Output Format
-
-### Discovery Summary
-```
-## Incomplete Work Found
+* **Think, don't checklist.** Understand the project first. What is it trying to do? What would "done" look like?
+* **Delegate workers** for parallel research. You synthesize and verify.
+* **Fix, don't report.** Implement solutions directly.
+* **One pass.** No deferrals. Complete each fix fully.
 
-### Critical (X items)
-- [ ] File:line - Description
+## How to Find Incomplete Work
 
-### High (X items)
-- [ ] File:line - Description
+Don't grep for TODO and call it done. Incomplete work hides in:
 
-### Medium (X items)
-- [ ] File:line - Description
+**What's explicitly unfinished** — Yes, scan for TODO/FIXME/HACK. But ask: why are they there? What was the person avoiding?
 
-### Low (X items)
-- [ ] File:line - Description
-```
+**What's implicitly broken** — Code that "works" but:
+- Fails silently (empty catch blocks, swallowed errors)
+- Works only in happy path (no validation, no edge cases)
+- Works but confuses users (unclear errors, missing feedback)
+- Works but can't be debugged (no logs, no context)
 
-### Progress Updates
-```
-✓ Fixed: [description] (file:line)
-⚠ Blocked: [description] - needs [reason]
-→ Deep dive: invoking /review [domain]
-↻ Loop: re-invoking /continue
-```
+**What's missing entirely** — Features referenced but not implemented. UI that leads nowhere. Promises in docs that code doesn't deliver.
 
-### Completion
-```
-## Continue Complete
+## The Real Test
+
+For each part of the system, ask:
+
+> "If I were a user trying to accomplish their goal, where would I get stuck?"
+
+> "If this broke at 3am, could someone figure out why?"
+
+> "If requirements changed tomorrow, what would be painful to modify?"
+
+> "If we had 100x traffic, what would fall over first?"
+
+These questions reveal incompleteness that checklists miss.
+
+## Execution
+
+1. **Understand the project** — Read README, main entry points, core flows. What is this thing supposed to do?
+
+2. **Walk the critical paths** — Trace actual user journeys through code. Where does the path get uncertain, error-prone, or incomplete?
+
+3. **Find the gaps** — Not just TODOs, but:
+   - Dead ends (code that starts something but doesn't finish)
+   - Weak spots (minimal implementation that will break under pressure)
+   - Missing pieces (what's referenced but doesn't exist)
 
-✓ X issues fixed
-⚠ X issues need manual intervention
-→ Invoked /review for: [domains]
+4. **Prioritize by impact** — What blocks users? What causes data loss? What makes debugging impossible? Fix those first.
+
+5. **Fix completely** — Don't patch. Understand root cause. Implement proper solution. Test it works.
+
+## Skills
+
+Domain knowledge auto-activates when relevant. Available skills:
+
+auth, account-security, privacy, billing, pricing, ledger, security, trust-safety, uiux, seo, pwa, performance, i18n, database, data-architecture, storage, observability, operability, delivery, growth, referral, support, admin, discovery, code-quality
+
+## Loop
+
+After fixing: "Did my fixes introduce new gaps? Did fixing X reveal Y was also broken?"
+
+If yes → run `/continue` again. If no Critical/High issues remain → done.
+
+## Output
 
-Next: [/continue again | no further action needed]
 ```
+## What I Found
+
+[Describe the gaps discovered — not a checklist, but an understanding of what's incomplete and why]
+
+## What I Fixed
+
+- [Description of fix and why it matters]
 
-## Driving Questions
+## What Remains
 
-1. **User**: What flows break or confuse real users? Where do they get stuck?
-2. **Developer**: What would frustrate someone onboarding to this codebase?
-3. **Admin/Ops**: What would make a 3am incident harder to debug?
-4. **Security**: What incomplete validation could be exploited?
-5. **Quality**: What "temporary" solutions became permanent debt?
-6. **Scale**: What works now but will break at 10x growth?
+- [Issues that need human decision or are blocked]
+
+## Next
+
+[/continue again | done]
+```

package/assets/slash-commands/review.md

@@ -1,94 +1,44 @@
 ---
 name: review
-description: Review codebase by domain - usage: /review auth, /review billing, etc.
+description: Review codebase by topic - /review <what to review>
 agent: coder
 args:
-  - name: domain
-    description: Domain to review (auth, billing, security, etc.)
+  - name: topic
+    description: What to review (e.g., auth, security, "the login flow", "why it's slow")
     required: true
 ---
 
 # Review: $ARGS
 
-Perform a focused review of the specified domain(s) in this codebase.
-
 ## Mandate
 
-* **Delegate to multiple workers** to research different aspects in parallel; you act as the **final gate** to synthesize and verify quality.
-* **Deep, thorough analysis**: don't skim — understand root causes and systemic patterns.
-* **Review then Act**: identify issues, then **implement fixes directly**. Don't just report — fix.
-* **Single-pass delivery**: no deferrals; deliver complete implementation.
-* **Explore beyond the spec**: identify gaps, inefficiencies, and opportunities the checklist doesn't cover.
-
-## Guidelines Reference
-
-Based on the domain(s) requested, read the relevant guideline(s) below. You may read multiple guidelines in parallel if the review spans multiple domains.
+* **Understand first.** Absorb the principles, then apply judgment.
+* **Think like the failure mode.** Security? Think like an attacker. Performance? Think like a slow network. Auth? Think like a confused user.
+* **Delegate workers** for parallel research. You synthesize and verify.
+* **Fix, don't report.** Implement solutions directly.
 
-| Domain | Guideline | Description |
-|--------|-----------|-------------|
-| **Identity & Auth** |||
-| `auth` | `/guideline-auth` | Sign-in, SSO, passkeys, verification |
-| `account-security` | `/guideline-account-security` | MFA, session management, account recovery |
-| `privacy` | `/guideline-privacy` | Data handling, consent, GDPR/CCPA |
-| **Billing & Revenue** |||
-| `billing` | `/guideline-billing` | Stripe integration, webhooks, subscriptions |
-| `pricing` | `/guideline-pricing` | Pricing models, tiers, feature gating |
-| `ledger` | `/guideline-ledger` | Transaction records, audit trails, reconciliation |
-| **Security** |||
-| `security` | `/guideline-security` | OWASP, input validation, secrets management |
-| `trust-safety` | `/guideline-trust-safety` | Abuse prevention, rate limiting, fraud |
-| **Frontend & UX** |||
-| `uiux` | `/guideline-uiux` | Design system, accessibility, interactions |
-| `seo` | `/guideline-seo` | Meta tags, structured data, crawlability |
-| `pwa` | `/guideline-pwa` | Service workers, offline, installability |
-| `performance` | `/guideline-performance` | Core Web Vitals, bundle size, caching |
-| `i18n` | `/guideline-i18n` | Localization, routing, hreflang |
-| **Data** |||
-| `database` | `/guideline-database` | Schema design, indexes, migrations |
-| `data-architecture` | `/guideline-data-architecture` | Data models, relationships, integrity |
-| `storage` | `/guideline-storage` | File uploads, CDN, blob storage |
-| **Operations** |||
-| `observability` | `/guideline-observability` | Logging, metrics, tracing, alerts |
-| `operability` | `/guideline-operability` | Deployment, rollback, feature flags |
-| `delivery` | `/guideline-delivery` | CI/CD, testing, release process |
-| **Growth & Support** |||
-| `growth` | `/guideline-growth` | Onboarding, activation, retention |
-| `referral` | `/guideline-referral` | Referral programs, viral loops |
-| `support` | `/guideline-support` | Help systems, tickets, documentation |
-| **Admin & Discovery** |||
-| `admin` | `/guideline-admin` | Admin panel, RBAC, config management |
-| `discovery` | `/guideline-discovery` | Feature discovery, competitive analysis |
-| **Code Quality** |||
-| `code-quality` | `/guideline-code-quality` | Patterns, testing, maintainability |
+## Skills
 
-## Execution
+Domain knowledge is available through Skills that auto-activate based on context:
 
-1. Parse the `$ARGS` to identify which domain(s) to review
-2. Read the corresponding guideline file(s) — **read in parallel** if multiple domains
-3. Use the guideline's Tech Stack, Non-Negotiables, Context, and Driving Questions to guide your review
-4. Delegate workers to investigate different aspects simultaneously
-5. Synthesize findings and implement fixes
+auth, account-security, privacy, billing, pricing, ledger, security, trust-safety, uiux, seo, pwa, performance, i18n, database, data-architecture, storage, observability, operability, delivery, growth, referral, support, admin, discovery, code-quality
 
-## Multi-Domain Reviews
+You don't need to invoke them — they activate when relevant.
 
-You can review multiple domains at once:
-- `/review auth security` — Review both auth and security
-- `/review billing pricing ledger` — Full revenue stack review
-- `/review performance seo pwa` — Frontend optimization review
-
-When reviewing multiple domains, look for **cross-cutting concerns** and **gaps between domains**.
-
-## Output Format
+## Output
 
 ```
-## Review: [domain(s)]
+## Review: [topic]
+
+### Understanding
+[How this is implemented. Architecture, choices, tradeoffs.]
 
-### Critical Issues
-- [ ] Issue description → Fix implemented
+### Issues
+[What's wrong and why it matters]
 
-### Improvements Made
-- ✓ What was fixed/improved
+### Fixed
+[Changes made]
 
-### Recommendations
-- Future considerations (if can't fix now)
+### Remaining
+[Needs human decision or blocked]
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@sylphx/flow",
-	"version": "2.16.0",
+	"version": "2.16.2",
 	"description": "One CLI to rule them all. Unified orchestration layer for Claude Code, OpenCode, Cursor and all AI development tools. Auto-detection, auto-installation, auto-upgrade.",
 	"type": "module",
 	"bin": {