Update teak-raycast extension

[praveenjuge]

Description

Updates the Teak extension to 1.0.70. Search, favorites, and AI tools now use Teak's current card listing API, fixing search and favorites against the latest Teak backend.

• Search, favorites, and AI tools now use Teak's current card listing API
• Fixed search and favorites against the latest Teak backend

Validation

• ray build succeeds (14 entry points compile, TS defs generated).
• ray lint clean (package.json, package-lock.json, icons, metadata, ESLint, Prettier).
• 64 unit tests pass (bun test), including exact request-URL assertions for the new transport.
• Live round-trip of the shipped client code (create/search/favorite/favorites/get/update/tags/delete) against a dev backend: pass, with zero calls to retired endpoints.
• No command, view, preference, or asset changes in this update.

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and verified the distribution build (build + lint + unit tests + live API round-trip of the shipped client)
• 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 15 business days.

[greptile-apps]

Greptile Summary

Teak's Raycast extension now uses the current card API for search, favorites, and AI tools, while its local development and sign-out flows match the newer backend. The PR also updates extension metadata and removes an unrelated MarkMarks parser change.

• Search and favorites use the shared paged card listing API.
• Development and production requests use the current Teak backend URLs.
• Sign-out revokes credentials before clearing the local session.
• Save actions preserve the user's original text.
• Documentation and dependency metadata are updated for version 1.0.70.

Confidence Score: 4/5

The code changes look safe, but the changelog rule must be fixed before merge.

The current card API and sign-out changes are covered by focused tests. The new changelog title uses a fixed date instead of the required merge-date placeholder.

Files Needing Attention: extensions/teak-raycast/CHANGELOG.md

Important Files Changed

Filename	Overview
extensions/teak-raycast/CHANGELOG.md	The new entry describes the update, but its title replaces the required {PR_MERGE_DATE} placeholder with a fixed date.
extensions/teak-raycast/package.json	The manifest updates the extension and dependency versions. It now includes the required $schema field.
extensions/teak-raycast/src/lib/api.ts	Card search and favorites now call the current /cards listing route and ask for full card fields.
extensions/teak-raycast/src/lib/oauth.ts	Sign-out now revokes the stored session before deleting local tokens and guards against sign-in races.

Prompt To Fix All With AI

### Issue 1
extensions/teak-raycast/CHANGELOG.md:3
This must stay as `{PR_MERGE_DATE}`. Raycast fills that value when the PR merges, so replace the fixed date with the placeholder.

```suggestion
## [Reliable search and favorites] - {PR_MERGE_DATE}
```

---

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

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

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​types/​node@​26.6.1

View full report

[pernielsentikaer]

Looks good to me, approved 🔥

[github-actions]

Published to the Raycast Store:
https://raycast.com/praveenjuge/teak-raycast

[raycastbot]

🎉 🎉 🎉

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

[greptile-apps]

This must stay as {PR_MERGE_DATE}. Raycast fills that value when the PR merges, so replace the fixed date with the placeholder.

Suggested change

	## [Reliable search and favorites] - 2026-09-16
	## [Reliable search and favorites] - {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/teak-raycast/CHANGELOG.md
Line: 3

Comment:
This must stay as `{PR_MERGE_DATE}`. Raycast fills that value when the PR merges, so replace the fixed date with the placeholder.

```suggestion
## [Reliable search and favorites] - {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.

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!