chore(deps): WIP upgrade dependencies (issue #45)

Author: sm17p

.changeset/config.json

@@ -1,11 +1,11 @@
 {
-	"$schema": "https://unpkg.com/@changesets/config@3.1.1/schema.json",
-	"changelog": "@changesets/cli/changelog",
-	"commit": false,
-	"fixed": [],
-	"linked": [],
-	"access": "restricted",
-	"baseBranch": "main",
-	"updateInternalDependencies": "patch",
-	"ignore": []
+  "$schema": "https://unpkg.com/@changesets/config@3.1.1/schema.json",
+  "changelog": "@changesets/cli/changelog",
+  "commit": false,
+  "fixed": [],
+  "linked": [],
+  "access": "restricted",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "ignore": []
 }

.cursor/rules/skill-maintenance.mdc

@@ -0,0 +1,19 @@
+---
+description: When changing deps, scripts, e2e, release, or issue format, update the matching project skills and note it in the response
+alwaysApply: true
+---
+
+# Skill maintenance
+
+When you change any of the following, update the corresponding skill(s) in `.cursor/skills/` and briefly mention in your response that skills were updated.
+
+| Change | Update these skills |
+|--------|----------------------|
+| Key dependencies (WXT, Svelte, Playwright, changesets, oxlint, dprint) or build/config (wxt.config.ts, .oxlintrc.json) | wxt-svelte-extension (SKILL.md; reference.md if a new known issue) |
+| package.json scripts (dev/build/zip) or new build targets | wxt-svelte-extension, releases-changesets if release steps change |
+| E2E layout (e2e/tests, e2e/pages, fixture file path or name) | e2e-playwright-extension |
+| Release workflow (.changeset/, release steps, workflow_dispatch) | releases-changesets |
+| Issue refinement format or label set (docs/ISSUE_REFINEMENTS.md) | issue-refinement-triage |
+| New recurring “known issue” that should guide extension code | wxt-svelte-extension/reference.md |
+
+Read the current skill file before editing so the update stays consistent with existing structure and wording.

.cursor/skills/e2e-playwright-extension/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: e2e-playwright-extension
+description: Adds or updates extension E2E tests using the project Playwright setup and fixture (load unpacked extension, popup/background). Use when adding e2e for a feature, fixing failing e2e, or when changing popup/options/background flows.
+---
+
+# E2E with Playwright (extension)
+
+## Layout
+
+- Tests in [e2e/tests/](e2e/tests/)
+- Shared fixture in [e2e/fixutes.ts](e2e/fixutes.ts) (note: filename typo in repo)
+- Page helpers in [e2e/pages/](e2e/pages/) (e.g. [e2e/pages/popup.ts](e2e/pages/popup.ts))
+
+## Fixture
+
+The fixture extends Playwright with:
+
+- **context:** Firefox persistent context that loads the unpacked extension from `dist/firefox-mv3`
+- **extensionId:** Resolved from the service worker (MV3) or background page otherwise
+
+Use `context` and `extensionId` in tests. Import the extended `test` and `expect` from the fixture.
+
+## Popup
+
+Navigate to `chrome-extension://${extensionId}/popup.html`. Use helpers like `openPopup(page, extensionId)` from [e2e/pages/popup.ts](e2e/pages/popup.ts) for consistent setup.
+
+## Run
+
+- `pnpm test:e2e`
+- Build the extension first so `dist/` exists: `pnpm build:firefox` or `pnpm build`
+
+## Note
+
+`playwright-webextext` is in devDependencies for potential future use; current tests use the custom fixture in `fixutes.ts`.

.cursor/skills/issue-refinement-triage/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: issue-refinement-triage
+description: Refines GitHub issues into the ISSUE_REFINEMENTS format and keeps docs/ISSUE_REFINEMENTS.md in sync. Use when triaging issues, refining a new issue, updating the refinements doc, or when the user asks to refine an issue or add to refinements.
+---
+
+# Issue Refinement and Triage
+
+## Canonical source
+
+Read [docs/ISSUE_REFINEMENTS.md](docs/ISSUE_REFINEMENTS.md) for the current open/closed list and label table before editing.
+
+## Issue block template
+
+Each refined issue uses this format. Separate blocks with `---`.
+
+```markdown
+### #N — Title
+
+**Labels:** `label1` `label2`
+**Context:** Raw description or user report.
+**Refined:** One-line actionable scope or decision.
+**My comments:** _(add notes here)_
+```
+
+## Labels (only these)
+
+| Label              | Use for                                |
+| ------------------ | -------------------------------------- |
+| `bug`              | Something broken or incorrect behavior |
+| `documentation`    | Docs, README, FAQ, browser support     |
+| `enhancement`      | New feature or improvement             |
+| `good first issue` | Clear, scoped tasks for contributors   |
+| `question`         | Open questions, naming, investigation  |
+| `UI/UX`            | User-facing behavior, flows, layout    |
+| `Brainstorm`       | Ideas, naming, long-running discussion |
+| `infrastructure`   | CI/CD, release, monitoring, tooling    |
+
+Suggest only these labels; use space-separated list in the block.
+
+## Workflow
+
+1. **New or raw issue:** Propose labels (from the table) and a one-line **Refined** that scopes or clarifies the issue.
+2. **Updating ISSUE_REFINEMENTS:** Add new refined issues under "Open issues (refined)". When an issue is closed, move its block to "Closed issues (reference)" and keep the same format.
+3. **My comments:** Reserved for maintainer notes (priority, blockers, batching). Leave as `*(add notes here)*` if no note.

.cursor/skills/jj-bookmark-push/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: jj-bookmark-push
+description: Uses jj (Jujutsu VCS) to create or update bookmarks and push to the Git remote. Use when creating a branch/bookmark, moving a bookmark to the current revision, or pushing changes with jj instead of git.
+---
+
+# jj bookmark and push
+
+Use jj for version control in this project (not git) when creating branches, updating bookmarks, or pushing.
+
+## Create or update a bookmark
+
+Bookmarks are named pointers (like Git branches). Set or move a bookmark to the current revision:
+
+```bash
+jj bookmark set <name>
+```
+
+Set to a specific revision:
+
+```bash
+jj bookmark set <name> -r <rev>
+```
+
+Short form: `jj b s <name>`. Use `-B`/`--allow-backwards` to move a bookmark backwards. New commits do not move bookmarks automatically; set the bookmark after committing if you want it to point at the new commit.
+
+## Push to remote
+
+Push one bookmark (maps to same-named Git branch on remote):
+
+```bash
+jj git push -b <name>
+```
+
+Push all bookmarks: `jj git push --all`. Push only tracked: `jj git push --tracked`. Specify remote: `jj git push --remote <remote>` (default is origin).
+
+Push performs safety checks (similar to `git push --force-with-lease`). If the remote bookmark moved, run `jj git fetch` and resolve any bookmark conflict, then push again.
+
+## Quick workflow
+
+1. Make changes; commit with `jj commit` / `jj new` etc.
+2. `jj bookmark set <branch-name>` so the bookmark points at the revision to publish.
+3. `jj git push -b <branch-name>`.
+
+List bookmarks: `jj bookmark list` or `jj b l`. List with remotes: `jj bookmark list --all`.

.cursor/skills/releases-changesets/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: releases-changesets
+description: Uses changesets for versioning and changelog; avoids manual version bumps; aligns with build/zip and workflow_dispatch. Use when cutting a release, adding a changeset, preparing for publish, or when touching version or changelog.
+---
+
+# Releases and Versioning (changesets)
+
+## Rule
+
+All user-facing or notable changes get a changeset in [.changeset/](.changeset/). Do not edit `package.json` version manually for releases.
+
+## Adding a changeset
+
+- Run `pnpm changeset`, or add a new `.md` file in `.changeset/` with the standard format: semver type (major/minor/patch) and a short summary for the changelog.
+
+## Config
+
+[.changeset/config.json](.changeset/config.json): `changelog: "@changesets/cli/changelog"`, `commit: false`, `baseBranch: "main"`.
+
+## Release steps
+
+1. Build both targets: `pnpm build:all`
+2. Create zips: `pnpm zip:all`
+3. workflow_dispatch (e.g. issue #27) is the intended automation when available; document in README when in place.

.cursor/skills/skill-hygiene/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: skill-hygiene
+description: Checklist for updating project skills when the codebase or workflow changes. Use when applying the skill-maintenance rule, after dependency upgrades or script/e2e/release/issue-format changes, or when the user asks how to keep skills up to date.
+---
+
+# Skill hygiene
+
+When updating a skill (see `.cursor/rules/skill-maintenance.mdc` for when to do so), read the current skill file first and then apply the checks below for the relevant skill(s).
+
+## issue-refinement-triage
+
+- Issue block template still matches `docs/ISSUE_REFINEMENTS.md`.
+- Label table matches the "Label usage summary" in ISSUE_REFINEMENTS (same labels and "Use for" text).
+- Workflow steps still reflect how open/closed issues and "My comments" are used.
+
+## wxt-svelte-extension
+
+- **Stack:** Entrypoints, config path, srcDir/outDir match current layout.
+- **Scripts table:** Commands and purpose match `package.json` (dev, build, zip; Chrome vs Firefox).
+- **Constraints:** No new dev data, storage prefix, shadow DOM isolation still accurate; wording matches current issues if referenced.
+- **reference.md:** Known-issues list (e.g. #36, #17, #25) is current; add new recurring issues that should guide code, remove or note when an issue is closed.
+
+## releases-changesets
+
+- Rule and "Add a changeset" steps match `.changeset/config.json` and how the repo uses changesets.
+- Release steps (build:all, zip:all, workflow_dispatch) match current process; update when CI or release automation changes.
+
+## e2e-playwright-extension
+
+- **Layout:** Paths (e2e/tests, e2e/pages, fixture file) match repo; fix fixture filename in skill if the typo is ever fixed in repo.
+- **Fixture:** context/extensionId and MV3 vs background page still match [e2e/fixutes.ts](e2e/fixutes.ts).
+- **Run:** `pnpm test:e2e` and build-before-test still correct.
+
+## After editing
+
+- Keep SKILL.md under 500 lines; move long detail to reference.md if needed.
+- Descriptions (frontmatter) stay third-person and include WHAT and WHEN.
+- Links stay one level deep (no deep nesting from SKILL.md).

.cursor/skills/wxt-svelte-extension/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: wxt-svelte-extension
+description: Provides project context for the amgiflol WXT + Svelte 5 browser extension. Use when adding or editing extension code, adding entrypoints, fixing extension bugs, or when working in src/entrypoints or wxt.config.ts.
+---
+
+# WXT + Svelte Extension (amgiflol)
+
+## Stack
+
+- WXT, Svelte 5 (runes), UnoCSS
+- Entrypoints in [src/entrypoints/](src/entrypoints/) (e.g. background.ts, content.ts)
+- Config in [wxt.config.ts](wxt.config.ts); srcDir `src`, outDir `dist`
+
+## Scripts
+
+| Command                     | Purpose                  |
+| --------------------------- | ------------------------ |
+| `pnpm dev`                  | Chrome dev (MV3)         |
+| `pnpm dev:firefox`          | Firefox dev (MV2 in dev) |
+| `pnpm build`                | Chrome build (MV3)       |
+| `pnpm build:firefox`        | Firefox build (MV3)      |
+| `pnpm build:all`            | Both targets             |
+| `pnpm zip` / `pnpm zip:all` | Distribution zips        |
+
+## Constraints
+
+- Do not create new data in dev; it breaks seeding.
+- Storage keys: use a fixed prefix (e.g. `amgiflol_`) for all extension storage to avoid collisions with host page (see [reference.md](reference.md)).
+- Extension UI in shadow DOM: isolate from host page styles (e.g. WXT ShadowRootContentScriptUiOptions) so host root font/CSS vars do not affect the UI.
+
+## Lint and format
+
+- `pnpm lint` (oxlint); import order and sort-imports per [.oxlintrc.json](.oxlintrc.json)
+- `pnpm fmt` (oxfmt); `pnpm fmt:check` to check only
+
+## Additional context
+
+For known issues and when to apply them (storage prefix, shadow root isolation, Firefox quirks), see [reference.md](reference.md).

.cursor/skills/wxt-svelte-extension/reference.md

@@ -0,0 +1,7 @@
+# Known issues (reference)
+
+When touching related code, consider these tracked issues:
+
+- **#36 — Prefix local storage keys:** Use a fixed prefix (e.g. `amgiflol_`) for all extension storage keys to avoid collisions with host page storage.
+- **#17 — Shadow root UI isolation:** Host page root font size / CSS vars can affect extension shadow root UI. Use WXT ShadowRootContentScriptUiOptions (e.g. inheritStyles) or isolate so extension UI is not affected by site globals.
+- **#25 — Style tags removed on firefox.com:** Firefox-specific behavior on some sites; shadow root styles removed. Reproduce and narrow (extension injection vs site CSP vs browser quirk) before changing code.

.oxfmtrc.json

@@ -0,0 +1,32 @@
+{
+  "$schema": "./node_modules/oxfmt/configuration_schema.json",
+  "printWidth": 80,
+  "useTabs": true,
+  "tabWidth": 4,
+  "semi": true,
+  "singleQuote": false,
+  "trailingComma": "all",
+  "ignorePatterns": [
+    "**/node_modules/**",
+    "**/*-lock.yaml",
+    "**/*-workspace.yaml",
+    "dist/**",
+    ".wxt/**",
+    ".vscode/**"
+  ],
+  "overrides": [
+    {
+      "files": ["*.json", "*.jsonc"],
+      "options": {
+        "useTabs": false,
+        "tabWidth": 2
+      }
+    },
+    {
+      "files": ["*.md", "*.yml", "*.yaml"],
+      "options": {
+        "tabWidth": 2
+      }
+    }
+  ]
+}