Block-based editing: selection, drag-and-drop, and actions menu

.claude/skills/mass-bug-fixing/SKILL.md

@@ -3,7 +3,8 @@ name: mass-bug-fixing
 description: |
   Process multiple bugs from a Fizzy board (or GitHub issues) in parallel.
   Uses worktree agents to reproduce, fix, test, create PRs, and comment on cards.
-invocation: user
+invocation: auto_and_user
+auto_trigger: when the user asks to fix more than one bug at a time (e.g., provides multiple bug URLs, card numbers, or issue references)
 user_invocation: /mass-bug-fixing
 ---
 

.github/workflows/benchmarks.yml

@@ -28,7 +28,7 @@ jobs:
       - name: Set up Node.js
         uses: actions/setup-node@53b83947a5a98c8d113130e565377fae1a50d02f # v6.3.0
         with:
-          node-version: "20"
+          node-version: "22"
           cache: "yarn"
 
       - name: Install JavaScript dependencies

.github/workflows/ci.yml

@@ -20,15 +20,15 @@ jobs:
           persist-credentials: false
 
       - name: Set up Ruby
-        uses: ruby/setup-ruby@319994f95fa847cf3fb3cd3dbe89f6dcde9f178f # v1.295.0
+        uses: ruby/setup-ruby@3ff19f5e2baf30647122352b96108b1fbe250c64 # v1.299.0
         with:
           ruby-version: .ruby-version
           bundler-cache: true
 
       - name: Set up Node.js
         uses: actions/setup-node@53b83947a5a98c8d113130e565377fae1a50d02f # v6.3.0
         with:
-          node-version: '20'
+          node-version: '22'
           cache: 'yarn'
 
       - name: Install JavaScript dependencies
@@ -73,7 +73,7 @@ jobs:
       - name: Set up Node.js
         uses: actions/setup-node@53b83947a5a98c8d113130e565377fae1a50d02f # v6.3.0
         with:
-          node-version: '20'
+          node-version: '22'
           cache: 'yarn'
 
       - name: Install JavaScript dependencies
@@ -87,6 +87,19 @@ jobs:
     runs-on: ubuntu-latest
     permissions:
       contents: read
+
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - name: "Rails 8.1 (no adapter)"
+            use_legacy_rails: "true"
+          - name: "Rails main (with adapter)"
+            use_legacy_rails: ""
+
+    env:
+      USE_RAILS_WITHOUT_ACTION_TEXT_ADAPTER: ${{ matrix.use_legacy_rails }}
+
     steps:
       - name: Install packages
         run: sudo apt-get update && sudo apt-get install --no-install-recommends -y build-essential git libyaml-dev pkg-config google-chrome-stable mupdf build-essential ffmpeg groff libreoffice-writer libreoffice-impress libreoffice-calc mupdf-tools libvips zip
@@ -97,15 +110,16 @@ jobs:
           persist-credentials: false
 
       - name: Set up Ruby
-        uses: ruby/setup-ruby@319994f95fa847cf3fb3cd3dbe89f6dcde9f178f # v1.295.0
+        uses: ruby/setup-ruby@3ff19f5e2baf30647122352b96108b1fbe250c64 # v1.299.0
         with:
           ruby-version: .ruby-version
           bundler-cache: true
+          cache-version: ${{ matrix.name }}
 
       - name: Set up Node.js
         uses: actions/setup-node@53b83947a5a98c8d113130e565377fae1a50d02f # v6.3.0
         with:
-          node-version: '20'
+          node-version: '22'
           cache: 'yarn'
 
       - name: Install JavaScript dependencies
@@ -125,7 +139,7 @@ jobs:
         uses: actions/upload-artifact@bbbca2ddaa5d8feaa63e36b76fdaad77386f024f # v7.0.0
         if: failure()
         with:
-          name: screenshots
+          name: screenshots-${{ matrix.name }}
           path: ${{ github.workspace }}/test/dummy/tmp/screenshots
           if-no-files-found: ignore
 
@@ -147,15 +161,31 @@ jobs:
       - name: Set up Node.js
         uses: actions/setup-node@53b83947a5a98c8d113130e565377fae1a50d02f # v6.3.0
         with:
-          node-version: '20'
+          node-version: '22'
           cache: 'yarn'
 
       - name: Install JavaScript dependencies
         run: yarn install --frozen-lockfile
 
-      - name: Install Playwright browsers
+      - name: Get Playwright version
+        id: playwright-version
+        run: echo "version=$(npx playwright --version)" >> "$GITHUB_OUTPUT"
+
+      - name: Cache Playwright browsers
+        id: playwright-cache
+        uses: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830 # v4.3.0
+        with:
+          path: ~/.cache/ms-playwright
+          key: playwright-${{ matrix.browser }}-${{ steps.playwright-version.outputs.version }}
+
+      - name: Install Playwright browser
+        if: steps.playwright-cache.outputs.cache-hit != 'true'
         run: npx playwright install --with-deps ${{ matrix.browser }}
 
+      - name: Install Playwright system deps
+        if: steps.playwright-cache.outputs.cache-hit == 'true'
+        run: npx playwright install-deps ${{ matrix.browser }}
+
       - name: Run Playwright tests
         run: yarn test:browser:${{ matrix.browser }}
 

.github/workflows/docs.yml

@@ -30,15 +30,15 @@ jobs:
           persist-credentials: false
 
       - name: Setup Ruby
-        uses: ruby/setup-ruby@319994f95fa847cf3fb3cd3dbe89f6dcde9f178f # v1.295.0
+        uses: ruby/setup-ruby@3ff19f5e2baf30647122352b96108b1fbe250c64 # v1.299.0
         with:
           ruby-version: '3.3'
           bundler-cache: true
           working-directory: docs
 
       - name: Setup Pages
         id: pages
-        uses: actions/configure-pages@983d7736d9b0ae728b81ab479565c72886d7745b # v5.0.0
+        uses: actions/configure-pages@45bfe0192ca1faeb007ade9deae92b16b8254a0d # v6.0.0
 
       - name: Build with Jekyll
         run: bundle exec jekyll build --baseurl "${STEPS_PAGES_OUTPUTS_BASE_PATH}"
@@ -63,4 +63,4 @@ jobs:
     steps:
       - name: Deploy to GitHub Pages
         id: deployment
-        uses: actions/deploy-pages@d6db90164ac5ed86f2b6aed7e0febac5b3c0c03e # v4.0.5
+        uses: actions/deploy-pages@cd2ce8fcbc39b97be8ca5fce6e763baed58fa128 # v5.0.0

.gitignore

@@ -20,6 +20,8 @@
 /test/browser/playwright-report/
 /test/browser/blob-report/
 
+Gemfile.lock
+
 # Jekyll docs
 /docs/_site/
 /docs/.jekyll-cache/

AGENTS.md

@@ -49,12 +49,14 @@ When changing how Lexxy formats or serializes content (new inline styles, node t
 
 ## Fixing Bugs
 
+**Important:** Some bugs filed against Lexxy are actually bugs in the host application (e.g., BC5 modal behavior, server-side preview rendering, Turbo interactions). When a bug's root cause is in a 37signals app rather than in Lexxy itself, use the `/bugs-fix` skill from `basecamp/coworker` to fix it in the appropriate app repo (e.g., `~/Work/basecamp/bc3`). The workflow below applies only to bugs whose root cause is in Lexxy.
+
 Follow this mandatory workflow. Every step must complete before moving to the next.
 
-1. **Classify** — Determine if the bug is a **core editing bug** (JS behavior: typing, cursor, selection, formatting, paste, toolbar, nodes, extensions) or a **system-level bug** (e.g., Action Text, uploads, Trix conversion, persistence, prompt/SGID resolution, Turbo).
+1. **Classify** — Determine if the bug is a **core editing bug** (JS behavior: typing, cursor, selection, formatting, paste, toolbar, nodes, extensions), a **system-level bug** (e.g., Action Text, uploads, Trix conversion, persistence, prompt/SGID resolution, Turbo), or a **host app bug** (e.g., BC5 modal/composer behavior, server-side preview rendering, Turbo frame interactions). Host app bugs should be fixed in the app repo using `/bugs-fix` from `basecamp/coworker`, not here.
 2. **Reproduce** — Use `/bugs-reproducer` to write a failing test. This skill is ONLY for reproduction — do not investigate fixes or modify source code during this step. Core editing bugs go to Playwright (`test/browser/tests/`), system-level bugs go to Capybara (`test/system/`). Write the test, run it, and **confirm it fails before touching any source code.** A test that hasn't been seen failing proves nothing — it could be passing for the wrong reason. The failing test is your evidence that the bug is real. Do NOT skip this step even if the root cause seems obvious. If you have a justified reason to skip (e.g., the bug is purely visual and untestable), state the justification explicitly before proceeding.
 3. **Fix** — Now investigate the root cause and work on the fix until the reproduction test passes.
 4. **Test** — Ensure a regression test covers the bug. If you reproduced with Playwright or Capybara in step 2, you already have it. If you used Selenium as a fallback, write a proper test now. Then run the full test suite (`yarn test:browser` for Playwright, `bin/rails test:all` for Capybara) to discard regressions. **Always run `yarn lint` after making changes and fix any lint errors before committing.**
-5. **PR & Copilot review** — Push the branch, create a PR, and request a GitHub Copilot review (`gh api repos/<owner>/<repo>/pulls/<number>/requested_reviewers -f "reviewers[]=copilot-pull-request-reviewer[bot]"`). When the review arrives, reply to each comment on GitHub. For actionable feedback (real bugs, internal API misuse, flaky test patterns), write a test that validates the issue first, then fix it. Decline cosmetic or low-value suggestions with a brief rationale.
+5. **PR & Copilot review** — Push the branch, create a **draft** PR (`gh pr create --draft`), and request a GitHub Copilot review (`gh api repos/<owner>/<repo>/pulls/<number>/requested_reviewers -f "reviewers[]=copilot-pull-request-reviewer[bot]"`). When the review arrives, reply to each comment on GitHub. For actionable feedback (real bugs, internal API misuse, flaky test patterns), write a test that validates the issue first, then fix it. Decline cosmetic or low-value suggestions with a brief rationale.
 6. **Validate** — Run `/manually-validate-fix <pr-number>` to validate the fix against both production (bug reproduces) and local (bug fixed). This step is mandatory after every PR — it catches cases where the automated test passes but the actual user-facing behavior is still broken.
 7. **Learn** — If the bug revealed a **family of bugs** (an architectural pattern or subsystem that produces recurring issues), update the "Common Bug Patterns" section in `/bugs-reproducer` (`.claude/skills/bugs-reproducer.md`). Each entry should describe a class of bugs, not an individual fix. Good: "Decorator node navigation" (a whole category). Bad: "Backtick shortcut only works one direction" (a single bug). Don't add notes about specific bugs — that's what the tests and commit messages are for.