[Super Productivity] require access token

[xmok]

Description

• Extension now requires API Token to use the local API (close [Super Productivity] Extension missing Authorization header — Local REST API token not sent #30157)

Screencast

super-productivity-260812.mp4

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

🔔 @pvnkmnk 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.

📋 Quick checkout commands

BRANCH="ext/super-productivity"
FORK_URL="https://github.com/xmok/raycast-extensions.git"
EXTENSION_NAME="super-productivity"
REPO_NAME="raycast-extensions"

git clone -n --depth=1 --filter=tree:0 -b $BRANCH $FORK_URL
cd $REPO_NAME
git sparse-checkout set --no-cone "extensions/$EXTENSION_NAME"
git checkout
cd "extensions/$EXTENSION_NAME"
npm install && npm run dev

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

The PR requires a Super Productivity local API access token and attaches it to API requests as a Bearer credential.

• Adds a required password preference and setup documentation.
• Adds the authorization header and updates API test preferences.
• Records the change in the extension changelog.

Confidence Score: 5/5

The PR appears safe to merge because no blocking failure remains.

No blocking failure remains.

Important Files Changed

Filename	Overview
extensions/super-productivity/src/api.ts	Reads the required token preference and includes it as a Bearer credential on local API requests.
extensions/super-productivity/src/api.test.ts	Updates the shared preference mock with an access-token value.
extensions/super-productivity/package.json	Adds the required password preference and records the new contributor.
extensions/super-productivity/README.md	Documents that users must obtain and enter the local REST API access token.
extensions/super-productivity/CHANGELOG.md	Adds a correctly positioned release entry for the token requirement.

_{Reviews (2): Last reviewed commit: "[Super Productivity] accessToken in test" | Re-trigger Greptile}

[greptile-apps]

Authentication header lacks test coverage

Every API operation now depends on the exact Authorization header, but the current preference mock supplies no accessToken and the fetch assertions accept any options object. An incorrect token value, header name, or authorization scheme can therefore pass CI while leaving every command unable to authenticate.

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/super-productivity/src/api.ts
Line: 31

Comment:
**Authentication header lacks test coverage**

Every API operation now depends on the exact `Authorization` header, but the current preference mock supplies no `accessToken` and the fetch assertions accept any options object. An incorrect token value, header name, or authorization scheme can therefore pass CI while leaving every command unable to authenticate.

---

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!