1.0.1

Fixed

• A corrupt or hand-edited data.json no longer stops the plugin from loading. Feed entries that are not usable (missing required fields or wrong types) are dropped on load instead of throwing during startup.
• The marketplace scorecard no longer flags the plugin's use of String.matchAll, String.trimStart/trimEnd as untyped. The declared TypeScript lib stopped at ES2018 while the code uses these ES2019/ES2020 methods, so the developer-dashboard scan, which type-checks without the plugin's development dependencies, saw them as any and reported no-unsafe warnings. The lib now includes ES2019 and ES2020, and a tsconfig.scan.json guard wired into npm run lint reproduces the scan's stricter view so the gap cannot recur. No runtime change: these methods already run on every supported Obsidian version.