[talakbairam]

What

Two new editor-tab pages and a folder move for the webview pages:

• Settings page (NoteRoot: Open Settings Page, pencil button in the Settings view): every setting in one tab, grouped, with search, an Only changed filter, defaults, origin (this folder / your settings), Reset and an editor for each kind (select, checkbox, text, number, list, Change… button).
• Tags & Categories page (NoteRoot: Open Tags & Categories Page, pencil button in the Tags & Categories view): categories, every-file categories, tags with their notes, tag patterns and the two automatic switches, with the same actions as the view.
• The pages of the webviews moved from media/ to a new top-level webview/ folder (quickNote/, settingsPage/, labelsPage/); media/ keeps the icons and the walkthrough. .vscodeignore ships webview/**.

Why

The Settings view and the Tags & Categories view only show one value or one row at a time and edit through popups. A page lets the user review everything at once and edit it in place. Webview pages are code, so they no longer sit in media/.

Testing

npm run format, npm run lint and npm run compile finish with no errors or warnings, and npx vsce ls lists the six files of webview/. I could not start the Extension Development Host (F5) from here, so neither page nor the Quick Note from its new folder has been seen running. New checklist items are in MANUAL-TESTING.md (Settings panel, Tags & Categories page).

Impact

• No setting, command id or stored data format changes; two new commands (noteRoot.openSettingsPage, noteRoot.openLabelsPage).
• Both pages write only through the existing code: applySettingEdit / resetSetting (same validation as the Settings view) and performLabelAction plus the tag pattern commands (same questions as the view). The webview messages are validated; notes and files are named by id or by a path from the model, never by a path from the page.
• editTagPattern and deleteTagPattern now also accept the pattern as text; LabelsTreeProvider exposes tagNotes() and patternMatches() (the kept scan).

Notes

• CHANGELOG.md is intentionally not updated in this PR.
• The four files .claude/rules/code-styles.md, .vscodeignore, CLAUDE.md and MANUAL-TESTING.md were LF in the working copy and are now CRLF (the repo has eol=crlf); the index is unchanged.

Checklist

• npm run format, npm run lint and npm run compile finish with no errors or warnings
• I tried it in the Extension Development Host (F5), or I say above what I could not try (not tried, said above)
• README.md, CHANGELOG.md and CLAUDE.md are updated if behaviour changed (README and CLAUDE.md yes, CHANGELOG not on purpose)
• No note contents, keys or paths outside the notes folder are logged or written