Update wp-bones extension

[gfazioli]

Description

Hardens the WP Bones menu-bar command against filesystem failures when reading from / writing to LocalStorage.

The crash was reported via Raycast's Extension Issues dashboard — an ENOSPC: no space left on device error fired by Node's writeFileSync while Raycast was flushing its internal com.raycast.api.cache/.../journal during a LocalStorage.getItem call:

menu-bar | Error: ENOSPC: no space left on device, open
'.../com.raycast.api.cache/.../journal'
   at Object.writeFileSync (node:fs:2430:20)

Fix

• Replaced useLocalStorage (from @raycast/utils) with direct LocalStorage.getItem/setItem calls (from @raycast/api), each wrapped in try/catch. On read failure the hook falls back to the initial version; on write failure the call is best-effort (a missed persistence won't crash the menu-bar).
• Fixed a faulty migration path of the legacy version-storage format that could trigger a false "new version available" notification on every launch. Stale legacy values are now discarded silently.

Other minor robustness improvements applied in the same iteration (defensive guards on documentation API responses, explicit error state in Ask WP Bones AI when the docs lookup fails, encodeURIComponent for the embedded blueprint URL in the Playground action) — full list in the CHANGELOG.

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Thank you for the update! 🎉

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 10-15 business days.

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates the WP Bones Raycast extension with new commands and UX improvements, plus bug fixes around version checking, documentation search, and menu bar behavior.

Changes:

• Added new commands: “Ask WP Bones AI” and “WP Bones Release Notes”
• Improved boilerplate/template flow with README preview and extra actions (e.g., Copy URL)
• Refactored version storage + comparison logic and hardened LocalStorage access against filesystem failures

Reviewed changes

Copilot reviewed 11 out of 14 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
extensions/wp-bones/src/use-wp-bones-template.tsx	Removed legacy templates search grid command (dead code cleanup).
extensions/wp-bones/src/templates.ts	Removed hardcoded templates list (dead code cleanup).
extensions/wp-bones/src/search-documentation.tsx	Switched to useFetch, added empty/error/no-results states, and “Copy URL” action.
extensions/wp-bones/src/release-notes.tsx	New command to fetch and render latest GitHub release notes.
extensions/wp-bones/src/menu-bar.tsx	Fixed state priority chain by using else if to avoid overwrites.
extensions/wp-bones/src/hooks/use-version.ts	Hardened LocalStorage reads/writes; updated version parsing/comparison.
extensions/wp-bones/src/create-wp-bones-template.tsx	Added README preview (⌘P) via GitHub repo + README fetch.
extensions/wp-bones/src/ask-ai.tsx	New “Ask WP Bones AI” command that builds context from docs search + AI streaming.
extensions/wp-bones/package.json	Registered new commands and added platforms metadata.
extensions/wp-bones/README.md	Updated feature list to reflect new commands and preview actions.
extensions/wp-bones/CHANGELOG.md	Added entries for the new features and fixes.

[greptile-apps]

Greptile Summary

This PR hardens several error-prone paths in the WP Bones extension: filesystem failures during LocalStorage reads/writes no longer crash the menu-bar command, a faulty version-storage migration that produced false "new version" banners on every launch is corrected, and both the search list and the AI prompt builder are guarded against malformed documentation API responses.

• use-version.ts replaces useLocalStorage with direct LocalStorage.getItem/setItem calls wrapped in try/catch, and treats any stored value below 1_000_000 as stale to avoid the broken migration multiplier.
• ask-ai.tsx and search-documentation.tsx add Array.isArray(d.items) guards before iteration and expose an explicit error state in the UI when the docs fetch fails.
• create-wp-bones-template.tsx URL-encodes the blueprint parameter before embedding it in the Playground URL.

Confidence Score: 5/5

Safe to merge — all changes are defensive hardening around I/O failures and API response validation, with no new logic paths that could introduce regressions.

The core fixes are straightforward and well-scoped: error boundaries wrap LocalStorage calls, migration logic is simplified to a safe no-op for stale values, and the only structural change (dropping useLocalStorage in favour of direct API calls) is self-contained to use-version.ts. The one open item is the hardcoded date in the changelog, which has no runtime impact.

No files require special attention beyond the minor {PR_MERGE_DATE} placeholder fix in CHANGELOG.md.

Important Files Changed

Filename	Overview
extensions/wp-bones/src/hooks/use-version.ts	Replaces useLocalStorage with direct LocalStorage API calls wrapped in try/catch; fixes migration by treating any stored value below 1_000_000 as stale rather than applying a broken multiplier.
extensions/wp-bones/src/ask-ai.tsx	Adds docsError handling from useFetch, explicit error UI state, and an Array.isArray guard on d.items before flatMap to prevent TypeErrors on malformed API responses.
extensions/wp-bones/src/search-documentation.tsx	Strengthens the Document type guard to also check typeof, null, and Array.isArray(items) before accepting an entry from the API response.
extensions/wp-bones/src/create-wp-bones-template.tsx	Extracts blueprint/playground URLs into named variables and wraps the blueprint URL with encodeURIComponent before embedding it as a query parameter.
extensions/wp-bones/CHANGELOG.md	New [Fixes] entry added at the top; hardcoded date 2026-05-26 is used instead of the {PR_MERGE_DATE} placeholder.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
extensions/wp-bones/CHANGELOG.md:3
The new entry uses a hardcoded date instead of the required `{PR_MERGE_DATE}` placeholder. The placeholder is the standard Raycast convention and is automatically replaced with the actual merge date on publish.

```suggestion
## [Fixes] - {PR_MERGE_DATE}
```

_{Reviews (5): Last reviewed commit: "Update CHANGELOG.md" | Re-trigger Greptile}

[0xdhrv]

Looks good to me, approved ✅

[github-actions]

Published to the Raycast Store:
https://raycast.com/Undolog/wp-bones

[raycastbot]

🎉 🎉 🎉

We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag.