Update supernotes extension to enable AI tools

[mattdelliott]

Description

• Enables AI Extension and allows for searching for cards, append to an existing card, or creating a new card.

Screencast

https://cln.sh/FRWgv49yw1XjNh0PX0KN

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 your first contribution! 🎉

🔔 @acnebs @tobeagram @peduarte you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

Due to our current reduced availability, the initial review may take up to 10-15 business days

[connebs]

Hey @mattdelliott, thanks for this. We were just discussing integrating the new Raycast AI features with the Supernotes extension, looks like you've beat us to it!

The only issue is that the date formatting feature unfortunately cannot work as written, as only a certain date format (ISO 8601 without a time) is accepted as the local_date property in the daily append endpoint. The good news is that we are actually already in the process of adding a standardized date format option to Supernotes itself, which will be coming in our next release.

However this would be a good time to better standardize that call so that it matches other integrations, which use two digits for month and day (this was actually an oversight when we first added local_date to the Raycast extension). So if you could remove the date formatting option feature, but leave in the formatting call with a strict date like below, that would be great.

const localDate = format(new Date(), "yyyy-MM-dd")

[mattdelliott]

Hey @connebs! That is great to hear. I removed that option and hardcoded the yyyy-MM-dd format. I could remove the date-fns dependency and just use padStart on the original way it was written if you want. Let me know if you would prefer for me to do that.

As far as the AI Extension goes, I just got some basics to get started, but I am sure there will be a lot more awesome use cases to implement.

[connebs]

Good point, I think for now padStart would be better since we are otherwise not using other features of date-fns

[mattdelliott]

Sounds good. I've made those changes.

[greptile-apps]

PR Summary

This PR adds AI Extension support to Supernotes, enabling interaction with the note-taking app through Raycast's AI interface.

• Added three new AI tools in /extensions/supernotes/src/tools/: search-cards.ts, append-card.ts, and create-card.ts for searching, appending to, and creating cards
• Added AI configuration in package.json with instructions and example inputs for handling markdown formatting and daily cards
• Fixed date formatting in sendToDaily function to properly zero-pad month and day values for consistent ISO-8601 format
• Updated documentation in README.md with a new "Tools" section describing the AI capabilities
• Added proper changelog entry with the {PR_MERGE_DATE} placeholder at the top of CHANGELOG.md

_{💡 (1/5) You can manually trigger the bot by mentioning @greptileai in a comment!}

_{7 file(s) reviewed, 4 comment(s)
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

logic: The JSDoc comment says "If not provided then ask for it" but the content field is not marked as optional in the type definition. Either make it optional with content?: string or update the comment.

Suggested change

	* The content markup to append to the card. If not provided then ask for it.
	*/
	content: string;
	* The content markup to append to the card. If not provided then ask for it.
	*/
	content?: string;

[greptile-apps]

syntax: Minor typo in comment: 'a cards' should be 'cards'

Suggested change

	* The search term to search for when looking for a cards, optional
	* The search term to search for when looking for cards, optional

[greptile-apps]

style: Consider making the limit configurable through the Input type to allow for more flexible searches

[greptile-apps]

style: Error handling could be improved by including the error details from fetched.body in the thrown error message