deprecate storytime

[andreaselia]

Description

Screencast

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 in the README are located outside the metadata folder if they were not generated with our metadata tool

[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 15 business days.

[greptile-apps]

Confidence Score: 4/5

[Medium impact] Replaces story generation feature with deprecation notice.

Remove the required OpenAI key and use the required changelog date placeholder before merging.

Findings

1.  Removal notice requires a key ▶
2.  Changelog date is hardcoded ▶

Fix with agent prompt

### Issue 1
extensions/storytime/src/index.tsx:5-9
The new notice still sits behind the required `openai_api_key` preference in `package.json`. Users without a saved key must enter one before Raycast opens the command, even though it no longer uses OpenAI. Remove the required preference so these users can see the deprecation notice without supplying an unused secret.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

### Issue 2
extensions/storytime/CHANGELOG.md:3
The new changelog heading uses `2026-10-12`, but the repository requires new changelog titles to use `{PR_MERGE_DATE}` so the release can insert the actual merge date. Replace the date with that placeholder before merging to satisfy the repository requirement.

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

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

StoryTime replaces story generation with a removal notice and adds a changelog entry.

• StoryTime opens with a notice that it is being removed.

_{Reviews (1) · Last reviewed commit: "deprecate storytime" · Reviewed by Greptile}

[greptile-apps]

Removal notice requires a key

The new notice still sits behind the required openai_api_key preference in package.json. Users without a saved key must enter one before Raycast opens the command, even though it no longer uses OpenAI. Remove the required preference so these users can see the deprecation notice without supplying an unused secret.

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/storytime/src/index.tsx
Line: 5-9

Comment:
**Removal notice requires a key**

The new notice still sits behind the required `openai_api_key` preference in `package.json`. Users without a saved key must enter one before Raycast opens the command, even though it no longer uses OpenAI. Remove the required preference so these users can see the deprecation notice without supplying an unused secret.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Changelog date is hardcoded

The new changelog heading uses 2026-10-12, but the repository requires new changelog titles to use {PR_MERGE_DATE} so the release can insert the actual merge date. Replace the date with that placeholder before merging to satisfy the repository requirement.

Suggested change

	## [Deprecated] - 2026-10-12
	## [Deprecated] - {PR_MERGE_DATE}

Rule Used: What: Changelog entries must use {PR_MERGE_DATE} placeholder in titles, be placed at the top of the file, and maintain descending version order. Why: Standardized placeholders and consistent ordering ensure changelogs are maintainable and merge da... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/storytime/CHANGELOG.md
Line: 3

Comment:
**Changelog date is hardcoded**

The new changelog heading uses `2026-10-12`, but the repository requires new changelog titles to use `{PR_MERGE_DATE}` so the release can insert the actual merge date. Replace the date with that placeholder before merging to satisfy the repository requirement.

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

**Rule Used:** What: Changelog entries must use `{PR_MERGE_DATE}` placeholder in titles, be placed at the top of the file, and maintain descending version order.  Why: Standardized placeholders and consistent ordering ensure changelogs are maintainable and merge da... ([source](https://app.greptile.com/raycast/-/custom-context?memory=c2214c11-df56-490a-b1c0-09a385df481a))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[github-actions]

Published to the Raycast Store:
https://raycast.com/andreaselia/storytime

[raycastbot]

🎉 🎉 🎉

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