Fix Obsidian plugin checks for inaccessible config files

[raulkolaric]

Description

This PR attempts to address #30308.

The Obsidian plugin readers call fs.readFileSync for each vault configuration. When macOS returned EPERM for an iCloud-hosted vault, that exception escaped during the shared plugin check and aborted the Daily Note command's render.

The shared plugin check now catches read failures for both community-plugins.json and core-plugins.json, logs them, and reports the vault as unavailable for the current render instead of crashing. It also marks that result as non-cacheable, so restoring filesystem access can be observed on the next check rather than leaving a transient failure in the process-wide cache. Successful reads, missing files, and malformed configuration keep their previous cache behavior.

The regression tests simulate EPERM for both files and verify that those results are not cacheable. I also added raulkolaric to the extension's contributor list.

Validation:

• npm test — 328 tests passed
• npm run lint
• npm run build

Fixes #30308

Screencast

Not included; this is a filesystem error path covered by unit tests.

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

🔔 @marcjulianschwarz @KevinBatdorf @iancanderson @pernielsentikaer @ofalvai @AdamAdamsMusic @FServais @rakoort @MuuNU @theherk @vicampuzano @ErBlack @byheaven @tofrankie @alexibuild @RLuf 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="codex/obsidian-plugin-file-permissions"
FORK_URL="https://github.com/raulkolaric/extensions.git"
EXTENSION_NAME="obsidian"
REPO_NAME="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 catches inaccessible Obsidian plugin configuration reads and prevents transient failures from entering the process-wide plugin-check cache.

• Adds a cacheability flag to plugin-check results.
• Handles community and core plugin read failures without aborting command rendering.
• Adds regression coverage for permission failures and updates contributor metadata.

Confidence Score: 4/5

The PR is not yet safe to merge because restored filesystem access remains unobserved while a plugin-checking component stays mounted.

The process-wide cache no longer stores transient failures, but useMemo still retains the negative result with unchanged vault and plugin dependencies, leaving long-lived plugin-dependent UI unavailable after access is restored.

Files Needing Attention: extensions/obsidian/src/utils/hooks.ts

Important Files Changed

Filename	Overview
extensions/obsidian/src/obsidian/internal/plugins.ts	Converts plugin-check results to a structured shape and marks filesystem read failures as non-cacheable.
extensions/obsidian/src/utils/hooks.ts	Skips the process-wide cache for transient failures, but the surrounding React memo still retains the failed result for the mounted component.
extensions/obsidian/src/tests/plugins.spec.ts	Adds direct regression tests confirming that community and core configuration read failures produce non-cacheable results.
extensions/obsidian/package.json	Adds the PR author to the extension contributor list.
extensions/obsidian/CHANGELOG.md	Adds a user-facing release note for inaccessible plugin configuration handling.

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

[pernielsentikaer]

Hey @raulkolaric — nice catch on the iCloud EPERM crash. Daily Note (and the other plugin-gated commands) no longer blow up when community-plugins.json / core-plugins.json cannot be read, and skipping the process-wide cache on those failures is the right call so a later run can see the vault again. The community/core tests and {PR_MERGE_DATE} changelog look solid. Thanks for the quick follow-up on Greptile’s first pass as well.

[github-actions]

Published to the Raycast Store:
https://raycast.com/marcjulian/obsidian

[raycastbot]

🎉 🎉 🎉

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