Format entire repo with Prettier

.claude/skills/verify/SKILL.md

@@ -13,7 +13,7 @@ the script lives outside the repo).
 ## Launch
 
 - Chromium needs `headless: false` plus args `--no-sandbox
-  --disable-setuid-sandbox --headless=old`. This is not a contradiction:
+--disable-setuid-sandbox --headless=old`. This is not a contradiction:
   `headless: false` stops Playwright adding its own headless flags (its
   headless mode uses the new headless shell, which drops WebGL), and
   `--headless=old` then puts Chromium itself in legacy headless mode,
@@ -53,8 +53,10 @@ the script lives outside the repo).
 flock.js listens on the top document. Stub and dispatch:
 
 ```js
-Object.defineProperty(document, "visibilityState",
-  { configurable: true, get: () => document.__fakeVis || "visible" });
-document.__fakeVis = "hidden"; // or "visible"
-document.dispatchEvent(new Event("visibilitychange"));
+Object.defineProperty(document, 'visibilityState', {
+  configurable: true,
+  get: () => document.__fakeVis || 'visible',
+});
+document.__fakeVis = 'hidden'; // or "visible"
+document.dispatchEvent(new Event('visibilitychange'));
 ```

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,9 +1,9 @@
 ---
 name: Bug report
 about: Create a report to help us improve
-title: ""
+title: ''
 labels: bug
-assignees: ""
+assignees: ''
 ---
 
 **Describe the bug**

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,9 +1,9 @@
 ---
 name: Feature request
 about: Suggest an idea for this project
-title: ""
+title: ''
 labels: enhancement
-assignees: ""
+assignees: ''
 ---
 
 **Is your feature request related to a problem? Please describe.**

.github/workflows/run-mocha-tests.yml

@@ -5,9 +5,9 @@ name: Run mocha tests
 
 on:
   push:
-    branches: ["testable"]
+    branches: ['testable']
   pull_request:
-    branches: ["testable"]
+    branches: ['testable']
 
 jobs:
   build:
@@ -28,7 +28,7 @@ jobs:
         uses: actions/setup-node@v5
         with:
           node-version: ${{ matrix.node-version }}
-          cache: "npm"
+          cache: 'npm'
       - run: npm ci
       - name: Get installed Playwright version
         id: playwright-version

.github/workflows/static.yml

@@ -3,7 +3,7 @@ name: Vite Github Pages Deploy
 on:
   # Runs on pushes targeting the default branch
   push:
-    branches: ["master", "main"]
+    branches: ['master', 'main']
   # Allows you to run this workflow manually from the Actions tab
   workflow_dispatch:
 
@@ -14,11 +14,11 @@ permissions:
   id-token: write
 
 concurrency:
-  group: "pages"
+  group: 'pages'
   cancel-in-progress: false
 
 env:
-  VITE_BASE_URL: "/${{ github.event.repository.name }}/"
+  VITE_BASE_URL: '/${{ github.event.repository.name }}/'
 
 jobs:
   # Build job

AGENTS.md

@@ -14,6 +14,7 @@
 - Review code for unnecessary complexity
 
 ## Style
+
 - Match the existing style
 - Comments should be infrequent
 - Comments should be genuinely noteworthy
@@ -27,4 +28,3 @@
 - If user verification is needed, describe the test to be carried out and request confirmation
 - Don't introduce security issues
 - Don't introduce changes that would break offline PWA behaviour
-

AI_POLICY.md

@@ -4,15 +4,15 @@ AI is a tool to support human creativity and responsibility, not replace it.
 
 ## Our overall goals are:
 
-- Open source principles  
-- Efficiency, particularly when funded with public money and adding accessibility features  
-- Quality and maintainability of code  
-- Consider workload on maintainers and contributors and avoiding barriers to contribution  
-- Humans are responsible for code and other assets, AI is a tool  
+- Open source principles
+- Efficiency, particularly when funded with public money and adding accessibility features
+- Quality and maintainability of code
+- Consider workload on maintainers and contributors and avoiding barriers to contribution
+- Humans are responsible for code and other assets, AI is a tool
 
 ## Contribution expectations
 
-The world has changed. We believe that open source projects need to be able to benefit from generative AI tools that have largely been trained on open source content. We need to do this in a way that is aligned with the goals of the project. 
+The world has changed. We believe that open source projects need to be able to benefit from generative AI tools that have largely been trained on open source content. We need to do this in a way that is aligned with the goals of the project.
 
 At this point we are not able to accept large contributions from fully automated contributors or contributors who are not known to the project.
 
@@ -54,4 +54,4 @@ We recognise that some potential contributors may wish to write code completely
 
 This policy will be reviewed regularly as the generative AI landscape changes.
 
-This policy is influenced by [NLnet Generative AI Policy](https://nlnet.nl/foundation/policies/generativeAI/) (we’re grateful that they listened to feedback as the open source community navigates this unprecedented change in how we develop software), the measured policy from [Apache Generative Tooling Guidelines](https://www.apache.org/legal/generative-tooling.html), and the ideas around community and human maintainers from [Ghostty AI Policy](https://github.com/ghostty-org/ghostty/blob/main/AI_POLICY.md).
+This policy is influenced by [NLnet Generative AI Policy](https://nlnet.nl/foundation/policies/generativeAI/) (we’re grateful that they listened to feedback as the open source community navigates this unprecedented change in how we develop software), the measured policy from [Apache Generative Tooling Guidelines](https://www.apache.org/legal/generative-tooling.html), and the ideas around community and human maintainers from [Ghostty AI Policy](https://github.com/ghostty-org/ghostty/blob/main/AI_POLICY.md).