📚 Document disable-email-verification team auto-add behavior

The configuration docs claimed it is not possible to add someone to a team without them accepting an invitation email, but the backend auto-adds existing profiles to the team when the email verification is disabled (create-invitation in app.rpc.commands.teams-invitations). Replace the incorrect sentence with an accurate exception note, add the missing disable-email-verification entry to the "Other flags" reference, document the CLI-created profile auto-add behavior in the docker getting-started guide, and describe the shortcut in the developer authentication docs. Closes #11424 Reported in #11376 AI-assisted-by: glm-5.3-flash
2026-09-10 20:59:12 -04:00 · 2026-08-28 17:16:00 +00:00
352 changed files with 6952 additions and 11881 deletions
@@ -1,91 +0,0 @@
-# Agent skills
-
-This folder is the single home for the skills our coding agents use.
-Each skill is a folder with a `SKILL.md` inside — a short instruction
-manual that an agent loads only when it needs it.
-
-One copy serves every tool:
-
- **opencode** reads this folder directly.
- **Claude Code** reads it through the `.claude/skills` symlink.
- **Codex** reads it directly.
-
-To change how the agents behave, edit the `SKILL.md` here. There is no
-second copy to keep in sync.
-
-## How the skills are organized
-
-**Flows** are the six skills you invoke by name. Each one covers one step
-in the life of a change: plan it, review the plan, implement it, review
-the code, open the pull request.
-
-**References** hold the quality standards. A flow's reviewer loads them;
-you rarely touch them directly.
-
-**Procedures** define how one concrete step is done — a plan document, an
-issue, a commit. Flows call them, but they also work on their own.
-
-**Utilities** are small helpers for everyday work: search, file lookup,
-JSON, REPL access, and so on.
-
-## Flows
-
-| Skill | What it does | When you would say |
-|---|---|---|
-| [`make-a-plan`](skills/make-a-plan/SKILL.md) | Researches the task, writes an implementation plan, asks you the open questions in plain language, and saves the plan to `.agents/plans/`. | "make a plan for the token refresh bug" |
-| [`review-plan`](skills/review-plan/SKILL.md) | Evaluates a plan before anyone writes code: completeness, ordering, risks. Approves it or asks for changes. | "review this plan before we start" |
-| [`implement-plan`](skills/implement-plan/SKILL.md) | Shows you the full flow first — the issue and branch it will create (or the branch it continues on), the execution style, and the task checklist — and, after your go-ahead, executes a ready plan. Default: every task, one commit. On request ("step by step"): one task, one commit, your confirmation between tasks. On request ("direct"): no issue and no branch, commits on the current branch. | "implement the plan" · "step by step, one commit per task" · "direct, no branch" |
-| [`review-code`](skills/review-code/SKILL.md) | Reviews a diff, branch, or PR and returns findings ranked by impact. | "review my changes before I push" |
-| [`create-pr`](skills/create-pr/SKILL.md) | Opens a pull request for the current branch — with checks on base branch, commits, issue, and push state — or updates an existing PR's title and description. | "open a PR for this branch" |
-| [`resolve-git-conflicts`](skills/resolve-git-conflicts/SKILL.md) | Untangles merge or rebase conflicts: explains both sides, proposes a resolution, applies it after you approve. Never runs `git rebase --continue`. | "resolve these conflicts" |
-
-## References
-
-| Skill | What it holds |
-|---|---|
-| [`plan-review-criteria`](skills/plan-review-criteria/SKILL.md) | The plan review rubric: six axes, severity levels, approval standard, output format. The `review-plan` reviewer loads it. |
-| [`code-review-criteria`](skills/code-review-criteria/SKILL.md) | The code review rubric: five axes, core principles (DRY, KISS, YAGNI), severity format, verdict. The `review-code` reviewer loads it. |
-
-## Procedures
-
-| Skill | What it does |
-|---|---|
-| [`planner`](skills/planner/SKILL.md) | The spec of a good plan: context, architecture decisions, tasks with acceptance criteria, checkpoints. Used by `make-a-plan`. |
-| [`create-issue`](skills/create-issue/SKILL.md) | Creates a GitHub issue that follows Penpot conventions. Used by `implement-plan`; also works on its own. |
-| [`create-commit`](skills/create-commit/SKILL.md) | Makes a commit the Penpot way: emoji subject, clear body, `AI-assisted-by` trailer. Used by `implement-plan`; also works alone when you say "commit this". |
-
-## Utilities
-
-| Skill | What it does |
-|---|---|
-| [`bat-cat`](skills/bat-cat/SKILL.md) | Read files in the terminal with syntax highlighting and line numbers. |
-| [`fd-find`](skills/fd-find/SKILL.md) | Find files by name or pattern, respecting `.gitignore`. |
-| [`ripgrep`](skills/ripgrep/SKILL.md) | Fast content search with regular expressions. |
-| [`jq-json-processor`](skills/jq-json-processor/SKILL.md) | Slice, filter, and reshape JSON output. |
-| [`nrepl-eval`](skills/nrepl-eval/SKILL.md) | Run Clojure or ClojureScript code in the live REPL sessions (backend and frontend). |
-| [`taiga`](skills/taiga/SKILL.md) | Look up Penpot issues, user stories, and tasks in Taiga. |
-| [`testing`](skills/testing/SKILL.md) | The repo's testing rules and TDD workflow, loaded before writing tests. |
-| [`local-ci`](skills/local-ci/SKILL.md) | Run CI-style lint, test, and format checks for the modules you touched with `scripts/ci`, and read the logs when they fail. |
-| [`security-and-hardening`](skills/security-and-hardening/SKILL.md) | Security checks for code that handles user input, auth, or external services. |
-| [`ste`](skills/ste/SKILL.md) | Rewrites prose in Simplified Technical English. Loads only when you name it. |
-| [`refine-prompt`](skills/refine-prompt/SKILL.md) | Rewrites a rough prompt into a clearer one. Never runs the prompt. |
-| [`update-changelog`](skills/update-changelog/SKILL.md) | Regenerates `CHANGES.md` from a GitHub milestone. |
-
-## A typical round
-
-1. `/make-a-plan` — you get a plan and a saved file in `.agents/plans/`.
-2. `/review-plan` — a second opinion; approve or request changes.
-3. `/implement-plan` — the code gets written and committed. Starting from a base branch, it also opens the GitHub issue and the `issue-NNNN` branch; the plans that follow continue on that same branch.
-4. `/review-code` — a reviewer checks the commit.
-5. `/create-pr` — the branch goes up as a pull request.
-
-Every step also works on its own, and you can always say what you want
-in plain words — the agents pick the right skill from what you say.
-
-## Adding or changing a skill
-
-Create a folder here with a `SKILL.md` inside. The file needs `name` and
-`description` in its frontmatter, and a clear "When to use" section so
-agents know when to reach for it. Keep one job per skill, and keep the
-two families apart: flows are named with a verb first; reference skills
-end in `-criteria`.
@@ -1,105 +0,0 @@
---
-name: create-pr
-description: PR flow — open a new PR for the current task branch (validates base branch, commits, issue and push state) or update an existing PR's title or description to match Penpot conventions. Use it when the user asks to open or create a PR, in any phrasing.
---
-
-# Create PR
-
-Two modes. **Open mode** takes the current task branch to a new, validated
-PR. **Update mode** rewrites an existing PR's title or description. Gather
-information, validate, and act in one pass. If validation fails, STOP with a
-single coherent message that lists every problem and states exactly what
-information is missing — never fix or work around problems silently.
-
-Both modes require an authenticated `gh` CLI (`gh auth status`) and never
-push — the user pushes from their own shell.
-
-## When to use
-
- The user asks to open or create a NEW PR for the current task branch, in
-  any phrasing ("open a PR", "create the pull request", "put this up for
-  review") — or runs `/create-pr`. → **Open mode**.
- The user asks to fix or update an EXISTING PR's title or description to
-  match conventions. → **Update mode**.
-
-If the running agent cannot write (for example, the plan agent), say so and
-stop — this skill needs the build agent.
-
-## Open mode
-
-### 1. Gather context (read-only)
-
- Current branch: `git rev-parse --abbrev-ref HEAD`.
- Target base branch: run `./scripts/detect-target-branch` from the repo root.
-  It prints the nearest ancestor branch of HEAD (exit 0) or fails (exit 1).
- Commits: `git log --oneline <base>..HEAD`.
- Push state (local): `git rev-parse --verify origin/<branch>` and compare
-  with HEAD. It reads the local remote-tracking ref — no network, no SSH. It
-  reflects the last push or fetch this clone knows about.
- Issue: from the session context, or from the branch name — `issue-NNNN`
-  maps to issue NNNN; recover its title and body with `gh issue view NNNN`.
-
-### 2. Validate — stop with one message if anything fails
-
-Run all checks before reporting, then report every failure together:
-
-1. **Base branch not usable.** If the script fails (exit 1), or its output —
-   after stripping an optional `remotes/origin/` prefix — is not one of the
-   canonical branches (`develop`, `staging`, `main`), stop and ask the user
-   to re-run with more context — for example, passing the base branch
-   explicitly in their invocation. An explicit base given by the user
-   overrides the script's output.
-2. **On a base branch.** There is no task branch to merge — say so and stop.
-3. **No commits.** The branch has no commits ahead of the base — say so and
-   stop.
-4. **No clear issue.** There is no issue in the session context, and the
-   branch name has no `issue-NNNN` pattern (or `gh issue view` finds nothing)
-   — say so and stop. Exception: the user's invocation says `no issue` /
-   `without issue` — then continue without an issue reference.
-5. **Branch not pushed.** The remote-tracking ref `origin/<branch>` is
-   missing, or `git rev-parse origin/<branch>` differs from HEAD — the
-   branch was never pushed, or has commits the remote does not have. Never
-   push yourself; ask the user to push and to run `/create-pr` again
-   afterwards, then stop.
-
-### 3. Already-open PR
-
-Check whether a PR already exists for this branch (`gh pr list --head
-<branch>`). If one exists, report its URL and stop — do not create a second
-one. Title or description fixes belong to Update mode.
-
-### 4. Write and create the PR
-
-Write the title and body following `mem:workflow/creating-prs` (title format,
-description structure, writing principles) and `mem:workflow/creating-commits`
-(commit type emojis). Derive the title and body from the commits and, when
-there is one, from the issue body. Reference the issue with `Closes #NNNN`.
-
-```bash
-gh pr create --repo penpot/penpot --title "<TITLE>" --body-file /tmp/pr-body.md
-```
-
-### 5. Report
-
-Report the PR URL and stop.
-
-## Update mode
-
-1. Identify the PR: the number given by the user, or `gh pr list --head
-   <branch>`.
-2. Write the new title and/or body following `mem:workflow/creating-prs`.
-3. Apply and verify:
-
-```bash
-gh pr edit <NUMBER> --repo penpot/penpot --title "<TITLE>" --body-file /tmp/pr-body.md
-gh pr view <NUMBER> --repo penpot/penpot --json title,body
-```
-
-4. Report and stop.
-
-## User context
-
-Extra context in the user's invocation (the message that triggered this skill)
-plays the role command arguments play elsewhere: overrides such as `no issue` /
-`without issue`, an explicit base branch (`from origin/staging`), a PR number
-for Update mode, and so on.
@@ -1,144 +0,0 @@
---
-name: implement-plan
-description: Implementation flow — execute a ready plan from the session context: read the plan, detect the flow, then present the full picture (issue and branch to create or the branch to continue on, execution style, task checklist) and wait for confirmation. Default is every task with one final commit; on request ("step by step"), one task and one commit at a time with a pause after each; on request ("direct"), no issue and no branch — the commit lands on the current branch. Use it when the user asks to implement or execute a plan, in any phrasing.
---
-
-# Implement Plan
-
-This flow is run once a plan is ready (for example, from plan mode). Execute
-the plan already prepared in the current session context. It never pushes —
-the user pushes.
-
-By default it ends with exactly one commit. When the user asks for it
-("step by step"), it commits once per task instead and waits for the
-user's confirmation after each one (see *Execution modes*).
-
-## When to use
-
- The user asks to implement or execute a plan, in any phrasing:
-  "implement the plan", "execute it", "go build it" — or runs
-  `/implement-plan`.
- A ready, reviewed plan is in the session context or a plan file path
-  was given (typically after `/make-a-plan` or `/review-plan`).
-
-Do not use it to produce plans — that is the `make-a-plan` flow.
-
-## 1. Read the plan first
-
-Identify the plan to execute — from the file path the user gave, the
-arguments, or the session context. Read it completely. Read the required
-memories before writing any code: `mem:critical-info` and the core memory
-of every module the plan touches, plus the deeper memories they reference
-(AGENTS.md governs this).
-
-## 2. Detect the flow (no questions)
-
-Inspect the current branch with `git rev-parse --abbrev-ref HEAD`, pick the
-mode, and announce it in one line before presenting anything. Detection is
-read-only: nothing is created until the user confirms (step 3).
-
- **On a base branch** (`main`, `develop`, `staging`) → **standalone mode**:
-  a new GitHub issue and a branch `issue-NNNN` will be created after the
-  user's confirmation.
- **On any other branch** (a feature branch, typically `issue-NNNN`) →
-  **continue mode**: the implementation continues on the current branch.
-  No issue or branch is created. The branch name provides the issue
-  reference when it follows the `issue-NNNN` pattern.
-
-Arguments override detection: `standalone`, `continue`, `direct`
-(`no branch` / `direct commit`), `no issue` / `without issue`, or an
-explicit base such as `from origin/develop`.
-
-**Direct mode** (`direct`, `no branch`, `direct commit`): no issue and
-no branch — the implementation and the commit land on the current branch
-as it is, even when it is a base branch. Best for small or tooling-only
-changes the user wants committed in place.
-
-**Standalone while already on a feature branch:** stop and explain that this
-would stack branches. Ask the user to re-run with an explicit base, for
-example `from origin/develop` — then branch from that base instead of HEAD.
-
-## 3. Present the checklist and wait
-
-Before touching the repository, show the user the full picture:
-
- **The flow**: whether the GitHub issue and the branch will be created
-  (standalone mode — give the planned branch name, `issue-NNNN` or
-  `plan-<slug>`), whether you continue on the current branch
-  (continue mode — name it), or whether everything lands on the current
-  branch as it is (direct mode — name it, and say so when it is a base
-  branch).
- **The execution style**: batch or step-by-step (see *Execution modes*).
- A checklist (todolist) of the plan's tasks, in order.
-
-Then WAIT for the user's explicit confirmation. Do not start until you
-have it. If the plan has no discrete tasks, ask the user how to split
-it, or propose running it as a single change.
-
-## 4. Execute the plan
-
-**Standalone setup, after the confirmation:** create the issue with the
-**`create-issue`** skill, following the *Creating Issues from Draft Body*
-flow in `mem:workflow/creating-issues`. Derive the issue title and body
-from the plan, capture the new issue's number — call it **NNNN** — and
-create the branch from the current HEAD:
-
-```
-git checkout -b issue-NNNN
-```
-
-If the arguments say `no issue` / `without issue`, skip the issue and
-create a branch named `plan-<slug>` instead, where `<slug>` is the plan
-title, lowercase and hyphen-separated.
-
-If the arguments say `direct` / `no branch` / `direct commit`, skip the
-issue and the branch: implement and commit on the current branch as it
-is. If it is a base branch, the checklist presentation already said so —
-no further confirmation is needed.
-
-### Batch mode (default)
-
-Implement every task in one go. Work methodically, keeping changes
-focused on what the issue requires. Respect the plan's proposed
-parallelization when it applies.
-
-When the implementation is complete, load the **`create-commit`** skill
-and follow its workflow to commit the changes. Provide a brief summary
-of what was implemented and why, the issue reference (`issue-NNNN`) when
-there is one, and the model name you are running as so the
-`AI-assisted-by` trailer is set correctly.
-
-### Step-by-step mode (on request)
-
-When the user asks for it — "step by step", "task by task", "one commit
-per task" — loop one task at a time:
-
- Execute exactly ONE task.
- Commit it now: load the **`create-commit`** skill and follow it —
-  one commit per task, never two tasks in one commit. Same inputs as
-  always: what and why, the issue reference, your model name.
- Show the user the result (what changed, files touched, how it was
-  verified).
- WAIT for the user's confirmation before starting the next task.
-
-Never batch in this mode: no two tasks in one commit, and no new task
-before the user confirms. If a task turns out much bigger than planned,
-stop and ask the user before splitting it.
-
-## When you are done
-
-End by suggesting the next steps (suggestions, not a required pipeline — any
-instruction from me overrides them):
-
- `/review-code` — to review the changes just committed; it routes to
-  `/make-a-plan` by itself if the findings need one.
- `/create-pr` — when the task is done and the branch is ready to merge.
-
-## User context
-
-Extra context in the user's invocation (the message that triggered this
-skill) plays the role command arguments play elsewhere: `standalone`,
-`continue`, `direct` (`no branch` / `direct commit`), `no issue` /
-`without issue`, an explicit base such as `from origin/develop`, or
-`step by step` / `one commit per task` for the step-by-step execution
-mode. Modes combine freely, for example "standalone step by step".
@@ -1,95 +0,0 @@
---
-name: local-ci
-description: Run local CI-style checks with ./scripts/ci (lint, tests, format) per monorepo module. Use when verifying changes before declaring work done, running lint or tests locally, fixing formatting, or repairing Clojure delimiter errors.
---
-
-# Local CI
-
-Run the same checks CI runs, locally, for the modules you touched, with
-`scripts/ci`. Each task writes a log file; the final summary says what
-passed and what failed.
-
-Full details: `mem:scripts/ci` (file: `.serena/memories/scripts/ci.md`)
-
-## When to use
-
- After implementing or fixing code — verify every module you touched
-  before declaring the work done.
- When the user asks to run CI, lint, tests, or format checks locally.
- When you changed `common/` — validate its consumers too.
-
-**Skip:** while exploring, planning, or reading code.
-
-## Command reference
-
-Run from the repo root:
-
-```bash
-./scripts/ci [OPTIONS] [MODULES...]
-```
-
-Modules: `frontend` `backend` `common` `render-wasm` `exporter` `mcp`
-`plugins` `library`, or `--all` for every module.
-
-With no task flags it runs three tasks per module, in order: **lint**,
-**test**, **fmt** (format check; `--fix` formats files instead).
-
-| Flag | Effect |
-|------|--------|
-| `--all` | Run every module |
-| `--exclude MOD` | Skip one module (repeatable) |
-| `--lint` / `--no-lint` | Run only lint / drop lint |
-| `--test` / `--no-test` | Run only tests / drop tests |
-| `--fmt` / `--no-fmt` | Run only format check / drop it |
-| `--fix` | Format files instead of checking (other tasks unaffected) |
-| `--paren-repair` | Fix delimiter errors in Clojure/CLJS files |
-| `--fail-fast` | Stop at the first failure |
-| `--quiet` | Suppress failure output |
-| `--dry-run` | Show what would run, execute nothing |
-| `--clean` | Delete the `.ci-logs/` directory |
-
-## Reading failures
-
-Every task writes its full output to `.ci-logs/<module>-<task>.log`. On
-failure the script prints only the last 30 lines. To diagnose a failure,
-**read the log file** — never re-run the command piped through filters
-(repo rule: redirect to a file first, then read it). The exit code is 1
-when any task failed; the summary lists each failed `module:task` and its
-log path.
-
-## Typical workflows
-
-```bash
-# Verify a module you changed: lint + tests + format check
-./scripts/ci frontend
-
-# Fast pass while iterating: lint only
-./scripts/ci --lint frontend
-
-# Lint + format check, skip the long test suite
-./scripts/ci --no-test frontend
-
-# Format the module without running the test suite
-./scripts/ci --fix --no-test frontend
-
-# Broke delimiters in Clojure/CLJS files: repair first, then lint
-./scripts/ci --paren-repair frontend
-./scripts/ci --lint frontend
-
-# Changed common/ — validate its consumers too
-./scripts/ci frontend backend exporter
-
-# Preview what would run, without running it
-./scripts/ci --dry-run --all
-```
-
-## Gotchas
-
- Run from the repo root.
- Test tasks are long-running (backend runs `clojure -M:dev:test`); give
-  the bash call a generous timeout (10–20 minutes) instead of letting it
-  time out mid-run.
- `mcp` has no lint task — it shows as skipped, not failed.
- `--paren-repair` only fixes delimiters; run lint afterwards to catch
-  what remains. See `mem:scripts/paren-repair`.
- What to run and how to read test results: `mem:testing`.
@@ -1,100 +0,0 @@
---
-name: make-a-plan
-description: Planning flow — research the subject of this session, produce an implementation plan with the planner skill, resolve open questions with the user in plain language, and save the final plan to .agents/plans/. Use it when the user asks to plan, design, or break down a task, in any phrasing.
---
-
-# Make a Plan
-
-Act as a senior software engineer: research the subject of this session in depth and
-produce a well-grounded, actionable implementation plan.
-
-If the running agent cannot write (for example, the plan agent), say so and
-stop — this skill needs the build agent to save the plan.
-
-## When to use
-
- The user asks to plan, design, or break down a task, in any phrasing:
-  "make a plan", "how would we build X", "design an approach for Y" —
-  or runs `/make-a-plan`.
- The user asks to rework or extend an existing plan (for example, after
-  review findings) — revise the saved plan file in place.
-
-Do not use it to execute a plan — that is the `implement-plan` flow.
-
-## Instructions
-
-1. **Produce the plan** with the `planner` skill. By default, research the
-   subject of this session and draft the plan yourself. If I ask for it (for
-   example, `delegated` in the user context), delegate to the `general` subagent
-   instead — the delegate must also follow the `planner` skill and receive all
-   the relevant session context (a review, user feedback, and so on).
-2. Before asking me to decide anything, explain the plan and every open question in
-   plain language. Assume I know only the high-level project goal, not the codebase,
-   architecture, implementation terms, or the problem this task solves.
-3. Once all decisions are answered and the plan is final, save it verbatim to the
-   announced path under `.agents/plans/` (create the directory if it does not
-   exist). This step is the flow's explicit authorization to write the plan
-   file — the only write allowed here. If I later ask for changes, update the
-   saved file directly.
-4. Present me with a clear, self-contained summary of the plan's most relevant points
-   only after all required decisions have been answered. Write it for someone who knows
-   only the project's high-level goal and may not know the plan's low-level context.
-   Explain necessary technical language in plain terms, include the problem being
-   solved and the proposed outcome, and do not assume that listing technical task names
-   is enough.
-
-### Hard rule — read-only while planning
-
-While this flow runs, act read-only: research with read-only tools only.
-Never edit source files, never run builds, tests, linters, or any command that
-modifies state, and never commit. The single allowed write is the plan file in
-step 3. This rule expires when I approve the plan or move on to another task;
-then you act as a normal build agent again.
-
-When the plan contains open questions, do not show them as bare technical questions or
-assume that I understand the technical language or technical words used in the plan.
-For each question, first explain:
-
- What part of the user problem the decision affects.
- The relevant concept from the beginning, with a small concrete example.
- What each available option would make the system do.
- The practical benefits, costs, risks, and user-visible consequences of each option.
- Which option the planner recommends and why.
-
-Only after that explanation, use the `question` tool to ask the decision with clear,
-non-technical option labels. Put the recommended option first and mark it as
-`(Recommended)`. Group related questions when their context is shared, but do not ask a
-question whose meaning has not already been explained.
-
-If I say that I do not understand a question or its choices, do not treat my previous
-answer as valid. Explain the concepts again from the high-level project goal, use a more
-concrete example, explain the implications, and ask the question again with the
-`question` tool. Repeat this until I can make an informed choice. If one answer creates
-new design consequences or additional decisions, explain those consequences before
-asking any new question.
-
-Distinguish clearly between requirements already fixed by the roadmap or existing
-architecture and choices that actually require my input. Do not ask me to choose an
-implementation detail when the plan can resolve it safely without changing the public
-behavior. If there are no decisions that require my input, say so and present the
-summary.
-
-IMPORTANT: **Under no circumstances execute the plan. Wait for the user to review it
-after all possible questions have been answered.** The final summary must explain the
-problem being solved, the proposed behavior, the main user-visible workflow, important
-constraints and risks, what is deliberately out of scope, and the path where the plan
-is saved. Never assume that a short list of task names is enough context. End
-the final response by suggesting the next steps, in this order:
-
-1. `/review-plan` — to get a second opinion on the plan before executing it.
-2. `/implement-plan` — to execute the plan from the current session context.
-
-These are suggestions, not a required pipeline — any instruction from me
-overrides them (for example, asking you to implement the plan directly).
-
-## User context
-
-Extra context in the user's invocation (the message that triggered this skill)
-plays the role command arguments play elsewhere: for example, `delegated` to
-hand the research and drafting to the `general` subagent, or corrections and
-feedback about a previous plan.
@@ -1,205 +0,0 @@
---
-name: planner
-description: Read-only planning and architecture analysis — produce a structured implementation plan with task breakdown, acceptance criteria, sizing, and checkpoints. Always output to the user with the plan, suggested save path and the next steps.
---
-
-# Planner
-
-Produce a plan that another engineer or agent can execute without guessing.
-
-## When to Use
-
- The user asks for a plan, design, or analysis of a feature or bug.
- The user wants to understand which parts of the codebase a task will touch.
- The user needs a step-by-step implementation plan with file paths, function
-  names, and test strategy.
- The user asks "how would I implement X?" or "what's involved in fixing Y?".
- The user is about to start non-trivial work and wants a bite-sized task
-  breakdown.
- A task feels too large or vague to start.
- Work needs to be parallelized across multiple agents or sessions.
-
-Do not use for a small change with obvious scope or an existing executable plan.
-
-## CRITICAL: Required Reading Before Planning
-
-Before drafting any plan, work through the project's own guidance:
-
-1. Read `critical-info` (`.serena/memories/critical-info.md`) — the entry point
-   that describes the monorepo structure and module dependency graph.
-2. From `critical-info`, identify which modules your task affects.
-3. Read each affected module's core memory, e.g. `mem:frontend/core`,
-   `mem:backend/core`, `mem:common/core`, `mem:exporter/core`,
-   `mem:render-wasm/core`. Follow `mem:` references deeper as needed.
-4. For each affected module, note its lint, format, and test commands so the
-   plan can include concrete verification steps.
-
-Skipping this step is the #1 cause of incorrect or incomplete plans.
-
-## Constraints
-
- You are **analysis-only** — never create, edit, or delete source code. The
-  only file you may write is the plan itself, and only when the command or
-  user explicitly instructs you to save it.
- You do **not** run builds, tests, linters, or any commands that modify state.
- You do **not** create git commits or interact with version control.
- You do **not** execute shell commands beyond read-only searches (`rg`, `ls`,
-  `find`, `cat`, `bat`).
- Your output is a structured plan or analysis, ready for handoff to an
-  engineer agent or developer.
-
-## Planning Process
-
-1. Define the problem, desired outcome, constraints, and exclusions.
-2. Trace the current behavior through the affected modules.
-3. Map dependencies and choose an implementation order that builds foundations
-   before their consumers.
-4. Identify open product or architecture decisions. Resolve implementation
-   details from existing conventions when they do not affect public behavior.
-5. Identify edge cases, security and data risks, performance bounds, breaking
-   changes, and external dependencies.
-6. Split the work into small, ordered tasks. Prefer complete testable slices
-   over unrelated layer-wide batches. Apply DRY and KISS to the proposed
-   implementation.
-7. Define exact acceptance criteria and verification for every task.
-8. Add a checkpoint after every two or three tasks in a longer plan.
-9. State which tasks can run in parallel and which must remain sequential.
-
-## Task Format
-
-Each task follows this structure:
-
-```markdown
-## Task [N]: [Short descriptive title]
-
-**Description:** One or two paragraphs explaining what this task accomplishes.
-Should be clear and concise.
-
-**Rationale:** Why this task exists and why this approach over the obvious
-alternatives — design decisions, trade-offs, constraints discovered during
-analysis. One or two sentences; skip only if genuinely trivial.
-
-**Code sketch (optional):** Signature-, type-, or shape-level example when the
-intended interface is non-obvious. Keep it short — a skeleton that fixes the
-contract (function signature, model fields, error shape), never a full
-implementation. Omit when the task is mechanical.
-
-**Acceptance criteria:**
- [ ] [Specific, testable condition]
- [ ] [Specific, testable condition]
-
-**Verification:**
- [ ] Relevant tests pass (module-specific test command).
- [ ] Lint/formatter passes (module-specific check command), if applicable.
- [ ] The core flow works end-to-end, if applicable.
-
-**Dependencies:** [Task numbers this depends on, or "None"]
-
-**Files likely touched:**
- `path/to/file.clj`
- `path/to/file_test.clj`
-
-**Estimated scope:** [XS: 1 file | S: 1-2 files | M: 3-5 files | L: 5+ files]
-```
-
-Use commands from `mem:testing` and affected module memories. Never substitute
-generic text such as "run the tests" when the project documents an exact
-command.
-
-When possible, design each task with TDD in mind: acceptance criteria double as a test
-list, and the natural first step of the task is writing those tests before the
-implementation. Some tasks resist this (config, migrations, pure wiring) — for those, keep
-the usual verification steps.
-
-## Task Sizing
-
-| Size | Files | Scope | Example |
-|------|-------|-------|---------|
-| **XS** | 1 | Single function, config change, or schema tweak | Add a validation rule |
-| **S** | 1-2 | One handler or component method | Add a new RPC endpoint |
-| **M** | 3-5 | One vertical feature slice | Bookmark CRUD with tests |
-| **L** | 5-8 | Multi-component feature | Search with filtering and pagination |
-| **XL** | 8+ | **Too large — break it down further** | — |
-
-Split a task when it contains independent outcomes, spans unrelated systems, or cannot be
-completed and verified in one focused session (if a task is XL, it should be broken into
-smaller tasks; agents perform best on S and M tasks).
-
-## Task order and checkpoints
-
-Arrange tasks so that:
-
-1. Dependencies are satisfied (build foundation first)
-2. Each task leaves the system in a working state
-3. Verification checkpoints occur after every 2-3 tasks
-4. High-risk tasks are early (fail fast)
-
-Add explicit checkpoints with the relevant module commands:
-
-```markdown
-### Checkpoint: After Tasks 1-3
- [ ] Relevant tests pass (module-specific command).
- [ ] The relevant build or compilation passes, if applicable.
- [ ] The core flow works end-to-end.
-```
-
-## Output Format
-
-The plan is always delivered in the response so the user sees it regardless
-of which agent is running the skill. File writes follow `Constraints` —
-by default announce the path instead of writing.
-
-Announce the save path `.agents/plans/YYYY-MM-DD-<slug>.md` (today's date,
-lowercase hyphen-separated slug, e.g. `2026-09-10-add-batch-get-profiles`;
-an explicit user path wins).
-
-End the response by suggesting the next steps: `/review-plan` to get a second
-opinion on the plan and `/implement-plan` to execute it.
-
-### Plan Structure
-
-Use this document shape:
-
-```markdown
-# Plan: Title
-
-## Context
-## Affected Modules
-## Architecture Decisions
-## Risks and Considerations
-## Approach
-## Task List
-## Verification and Testing
-## Parallelization
-## Open Questions
-```
-
-Omit empty sections only when they do not apply. Every implementation task
-still requires acceptance criteria, verification, dependencies, likely files,
-and scope.
-
-When the plan is purely analytical (e.g. a code review or feasibility study
-with no implementation), skip the **Approach** and **Task List** sections and
-lead with **Findings** instead, keeping the rest of the structure.
-
-## Common Rationalizations
-
-| Rationalization | Reality |
-|---|---|
-| "I'll figure it out as I go" | That's how you end up with a tangled mess and rework. 10 minutes of planning saves hours. |
-| "The tasks are obvious" | Write them down anyway. Explicit tasks surface hidden dependencies and forgotten edge cases. |
-| "Planning is overhead" | Planning is the task. Implementation without a plan is just typing. |
-| "I can hold it all in my head" | Context windows are finite. Written plans survive session boundaries and compaction. |
-
-## Verification Checklist
-
-Before delivering the plan, confirm:
-
- [ ] Every task has acceptance criteria
- [ ] Every task has a verification step
- [ ] Task dependencies are identified and ordered correctly
- [ ] No task is XL or larger — break it down instead
- [ ] Checkpoints exist after every 2-3 tasks
- [ ] The response states the plan's path (saved or suggested) and suggests
-      `/review-plan` and `/implement-plan`
- [ ] The plan is ready for human review
@@ -1,47 +0,0 @@
---
-name: resolve-git-conflicts
-description: Conflict resolution flow — understand the local git conflicts, present a resolution plan, and resolve them after the user approves it. Never continues the rebase. Use it when the repo has unresolved conflicts (rebase, merge, cherry-pick) or the user asks to resolve them.
---
-
-# Resolve Git Conflicts
-
-Resolve conflicts in the local repository. The user handles finishing the
-rebase themselves — you must **never** run `git rebase --continue`,
-`git rebase --skip`, `git merge --continue`, or anything similar.
-
-## When to use
-
- The repository has unresolved conflicts — during a rebase, merge, or
-  cherry-pick — whether the user asks about them or not.
- The user asks to resolve conflicts, in any phrasing: "fix the merge
-  conflicts", "resolve these", "what's conflicting here?".
-
-## Phase 1 — Understand the problem (read-only)
-
-1. Run `git status` to detect the conflict state (rebase, merge, cherry-pick, etc.) and list conflicted files.
-2. For each conflicted (unmerged) file, understand the situation **without modifying anything**:
-   - Read the file and identify the conflict markers (`<<<<<<<`, `=======`, `>>>>>>>`).
-   - Inspect both sides — `git show <ours>:<file>` and `git show <theirs>:<file>` — plus `git log`/`git show` on the commits involved to understand intent.
-   - Identify what each side changed and why, and how they should be combined.
-
-## Phase 2 — Present the resolution plan
-
-3. **Present a clear plan to the user before touching any file.** For each conflicted file, state:
-   - What each side changed and why.
-   - Your proposed resolution and the reasoning behind it.
-   - How the two sides are combined (both additive → merge; both modify the same code → keep the semantically correct version, merging intent from both sides when clear from code and context).
-4. **Ask the user only when genuinely unclear.** Do not ask about anything you can determine yourself from the code, commit messages, or context. Only decisions that are not determinable and change the outcome (e.g. conflicting product decisions, which side to discard) warrant a question. **Collect all such questions together in an "Open Questions" section at the end of the plan**, so the user has full context to answer them properly.
-5. **Wait for the user to accept the plan** (and answer any open questions) before editing, staging, or otherwise modifying anything.
-
-## Phase 3 — Execute
-
-6. Resolve each conflicted file by editing the file to the agreed merged content and removing all conflict markers.
-
-## Phase 4 — Stage and verify
-
-7. **Stage every resolved file** with `git add <file>`. Do not stage unrelated untracked files unless clearly part of the resolution.
-8. Verify no conflict markers remain (search for `<<<<<<<` / `>>>>>>>` in resolved files) and that `git status` shows no unmerged paths.
-
-## Phase 5 — Report
-
-9. Briefly report the conflict state, how each conflicted file was resolved (and any answers received to open questions), and stop — do **not** run `git rebase --continue` or any other continuation command.
@@ -1,73 +0,0 @@
---
-name: review-code
-description: Code review flow — review a diff, PR, or code change, delegating the review to a subagent that follows the code-review-criteria skill. Use it when the user asks to review code or a PR, in any phrasing.
---
-
-# Review Code
-
-Act as a senior software engineer and perform a thorough code review.
-
-## When to use
-
- The user asks to review code, in any phrasing: "review this diff",
-  "review the PR", "check my changes", "code review" — or runs
-  `/review-code`.
- A commit, branch, PR, or diff is ready and the user wants it assessed
-  before merge.
-
-## Instructions
-
-1. **Determine what is being reviewed** from the user context: a working-tree
-   diff, a commit range, a branch, a PR (number or URL), or specific files. If
-   the target is ambiguous, ask before reviewing.
-2. Delegate the review to the `general` subagent (via the task tool), unless the
-   user specifies another agent. Include in the prompt the
-   **`code-review-criteria`** skill name and all user context.
-3. When the subagent returns, output the review to the user verbatim. Do not
-   summarize it and do not act on its findings.
-4. Right after the review, suggest how to proceed based on the findings. These
-   are suggestions — the user decides:
-   - **Approve (no required changes):** say so — there is nothing to address.
-   - **Minor findings (nits):** applying them directly as-is is fine once the
-     review is done — no plan needed.
-   - **Substantive findings:** suggest `/make-a-plan` to make a plan to address
-     them.
-
-### Hard rule — read-only while reviewing
-
-This flow is read-only **for the duration of the review**: from the moment it
-starts until the user considers the review finished (including any feedback,
-questions, or clarifications about it). During that period, never fix,
-implement, edit files or create commits — not even "obvious" fixes derived from
-the findings. Once the user explicitly states the review is done (or moves on to
-a different task), this rule no longer applies and you act as a normal build
-agent again.
-
-## Instructions for the subagent
-
-1. Load the **`code-review-criteria`** skill and follow its process and output
-   format.
-2. Read `AGENTS.md` (if present) and follow its instructions for finding and
-   reading all related testing documentation from memories before reviewing.
-3. Return in your final message the COMPLETE review, verbatim, exactly as the
-   skill instructs it to be produced. Do not summarize it — include the full
-   structured review.
-
-### Strong rules for the subagent
-
-1. Do not invent problems. Every finding must be real and actionable.
-2. Read-only: do not modify any file and do not create a commit — reviewing
-   never writes.
-3. Be specific and constructive. "This could be better" is not helpful — explain
-   why and how.
-4. Prioritize by impact. One structural issue outweighs ten nits.
-5. Missing tests are an issue, not a suggestion. Report as a severity-tagged
-   finding — never as a recommendation.
-6. Skip generated files, lockfile-only changes, and unrelated modifications
-   unless they introduce security risks.
-
-## User context
-
-Extra context in the user's invocation (the message that triggered this skill)
-plays the role command arguments play elsewhere: for example, a PR number or
-URL, a commit range, specific files, or a different agent to run the review.
@@ -1,71 +0,0 @@
---
-name: review-plan
-description: Plan review flow — evaluate an implementation plan before it is executed, delegating the review to a subagent that follows the plan-review-criteria skill. Use it when the user asks to review a plan, in any phrasing.
---
-
-# Review Plan
-
-Act as a senior software engineer and perform a thorough review of an
-implementation plan.
-
-## When to use
-
- The user asks to review a plan, in any phrasing: "review this plan",
-  "does this plan look right?", "second opinion on the plan" — or runs
-  `/review-plan`.
- A plan was just produced (typically by `/make-a-plan`) and the user
-  wants it evaluated before executing it.
-
-## Instructions
-
-1. **Determine the plan under review** from the session context (for example, a
-   plan just produced by `/make-a-plan`) or from a plan file path given by the
-   user (typically under `.agents/plans/`). If a file path is given, read the
-   file first so the complete plan is in context.
-2. Delegate the review to the `general` subagent (via the task tool), unless the
-   user specifies another agent. Include in the prompt the
-   **`plan-review-criteria`** skill name and all user context.
-3. When the subagent returns, output the review to the user verbatim. Do not
-   summarize it and do not act on its findings.
-4. Right after the review, suggest the next step based on the verdict. These
-   are suggestions — the user decides, and any instruction overrides them:
-   - **Approve** → suggest `/implement-plan` to execute it.
-   - **Request changes** → suggest `/make-a-plan` to make a plan to address the
-     findings.
-
-### Hard rule — read-only while reviewing
-
-This flow is read-only **for the duration of the review**: from the moment it
-starts until the user considers the review finished (including any feedback,
-questions, or clarifications about it). During that period, never fix,
-implement, edit files or create commits — not even "obvious" fixes derived from
-the findings. Once the user explicitly states the review is done (or moves on to
-a different task), this rule no longer applies and you act as a normal build
-agent again.
-
-## Instructions for the subagent
-
-1. Load the **`plan-review-criteria`** skill and follow its process and output
-   format.
-2. Read `AGENTS.md` (if present) and follow its instructions for finding and
-   reading all related documentation and testing memories before reviewing.
-3. Return in your final message the COMPLETE review, verbatim, exactly as the
-   skill instructs it to be produced. Do not summarize it — include the full
-   structured review.
-
-### Strong rules for the subagent
-
-1. Do not invent problems. Every finding must be real and actionable.
-2. Read-only: do not modify any file and do not create a commit — reviewing
-   never writes.
-3. Be specific and constructive. "This could be better" is not helpful — explain
-   why and how.
-4. Prioritize by impact. One structural issue outweighs ten nits.
-5. Judge the plan as the implementer would: every task executable without
-   guessing, ordering follows the dependency graph, risks named.
-
-## User context
-
-Extra context in the user's invocation (the message that triggered this skill)
-plays the role command arguments play elsewhere: for example, a plan file path
-to review, or a different agent to run the review.
@@ -1 +0,0 @@
-../.agents/skills
@@ -1,44 +0,0 @@
-name: _ADHOC
-
-run-name: >-
-  _ADHOC (${{ inputs.gh_ref }}${{ inputs.nitrate_ref != '' && format(' / nitrate:{0}', inputs.nitrate_ref) || '' }})
-
-on:
-  workflow_dispatch:
-    inputs:
-      gh_ref:
-        description: 'Branch/ref to build in penpot/penpot'
-        type: string
-        required: true
-      nitrate_ref:
-        description: 'Branch/ref to build admin-console in penpot/penpot-nitrate (defaults to gh_ref)'
-        type: string
-        required: false
-      force:
-        description: 'Rebuild and overwrite even if already built/promoted'
-        type: boolean
-        required: false
-        default: false
-
-jobs:
-  build-bundle:
-    uses: ./.github/workflows/build-bundle.yml
-    secrets: inherit
-    with:
-      gh_ref: ${{ inputs.gh_ref }}
-      force: ${{ inputs.force }}
-
-  build-docker:
-    needs: build-bundle
-    uses: ./.github/workflows/build-docker.yml
-    secrets: inherit
-    with:
-      gh_ref: ${{ inputs.gh_ref }}
-      force: ${{ inputs.force }}
-
-  build-docker-admin-console:
-    uses: ./.github/workflows/build-docker-admin-console.yml
-    secrets: inherit
-    with:
-      gh_ref: ${{ inputs.nitrate_ref || inputs.gh_ref }}
-      force: ${{ inputs.force }}
@@ -9,11 +9,6 @@ on:
        type: string
        required: true
        default: 'develop'
-      force:
-        description: 'Rebuild and overwrite even if this version already exists in S3'
-        type: boolean
-        required: false
-        default: false
  workflow_call:
    inputs:
      gh_ref:
@@ -21,31 +16,20 @@ on:
        type: string
        required: true
        default: 'develop'
-      force:
-        description: 'Rebuild and overwrite even if this version already exists in S3'
-        type: boolean
-        required: false
-        default: false

-# Literal group name: under `workflow_call`, `github.workflow` resolves to the
-# caller's workflow, which put this workflow and the other reusable one called
-# by the same caller into a single shared group, and left a manual dispatch of
-# the same ref in a group of its own, free to race on the same artifacts.
 concurrency:
-  group: build-bundle-${{ inputs.gh_ref }}
+  group: ${{ github.workflow }}-${{ inputs.gh_ref }}
  cancel-in-progress: true

 jobs:
  # ── 1. Decide whether there is anything to build ───────────────────────
  check:
    name: Check current bundle
-    runs-on: penpot-standar-runner
+    runs-on: penpot-runner-01
    timeout-minutes: 10
    outputs:
      gh_ref: ${{ steps.vars.outputs.gh_ref }}
      bundle_version: ${{ steps.vars.outputs.bundle_version }}
-      sha: ${{ steps.vars.outputs.sha }}
-      commit_title: ${{ steps.vars.outputs.commit_title }}
      exists: ${{ steps.check.outputs.exists }}

    steps:
@@ -60,12 +44,10 @@ jobs:
        run: |
          echo "gh_ref=${{ inputs.gh_ref || github.ref_name }}" >> $GITHUB_OUTPUT
          echo "bundle_version=$(git describe --tags --always)" >> $GITHUB_OUTPUT
-          echo "sha=$(git rev-parse --short=12 HEAD)" >> $GITHUB_OUTPUT
-          echo "commit_title=$(git log -1 --pretty=%s)" >> $GITHUB_OUTPUT

      # The uploaded zip carries its version as S3 metadata. If the
      # existing object was already built from this same commit, the
-      # whole build job is skipped. `force` bypasses this check entirely.
+      # whole build job is skipped.
      - name: Check if this bundle is already built
        id: check
        env:
@@ -73,16 +55,6 @@ jobs:
          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
          AWS_DEFAULT_REGION: ${{ secrets.AWS_REGION }}
        run: |
-          if [ "${{ inputs.force }}" = "true" ]; then
-            echo "exists=false" >> $GITHUB_OUTPUT
-            {
-              echo "### 🔁 Bundle build forced"
-              echo ""
-              echo "\`force: true\` — skipping the S3 version check."
-            } >> "$GITHUB_STEP_SUMMARY"
-            exit 0
-          fi
-
          EXISTING_VERSION=$(aws s3api head-object \
            --bucket ${{ secrets.S3_BUCKET }} \
            --key "penpot-${{ steps.vars.outputs.gh_ref }}.zip" \
@@ -103,7 +75,7 @@ jobs:
  # ── 2. Build and upload, only when needed ──────────────────────────────
  build:
    name: Build and Upload Penpot Bundle
-    runs-on: penpot-standar-runner
+    runs-on: penpot-runner-01
    timeout-minutes: 90
    needs: check
    if: needs.check.outputs.exists == 'false'
@@ -141,20 +113,10 @@ jobs:
            s3://${{ secrets.S3_BUCKET }}/penpot-${{ needs.check.outputs.gh_ref }}.zip \
            --metadata bundle-version=${{ needs.check.outputs.bundle_version }}

-      - name: Write step summary
-        run: |
-          {
-            echo "### ✅ Bundle built"
-            echo ""
-            echo "- Version: \`${{ needs.check.outputs.bundle_version }}\` (\`git describe --tags --always\`)"
-            echo "- Commit: [\`${{ needs.check.outputs.sha }}\`](https://github.com/${{ github.repository }}/commit/${{ needs.check.outputs.sha }}) — ${{ needs.check.outputs.commit_title }}"
-            echo "- Built at: $(date -u +'%Y-%m-%d %H:%M:%S UTC')"
-          } >> "$GITHUB_STEP_SUMMARY"
-
  # ── 3. Single failure notification for the whole workflow ─────────────
  notify:
    name: Notify failure
-    runs-on: penpot-standar-runner
+    runs-on: penpot-runner-01
    timeout-minutes: 5
    needs: [check, build]
    if: failure()
@@ -1,30 +1,16 @@
 name: _DEVELOP

-run-name: >-
-  _DEVELOP (develop @ ${{ github.sha }})
-
 on:
  workflow_dispatch:
-    inputs:
-      force:
-        description: 'Rebuild and overwrite even if already built/promoted'
-        type: boolean
-        required: false
-        default: false
  schedule:
    - cron: '16 5-20 * * 1-5'

-concurrency:
-  group: ${{ github.workflow }}
-  cancel-in-progress: true
-
 jobs:
  build-bundle:
    uses: ./.github/workflows/build-bundle.yml
    secrets: inherit
    with:
      gh_ref: "develop"
-      force: ${{ inputs.force || false }}

  build-docker:
    needs: build-bundle
@@ -32,11 +18,9 @@ jobs:
    secrets: inherit
    with:
      gh_ref: "develop"
-      force: ${{ inputs.force || false }}

-  build-docker-admin-console:
+  build-admin-console-docker:
    uses: ./.github/workflows/build-docker-admin-console.yml
    secrets: inherit
    with:
      gh_ref: "develop"
-      force: ${{ inputs.force || false }}
@@ -13,11 +13,6 @@ on:
        type: string
        required: false
        default: 'develop'
-      force:
-        description: 'Rebuild and overwrite even if already built'
-        type: boolean
-        required: false
-        default: false
  workflow_call:
    inputs:
      gh_ref:
@@ -29,11 +24,6 @@ on:
        type: string
        required: false
        default: 'develop'
-      force:
-        description: 'Rebuild and overwrite even if already built'
-        type: boolean
-        required: false
-        default: false
    secrets:
      ORG_WORKFLOW_TOKEN:
        description: 'Token with Actions write access on penpot-nitrate'
@@ -57,7 +47,6 @@ jobs:

          gh workflow run "$WORKFLOW" --repo "$REPO" --ref "$DISPATCH_REF" \
            -f gh_ref="$GH_REF" \
-            -f force="${{ inputs.force }}" \
            -f caller_run_id="$DISTINCT_ID" \
            -f caller_run_url="$CALLER_URL"

@@ -6,7 +6,7 @@ on:
 jobs:
  build-and-push:
    name: Build and push DevEnv Docker image
-    runs-on: penpot-standar-runner
+    runs-on: penpot-runner-02

    steps:
      - name: Set common environment variables
@@ -8,11 +8,6 @@ on:
        type: string
        required: true
        default: 'develop'
-      force:
-        description: 'Rebuild and overwrite even if this sha is already promoted'
-        type: boolean
-        required: false
-        default: false
  workflow_call:
    inputs:
      gh_ref:
@@ -20,18 +15,9 @@ on:
        type: string
        required: true
        default: 'develop'
-      force:
-        description: 'Rebuild and overwrite even if this sha is already promoted'
-        type: boolean
-        required: false
-        default: false

-# Literal group name: under `workflow_call`, `github.workflow` resolves to the
-# caller's workflow, which put this workflow and the other reusable one called
-# by the same caller into a single shared group, and left a manual dispatch of
-# the same ref in a group of its own, free to race on the same artifacts.
 concurrency:
-  group: build-docker-${{ inputs.gh_ref }}
+  group: ${{ github.workflow }}-${{ inputs.gh_ref }}
  cancel-in-progress: true

 env:
@@ -46,13 +32,12 @@ jobs:
  # ── 1. Resolve the build key and check the whole set at once ───────────
  prepare:
    name: Prepare
-    runs-on: penpot-standar-runner
+    runs-on: penpot-runner-02
    timeout-minutes: 15
    outputs:
      gh_ref: ${{ steps.vars.outputs.gh_ref }}
      bundle_version: ${{ steps.vars.outputs.bundle_version }}
-      sha: ${{ steps.vars.outputs.sha }}
-      commit_title: ${{ steps.vars.outputs.commit_title }}
+      build_key: ${{ steps.vars.outputs.build_key }}
      exists: ${{ steps.check.outputs.exists }}

    steps:
@@ -70,8 +55,6 @@ jobs:
        run: |
          GH_REF="${{ inputs.gh_ref || github.ref_name }}"
          echo "gh_ref=$GH_REF" >> $GITHUB_OUTPUT
-          echo "sha=$(git rev-parse --short=12 HEAD)" >> $GITHUB_OUTPUT
-          echo "commit_title=$(git log -1 --pretty=%s)" >> $GITHUB_OUTPUT

          BUNDLE_VERSION=$(aws s3api head-object \
            --bucket ${{ secrets.S3_BUCKET }} \
@@ -80,11 +63,15 @@ jobs:
            --output text)
          echo "bundle_version=$BUNDLE_VERSION" >> $GITHUB_OUTPUT

+          # Image content = bundle + docker build context, so the build key
+          # combines both.
+          CTX_HASH=$(git rev-parse "HEAD:docker/images" | cut -c1-12)
+          echo "build_key=${BUNDLE_VERSION}-${CTX_HASH}" >> $GITHUB_OUTPUT
+
      # The image set is a single block, so a single set-level check is
      # enough: `promote` drops a marker object in S3 only after every
      # image was built AND every branch tag was moved. Marker present
-      # means there is nothing at all to do for this commit. `force`
-      # bypasses this check entirely.
+      # means there is nothing at all to do for this build key.
      - name: Check if this image set is already built
        id: check
        env:
@@ -92,30 +79,15 @@ jobs:
          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
          AWS_DEFAULT_REGION: ${{ secrets.AWS_REGION }}
        run: |
-          if [ "${{ inputs.force }}" = "true" ]; then
-            echo "exists=false" >> $GITHUB_OUTPUT
-            mkdir -p "$BUNDLE_CACHE"
-            find "$BUNDLE_CACHE" -type f -mtime +1 -delete || true
-            ZIP="$BUNDLE_CACHE/penpot-${{ steps.vars.outputs.bundle_version }}.zip"
-            aws s3 cp "s3://${{ secrets.S3_BUCKET }}/penpot-${{ steps.vars.outputs.gh_ref }}.zip" "$ZIP.$$.tmp"
-            mv "$ZIP.$$.tmp" "$ZIP"
-            {
-              echo "### 🔁 Image set build forced"
-              echo ""
-              echo "\`force: true\` — skipping the S3 marker check."
-            } >> "$GITHUB_STEP_SUMMARY"
-            exit 0
-          fi
-
          if aws s3api head-object \
               --bucket ${{ secrets.S3_BUCKET }} \
-               --key "markers/images-sha-${{ steps.vars.outputs.sha }}" \
+               --key "markers/images-${{ steps.vars.outputs.build_key }}" \
               > /dev/null 2>&1; then
            echo "exists=true" >> $GITHUB_OUTPUT
            {
              echo "### ⏭️ Image set build skipped"
              echo ""
-              echo "The whole set was already built and promoted for \`sha-${{ steps.vars.outputs.sha }}\`."
+              echo "The whole set was already built and promoted for \`${{ steps.vars.outputs.build_key }}\`."
            } >> "$GITHUB_STEP_SUMMARY"
          else
            echo "exists=false" >> $GITHUB_OUTPUT
@@ -125,7 +97,7 @@ jobs:
            # prune stale bundles while at it.
            mkdir -p "$BUNDLE_CACHE"
            find "$BUNDLE_CACHE" -type f -mtime +1 -delete || true
-            ZIP="$BUNDLE_CACHE/penpot-${{ steps.vars.outputs.bundle_version }}.zip"
+            ZIP="$BUNDLE_CACHE/penpot-${{ steps.vars.outputs.build_key }}.zip"
            if [ ! -f "$ZIP" ]; then
              aws s3 cp "s3://${{ secrets.S3_BUCKET }}/penpot-${{ steps.vars.outputs.gh_ref }}.zip" "$ZIP.$$.tmp"
              mv "$ZIP.$$.tmp" "$ZIP"
@@ -135,7 +107,7 @@ jobs:
  # ── 2. One build per image, in parallel, only when needed ──────────────
  build:
    name: Build ${{ matrix.image }}
-    runs-on: penpot-standar-runner
+    runs-on: penpot-runner-02
    timeout-minutes: 60
    needs: prepare
    if: needs.prepare.outputs.exists == 'false'
@@ -166,7 +138,7 @@ jobs:
          username: ${{ secrets.DOCKER_USERNAME }}
          password: ${{ secrets.DOCKER_PASSWORD }}

-      # To avoid the "429 Too Many Requests" error when downloading
+      # To avoid the “429 Too Many Requests” error when downloading
      # images from DockerHub for unregistered users.
      # https://docs.docker.com/docker-hub/usage/
      - name: Login to DockerHub Registry
@@ -197,7 +169,7 @@ jobs:
          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
          AWS_DEFAULT_REGION: ${{ secrets.AWS_REGION }}
        run: |
-          ZIP="$BUNDLE_CACHE/penpot-${{ needs.prepare.outputs.bundle_version }}.zip"
+          ZIP="$BUNDLE_CACHE/penpot-${{ needs.prepare.outputs.build_key }}.zip"
          if [ ! -f "$ZIP" ]; then
            echo "Bundle not found in host cache; falling back to S3."
            mkdir -p "$BUNDLE_CACHE"
@@ -237,7 +209,7 @@ jobs:
          sbom: true
          # Immutable tag only; branch tags are moved atomically for the
          # whole image set by the `promote` job.
-          tags: ${{ secrets.DOCKER_REGISTRY }}/${{ matrix.image }}:sha-${{ needs.prepare.outputs.sha }}
+          tags: ${{ secrets.DOCKER_REGISTRY }}/${{ matrix.image }}:build-${{ needs.prepare.outputs.build_key }}
          labels: ${{ steps.meta.outputs.labels }}
          cache-from: type=registry,ref=${{ secrets.DOCKER_REGISTRY }}/${{ matrix.image }}:buildcache
          cache-to: type=registry,ref=${{ secrets.DOCKER_REGISTRY }}/${{ matrix.image }}:buildcache,mode=max
@@ -248,7 +220,7 @@ jobs:
  # the S3 marker guarantees the branch tags were already moved.
  promote:
    name: Promote image set
-    runs-on: penpot-standar-runner
+    runs-on: penpot-runner-02
    timeout-minutes: 10
    needs: [prepare, build]

@@ -273,7 +245,7 @@ jobs:
          for image in $ALL_IMAGES; do
            docker buildx imagetools create \
              -t "${{ secrets.DOCKER_REGISTRY }}/$image:${{ needs.prepare.outputs.gh_ref }}" \
-              "${{ secrets.DOCKER_REGISTRY }}/$image:sha-${{ needs.prepare.outputs.sha }}"
+              "${{ secrets.DOCKER_REGISTRY }}/$image:build-${{ needs.prepare.outputs.build_key }}"
          done

      # The marker is written LAST: its presence certifies that all five
@@ -285,24 +257,17 @@ jobs:
          AWS_DEFAULT_REGION: ${{ secrets.AWS_REGION }}
        run: |
          echo "${{ github.run_id }}" | aws s3 cp - \
-            "s3://${{ secrets.S3_BUCKET }}/markers/images-sha-${{ needs.prepare.outputs.sha }}"
-
-      - name: Write step summary
-        run: |
+            "s3://${{ secrets.S3_BUCKET }}/markers/images-${{ needs.prepare.outputs.build_key }}"
          {
            echo "### ✅ Image set promoted"
            echo ""
-            echo "- Version: \`${{ needs.prepare.outputs.bundle_version }}\` (\`git describe --tags --always\`)"
-            echo "- Commit: [\`${{ needs.prepare.outputs.sha }}\`](https://github.com/${{ github.repository }}/commit/${{ needs.prepare.outputs.sha }}) — ${{ needs.prepare.outputs.commit_title }}"
-            echo "- Built at: $(date -u +'%Y-%m-%d %H:%M:%S UTC')"
-            echo ""
-            echo "All \`:${{ needs.prepare.outputs.gh_ref }}\` tags now point to \`sha-${{ needs.prepare.outputs.sha }}\`."
+            echo "All \`:${{ needs.prepare.outputs.gh_ref }}\` tags now point to \`build-${{ needs.prepare.outputs.build_key }}\`."
          } >> "$GITHUB_STEP_SUMMARY"

  # ── 4. Single failure notification for the whole workflow ─────────────
  notify:
    name: Notify failure
-    runs-on: penpot-standar-runner
+    runs-on: penpot-runner-02
    timeout-minutes: 5
    needs: [prepare, build, promote]
    if: failure()
@@ -1,30 +1,16 @@
 name: _STAGING

-run-name: >-
-  _STAGING (staging)
-
 on:
  workflow_dispatch:
-    inputs:
-      force:
-        description: 'Rebuild and overwrite even if already built/promoted'
-        type: boolean
-        required: false
-        default: false
  schedule:
    - cron: '36 5-20 * * 1-5'

-concurrency:
-  group: ${{ github.workflow }}
-  cancel-in-progress: true
-
 jobs:
  build-bundle:
    uses: ./.github/workflows/build-bundle.yml
    secrets: inherit
    with:
      gh_ref: "staging"
-      force: ${{ inputs.force || false }}

  build-docker:
    needs: build-bundle
@@ -32,11 +18,9 @@ jobs:
    secrets: inherit
    with:
      gh_ref: "staging"
-      force: ${{ inputs.force || false }}

-  build-docker-admin-console:
+  build-admin-console-docker:
    uses: ./.github/workflows/build-docker-admin-console.yml
    secrets: inherit
    with:
      gh_ref: "staging"
-      force: ${{ inputs.force || false }}
@@ -1,33 +1,17 @@
 name: _TAG

-run-name: >-
-  _TAG (${{ github.ref_name }} @ ${{ github.sha }})
-
 on:
  workflow_dispatch:
-    inputs:
-      force:
-        description: 'Rebuild and overwrite even if already built/promoted (manual re-releases only)'
-        type: boolean
-        required: false
-        default: false
  push:
    tags:
      - '*'

-# Keyed by ref and never cancelling: pushing 2.17.2 shortly after 2.17.2-RC1
-# must not abort the release already in flight.
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref_name }}
-  cancel-in-progress: false
-
 jobs:
  build-bundle:
    uses: ./.github/workflows/build-bundle.yml
    secrets: inherit
    with:
      gh_ref: ${{ github.ref_name }}
-      force: ${{ inputs.force || false }}

  build-docker:
    needs: build-bundle
@@ -35,21 +19,11 @@ jobs:
    secrets: inherit
    with:
      gh_ref: ${{ github.ref_name }}
-      force: ${{ inputs.force || false }}
-
-  build-docker-admin-console:
-    uses: ./.github/workflows/build-docker-admin-console.yml
-    secrets: inherit
-    with:
-      gh_ref: ${{ github.ref_name }}
-      force: ${{ inputs.force || false }}

  notify:
    name: Notifications
-    runs-on: ubuntu-latest
-    needs:
-      - build-docker
-      - build-docker-admin-console
+    runs-on: ubuntu-24.04
+    needs: build-docker
    steps:
      - name: Notify Mattermost
        uses: mattermost/action-mattermost-notify@ae31bb6f9e26a54336e79696f108a2c91cf55b4e # v2.1.0
@@ -63,9 +37,7 @@ jobs:

  publish-final-tag:
    if: ${{ !contains(github.ref_name, '-RC') && !contains(github.ref_name, '-alpha') && !contains(github.ref_name, '-beta')  && contains(github.ref_name, '.') }}
-    needs:
-      - build-docker
-      - build-docker-admin-console
+    needs: build-docker
    uses: ./.github/workflows/release.yml
    secrets: inherit
    with:
@@ -1,24 +0,0 @@
-name: _TMP TOKENS
-
-on:
-  workflow_dispatch:
-  schedule:
-    - cron: '46 5-20 * * 1-5'
-
-concurrency:
-  group: ${{ github.workflow }}
-  cancel-in-progress: true
-
-jobs:
-  build-bundle:
-    uses: ./.github/workflows/build-bundle.yml
-    secrets: inherit
-    with:
-      gh_ref: "hiru-tokens-in-libs"
-
-  build-docker:
-    needs: build-bundle
-    uses: ./.github/workflows/build-docker.yml
-    secrets: inherit
-    with:
-      gh_ref: "hiru-tokens-in-libs"
@@ -34,7 +34,7 @@ permissions:

 jobs:
  deploy:
-    runs-on: penpot-standar-runner
+    runs-on: penpot-runner-01
    steps:
      - name: Checkout
        uses: actions/checkout@v6
@@ -19,7 +19,7 @@ permissions:

 jobs:
  release:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
    outputs:
      version: ${{ steps.vars.outputs.gh_ref }}
      release_notes: ${{ steps.extract_release_notes.outputs.release_notes }}
@@ -32,7 +32,7 @@ jobs:
  test-backend:
    if: ${{ !github.event.pull_request.draft }}
    name: "Backend Tests"
-    runs-on: penpot-extended-runner
+    runs-on: penpot-runner-02
    container:
      image: penpotapp/devenv:latest
      volumes:
@@ -30,7 +30,7 @@ jobs:
  test-common:
    if: ${{ !github.event.pull_request.draft }}
    name: "Common Tests"
-    runs-on: penpot-extended-runner
+    runs-on: penpot-runner-02
    container:
      image: penpotapp/devenv:latest
      volumes:
@@ -38,7 +38,7 @@ jobs:
  composable-test-suite:
    if: ${{ !github.event.pull_request.draft }}
    name: "Run composable test suite (mocked backend)"
-    runs-on: penpot-extended-runner
+    runs-on: penpot-runner-02
    container:
      image: penpotapp/devenv:latest
      volumes:
@@ -32,7 +32,7 @@ jobs:
  test-exporter:
    if: ${{ !github.event.pull_request.draft }}
    name: "Exporter Tests"
-    runs-on: penpot-extended-runner
+    runs-on: penpot-runner-02
    container:
      image: penpotapp/devenv:latest
      volumes:
@@ -34,7 +34,7 @@ jobs:
  test-frontend:
    if: ${{ !github.event.pull_request.draft }}
    name: "Frontend Tests"
-    runs-on: penpot-extended-runner
+    runs-on: penpot-runner-02
    container:
      image: penpotapp/devenv:latest
      volumes:
@@ -5,37 +5,11 @@ defaults:
    shell: bash

 on:
-  workflow_dispatch:
-    inputs:
-      gh_ref:
-        description: 'Name of the branch or ref'
-        type: string
-        required: true
-        default: 'develop'
-
-      shards:
-        description: 'Shard layout (JSON array)'
-        type: choice
-        required: true
-        default: '[1, 2, 3, 4]'
-        options:
-          - '[1, 2, 3, 4]'
-          - '[1, 2, 3, 4, 5, 6]'
-          - '[1, 2]'
-          - '[1]'
-
-      workers:
-        description: 'Playwright workers per shard'
-        type: string
-        required: true
-        default: '2'
-
  pull_request:
    paths:
      - 'frontend/**'
      - 'common/**'
      - 'render-wasm/**'
-      - '.github/workflows/tests-integration.yml'

    types:
      - opened
@@ -51,41 +25,25 @@ on:
      - 'frontend/**'
      - 'common/**'
      - 'render-wasm/**'
-      - '.github/workflows/tests-integration.yml'

 concurrency:
-  group: ${{ github.workflow }}-${{ github.event.pull_request.number || inputs.gh_ref || github.ref }}
+  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
  cancel-in-progress: true

 jobs:
  build-integration:
    if: ${{ !github.event.pull_request.draft }}
    name: "Build Integration Bundle"
-    runs-on: penpot-extended-runner
-    timeout-minutes: 30
+    runs-on: penpot-runner-02
    container:
      image: penpotapp/devenv:latest
      volumes:
        - /var/cache/github-runner/m2:/root/.m2
        - /var/cache/github-runner/gitlib:/root/.gitlibs

-    outputs:
-      bundle_key: ${{ steps.vars.outputs.bundle_key }}
-
    steps:
-      # An empty `ref` makes checkout fall back to its default (the PR merge
-      # ref on pull_request, the pushed ref on push).
      - name: Checkout repository
        uses: actions/checkout@v6
-        with:
-          ref: ${{ inputs.gh_ref }}
-
-      # The cache key must come from the SHA actually checked out: on a manual
-      # run `github.sha` points at the dispatching ref, not at `gh_ref`.
-      - name: Extract cache key
-        id: vars
-        run: |
-          echo "bundle_key=integration-bundle-$(git rev-parse HEAD)" >> $GITHUB_OUTPUT

      - name: Build Bundle
        working-directory: ./frontend
@@ -95,142 +53,58 @@ jobs:
      - name: Store Bundle Cache
        uses: actions/cache@v5
        with:
-          key: ${{ steps.vars.outputs.bundle_key }}
+          key: "integration-bundle-${{ github.sha }}"
          path: frontend/resources/public

  test-integration:
    if: ${{ !github.event.pull_request.draft }}
-    name: "Integration Tests (${{ matrix.shard }})"
-    runs-on: penpot-extended-runner
-    timeout-minutes: 40
-
-    needs: build-integration
-
-    strategy:
-      fail-fast: false
-      matrix:
-        shard: ${{ fromJSON(inputs.shards || '[1, 2, 3, 4]') }}
-
+    name: "Integration Tests"
+    runs-on: penpot-runner-02
    container:
      image: penpotapp/devenv:latest
      volumes:
        - /var/cache/github-runner/m2:/root/.m2
        - /var/cache/github-runner/gitlib:/root/.gitlibs
-        - /var/cache/github-runner/ms-playwright:/ms-playwright
-      env:
-        PLAYWRIGHT_BROWSERS_PATH: /ms-playwright
+
+    needs: build-integration

    steps:
      - name: Checkout Repository
        uses: actions/checkout@v6
-        with:
-          ref: ${{ inputs.gh_ref }}

      - name: Restore Cache
        uses: actions/cache/restore@v5
        with:
-          key: ${{ needs.build-integration.outputs.bundle_key }}
+          key: "integration-bundle-${{ github.sha }}"
          path: frontend/resources/public

-      - name: Install deps
-        working-directory: ./frontend
-        run: |
-          corepack enable;
-          corepack install;
-          pnpm install --frozen-lockfile;
-
-      # No-op once the shared volume is warm; keeps the first run working.
-      - name: Install Playwright Chromium
-        working-directory: ./frontend
-        run: pnpm exec playwright install chromium
-
-      # `strategy.job-total` is the matrix size, so the shard denominator
-      # follows the `shards` input without being hardcoded.
      - name: Run Tests
        working-directory: ./frontend
        env:
-          WORKERS: ${{ inputs.workers }}
-        run: |
-          WORKERS=${WORKERS:-2}
-          echo "Running shard ${{ matrix.shard }}/${{ strategy.job-total }} with $WORKERS workers"
-          pnpm exec playwright test --project default \
-            --workers="$WORKERS" \
-            --shard=${{ matrix.shard }}/${{ strategy.job-total }} \
-            --reporter=blob
-
-      - name: Upload blob report
-        uses: actions/upload-artifact@v7
-        if: always()
-        with:
-          name: integration-blob-report-${{ matrix.shard }}
-          path: frontend/blob-report/
-          overwrite: true
-          retention-days: 3
-
-      - name: Upload test result
-        uses: actions/upload-artifact@v7
-        if: always()
-        with:
-          name: integration-tests-result-${{ matrix.shard }}
-          path: frontend/test-results/
-          overwrite: true
-          if-no-files-found: ignore
-          retention-days: 3
-
-  merge-reports:
-    if: ${{ always() && !github.event.pull_request.draft && needs.test-integration.result != 'skipped' }}
-    name: "Merge Integration Reports"
-    runs-on: penpot-extended-runner
-    timeout-minutes: 15
-
-    needs: test-integration
-
-    container:
-      image: penpotapp/devenv:latest
-      volumes:
-        - /var/cache/github-runner/m2:/root/.m2
-        - /var/cache/github-runner/gitlib:/root/.gitlibs
-
-    steps:
-      - name: Checkout Repository
-        uses: actions/checkout@v6
-        with:
-          ref: ${{ inputs.gh_ref }}
-
-      - name: Install deps
-        working-directory: ./frontend
-        run: |
-          corepack enable;
-          corepack install;
-          pnpm install --frozen-lockfile;
-
-      - name: Download blob reports
-        uses: actions/download-artifact@v7
-        with:
-          path: frontend/all-blob-reports
-          pattern: integration-blob-report-*
-          merge-multiple: true
-
-      - name: Merge into HTML report
-        working-directory: ./frontend
-        env:
+          PLAYWRIGHT_REPORTER: list,json
          PLAYWRIGHT_JSON_OUTPUT_NAME: report.json
        run: |
-          pnpm exec playwright merge-reports \
-            --reporter=html,json,list ./all-blob-reports
+          ./scripts/test-e2e

-      - name: Test summary
+      - name: Flaky summary
        if: always()
        working-directory: ./frontend
        run: |
          if [ ! -f report.json ]; then
-            echo "No report produced (all shards failed early)." >> "$GITHUB_STEP_SUMMARY"
+            echo "No report.json produced (the run failed early)." >> "$GITHUB_STEP_SUMMARY"
            exit 0
          fi
-          jq -r -f ../.github/scripts/playwright-summary.jq report.json >> "$GITHUB_STEP_SUMMARY"

-      # Kept for 30 days so flakiness rates can be aggregated across runs
-      # without scraping job logs.
+          jq -r '
+            [ .. | objects
+              | select(has("tests") and has("file"))
+              | select(any(.tests[]; .status == "flaky"))
+              | "- `\(.file):\(.line)` — \(.title)"
+            ] as $f
+            | "## Flaky tests: \($f | length)\n"
+              + (if ($f | length) == 0 then "_none_" else ($f | join("\n")) end)
+          ' report.json >> "$GITHUB_STEP_SUMMARY"
+
      - name: Upload JSON report
        uses: actions/upload-artifact@v7
        if: always()
@@ -238,13 +112,13 @@ jobs:
          name: integration-json-report
          path: frontend/report.json
          overwrite: true
-          if-no-files-found: ignore
          retention-days: 30

-      - name: Upload HTML report
+      - name: Upload test result
        uses: actions/upload-artifact@v7
+        if: always()
        with:
-          name: integration-html-report
-          path: frontend/playwright-report/
+          name: integration-tests-result
+          path: frontend/test-results/
          overwrite: true
-          retention-days: 7
+          retention-days: 3
@@ -32,7 +32,7 @@ jobs:
  test-library:
    if: ${{ !github.event.pull_request.draft }}
    name: "Library Tests"
-    runs-on: penpot-extended-runner
+    runs-on: penpot-runner-02
    container:
      image: penpotapp/devenv:latest
      volumes:
@@ -28,7 +28,7 @@ jobs:
  test-mcp:
    if: ${{ !github.event.pull_request.draft }}
    name: "Test MCP"
-    runs-on: penpot-extended-runner
+    runs-on: penpot-runner-02
    container: penpotapp/devenv:latest

    steps:
@@ -53,7 +53,7 @@ jobs:
  api-test-suite-mocked:
    if: ${{ github.event_name != 'workflow_dispatch' && !github.event.pull_request.draft }}
    name: "Run Plugin API Test Suite (mocked)"
-    runs-on: penpot-extended-runner
+    runs-on: penpot-runner-02
    container:
      image: penpotapp/devenv:latest
      volumes:
@@ -95,7 +95,7 @@ jobs:
  # api-test-suite-live:
  #   if: ${{ github.event_name == 'workflow_dispatch' }}
  #   name: Run Plugin API Test Suite (live)
-  #   runs-on: penpot-extended-runner
+  #   runs-on: penpot-runner-02
  #   container:
  #     image: penpotapp/devenv:latest
  # 
@@ -30,7 +30,7 @@ jobs:
  test-plugins:
    if: ${{ !github.event.pull_request.draft }}
    name: Plugins Runtime Linter & Tests
-    runs-on: penpot-extended-runner
+    runs-on: penpot-runner-02
    container:
      image: penpotapp/devenv:latest
      volumes:
@@ -30,7 +30,7 @@ jobs:
  test-render-wasm:
    if: ${{ !github.event.pull_request.draft }}
    name: "Render WASM Tests"
-    runs-on: penpot-extended-runner
+    runs-on: penpot-runner-02
    container:
      image: penpotapp/devenv:latest
      volumes:
@@ -97,11 +97,10 @@ opencode.json
 /.idea
 *.iml
 /.claude
-/CLAUDE.md
 /.playwright-mcp
 /.devenv/mcp/
 /opencode.json
-/.agents/plans
+/.opencode/plans
 /.opencode/reports
 /.opencode/prompts
 /.ci-logs
@@ -1,10 +0,0 @@
---
-description: Create a PR for the current task branch or update an existing one — loads and follows the create-pr skill
-agent: build
---
-
-Load the **`create-pr`** skill and follow it as your only instruction.
-
-## User input, overrides and additional context
-
-$ARGUMENTS
@@ -1,10 +1,42 @@
 ---
-description: Execute a ready plan — task checklist, your confirmation, then all tasks with one commit (default) or step by step with a commit and a pause per task; creates issue + branch when on a base branch, or commits on the current branch with "direct" — loads and follows the implement-plan skill
+description: Execute a ready plan end-to-end — create a GitHub issue, branch issue-NNNN, implement the plan, then commit via the create-commit skill
 agent: build
 ---

-Load the **`implement-plan`** skill and follow it as your only instruction.
+# Implement Plan

-## User input, overrides and additional context
+This command is run once a plan is ready (for example, from plan mode). Execute
+the plan already prepared in the current session context — it does not take
+extra arguments. Follow these steps in order.

-$ARGUMENTS
+## 1. Create the issue
+
+Use the **`create-issue`** skill, following the *Creating Issues from Draft Body*
+flow in `mem:workflow/creating-issues`. Derive the issue title and body from the
+plan. Capture the new issue's number — call it **NNNN** (needed for the branch
+name and the commit reference).
+
+## 2. Create the branch
+
+Create and switch to a branch named after the issue:
+
+```
+git checkout -b issue-NNNN
+```
+
+(Replace NNNN with the issue number from step 1.)
+
+## 3. Execute the plan
+
+Implement the prepared plan from the session context. Work methodically, keeping
+changes focused on what the issue requires. Do not commit — the commit happens in
+step 4.
+
+## 4. Commit with the create-commit skill
+
+After the implementation is complete, load the **`create-commit`** skill and
+follow its workflow to commit the changes. Provide a brief summary of what was
+implemented and why, the issue reference (`issue-NNNN`), and the model name you
+are running as so the `AI-assisted-by` trailer is set correctly.
+
+Do not push. Pushing is handled separately by the user.
@@ -1,10 +0,0 @@
---
-description: Investigate the chosen task, produce an implementation plan, and save it — loads and follows the make-a-plan skill
-agent: build
---
-
-Load the **`make-a-plan`** skill and follow it as your only instruction.
-
-## User input, overrides and additional context
-
-$ARGUMENTS
@@ -1,6 +1,40 @@
 ---
-description: Resolve local git conflicts and stage the resolved files; never continues the rebase — loads and follows the resolve-git-conflicts skill
+description: Resolve local git conflicts and stage the resolved files with git add — never continues the rebase
 agent: build
 ---

-Load the **`resolve-git-conflicts`** skill and follow it as your only instruction.
+# Fix Git Conflicts
+
+Resolve conflicts in the local repository. The user handles finishing the
+rebase themselves — you must **never** run `git rebase --continue`,
+`git rebase --skip`, `git merge --continue`, or anything similar.
+
+## Phase 1 — Understand the problem (read-only)
+
+1. Run `git status` to detect the conflict state (rebase, merge, cherry-pick, etc.) and list conflicted files.
+2. For each conflicted (unmerged) file, understand the situation **without modifying anything**:
+   - Read the file and identify the conflict markers (`<<<<<<<`, `=======`, `>>>>>>>`).
+   - Inspect both sides — `git show <ours>:<file>` and `git show <theirs>:<file>` — plus `git log`/`git show` on the commits involved to understand intent.
+   - Identify what each side changed and why, and how they should be combined.
+
+## Phase 2 — Present the resolution plan
+
+3. **Present a clear plan to the user before touching any file.** For each conflicted file, state:
+   - What each side changed and why.
+   - Your proposed resolution and the reasoning behind it.
+   - How the two sides are combined (both additive → merge; both modify the same code → keep the semantically correct version, merging intent from both sides when clear from code and context).
+4. **Ask the user only when genuinely unclear.** Do not ask about anything you can determine yourself from the code, commit messages, or context. Only decisions that are not determinable and change the outcome (e.g. conflicting product decisions, which side to discard) warrant a question. **Collect all such questions together in an "Open Questions" section at the end of the plan**, so the user has full context to answer them properly.
+5. **Wait for the user to accept the plan** (and answer any open questions) before editing, staging, or otherwise modifying anything.
+
+## Phase 3 — Execute
+
+6. Resolve each conflicted file by editing the file to the agreed merged content and removing all conflict markers.
+
+## Phase 4 — Stage and verify
+
+7. **Stage every resolved file** with `git add <file>`. Do not stage unrelated untracked files unless clearly part of the resolution.
+8. Verify no conflict markers remain (search for `<<<<<<<` / `>>>>>>>` in resolved files) and that `git status` shows no unmerged paths.
+
+## Phase 5 — Report
+
+9. Briefly report the conflict state, how each conflicted file was resolved (and any answers received to open questions), and stop — do **not** run `git rebase --continue` or any other continuation command.
@@ -1,10 +0,0 @@
---
-description: Code review — review a diff, PR, or code change — loads and follows the review-code skill
-agent: build
---
-
-Load the **`review-code`** skill and follow it as your only instruction.
-
-## User input, overrides and additional context
-
-$ARGUMENTS
@@ -1,10 +0,0 @@
---
-description: Plan review — evaluate an implementation plan before executing it — loads and follows the review-plan skill
-agent: build
---
-
-Load the **`review-plan`** skill and follow it as your only instruction.
-
-## User input, overrides and additional context
-
-$ARGUMENTS
@@ -0,0 +1,25 @@
+Act as a senior software engineer and perform a thorough review.
+
+## Instructions
+
+1. **Determine what is being reviewed** from the provided context:
+   - **If it is a plan** (implementation plan, design document, task breakdown) → load the **`plan-review`** skill.
+   - **If it is code** (diff, PR, code change) → load the **`code-review`** skill.
+
+2. Read `AGENTS.md` and follow its instructions for finding and reading all related testing documentation from memories before reviewing.
+
+3. **Skip generated files, lockfile-only changes, and unrelated modifications** unless they introduce security risks.
+
+4. Follow the loaded skill's process and produce its output format.
+
+## Strong Rules
+
+1. Do not invent problems. Every finding must be real and actionable.
+2. Do not modify any code and do not create a commit — this command only reviews.
+3. Be specific and constructive. "This could be better" is not helpful — explain why and how.
+4. Prioritize by impact. One structural issue outweighs ten nits.
+5. Missing tests are an issue, not a suggestion. Report as a severity-tagged finding — never as a recommendation.
+
+## Context
+
+$ARGUMENTS
@@ -9,11 +9,6 @@ metadata: {"clawdbot":{"emoji":"🦇","requires":{"bins":["bat"]},"install":[{"i

 `cat` with syntax highlighting, line numbers, and Git integration.

-## When to use
-
- Reading or displaying a file in the terminal — prefer it over plain
-  `cat`: syntax highlighting, line numbers, git-side indicators.
-
 ## Quick Start

 ### Basic usage
@@ -1,9 +1,9 @@
 ---
-name: code-review-criteria
-description: Code review criteria — the five review axes, core principles, severity format, and verdict for reviewing code changes. Loaded by the reviewer subagent of the review-code flow. Not a user-facing flow — to review code, use the review-code flow.
+name: code-review
+description: Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
 ---

-# Code Review Criteria and Quality
+# Code Review and Quality

 ## Overview

@@ -13,10 +13,11 @@ Multi-dimensional code review with quality gates. Every change gets reviewed bef

 ## When to Use

- The reviewer subagent of the `review-code` flow loads this skill to perform
-  the review of a code change.
- To review code, always go through the `review-code` flow — never load this
-  skill directly for that. This is the criteria reference, not the flow.
+- Before merging any PR or change
+- After completing a feature implementation
+- When another agent or model produced code you need to evaluate
+- When refactoring existing code
+- After any bug fix (review both the fix and the regression test)

 ## Core Principles

@@ -105,8 +106,6 @@ For detailed security guidance, see `security-and-hardening`.
 | **Low:** | Minor, optional | Author may ignore — formatting, style preferences |
 | **Suggestion:** | Worth considering | Not required, but improves the code |

-**Unique finding IDs.** Assign every finding a stable identifier: `F1`, `F2`, `F3`, … numbered in order of severity (Critical first, then High, Medium, Low, Suggestion). Use the ID everywhere the finding is mentioned — in section headers, in the verdict, in follow-up discussion. Never renumber within a review. Example: `**F3 (High)** — `app/validate.cljs:42` — duplicate branch logic…`.
-
 For each finding, describe the circumstances under which it could fail: specific inputs, load conditions, timing, or user actions that trigger the problem. "This crashes when input is null" is actionable; "this might crash" is not.

 Lead with what matters: correctness and security first, then structural issues, then everything else. A few high-conviction comments beat a long list.
@@ -123,11 +122,11 @@ Briefly explain what the code does and give an overall assessment.

 ### Critical and High-Priority Issues

-List problems that could cause security incidents, data loss, crashes, incorrect behavior, or major performance degradation. Each finding gets its unique ID (`F1`, `F2`, …). For each: state the severity, identify the file/function/code section, explain why it's a problem, describe failure circumstances, and provide a concrete improvement with corrected code when useful.
+List problems that could cause security incidents, data loss, crashes, incorrect behavior, or major performance degradation. For each: state the severity, identify the file/function/code section, explain why it's a problem, describe failure circumstances, and provide a concrete improvement with corrected code when useful.

 ### Other Findings

-List medium- and low-priority issues, including maintainability and design concerns. Continue the ID sequence started above (`F3`, `F4`, …).
+List medium- and low-priority issues, including maintainability and design concerns.

 ### Suggested Refactoring

@@ -149,8 +148,6 @@ Choose one:
 - **Approve with minor changes** — Good to merge after addressing low/medium issues
 - **Request changes** — Critical or high issues must be resolved before merge

-List the finding IDs the verdict depends on (e.g. "Request changes: F1, F4").
-
 ## Change Sizing

 Small, focused changes are easier to review, faster to merge, and safer to deploy.
@@ -234,13 +231,25 @@ For supply-chain risk triage, follow the `security-and-hardening` skill.

 ## Verification

-Before emitting the verdict, verify the change as it stands. This is the reviewer's own due diligence — it covers the state of the code at review time, not the later resolution of findings (fixing findings is the author's job; confirming them is a new review):
+After review is complete:

- [ ] Tests pass — run them yourself, don't trust the claim
+- [ ] All Critical issues are resolved
+- [ ] All Required (no-prefix) changes are resolved or explicitly deferred with justification
+- [ ] Tests pass
 - [ ] Build succeeds
 - [ ] The verification story is documented (what changed, how it was verified)
 - [ ] Dependency upgrades reviewed against changelog, isolated per package, verified by green suite

+## Multi-Model Review Pattern
+
+Use different models for different review perspectives:
+
+```
+Model A writes the code → Model B reviews → Model A addresses feedback → Human makes the final call
+```
+
+Different models have different blind spots.
+
 ## See Also

 - For detailed security review guidance, see `security-and-hardening`
@@ -0,0 +1,39 @@
+---
+name: create-pr
+description: Create or update a GitHub PR following Penpot conventions.
+---
+
+# Skill: create-pr
+
+Create or update a GitHub PR. Read and follow:
+- `mem:workflow/creating-prs` — title format, description structure, writing principles
+- `mem:workflow/creating-commits` — commit type emojis
+
+## When to Use
+
+- Creating a new PR from a feature branch
+- Updating an existing PR's title or description to match conventions
+
+## Prerequisites
+
+- `gh` CLI authenticated (`gh auth status`)
+
+## Commands
+
+**Create:**
+
+```bash
+gh pr create --repo penpot/penpot --title "<TITLE>" --body-file /tmp/pr-body.md
+```
+
+**Update:**
+
+```bash
+gh pr edit <NUMBER> --repo penpot/penpot --title "<TITLE>" --body-file /tmp/pr-body.md
+```
+
+**Verify:**
+
+```bash
+gh pr view <NUMBER> --repo penpot/penpot --json title,body
+```
@@ -9,11 +9,6 @@ metadata: {"clawdbot":{"emoji":"📂","requires":{"bins":["fd"]},"install":[{"id

 User-friendly alternative to `find` with smart defaults.

-## When to use
-
- Locating files or directories by name or pattern — prefer it over
-  plain `find`: simpler syntax, smart defaults, respects `.gitignore`.
-
 ## Quick Start

 ### Basic search
@@ -9,11 +9,6 @@ metadata: {"clawdbot":{"emoji":"🔍","requires":{"bins":["jq"]},"install":[{"id

 Process, filter, and transform JSON data with jq.

-## When to use
-
- Parsing, filtering, or transforming JSON from commands, files, or API
-  responses — slicing, reshaping, or validating JSON output.
-
 ## Quick Examples

 ### Basic filtering
@@ -10,12 +10,6 @@ Evaluate Clojure (or ClojureScript) code via a running nREPL server using

 Full documentation: `mem:scripts/nrepl-eval` (file: `.serena/memories/scripts/nrepl-eval.md`)

-## When to use
-
- Evaluating Clojure or ClojureScript code against the running nREPL
-  sessions (backend 6064, frontend 3447) — live inspection, patching, or
-  debugging.
-
 ## Quick Reference

 ```bash
@@ -1,9 +1,9 @@
 ---
-name: plan-review-criteria
-description: Plan review criteria — the six review axes, severity rubric, approval standard, and output format for reviewing implementation plans. Loaded by the reviewer subagent of the review-plan flow. Not a user-facing flow — to review a plan, use the review-plan flow.
+name: plan-review
+description: Reviews implementation plans for quality, completeness, and actionability. Use after a plan is produced by the planner skill, before starting implementation. Use when evaluating a plan written by yourself, another agent, or a human.
 ---

-# Plan Review Criteria
+# Plan Review

 ## Overview

@@ -13,10 +13,10 @@ Multi-dimensional plan review with quality gates. Every plan gets reviewed befor

 ## When to Use

- The reviewer subagent of the `review-plan` flow loads this skill to perform
-  the review of a plan.
- To review a plan, always go through the `review-plan` flow — never load this
-  skill directly for that. This is the criteria reference, not the flow.
+- After the planner skill produces a plan
+- Before starting implementation on any non-trivial task
+- When reviewing a plan written by another agent or a human
+- When a plan feels too large, vague, or risky to start

 **Do NOT use for:** Single-file changes with obvious scope, or when the task is trivial enough to just do.

@@ -87,7 +87,7 @@ Can an implementer actually execute this?

 ### 6. Proposed Code Quality *(when the plan includes implementation details)*

-If the plan proposes code shapes, function signatures, data structures, or API designs, evaluate those proposals against `code-review-criteria`:
+If the plan proposes code shapes, function signatures, data structures, or API designs, evaluate those proposals against `code-review` criteria:

 - **Correctness:** Do the proposed types/signatures handle edge cases (null, empty, boundaries)?
 - **Readability:** Are proposed names descriptive and consistent with project conventions?
@@ -215,7 +215,7 @@ Check that the plan can actually confirm it worked:
 If the plan includes code snippets, types, or API designs:

 ```
- Load code-review-criteria skill for criteria
+- Load code-review skill for criteria
 - Check proposed signatures for edge cases
 - Verify naming follows project conventions
 - Confirm abstractions follow existing patterns
@@ -310,6 +310,6 @@ If the plan includes code snippets, types, or API designs:
 ## See Also

 - For producing plans, use the `planner` skill
- For reviewing implemented code, use `code-review-criteria` — also the criteria source for axis 6
+- For reviewing implemented code, use `code-review` — also the criteria source for axis 6
 - For security-specific concerns, see `security-and-hardening`
 - For testing strategy guidance, see `testing`
@@ -0,0 +1,271 @@
+---
+name: planner
+description: Read-only planning and architecture analysis for Penpot — produce a structured implementation plan (Context, Affected modules, Approach, Risks, Testing). Always output to the user; additionally save to .opencode/plans/YYYY-MM-DD-<title>.md.
+---
+
+# Planner
+
+Read-only senior software architect role for Penpot. Produces structured
+implementation plans that engineers or other agents can execute. Never writes
+or modifies code.
+
+## When to Use
+
+- The user asks for a plan, design, or analysis of a feature or bug.
+- The user wants to understand which parts of the codebase a task will touch.
+- The user needs a step-by-step implementation plan with file paths, function
+  names, and test strategy.
+- The user asks "how would I implement X?" or "what's involved in fixing Y?".
+- The user is about to start non-trivial work and wants a bite-sized task
+  breakdown.
+
+Do **not** use this skill to actually implement anything — it is read-only.
+
+## Role
+
+You are a Senior Software Architect working on Penpot, an open-source design
+tool. Your sole responsibility is planning and analysis — you do NOT write or
+modify code.
+
+You help users understand the codebase, design solutions, and create detailed
+implementation plans that other agents or developers can execute. Document
+everything they need to know: which files to touch for each task, code patterns,
+tests, and how to verify correctness. Apply DRY and KISS principles.
+
+Do **not** suggest commit messages or commit names anywhere in your plans or
+responses — committing is the developer's responsibility.
+
+## Required Reading Before Planning
+
+Before drafting any plan, work through the project's own guidance:
+
+1. Read `critical-info` (`.serena/memories/critical-info.md`) — the entry point
+   that describes the monorepo structure and module dependency graph.
+2. From `critical-info`, identify which modules your task affects.
+3. Read each affected module's core memory, e.g. `mem:frontend/core`,
+   `mem:backend/core`, `mem:common/core`, `mem:exporter/core`,
+   `mem:render-wasm/core`. Follow `mem:` references deeper as needed.
+4. For each affected module, note its lint, format, and test commands so the
+   plan can include concrete verification steps.
+
+Skipping this step is the #1 cause of incorrect or incomplete plans.
+
+## The Planning Process
+
+### Phase 1: Architecture Analysis
+
+1. Read the spec, requirements, or feature request.
+2. Analyze the codebase architecture and identify affected modules.
+3. Read project conventions (starting with `critical-info` and module core
+   memories) before drafting.
+4. Map dependencies between components (see the dependency graph in
+   `critical-info`).
+5. Identify risks, edge cases, performance implications, and breaking changes.
+
+### Phase 2: Task Breakdown
+
+Implementation order follows the monorepo's dependency graph:
+`frontend -> common`, `backend -> common`, `exporter -> common`,
+`frontend -> render-wasm`. Build shared foundations first, then layer
+consumers on top.
+
+#### Slice Vertically
+
+Instead of building all of common, then all of backend, then all of frontend —
+build one complete feature path at a time:
+
+```
+Task 1: common data types + schema             ← foundation
+Task 2: backend RPC handler + persistence
+Task 3: frontend UI component + API integration
+```
+
+Each vertical slice delivers working, testable functionality.
+
+#### Write Tasks
+
+Each task follows this structure:
+
+```markdown
+## Task [N]: [Short descriptive title]
+
+**Description:** One paragraph explaining what this task accomplishes.
+
+**Acceptance criteria:**
+- [ ] [Specific, testable condition]
+- [ ] [Specific, testable condition]
+
+**Verification:**
+- [ ] Tests pass (module-specific test command)
+- [ ] Lint/formatter passes (module-specific check command)
+
+**Dependencies:** [Task numbers this depends on, or "None"]
+
+**Files likely touched:**
+- `path/to/file.clj`
+- `path/to/file_test.clj`
+```
+
+Replace "module-specific test command" with the actual commands for the module
+(e.g. `clojure -M:dev:test` for backend/common, `npx shadow-cljs compile test && npx karma start` for frontend,
+or the commands noted in the module's core memory).
+
+#### Estimate Scope
+
+| Size | Files | Scope |
+|------|-------|-------|
+| **XS** | 1 | Single function, config change, or schema tweak |
+| **S** | 1-2 | One handler or component method |
+| **M** | 3-5 | One vertical feature slice |
+| **L** | 5-8 | Multi-component feature |
+| **XL** | 8+ | **Too large — break it down further** |
+
+If a task is L or larger, break it into smaller tasks. Agents perform best on
+S and M tasks.
+
+**When to break a task down further:**
+- It would take more than one focused session
+- You cannot describe the acceptance criteria in 3 or fewer bullet points
+- It touches two or more independent subsystems
+- You find yourself writing "and" in the task title (a sign it is two tasks)
+
+#### Order and Checkpoints
+
+Arrange tasks so that:
+
+1. Dependencies are satisfied (build foundation first)
+2. Each task leaves the system in a working state
+3. Verification checkpoints occur after every 2-3 tasks
+4. High-risk tasks are early (fail fast)
+
+Add explicit checkpoints with the relevant module commands:
+
+```markdown
+## Checkpoint: After Tasks 1-3
+- [ ] All tests pass (module-specific command)
+- [ ] Lint/format passes (module-specific command)
+- [ ] Core flow works end-to-end
+- [ ] Review with human before proceeding
+```
+
+## Requirements
+
+- Analyze the codebase architecture and identify affected modules.
+- Read project conventions before drafting (start with `critical-info` and
+  affected module core memories).
+- Break down complex features or bugs into atomic, actionable steps.
+- Propose solutions with clear rationale, trade-offs, and sequencing.
+- Identify risks, edge cases, performance implications, and breaking changes.
+- Apply DRY and KISS principles to the proposed implementation.
+- Define a testing strategy aligned with each affected module's tooling.
+- Every task must have acceptance criteria and verification steps.
+- Checkpoints must exist between major phases.
+
+## Constraints
+
+- You are **analysis-only** — never create, edit, or delete source code.
+- The only file write you may attempt is the plan itself, saved to
+  `.opencode/plans/`.
+- You do **not** run builds, tests, linters, or any commands that modify state.
+- You do **not** create git commits or interact with version control.
+- You do **not** execute shell commands beyond read-only searches.
+- Your output is a structured plan or analysis, ready for handoff to an
+  engineer agent or developer.
+
+## Output Format
+
+The plan is always delivered in the response so the user sees it regardless
+of which agent is running the skill.
+
+Additionally, save the plan to:
+
+```
+.opencode/plans/YYYY-MM-DD-<plan-one-line-title>.md
+```
+
+Use today's date in the user's local timezone. The `<plan-one-line-title>`
+slug is lowercase, hyphen-separated, and a short summary of the task
+(e.g. `add-batch-get-profiles-for-file-comments`). Create the
+`.opencode/plans/` directory if it does not exist.
+
+Always attempt the write. If the user explicitly provides a target file path,
+use that path instead of the default.
+
+### Plan Document Template
+
+```markdown
+# Plan: [Feature/Project Name]
+
+## Context
+[One paragraph: what is the problem or feature request? Why is it needed?]
+
+## Affected Modules
+[Which modules of the monorepo are involved? Reference module paths and any
+`mem:` memories that were consulted.]
+
+## Architecture Decisions
+- [Key decision 1 and rationale]
+- [Key decision 2 and rationale]
+
+## Risks & Considerations
+[Edge cases, performance implications, breaking changes, migration concerns,
+security implications.]
+
+## Approach
+[Step-by-step implementation plan with file paths, function names, and code
+shape where applicable. Group steps into atomic, ordered tasks.]
+
+## Task List
+
+### Phase 1: Foundation
+- [ ] Task 1: ...
+- [ ] Task 2: ...
+
+### Checkpoint: Phase 1
+- [ ] Tests pass, lint/formatter clean (module-specific commands)
+
+### Phase 2: Core Features
+- [ ] Task 3: ...
+- [ ] Task 4: ...
+
+### Checkpoint: Phase 2
+- [ ] End-to-end flow works
+
+### Phase 3: Polish
+- [ ] Task 5: ...
+- [ ] Task 6: ...
+
+### Checkpoint: Complete
+- [ ] All acceptance criteria met
+- [ ] Ready for review
+
+## Testing Strategy
+[How to verify: which test commands to run per module, what cases to cover,
+manual verification steps, lint/format checks. Consult each module's core
+memory for the exact commands.]
+
+## Parallelization Opportunities
+- **Safe to parallelize:** Independent feature slices across separate
+  modules, tests for already-implemented features
+- **Must be sequential:** Shared common schema changes, database migrations
+- **Needs coordination:** Features that share a contract (define the contract
+  first, then parallelize)
+
+## Open Questions
+- [Question needing human input]
+```
+
+When the plan is purely analytical (e.g. a code review or feasibility study
+with no implementation), skip the **Approach** and **Task List** sections and
+lead with **Findings** instead, keeping the rest of the structure.
+
+## Verification Checklist
+
+Before starting implementation, confirm:
+
+- [ ] Every task has acceptance criteria
+- [ ] Every task has a verification step
+- [ ] Task dependencies are identified and ordered correctly
+- [ ] No task touches more than ~5 files
+- [ ] Checkpoints exist between major phases
+- [ ] The human has reviewed and approved the plan
@@ -9,11 +9,6 @@ metadata: {"clawdbot":{"emoji":"🔎","requires":{"bins":["rg"]},"install":[{"id

 Fast, smart recursive search. Respects `.gitignore` by default.

-## When to use
-
- Searching file contents across the repo for regex patterns — the
-  default code search, respects `.gitignore`.
-
 ## Quick Start

 ### Basic search
@@ -9,13 +9,6 @@ Apply the ASD-STE100 standard to all prose you produce in this task. Do not anno

 Compliance note (for you, not for output): the official specification and its dictionary are copyright ASD. This skill encodes paraphrased rules and a publicly sourced word list. For certified aerospace/defense deliverables, tell the user that full compliance requires the free official specification (asd-ste100.org) and a human sign-off. Never claim certified compliance.

-## When to use
-
-Only when the user explicitly invokes it: they type `/ste`, or say "use
-the ste skill" / "apply ASD-STE100". Requests like "simplify this",
-"make it clearer", or "shorter sentences" do NOT invoke it — respond
-normally unless it is named.
-
 ## Step 0 — Classify the text

 Before writing a single sentence, decide: is this **procedural** text (instructions someone follows) or **descriptive** text (explanation, background, description)? Every limit below depends on this. Mixed documents get classified section by section.
@@ -11,12 +11,6 @@ Fetch information from Taiga public API for the **Penpot** project

 **No authentication required** — only public project data is accessed.

-## When to use
-
- The user asks about Penpot issues, user stories, or tasks tracked in
-  Taiga — fetch them via the public API (project id 345963), no
-  authentication needed.
-
 ## Prerequisites

 - `python3` — the `scripts/taiga.py` CLI script is self-contained (stdlib only)
@@ -477,15 +477,9 @@ There are exactly two types:
   release, but the PR is being released elsewhere — the fix may not
   actually ship here.
 2. **PR is in the milestone, but the issue it closes is in a different
-   milestone.** The PR is being released here, but the issue it fixes is
-   being released in a different version — the changelog pairing is
-   misleading.
-
-   **Exception — issue with no milestone is NOT an anomaly.** Milestones
-   are only required for issues tracked in the "Main" project. A milestone
-   PR that closes an issue with no milestone references an issue from
-   another (probably private) project; that is expected and the issue is
-   not part of this changelog. Do not report it.
+   milestone (or has no milestone).** The PR is being released here, but
+   the issue it fixes is being released in a different version (or never
+   tracked in a milestone) — the changelog pairing is misleading.

 **Anything else is not an anomaly.** Other discrepancies (exclusion
 labels on in-changelog issues, missing valid issues, unmerged PR
@@ -641,10 +635,6 @@ for pr_num in sorted(changelog_prs):
    if get_pr_milestone(pr_num) != MILESTONE: continue
    for issue_num in pr.get('closing_issues', []):
        issue_ms = get_issue_milestone(issue_num)
-        # No milestone = issue from another (probably private) project —
-        # milestones are only required for the "Main" project. Not an
-        # anomaly, and the issue never belongs in this changelog.
-        if issue_ms is None: continue
        if issue_ms != MILESTONE:
            anomalies_b.append({
                'pr': pr_num,
@@ -667,7 +657,7 @@ with open(OUTPUT, 'w') as f:

    f.write('## Summary\n\n')
    f.write(f'- **Issue in {MILESTONE}, referenced PR in different milestone or no milestone:** {n_a}\n')
-    f.write(f'- **PR in {MILESTONE}, closing issue in a different milestone:** {n_b}\n')
+    f.write(f'- **PR in {MILESTONE}, closing issue in different milestone or no milestone:** {n_b}\n')
    f.write(f'- **Total anomalies:** {n_a + n_b}\n\n')

    # --- Anomalies section ---
@@ -696,7 +686,7 @@ with open(OUTPUT, 'w') as f:
                f.write('\n')

        if n_b:
-            f.write(f'\n### PR in {MILESTONE}, closing issue in a different milestone\n\n')
+            f.write(f'\n### PR in {MILESTONE}, closing issue in different milestone or no milestone\n\n')
            by_pr = {}
            for b in anomalies_b:
                by_pr.setdefault(b['pr'], []).append(b)
@@ -731,11 +721,8 @@ milestone mismatches between issues and their referenced PRs:

 1. **Issue in milestone, referenced PR in different milestone or no milestone** —
   the changelog claims a fix here, but the PR is released elsewhere.
-2. **PR in milestone, closing issue in a different milestone** —
+2. **PR in milestone, closing issue in different milestone or no milestone** —
   the PR is released here, but the issue it fixes belongs to another version.
-   (An issue with *no* milestone belongs to another, probably private,
-   project — milestones are only required on the "Main" project — so it is
-   neither an anomaly nor a changelog candidate.)

 **Rule violations are not in the report** — they are workflow errors the
 LLM must fix directly in `CHANGES.md` during step 6a (pre-flight checks).
@@ -812,11 +799,8 @@ self-contained and clickable in any Markdown viewer.
 - **Anomaly = milestone mismatch only.** The report contains only milestone
  mismatches: (1) the issue is in this milestone but the referenced PR is
  in a different milestone (or unassigned), and (2) the PR is in this
-  milestone but the issue it closes is in a different milestone. An
-  *unassigned* (milestone-less) issue closed by a milestone PR is **not**
-  an anomaly: milestones are required only for the "Main" project, so such
-  issues come from another (probably private) project and are not changelog
-  candidates. These anomalies are reported because the changelog pairing is
+  milestone but the issue it closes is in a different milestone (or
+  unassigned). These are anomalies because the changelog pairing is
  *misleading* — the human needs to decide whether the milestone or the
  changelog is wrong. All other discrepancies (exclusion labels, missing
  valid issues, unmerged PR references, duplicates, stale milestone
@@ -14,11 +14,7 @@ You are working on the GitHub project `penpot/penpot`, a monorepo.
  - Before `git commit` → `mem:workflow/creating-commits` (subject format, body, `AI-assisted-by: model-name` trailer)
  - Before `gh issue create` → `mem:workflow/creating-issues` (title derivation, body template, labels, Issue Type)
  - Before `gh pr create` / `gh pr edit` → `mem:workflow/creating-prs` (title format, body structure, "Note:" line)
- Before a repo-wide pnpm version update → `mem:workflow/updating-pnpm` (workspace
-  layout, `corepack use` sweep order, the stamp-missing-field and
-  ignored-builds gotchas, verification steps)
 - **Never `git push`, force-push, or modify `git origin`** (or any other remote). The user pushes from their own shell; if a push is required, say so and wait. Never amend a commit that the user has already pushed unless explicitly asked.
- **Never edit `CHANGES.md` by hand.** The changelog is generated from GitHub milestones during the release process; update it only via the `update-changelog` skill flow or on explicit user request.
 - You have access to the GitHub CLI `gh` or corresponding MCP tools.
 - Issues are also managed on Taiga. Read issues using the `read_taiga_issue` tool.
 - Before writing code, analyze the task in depth and describe your plan. If the task is complex, break it down into atomic steps.
@@ -74,14 +70,6 @@ module. You can read it from `mem:<MODULE>/core`
 - `scripts/error-reports.mjs` — Query error reports via RPC API with token
  authentication. Supports list/get operations with filtering and pagination.
  See `mem:scripts/error-reports`.
- `scripts/clean-node-modules` — Remove stale `node_modules` from all pnpm
-  workspaces (root, modules, member packages). Keeps the shared pnpm store
-  at `<repo>/.pnpm-store` unless `--store`; ignores `external/` and
-  `.opencode/`. Usage and reinstall steps: `mem:workflow/updating-pnpm`.
- `scripts/ci` — CI orchestration script: runs lint, tests, and format
-  checks per module (`frontend backend common render-wasm exporter mcp
-  plugins library`). Logs go to `.ci-logs/`; read the log file on failure.
-  See `mem:scripts/ci`.

 # Dependency graph

@@ -6,7 +6,6 @@ Compose-based dev environment under `docker/devenv/`, driven by `manage.sh`. Par

 - `penpotdev-infra`: shared `postgres`, `minio`, `minio-setup`, `mailer`, `ldap`. File: `docker-compose.infra.yml`.
 - `penpotdev-wsN` (N=0,1,…): per-instance `main` + `redis` (Valkey). File: `docker-compose.main.yml`. ws0 (a.k.a. `main`) binds `$PWD`; ws1+ bind clones at `${PENPOT_WORKSPACES_DIR}/wsN/` (default `~/.penpot/penpot_workspaces/`), maintained by the developer.
- Optional overlay `docker-compose.opencode.yml`: added by `instance-compose` as an extra `-f` only when `PENPOT_OPENCODE_CONFIG_DIR` is set (i.e. `run-devenv --opencode-config-dir DIR` ran in this process). Bind-mounts the host dir at `/home/penpot/.config/opencode` (`:z`). Flag-only, per-call; not read from ambient env. Parser `parse-opencode-config-dir` absolutizes (`~`, realpath) because compose resolves relative bind sources against the compose file's dir. Only instances brought up with the flag get the mount.
 - All projects join external network `penpot_shared`. Created idempotently by `ensure-devenv-network`, never removed by lifecycle commands.

 ## Source-of-truth files
@@ -66,7 +65,7 @@ No `--delete` on the working-tree pass: gitignored caches in the workspace survi

 ## CLI surface

- `run-devenv --agentic [--ws main|0|wsN|N] [--sync] [--serena-context CTX] [--opencode-config-dir DIR]`: bring one instance up. Agentic only — MCP and Serena windows are always created. Default target main. Errors out if the target is already running. `--sync` is rejected on main; on ws1+ it's optional (forced only when the workspace dir does not exist yet). `--opencode-config-dir DIR` bind-mounts DIR at `~/.config/opencode` in-container via the optional overlay above; mount applies at container creation, so changing it requires stop + re-run.
+- `run-devenv --agentic [--ws main|0|wsN|N] [--sync] [--serena-context CTX]`: bring one instance up. Agentic only — MCP and Serena windows are always created. Default target main. Errors out if the target is already running. `--sync` is rejected on main; on ws1+ it's optional (forced only when the workspace dir does not exist yet).
 - `stop-devenv [--ws main|0|wsN|N] [--all]`: stop instances. Flags mutually exclusive. `--ws N` stops just that workspace. `--ws 0` or no flag stops ws0; shared infra shuts down only if no other instances remain. `--all` stops every ws highest-first then ws0, then infra.
 - `run-devenv`: legacy alias, ws0 non-agentic attached.
 - `attach-devenv [--ws main|0|wsN|N]`: pure attach. Fails fast if instance/session missing.
@@ -1,61 +0,0 @@
-# CI (scripts/ci)
-
-`scripts/ci` runs CI-style checks — lint, tests, format — for one or more
-monorepo modules and prints a per-task summary. It is the local equivalent
-of CI; use it to verify changes before declaring work done.
-
-## When to use
-
- After implementing or fixing code in a module: run its checks before
-  finishing (AGENTS.md: run the applicable lint and format checks).
- When `common/` changed: validate its consumers too (frontend, backend,
-  exporter; see the dependency graph in `mem:critical-info`).
- To fix formatting across a module (`--fix`) or repair delimiters
-  (`--paren-repair`) before linting.
-
-## How to use (CLI)
-
-Run from the repo root:
-
-```bash
-./scripts/ci MODULE...                  # lint + test + fmt per module
-./scripts/ci --all --no-test            # lint + fmt on all modules
-./scripts/ci --lint frontend            # lint only
-./scripts/ci --fix --no-test frontend   # format files, skip tests
-./scripts/ci --paren-repair --all       # fix delimiters in all Clojure modules
-./scripts/ci --dry-run --all            # preview what would run
-```
-
-Modules: `frontend backend common render-wasm exporter mcp plugins library`.
-
-Flags:
-
- Default tasks: `lint`, `test`, `fmt` (format check; `--fix` formats
-  instead).
- `--lint` / `--test` / `--fmt` run one task only; `--no-lint` /
-  `--no-test` / `--no-fmt` drop one task from the default set.
- `--paren-repair` runs only the delimiter repair — it wraps
-  `scripts/paren-repair` over each module's Clojure/CLJS sources; see
-  `mem:scripts/paren-repair`.
- `--all` selects every module; `--exclude MOD` drops one (repeatable).
- `--fail-fast` stops at the first failure; `--quiet` suppresses failure
-  output; `--dry-run` prints commands without running; `--clean` removes
-  the log directory.
-
-## Logs and exit codes
-
- Full output of every task: `.ci-logs/<module>-<task>.log`.
- On failure the script prints the last 30 lines; the final summary lists
-  every failed `module:task` with its log path.
- Exit code 0 when all selected tasks passed, 1 otherwise.
- Diagnose failures by reading the log file — never pipe test output
-  through filters (AGENTS.md hard rule).
-
-## Notes
-
- `mcp` has no lint task (shows as skipped). `render-wasm` uses `./lint`,
-  `./test`, and `cargo fmt`.
- Test tasks are long-running (backend: `clojure -M:dev:test`); use a
-  generous timeout when calling it from an agent shell.
- Skill entry point: `.agents/skills/local-ci/SKILL.md`.
- Testing principles and output discipline: `mem:testing`.
@@ -351,5 +351,5 @@ gh issue view <NUMBER> --repo penpot/penpot --json title
 ## See Also

 - End-to-end orchestration entry point: the `create-issue` skill at
-  `.agents/skills/create-issue/SKILL.md`. The skill is a thin entry
+  `.opencode/skills/create-issue/SKILL.md`. The skill is a thin entry
  point; this memory is the canonical home for all issue-creation rules.
@@ -1,12 +1,6 @@
 # Creating Pull Requests

-PR only on explicit request.
-
-## Branch Naming
-
- Primary: `issue-NNNN` — one branch per GitHub issue (e.g. `issue-11525`).
- No issue: free-form descriptive name, dash-separated, no slashes (e.g. `fix-ellipse-icon-typo`, `feat-auto-link-libraries`).
- If the user already created the branch, use it as-is — never rename.
+PR only on explicit request. Branch: issue/feature-specific; fallback `<type>/<short-description>` (`fix/...`, `feat/...`, `refactor/...`, `docs/...`, `chore/...`, `perf/...`).

 ## Target Branch

@@ -1,91 +0,0 @@
-# Updating pnpm Across All Workspaces
-
-Canonical procedure. Run it from the repo root with the log redirected to a
-file (never pipe tool output through filters).
-
-## Layout facts
-
- The repo has 11 pnpm workspaces, each with its own `pnpm-workspace.yaml`
-  and `pnpm-lock.yaml`: the repo root plus `backend`, `common`, `docs`,
-  `exporter`, `frontend`, `library`, `mcp`, `media-processor`, `plugins`,
-  and `render-wasm`.
- Every package inside a module workspace (for example all `plugins/apps/*`
-  and `plugins/libs/*` packages) is a plain member of that module's
-  workspace. Members must not carry their own `pnpm-workspace.yaml` or
-  `pnpm-lock.yaml`; their dependencies resolve through the parent
-  workspace's lockfile.
- One shared pnpm store for the whole repo: `<repo>/.pnpm-store`. Every
-  workspace yaml sets it explicitly: `storeDir: .pnpm-store` at the root,
-  `storeDir: ../.pnpm-store` in each module. pnpm resolves the value
-  against the workspace root, so all workspaces land on the same store.
-  Do not remove these lines: nested workspaces do not inherit settings,
-  and without them each workspace may resolve a different store.
- The store survives `node_modules` cleans. It is content-addressed and
-  integrity-verified, so it cannot go stale; staleness lives in
-  node_modules. Only `scripts/clean-node-modules --store` removes it.
- Every `package.json` (about 35 of them) must carry a `packageManager` field
-  with the identical `pnpm@<version>+sha512.<hash>` value. Do not let them drift.
- CI pins no pnpm version; workflows rely on corepack reading
-  `packageManager`. Fixing the fields fixes CI.
-
-## Procedure
-
-1. Resolve the target tag first and note the version. Example:
-   `npm view pnpm dist-tags --json` for `next-12` (latest 12.x). The tag
-   moves over time; always re-check.
-2. List every directory with a `package.json`, excluding `node_modules`
-   (`fd -H -t f package.json -E node_modules`). This list is the work set;
-   do not maintain a hand-written list.
-3. Run `corepack use pnpm@<tag>` in workspace roots first, then members.
-   `corepack use` stamps `packageManager` in the nearest package.json and
-   runs an install. Member runs repeat the workspace install; after the root
-   run they are quick no-ops.
-4. If a run fails, fix the cause (see gotchas) and re-run that directory.
-
-## Gotchas
-
- `corepack use` only updates an existing `packageManager` field. If a
-  package.json lacks the field, corepack walks up to the nearest ancestor
-  that has one and stamps that file instead; the member stays unstamped.
-  After the sweep, assert every package.json carries the field. For a
-  missing one, insert the identical `pnpm@<version>+sha512.<hash>` string,
-  then re-run `corepack use pnpm@<tag>` in that directory.
- A workspace may fail with `ERR_PNPM_IGNORED_BUILDS`, and pnpm then writes
-  a placeholder scaffold into its `pnpm-workspace.yaml`:
-  `allowBuilds: esbuild: set this to true or false`. Current pnpm writes
-  only the `allowBuilds` placeholder; any legacy key still present
-  (`ignoredBuiltDependencies`, `onlyBuiltDependencies`,
-  `neverBuiltDependencies`) is ignored since pnpm 11. Repo convention is
-  `allowBuilds: esbuild: true`. Replace the placeholder and drop the
-  legacy entry, then re-run.
- `plugins/apps/composable-test-suite` once had its own
-  `pnpm-workspace.yaml` and acted as a nested workspace root. That state is
-  gone on purpose: pnpm picks the nearest `pnpm-workspace.yaml` walking up,
-  so a nested one silently forks install and lockfile behavior. Do not
-  reintroduce it.
- Expect metadata-only lockfile diffs when only the pnpm version moves:
-  the pnpm self-reference entries, plus a new `packageManagerDependencies`
-  section in lockfiles last written by older pnpm. Large diffs mean
-  re-resolution; inspect them before accepting.
-
-## Verification
-
- Every `packageManager` field is byte-identical (same version and hash).
- `pnpm --version` in each workspace prints the target version.
- `pnpm install --frozen-lockfile` succeeds in each of the 11 workspaces.
- `git diff` on lockfiles matches the expectations above.
-
-## Cleaning stale node_modules
-
- `scripts/clean-node-modules` removes every workspace `node_modules`: the
-  repo root, all module workspaces, and all member packages. Use it when
-  installs misbehave after dependency changes: clean, reinstall, done.
- Flags: `-n/--dry-run` lists without deleting; `--store` also removes the
-  shared pnpm store at `<repo>/.pnpm-store` (the next install re-downloads
-  what it held). `external/` (vendored dependency trees with their own
-  lifecycles) and `.opencode/` are always ignored.
- The script never touches the pnpm store by default, so the reinstall
-  after cleaning reuses cached packages (zero downloads).
- After cleaning, run `pnpm install` in each workspace root to restore the
-  development environment; `frontend` postinstall also reinstalls and
-  builds `plugins-runtime`.
@@ -8,15 +8,9 @@
  wait for the user to push. Do not change the remote URL, do not switch SSH↔HTTPS.
 - **Never amend a commit that has been pushed** unless the user explicitly asks.
  If the user pushes, treat that commit as final from the agent's side.
- **Never edit `CHANGES.md` by hand** in commits or PRs. The changelog is
-  generated from GitHub milestones during the release process; update it only
-  via the `update-changelog` skill flow or on explicit user request.
 - **Never pipe test output directly to filters** (`| head`, `| tail`, `| grep`, etc.).
  Always redirect to a file first: `command > /tmp/output.txt 2>&1`, then read/grep the file.
  This prevents hiding test failures. See `mem:testing` for details.
- **`.claude/skills` is a symlink to `.agents/skills`.**
-  Edit skills only in their canonical location (`.agents/skills`); never edit
-  through `.claude/skills`.
 - **Read the workflow memory BEFORE the corresponding action**:
  - Before `git commit` → `mem:workflow/creating-commits` (commit format, AI-assisted-by trailer)
  - Before `gh issue create` → `mem:workflow/creating-issues` (title derivation, body template, Issue Type)
@@ -58,15 +52,7 @@ Skipping this step is the #1 cause of incorrect or incomplete work.

 ## Writing Rules

-Writing rules, from Orwell, 1946. These govern prose: docs, PR text, messages. Never touch code or technical terms; swap in everyday words only where precision survives.
-
-1. Never use a metaphor, simile or other figure of speech which you are used to seeing in print.
-2. Never use a long word where a short one will do.
-3. If it is possible to cut a word out, always cut it out.
-4. Never use the passive where you can use the active.
-5. Never use a foreign phrase, a scientific word or a jargon word if you can think of an everyday English equivalent.
-6. Break any of these rules sooner than say anything outright barbarous.
-Review every prose output against these rules before delivering.
+Use the `ste` skill when the user explicitly requests STE, `/ste`, or ASD-STE100.

 ---

@@ -148,6 +134,6 @@ precision while maintaining a strong focus on maintainability and performance.
 - `scripts/nrepl-eval.mjs` — Evaluate Clojure code via nREPL (backend + frontend).
 - `scripts/check-commit` — Validate commit messages against Penpot's commit guidelines.
 - `scripts/check-fmt-clj` — Check Clojure formatting without modifying files.
- `scripts/ci` — CI orchestration script for running lint, tests, and format checks across modules. See `mem:scripts/ci`.
+- `scripts/ci` — CI orchestration script for running lint, tests, and format checks across modules. See `scripts/ci --help`.
 - `scripts/gh.py` — Multi-purpose GitHub CLI helper. Subcommands: `issues` (list issues in a milestone), `prs` (fetch PR details), `advisories` (list/inspect security advisories). See `python3 scripts/gh.py --help`.

@@ -2,12 +2,6 @@

 ## 2.18.0 (Unreleased)

-### :rocket: Epics and highlights
-
- Group toolbar drawing tools into shape and free-draw flyouts [#9316](https://github.com/penpot/penpot/issues/9316) (PR: [#9480](https://github.com/penpot/penpot/pull/9480), [#10354](https://github.com/penpot/penpot/pull/10354))
- Add dedicated Line and Arrow drawing tools (by @davidv399) [#9145](https://github.com/penpot/penpot/issues/9145) (PR: [#9146](https://github.com/penpot/penpot/pull/9146))
- Show and manage comments while designing in the workspace [#10239](https://github.com/penpot/penpot/issues/10239) (PR: [#10275](https://github.com/penpot/penpot/pull/10275))
-
 ### :bug: Bugs fixed

 - Fix MCP integration hanging when the Penpot tab is backgrounded or frozen by the browser [#10323](https://github.com/penpot/penpot/issues/10323) (PR: [#10392](https://github.com/penpot/penpot/pull/10392))
@@ -17,136 +11,18 @@
 - Fix plugin API addTheme calls failing with the signature shown in the high-level overview [#10074](https://github.com/penpot/penpot/issues/10074) (PR: [#10359](https://github.com/penpot/penpot/pull/10359))
 - Fix empty text shape not being deleted on editor exit [#10540](https://github.com/penpot/penpot/issues/10540) (PR: [#10541](https://github.com/penpot/penpot/pull/10541))
 - Fix broken token pills showing wrong default state when not selected [#10524](https://github.com/penpot/penpot/issues/10524) (PR: [#10535](https://github.com/penpot/penpot/pull/10535))
+- Replace hyphens with bullets in subscription benefits list [#10547](https://github.com/penpot/penpot/issues/10547) (PR: [#10523](https://github.com/penpot/penpot/pull/10523))
 - Fix Chinese (zh-CN) translation showing wrong label for Intersection in board path menu (by @sawirricardo) [#10346](https://github.com/penpot/penpot/issues/10346) (PR: [#10381](https://github.com/penpot/penpot/pull/10381))
- Fix invalid formulas being accepted in numeric inputs (by @AKnassa) [#9581](https://github.com/penpot/penpot/issues/9581) (PR: [#10659](https://github.com/penpot/penpot/pull/10659))
- Fix radial gradient handles blowing up in size when rotated on ellipses (by @AKnassa) [#10069](https://github.com/penpot/penpot/issues/10069) (PR: [#10666](https://github.com/penpot/penpot/pull/10666))
- Fix plugin API validation errors being too generic to diagnose the failure (by @AKnassa) [#10072](https://github.com/penpot/penpot/issues/10072) (PR: [#10667](https://github.com/penpot/penpot/pull/10667))
- Fix crash with referential integrity error when deleting a component inside a grid (by @Alotor) [#10101](https://github.com/penpot/penpot/issues/10101) (PR: [#10956](https://github.com/penpot/penpot/pull/10956))
- Fix component copies not preserving rotation when the main component has changes [#10109](https://github.com/penpot/penpot/issues/10109) (PR: [#10574](https://github.com/penpot/penpot/pull/10574))
- Fix text width and height staying stale after setting growType in the plugin API [#10207](https://github.com/penpot/penpot/issues/10207) (PR: [#9898](https://github.com/penpot/penpot/pull/9898))
- Fix padding not painted until expanding the 4-sides padding option [#10278](https://github.com/penpot/penpot/issues/10278) (PR: [#10602](https://github.com/penpot/penpot/pull/10602))
- Fix files with custom fonts breaking with a referential integrity error when moved between teams (by @filipsajdak) [#10496](https://github.com/penpot/penpot/issues/10496) (PR: [#10837](https://github.com/penpot/penpot/pull/10837))
- Fix clicking overlapping comment bubbles zooming to 20000% without showing the comments [#10526](https://github.com/penpot/penpot/issues/10526) (PR: [#10543](https://github.com/penpot/penpot/pull/10543))
- Fix user menu subsections in the dashboard not closing when hovering away from the parent option (by @AKnassa) [#10549](https://github.com/penpot/penpot/issues/10549) (PR: [#10639](https://github.com/penpot/penpot/pull/10639))
- Fix self-hosted env-generated config.js being cached for 7 days so PENPOT_FLAGS changes did not reach already-cached browsers (by @filipsajdak) [#10556](https://github.com/penpot/penpot/issues/10556) (PR: [#11146](https://github.com/penpot/penpot/pull/11146))
- Fix color of selected text in light theme [#10570](https://github.com/penpot/penpot/issues/10570) (PR: [#10614](https://github.com/penpot/penpot/pull/10614))
- Fix margin input order being inconsistent with padding inputs and between collapsed and expanded states [#10578](https://github.com/penpot/penpot/issues/10578) (PR: [#10797](https://github.com/penpot/penpot/pull/10797))
- Fix uncaught DOMException when writing image/svg+xml content to the clipboard (by @AKnassa) [#10596](https://github.com/penpot/penpot/issues/10596) (PR: [#10663](https://github.com/penpot/penpot/pull/10663))
- Fix tick icons not aligned in the font selector [#10597](https://github.com/penpot/penpot/issues/10597) (PR: [#10774](https://github.com/penpot/penpot/pull/10774))
- Fix incorrect padding values when multiple shapes are selected [#10598](https://github.com/penpot/penpot/issues/10598) (PR: [#10602](https://github.com/penpot/penpot/pull/10602))
- Fix integrity errors related to variants not being repaired [#10606](https://github.com/penpot/penpot/issues/10606) (PR: [#10768](https://github.com/penpot/penpot/pull/10768))
- Fix changing password showing 'Password should be at least 8 characters' error on the old password field (by @AKnassa) [#10626](https://github.com/penpot/penpot/issues/10626) (PR: [#10661](https://github.com/penpot/penpot/pull/10661))
- Fix stroke caps disappearing when dragging [#10633](https://github.com/penpot/penpot/issues/10633) (PR: [#10634](https://github.com/penpot/penpot/pull/10634))
- Fix layout padding being saved as string after invalid input in multi-selection, causing persistence errors (by @niwinz) [#10638](https://github.com/penpot/penpot/issues/10638) (PR: [#10758](https://github.com/penpot/penpot/pull/10758))
- Fix inconsistent theme handling between Penpot and plugins [#10676](https://github.com/penpot/penpot/issues/10676) (PR: [#10677](https://github.com/penpot/penpot/pull/10677))
- Fix image stroke (strokeImage) support missing in the plugin API Stroke interface [#10682](https://github.com/penpot/penpot/issues/10682) (PR: [#10683](https://github.com/penpot/penpot/pull/10683))
- Fix SVG images not working as fill in the WebGL renderer [#10705](https://github.com/penpot/penpot/issues/10705) (PR: [#10707](https://github.com/penpot/penpot/pull/10707))
- Fix background blur not working on text shapes [#10706](https://github.com/penpot/penpot/issues/10706) (PR: [#10712](https://github.com/penpot/penpot/pull/10712))
- Fix background blur not applying on strokes [#10713](https://github.com/penpot/penpot/issues/10713) (PR: [#10716](https://github.com/penpot/penpot/pull/10716))
- Fix text shape with empty content breaking workspace updates [#10725](https://github.com/penpot/penpot/issues/10725) (PR: [#10731](https://github.com/penpot/penpot/pull/10731))
- Fix missing SVG option in the file filters when adding an image fill (by @LuBoys) [#10756](https://github.com/penpot/penpot/issues/10756) (PR: [#10771](https://github.com/penpot/penpot/pull/10771))
- Update onboarding image [#10779](https://github.com/penpot/penpot/issues/10779) (PR: [#10783](https://github.com/penpot/penpot/pull/10783))
- Fix main toolbar overlapping the grid edition bar [#10788](https://github.com/penpot/penpot/issues/10788) (PR: [#10789](https://github.com/penpot/penpot/pull/10789))
- Fix WASM renderer panic when the WebGL context is restored mid-reload [#10810](https://github.com/penpot/penpot/issues/10810) (PR: [#10824](https://github.com/penpot/penpot/pull/10824))
- Fix nginx frontend forwarding the client Host header to backend/exporter, breaking Istio strict mTLS routing (by @yamila-moreno) [#10835](https://github.com/penpot/penpot/issues/10835) (PR: [#11233](https://github.com/penpot/penpot/pull/11233))
- Fix tutorial templates with components causing errors [#10839](https://github.com/penpot/penpot/issues/10839)
- Fix plugin 'Try out' flow crashing when projects have not loaded yet [#10858](https://github.com/penpot/penpot/issues/10858) (PR: [#10859](https://github.com/penpot/penpot/pull/10859))
- Fix collapsed Fill color section on the design panel for new texts [#10860](https://github.com/penpot/penpot/issues/10860) (PR: [#10972](https://github.com/penpot/penpot/pull/10972))
- Fix grid item date tooltip in the project view showing 'Will be deleted' instead of creation date (by @0xTHAC0) [#10873](https://github.com/penpot/penpot/issues/10873) (PR: [#11161](https://github.com/penpot/penpot/pull/11161))
- Merge stop and start measurement shortcut to match current behavior [#10884](https://github.com/penpot/penpot/issues/10884) (PR: [#10906](https://github.com/penpot/penpot/pull/10906))
- Fix shape size badge displayed twice when a user with Viewer permissions selects a shape [#10893](https://github.com/penpot/penpot/issues/10893) (PR: [#10985](https://github.com/penpot/penpot/pull/10985))
- Fix main menu being covered by the toolbar [#10902](https://github.com/penpot/penpot/issues/10902) (PR: [#10926](https://github.com/penpot/penpot/pull/10926))
- Fix font family typography asset persisting across files in newly created text layers [#10925](https://github.com/penpot/penpot/issues/10925) (PR: [#11134](https://github.com/penpot/penpot/pull/11134))
- Fix error raised when editing justified text [#10944](https://github.com/penpot/penpot/issues/10944) (PR: [#10945](https://github.com/penpot/penpot/pull/10945))
- Fix MCP WebSocket proxy failing after penpot-mcp container restarts due to stale nginx DNS resolution (by @780Farva) [#10946](https://github.com/penpot/penpot/issues/10946) (PR: [#10947](https://github.com/penpot/penpot/pull/10947))
- Fix verification email address being unreadable due to low-contrast text on the register success page [#10950](https://github.com/penpot/penpot/issues/10950) (PR: [#10965](https://github.com/penpot/penpot/pull/10965))
- Fix image swatches displaying a wrong format in the color picker list view [#10951](https://github.com/penpot/penpot/issues/10951) (PR: [#10975](https://github.com/penpot/penpot/pull/10975))
- Fix text editor crashing when dropping dragged text after selecting all content [#10954](https://github.com/penpot/penpot/issues/10954) (PR: [#10959](https://github.com/penpot/penpot/pull/10959))
- Fix MCP tokens being usable as API access tokens [#10960](https://github.com/penpot/penpot/issues/10960) (PR: [#10962](https://github.com/penpot/penpot/pull/10962))
- Add size limit and rate limiting to the send-user-feedback endpoint [#10979](https://github.com/penpot/penpot/issues/10979) (PR: [#10990](https://github.com/penpot/penpot/pull/10990))
- Fix main menu not keeping alignment when the left sidebar is expanded [#10981](https://github.com/penpot/penpot/issues/10981) (PR: [#10986](https://github.com/penpot/penpot/pull/10986))
- Fix update-profile-props RPC method accepting undocumented keys [#10991](https://github.com/penpot/penpot/issues/10991) (PR: [#10992](https://github.com/penpot/penpot/pull/10992))
- Fix import-binfile RPC method schema accepting a file-id parameter [#10993](https://github.com/penpot/penpot/issues/10993) (PR: [#10994](https://github.com/penpot/penpot/pull/10994))
- Fix assemble-chunks session lookup ignoring the profile-id scope [#11011](https://github.com/penpot/penpot/issues/11011) (PR: [#11012](https://github.com/penpot/penpot/pull/11012))
- Validate font-id team ownership in create-font-variant [#11013](https://github.com/penpot/penpot/issues/11013) (PR: [#11014](https://github.com/penpot/penpot/pull/11014))
- Validate team ownership on file library link endpoints [#11015](https://github.com/penpot/penpot/issues/11015) (PR: [#11016](https://github.com/penpot/penpot/pull/11016))
- Limit object size allocation in the V1 binfile parser [#11017](https://github.com/penpot/penpot/issues/11017) (PR: [#11018](https://github.com/penpot/penpot/pull/11018))
- Limit recursion depth in the Fressian reader [#11019](https://github.com/penpot/penpot/issues/11019) (PR: [#11020](https://github.com/penpot/penpot/pull/11020))
- Limit concurrent imports in the import-binfile RPC method [#11023](https://github.com/penpot/penpot/issues/11023) (PR: [#11024](https://github.com/penpot/penpot/pull/11024))
- Validate content-type on management upload endpoints [#11025](https://github.com/penpot/penpot/issues/11025) (PR: [#11026](https://github.com/penpot/penpot/pull/11026))
- Fix webhook endpoints allowing unauthorized access via creator-id fallback [#11028](https://github.com/penpot/penpot/issues/11028) (PR: [#11029](https://github.com/penpot/penpot/pull/11029))
- Escape markdown in user-controlled fields of Mattermost error notifications [#11033](https://github.com/penpot/penpot/issues/11033) (PR: [#11034](https://github.com/penpot/penpot/pull/11034))
- Enforce file read permission check on asset endpoints [#11035](https://github.com/penpot/penpot/issues/11035) (PR: [#11036](https://github.com/penpot/penpot/pull/11036))
- Add accumulated storage byte quota for media uploads [#11037](https://github.com/penpot/penpot/issues/11037) (PR: [#11038](https://github.com/penpot/penpot/pull/11038))
- Add bounding box dimension limit to exports [#11041](https://github.com/penpot/penpot/issues/11041) (PR: [#11042](https://github.com/penpot/penpot/pull/11042))
- Sanitize embedded scripts in SVG uploads [#11043](https://github.com/penpot/penpot/issues/11043) (PR: [#11044](https://github.com/penpot/penpot/pull/11044))
- Fix duplicate file ID returning inconsistent error responses [#11045](https://github.com/penpot/penpot/issues/11045) (PR: [#11050](https://github.com/penpot/penpot/pull/11050))
- Enforce permission checks in WebSocket subscription handlers [#11052](https://github.com/penpot/penpot/issues/11052) (PR: [#11054](https://github.com/penpot/penpot/pull/11054))
- Fix 'something went wrong' popup when using incremental numerical input interaction [#11053](https://github.com/penpot/penpot/issues/11053) (PR: [#10794](https://github.com/penpot/penpot/pull/10794))
- Enforce password complexity validation on the backend [#11055](https://github.com/penpot/penpot/issues/11055) (PR: [#11059](https://github.com/penpot/penpot/pull/11059))
- Normalize string inputs before processing [#11060](https://github.com/penpot/penpot/issues/11060) (PR: [#11061](https://github.com/penpot/penpot/pull/11061))
- Add cooldown to avoid sending duplicate invitation emails [#11062](https://github.com/penpot/penpot/issues/11062) (PR: [#11063](https://github.com/penpot/penpot/pull/11063))
- Enable SSRF protection for organization SSO validation [#11064](https://github.com/penpot/penpot/issues/11064) (PR: [#11065](https://github.com/penpot/penpot/pull/11065))
- Fix clone-file-media-object allowing to clone media objects from files without read access [#11087](https://github.com/penpot/penpot/issues/11087) (PR: [#11090](https://github.com/penpot/penpot/pull/11090))
- Fix 404 error page logo not visible in dark mode [#11091](https://github.com/penpot/penpot/issues/11091) (PR: [#11167](https://github.com/penpot/penpot/pull/11167))
- Fix incorrect permission handling when creating an invitation [#11098](https://github.com/penpot/penpot/issues/11098) (PR: [#11099](https://github.com/penpot/penpot/pull/11099))
- Reject zero or negative total-chunks values in upload sessions [#11103](https://github.com/penpot/penpot/issues/11103) (PR: [#11104](https://github.com/penpot/penpot/pull/11104))
- Fix import-binfile accepting unsupported version values without validation [#11105](https://github.com/penpot/penpot/issues/11105) (PR: [#11107](https://github.com/penpot/penpot/pull/11107))
- Fix sessions remaining active on other devices after account deletion [#11114](https://github.com/penpot/penpot/issues/11114) (PR: [#11115](https://github.com/penpot/penpot/pull/11115))
- Use random UUIDs for share link IDs instead of a predictable scheme [#11116](https://github.com/penpot/penpot/issues/11116) (PR: [#11117](https://github.com/penpot/penpot/pull/11117))
- Fix plugin manifest fetch hanging indefinitely without timeout [#11119](https://github.com/penpot/penpot/issues/11119) (PR: [#11120](https://github.com/penpot/penpot/pull/11120))
- Use constant-time comparison for shared key authentication [#11121](https://github.com/penpot/penpot/issues/11121) (PR: [#11122](https://github.com/penpot/penpot/pull/11122))
- Fix ESC key not closing the comment input box after posting a comment in the workspace [#11128](https://github.com/penpot/penpot/issues/11128) (PR: [#11131](https://github.com/penpot/penpot/pull/11131))
- Fix token edit modal crashing when resolving tokens with group nodes [#11143](https://github.com/penpot/penpot/issues/11143) (PR: [#11144](https://github.com/penpot/penpot/pull/11144))
- Fix text editor crashing when pasting into an empty text shape [#11149](https://github.com/penpot/penpot/issues/11149) (PR: [#11150](https://github.com/penpot/penpot/pull/11150))
- Fix comment avatars appearing on top of rulers when scrolling the canvas (by @filipsajdak) [#11163](https://github.com/penpot/penpot/issues/11163) (PR: [#11168](https://github.com/penpot/penpot/pull/11168))
- Fix infinite loop of get-teams and get-team-members calls when granting team access from an email link [#11215](https://github.com/penpot/penpot/issues/11215) (PR: [#11223](https://github.com/penpot/penpot/pull/11223))
- Fix RPC requests bypassing rate limiting with fractional bucket refill intervals [#11253](https://github.com/penpot/penpot/issues/11253) (PR: [#11254](https://github.com/penpot/penpot/pull/11254))
- Fix tempfile bucket serving objects to any authenticated user instead of only the uploader [#11269](https://github.com/penpot/penpot/issues/11269) (PR: [#11270](https://github.com/penpot/penpot/pull/11270))
- Fix increasing a value by clicking and dragging in a numeric input [#11274](https://github.com/penpot/penpot/issues/11274) (PR: [#11334](https://github.com/penpot/penpot/pull/11334))
- Fix notification pill rendering unescaped HTML in the detail section when importing tokens [#11276](https://github.com/penpot/penpot/issues/11276) (PR: [#11275](https://github.com/penpot/penpot/pull/11275))
- Fix share-link holders reading pages outside the authorized scope via the get-page RPC command [#11281](https://github.com/penpot/penpot/issues/11281) (PR: [#11284](https://github.com/penpot/penpot/pull/11284))
- Fix incorrect permission handling when managing share links on a file [#11289](https://github.com/penpot/penpot/issues/11289) (PR: [#11290](https://github.com/penpot/penpot/pull/11290))
- Fix backend session remaining valid after logout when the auth-token cookie is replayed [#11316](https://github.com/penpot/penpot/issues/11316) (PR: [#11317](https://github.com/penpot/penpot/pull/11317))
- Fix get-team-invitation-token requiring only read permissions [#11358](https://github.com/penpot/penpot/issues/11358) (PR: [#11359](https://github.com/penpot/penpot/pull/11359))
- Fix missing text in legacy SVG board thumbnails [#10182](https://github.com/penpot/penpot/issues/10182) (PR: [#11552](https://github.com/penpot/penpot/pull/11552))
- Fix workspace crash when applying transform modifiers in the WASM renderer [#10894](https://github.com/penpot/penpot/issues/10894) (PR: [#10896](https://github.com/penpot/penpot/pull/10896))
- Limit ZIP entry count and object size on V3 binfile import [#11021](https://github.com/penpot/penpot/issues/11021) (PR: [#11022](https://github.com/penpot/penpot/pull/11022))
- Block plugin UI iframe URLs targeting the Penpot domain [#11271](https://github.com/penpot/penpot/issues/11271) (PR: [#11273](https://github.com/penpot/penpot/pull/11273))
- Restrict the MCP REPL code execution endpoint to development environments [#11283](https://github.com/penpot/penpot/issues/11283) (PR: [#11282](https://github.com/penpot/penpot/pull/11282))
- Filter share-link tokens from the get-view-only-bundle response [#11285](https://github.com/penpot/penpot/issues/11285) (PR: [#11286](https://github.com/penpot/penpot/pull/11286))
- Disable MCP developer tools in multi-user mode [#11291](https://github.com/penpot/penpot/issues/11291) (PR: [#11310](https://github.com/penpot/penpot/pull/11310))
- Fix Hide comments setting being ignored after opening the Comments section [#11308](https://github.com/penpot/penpot/issues/11308) (PR: [#11492](https://github.com/penpot/penpot/pull/11492))
- Block NAT64/6to4/Teredo IPv6 transition addresses in the SSRF guard [#11319](https://github.com/penpot/penpot/issues/11319) (PR: [#11320](https://github.com/penpot/penpot/pull/11320))
- Prevent team admins from removing the team owner [#11367](https://github.com/penpot/penpot/issues/11367) (PR: [#11368](https://github.com/penpot/penpot/pull/11368))
- Enforce share-link comment permissions and page scope [#11370](https://github.com/penpot/penpot/issues/11370) (PR: [#11371](https://github.com/penpot/penpot/pull/11371))
- Clean up orphaned teams, projects and files on profile deletion [#11394](https://github.com/penpot/penpot/issues/11394) (PR: [#11395](https://github.com/penpot/penpot/pull/11395))
- Fix crash when pressing Ctrl+D with no shape selected [#11448](https://github.com/penpot/penpot/issues/11448) (PR: [#11491](https://github.com/penpot/penpot/pull/11491))
- Fix text layout not updating when auto-width is set by double-clicking the bounding box [#11480](https://github.com/penpot/penpot/issues/11480) (PR: [#11541](https://github.com/penpot/penpot/pull/11541))
- Fix boolean shapes rendering deformed in the WASM renderer and exports [#11482](https://github.com/penpot/penpot/issues/11482) (PR: [#11551](https://github.com/penpot/penpot/pull/11551))

 ### :sparkles: New features & Enhancements

 - Group toolbar drawing tools into shape and free-draw flyouts [#9316](https://github.com/penpot/penpot/issues/9316) (PR: [#9480](https://github.com/penpot/penpot/pull/9480), [#10354](https://github.com/penpot/penpot/pull/10354))
 - Add outline stroke to Paths [#9961](https://github.com/penpot/penpot/issues/9961) (PR: [#8677](https://github.com/penpot/penpot/pull/8677))
+- Make throwValidationErrors default to true for v2 manifest plugins [#10401](https://github.com/penpot/penpot/issues/10401) (PR: [#10433](https://github.com/penpot/penpot/pull/10433))
 - Add dedicated Line and Arrow drawing tools (by @davidv399) [#9145](https://github.com/penpot/penpot/issues/9145) (PR: [#9146](https://github.com/penpot/penpot/pull/9146))
 - Refactor wasm rulers and UI state [#10116](https://github.com/penpot/penpot/issues/10116) (PR: [#10461](https://github.com/penpot/penpot/pull/10461))
 - Improve team invitations modal in the dashboard [#10484](https://github.com/penpot/penpot/issues/10484) (PR: [#10459](https://github.com/penpot/penpot/pull/10459))
- Highlight the first matching font in the font list when searching (by @ai-mountain) [#3204](https://github.com/penpot/penpot/issues/3204) (PR: [#9512](https://github.com/penpot/penpot/pull/9512), [#10450](https://github.com/penpot/penpot/pull/10450))
- Preserve token references when copying and pasting properties instead of resolving them to values (by @AKnassa) [#9582](https://github.com/penpot/penpot/issues/9582) (PR: [#10665](https://github.com/penpot/penpot/pull/10665))
- Add waitForLayoutUpdate method to the plugin API [#10136](https://github.com/penpot/penpot/issues/10136) (PR: [#9898](https://github.com/penpot/penpot/pull/9898))
- Show and manage comments while designing in the workspace [#10239](https://github.com/penpot/penpot/issues/10239) (PR: [#10275](https://github.com/penpot/penpot/pull/10275))
- Simplify MCP server configuration for common MCP clients [#10355](https://github.com/penpot/penpot/issues/10355) (PR: [#10604](https://github.com/penpot/penpot/pull/10604))
- Remove misleading MCP client JSON snippet from the key-generated modal (by @Shlok1729) [#10399](https://github.com/penpot/penpot/issues/10399) (PR: [#10415](https://github.com/penpot/penpot/pull/10415))
- Preview font families in the font selector [#10403](https://github.com/penpot/penpot/issues/10403) (PR: [#10411](https://github.com/penpot/penpot/pull/10411))
- Remember expanded/collapsed state of token sets in the color tokens picker (session scope) [#10551](https://github.com/penpot/penpot/issues/10551) (PR: [#10864](https://github.com/penpot/penpot/pull/10864))
- Show token sets in reverse order by default in the color tokens picker (by @rhinocap) [#10552](https://github.com/penpot/penpot/issues/10552) (PR: [#10658](https://github.com/penpot/penpot/pull/10658))
- Add multi-selection and bulk delete support to pages in the workspace sitemap [#10580](https://github.com/penpot/penpot/issues/10580) (PR: [#10581](https://github.com/penpot/penpot/pull/10581))
- Add a grid/list view toggle for files in the dashboard [#10691](https://github.com/penpot/penpot/issues/10691) (PR: [#10692](https://github.com/penpot/penpot/pull/10692))
- Migrate Docker images to Docker Hardened Images (DHI) [#10720](https://github.com/penpot/penpot/issues/10720) (PR: [#10732](https://github.com/penpot/penpot/pull/10732), [#10733](https://github.com/penpot/penpot/pull/10733), [#10734](https://github.com/penpot/penpot/pull/10734))
- Adopt React Aria [#10802](https://github.com/penpot/penpot/issues/10802) (PR: [#10675](https://github.com/penpot/penpot/pull/10675))
- Add plugin API function for awaiting component updates beyond waitForLayoutUpdate [#10927](https://github.com/penpot/penpot/issues/10927) (PR: [#10964](https://github.com/penpot/penpot/pull/10964))
- Emit open-workspace-file audit event with file statistics on workspace load [#11106](https://github.com/penpot/penpot/issues/11106) (PR: [#11138](https://github.com/penpot/penpot/pull/11138))
+
 ## 2.17.2

 ### :bug: Bugs fixed
@@ -3157,7 +3033,7 @@ is a number of cores)
 - Enable penpot SVG metadata only when exporting complete files [Taiga #1914](https://tree.taiga.io/project/penpot/us/1914?milestone=295883)
 - Export to PDF all artboards of one page [Taiga #1895](https://tree.taiga.io/project/penpot/us/1895)
 - Go to a undo step clicking on a history element of the list [Taiga #1374](https://tree.taiga.io/project/penpot/us/1374)
- Increment font size by 10 with shift+arrows [#1047](https://github.com/penpot/penpot/issues/1047)
+- Increment font size by 10 with shift+arrows [1047](https://github.com/penpot/penpot/issues/1047)
 - New shortcut to detach components Ctrl+Shift+K [Taiga #1799](https://tree.taiga.io/project/penpot/us/1799)
 - Set email inputs to type "email", to aid keyboard entry [Taiga #1921](https://tree.taiga.io/project/penpot/issue/1921)
 - Use shift+move to move element orthogonally [#823](https://github.com/penpot/penpot/issues/823)
@@ -1,3 +0,0 @@
-Read and follow the instructions in `AGENTS.md`.
-
-Treat `AGENTS.md` as the canonical project instruction file.
@@ -14,7 +14,6 @@ Center](https://help.penpot.app/).
 - [Reporting Bugs](#reporting-bugs)
 - [Pull Requests](#pull-requests)
  - [Workflow](#workflow)
-  - [Branch naming](#branch-naming)
  - [Format](#format)
    - [Title format](#title-format)
    - [Description](#description)
@@ -74,18 +73,6 @@ Advisories](https://github.com/penpot/penpot/security/advisories)
 4. **Format and lint** — run the checks described in
   [Formatting and Linting](#formatting-and-linting) before submitting.

-### Branch naming
-
-Branch names are not enforced, but we recommend the following:
-
- **`issue-NNNN`** — when working from a GitHub issue, name the branch after
-  it (e.g. `issue-11525`). This makes each PR's origin self-evident.
- Otherwise, use a short, descriptive name with words separated by hyphens
-  and no slashes (e.g. `fix-ellipse-icon-typo`, `feat-auto-link-libraries`).
-
-Since PRs are squash-merged, the branch name does not survive into the
-commit history — what matters is the [PR title](#title-format).
-
 ### Format

 #### Title
@@ -56,7 +56,6 @@ If your organization is scaling and needs extra support, we’re here to help. [

 - [Why Penpot](#why-penpot)
 - [Getting Started](#getting-started)
- [Penpot Enterprise](#penpot-enterprise)
 - [Community](#community)
 - [Contributing](#contributing)
 - [Resources](#resources)
@@ -94,12 +93,6 @@ Penpot is the only design & prototype platform that is deployment agnostic. You

 Learn how to install it with Docker, Kubernetes, Elestio or other options on [our website](https://penpot.app/self-host).

-<img width="100%" height="1010" alt="2" src="https://github.com/user-attachments/assets/243e796e-a140-481a-b68f-b24be6a70e37" />
-
-## Penpot Enterprise ##
-
-Penpot Enterprise is our paid plan for organizations that need to scale their design work across multiple teams with advanced governance, security, and administration. Manage teams and access from a centralized **Admin Console**, configure advanced permissions, and connect your **identity provider through SSO**. Available for cloud and self-hosted environments, it combines enterprise controls with Penpot’s open-source foundation and open standards.
-
 ## Community ##

 We love the Open Source software community. Contributing is our passion and if it’s yours too, participate and [improve](https://community.penpot.app/c/help-us-improve-penpot/7) Penpot. All your designs, code and ideas are welcome!
@@ -17,7 +17,7 @@

  io.prometheus/simpleclient_httpserver {:mvn/version "0.16.0"}

-  io.lettuce/lettuce-core {:mvn/version "7.7.0.RELEASE"}
+  io.lettuce/lettuce-core {:mvn/version "7.6.0.RELEASE"}
  ;; Minimal dependencies required by lettuce, we need to include them
  ;; explicitly because clojure dependency management does not support
  ;; yet the BOM format.
@@ -25,7 +25,7 @@
  io.micrometer/micrometer-observation {:mvn/version "1.14.2"}

  java-http-clj/java-http-clj {:mvn/version "0.4.3"}
-  com.google.guava/guava {:mvn/version "33.7.1-jre"}
+  com.google.guava/guava {:mvn/version "33.6.0-jre"}

  funcool/yetti
  {:git/tag "v11.10"
@@ -40,32 +40,32 @@
  nrepl/nrepl {:mvn/version "1.7.0"}

  org.postgresql/postgresql {:mvn/version "42.7.13"}
-  org.xerial/sqlite-jdbc {:mvn/version "3.53.4.0"}
+  org.xerial/sqlite-jdbc {:mvn/version "3.53.2.1"}

  com.zaxxer/HikariCP {:mvn/version "7.1.0"}

-  io.whitfin/siphash {:mvn/version "3.0.0"}
+  io.whitfin/siphash {:mvn/version "2.0.0"}

  buddy/buddy-hashers {:mvn/version "2.0.167"}
  buddy/buddy-sign {:mvn/version "3.6.1-359"}
-  org.passay/passay {:mvn/version "2.0.0"}
+  org.passay/passay {:mvn/version "1.6.6"}

  com.github.ben-manes.caffeine/caffeine {:mvn/version "3.2.4"}

-  org.jsoup/jsoup {:mvn/version "1.23.2"}
+  org.jsoup/jsoup {:mvn/version "1.23.1"}

  at.yawk.lz4/lz4-java
-  {:mvn/version "1.11.2"}
+  {:mvn/version "1.11.1"}

  org.clojars.pntblnk/clj-ldap {:mvn/version "0.0.17"}

  dawran6/emoji {:mvn/version "0.2.0"}
-  markdown-clj/markdown-clj {:mvn/version "1.12.9"}
+  markdown-clj/markdown-clj {:mvn/version "1.12.8"}

  ;; Pretty Print specs
  pretty-spec/pretty-spec {:mvn/version "0.1.4"}
-  software.amazon.awssdk/s3 {:mvn/version "2.54.5"}
-  software.amazon.awssdk/sts {:mvn/version "2.54.5"}}
+  software.amazon.awssdk/s3 {:mvn/version "2.50.1"}
+  software.amazon.awssdk/sts {:mvn/version "2.50.1"}}

 :paths ["src" "resources" "target/classes"]
 :aliases
@@ -4,7 +4,7 @@
  "license": "MPL-2.0",
  "author": "Kaleidos INC Sucursal en España SL",
  "private": true,
-  "packageManager": "pnpm@12.3.4+sha512.961aa41fb077da3a04a441d9f8e15ebc0c96da8ef710b2eb67bf9ee7cb0610eabd48f1fd85f51cffe73846785fa0f87c56a3a872a1d893f8446741b5cce45457",
+  "packageManager": "pnpm@11.20.0+sha512.9a6f330a95b66446ea088faf1521405a8a01f07fde7124cc9958dfed52d4bb436737e65b08f85f37b46fcba375092558ac51262b816844b22f63406ed166bfee",
  "repository": {
    "type": "git",
    "url": "https://github.com/penpot/penpot"
@@ -1,104 +1,3 @@
---
-lockfileVersion: '9.0'
-
-importers:
-
-  .:
-    configDependencies: {}
-    packageManagerDependencies:
-      pnpm:
-        specifier: 12.3.4
-        version: 12.3.4
-
-packages:
-
-  '@pnpm/exe.darwin-arm64@12.3.4':
-    resolution: {integrity: sha512-PAyUol8T1+/+ViOiXAt51ECA+QnfXCqz6foL4bW+LsoX0NcVd5XVEM2mRQu+LV4oc7uRz9zf9U0P+XFfuQeDAw==}
-    cpu: [arm64]
-    os: [darwin]
-
-  '@pnpm/exe.darwin-x64@12.3.4':
-    resolution: {integrity: sha512-fxP9JCk0Cdye+ePuj+GJJLMUMTqHGWRdb1dtv4How876uQ2ehxvenpgiYAir/ceO9PsYUZkFTtyZdx+rRu5QOA==}
-    cpu: [x64]
-    os: [darwin]
-
-  '@pnpm/exe.linux-arm64-musl@12.3.4':
-    resolution: {integrity: sha512-FBOt0/7ye6O6q4AllVV5QMviB6qE6fqkeczV/+MDWQsmo+QJrlfsh6X7CpH/tClVpBZEyIbjpUoT8bNhCYBxEg==}
-    cpu: [arm64]
-    os: [linux]
-    libc: [musl]
-
-  '@pnpm/exe.linux-arm64@12.3.4':
-    resolution: {integrity: sha512-t71AVA7LRqiKTyZ5xMYaZc2n5DfdpMbfokZuiIOXHBOM03ECnF0t4iYwaBDqJgVjlKYUOwaF/bRQajGNA4cJ4w==}
-    cpu: [arm64]
-    os: [linux]
-    libc: [glibc]
-
-  '@pnpm/exe.linux-x64-musl@12.3.4':
-    resolution: {integrity: sha512-RPmk7Jb/aYaFvL2iyDN/AtMY+hUEsue732WmXpcuQ9tBpMnGyA5py7Z3+e+qmQaJ0zY/4ni9jJiyPBQHujmv6w==}
-    cpu: [x64]
-    os: [linux]
-    libc: [musl]
-
-  '@pnpm/exe.linux-x64@12.3.4':
-    resolution: {integrity: sha512-2ZqOlSPkfwX1h5cR+FPiWf8+F+2hZT/3TvhUK5sigHqwaQCIiq8R7CGxhndKs63JtcLi2a1Qpo+wX/EoyfjyJQ==}
-    cpu: [x64]
-    os: [linux]
-    libc: [glibc]
-
-  '@pnpm/exe.win32-arm64@12.3.4':
-    resolution: {integrity: sha512-ANyrHqyqco6SXBysUTRF74itDyyraea7IbFsKFdNXTjcFnfycTDx37EwuhdpPYFNSIh2JhUG4fByclsRfiHX7w==}
-    cpu: [arm64]
-    os: [win32]
-
-  '@pnpm/exe.win32-x64@12.3.4':
-    resolution: {integrity: sha512-WH/KqBPY/hq2Tb7SgQltEZytimcjgKRaCRL/aM9CI0c67iKc5TVmHUhIiL3Ux9FB4bWn36i6XewUcScQI+zG8w==}
-    cpu: [x64]
-    os: [win32]
-
-  pnpm@12.3.4:
-    resolution: {integrity: sha512-lhqkH7B32joEpEHZ+OFevAyW2o73ELLrZ7+e58sGEOq9SPH9hfUc/+c4RnhfoPh8VqOocqHYk/hEZ0G1zORUVw==}
-    engines: {node: '>=18.*'}
-    hasBin: true
-
-snapshots:
-
-  '@pnpm/exe.darwin-arm64@12.3.4':
-    optional: true
-
-  '@pnpm/exe.darwin-x64@12.3.4':
-    optional: true
-
-  '@pnpm/exe.linux-arm64-musl@12.3.4':
-    optional: true
-
-  '@pnpm/exe.linux-arm64@12.3.4':
-    optional: true
-
-  '@pnpm/exe.linux-x64-musl@12.3.4':
-    optional: true
-
-  '@pnpm/exe.linux-x64@12.3.4':
-    optional: true
-
-  '@pnpm/exe.win32-arm64@12.3.4':
-    optional: true
-
-  '@pnpm/exe.win32-x64@12.3.4':
-    optional: true
-
-  pnpm@12.3.4:
-    optionalDependencies:
-      '@pnpm/exe.darwin-arm64': 12.3.4
-      '@pnpm/exe.darwin-x64': 12.3.4
-      '@pnpm/exe.linux-arm64': 12.3.4
-      '@pnpm/exe.linux-arm64-musl': 12.3.4
-      '@pnpm/exe.linux-x64': 12.3.4
-      '@pnpm/exe.linux-x64-musl': 12.3.4
-      '@pnpm/exe.win32-arm64': 12.3.4
-      '@pnpm/exe.win32-x64': 12.3.4
-
---
 lockfileVersion: '9.0'

 settings:
@@ -1,4 +1,2 @@
-storeDir: ../.pnpm-store
-
 minimumReleaseAgeExclude:
  - brace-expansion@5.0.8 || 5.0.9
@@ -14,21 +14,10 @@
   :iterations 3
   :parallelism 2})

-(def ^:private weak-options
-  {:alg :pbkdf2+sha256
-   :iterations 100})
-
 (defn derive-password
  [password]
  (hashers/derive password default-options))

-(defn derive-password-weak
-  "Derives a password using a fast algorithm (pbkdf2+sha256, 100 iterations).
-   Intended for demo users only — they are already gated behind the
-   `demo-users` config flag which is disabled in production."
-  [password]
-  (hashers/derive password weak-options))
-
 (defn verify-password
  [attempt password]
  (try
@@ -1037,7 +1037,7 @@
            provider        (prepare-organization-sso-provider cfg sso)
            _info           (get-info cfg provider state code)
            session         (session/get-session request)
-            exp             (ct/in-future {:hours 4})]
+            exp             (ct/in-future {:minutes 15})]
        (when (and session organization-id)
          (let [props (-> (or (:props session) {})
                          (update :sso assoc organization-id exp))]
@@ -9,9 +9,7 @@
  (:require
   [app.common.exceptions :as ex])
  (:import
-   [org.passay PasswordData]
-   [org.passay.data EnglishCharacterData]
-   [org.passay.rule CharacterCharacteristicsRule CharacterRule]))
+   [org.passay CharacterCharacteristicsRule CharacterRule EnglishCharacterData PasswordData]))

 (defonce ^:private passay-code->translation-key
  {"INSUFFICIENT_LOWERCASE"   "errors.weak-password.insufficient-lowercase"
@@ -20,13 +18,12 @@
   "INSUFFICIENT_SPECIAL"     "errors.weak-password.insufficient-special"})

 (defonce ^:private character-characteristics-rule
-  (CharacterCharacteristicsRule.
-   4
-   (into-array org.passay.rule.CharacterRule
-               [(CharacterRule. EnglishCharacterData/LowerCase 1)
+  (doto (CharacterCharacteristicsRule.)
+    (.setRules [(CharacterRule. EnglishCharacterData/LowerCase 1)
                (CharacterRule. EnglishCharacterData/UpperCase 1)
                (CharacterRule. EnglishCharacterData/Digit 1)
-                (CharacterRule. EnglishCharacterData/Special 1)])))
+                (CharacterRule. EnglishCharacterData/Special 1)])
+    (.setNumberOfCharacteristics 4)))

 (defn validate-password
  "Validates password strength.
@@ -42,7 +42,6 @@
   [datoteka.io :as io])
  (:import
   java.io.File
-   java.io.FilterInputStream
   java.io.InputStream
   java.io.OutputStreamWriter
   java.lang.AutoCloseable
@@ -431,32 +430,6 @@
  [^ZipFile input ^ZipEntry entry]
  (.getInputStream input entry))

-(defn- size-limiting-stream
-  "Wraps an InputStream to enforce a maximum number of decompressed bytes.
-  Raises :validation :max-file-size-reached when the limit is exceeded."
-  ^InputStream
-  [^InputStream input ^long max-size]
-  (let [counter (atom 0)
-        on-read (fn [n]
-                  (when (pos? n)
-                    (when (> (swap! counter + (long n)) max-size)
-                      (ex/raise :type :validation
-                                :code :max-file-size-reached
-                                :hint (str "stream exceeded max size: " max-size))))
-                  n)]
-    (proxy [FilterInputStream] [input]
-      (read
-        ([]
-         (let [b (.read input)]
-           (when (pos? b) (on-read 1))
-           b))
-        ([^bytes buf]
-         (on-read (.read input buf 0 (alength buf))))
-        ([^bytes buf off]
-         (on-read (.read input buf (int off) (- (alength buf) (int off)))))
-        ([^bytes buf off len]
-         (on-read (.read input buf (int off) (int len))))))))
-
 (defn- zip-entry-reader
  [^ZipFile input ^ZipEntry entry]
  (-> (zip-entry-stream input entry)
@@ -465,12 +438,10 @@
 (defn- zip-entry-storage-content
  "Wraps a ZipFile and ZipEntry into a penpot storage compatible
  object and avoid creating temporal objects"
-  [input entry & {:keys [max-size]}]
-  (let [stream-fn (fn []
-                    (cond-> (zip-entry-stream input entry)
-                      max-size (size-limiting-stream max-size)))
-        hash      (delay (->> (stream-fn)
-                              (sto.impl/calculate-hash)))]
+  [input entry]
+  (let [hash  (delay (->> entry
+                          (zip-entry-stream input)
+                          (sto.impl/calculate-hash)))]
    (reify
      sto.impl/IContentObject
      (get-size [_]
@@ -487,7 +458,7 @@
        (throw (UnsupportedOperationException. "not implemented")))

      (make-input-stream [_ _]
-        (stream-fn))
+        (zip-entry-stream input entry))
      (make-output-stream [_ _]
        (throw (UnsupportedOperationException. "not implemented"))))))

@@ -875,9 +846,9 @@

            ext     (cmedia/mtype->extension (:content-type object))
            path    (str "objects/" id ext)
-            content (zip-entry-storage-content input
-                                               (get-zip-entry input path)
-                                               :max-size (::bfc/import-max-object-size cfg))]
+            content (->> path
+                         (get-zip-entry input)
+                         (zip-entry-storage-content input))]

        (when (not= (:size object) (sto/get-size content))
          (ex/raise :type :validation
@@ -887,15 +858,6 @@
                    :expected-size (:size object)
                    :found-size (sto/get-size content)))

-        (when-let [max (::bfc/import-max-object-size cfg)]
-          (when (> (sto/get-size content) max)
-            (ex/raise :type :validation
-                      :code :max-file-size-reached
-                      :hint (str "storage object exceeds maximum size: " (sto/get-size content))
-                      :path path
-                      :max max
-                      :found (sto/get-size content))))
-
        (when-let [hash (get object :hash)]
          (when (not= hash (sto/get-hash content))
            (ex/raise :type :validation
@@ -978,15 +940,6 @@
  (let [manifest (-> (read-manifest input)
                     (validate-manifest))
        entries  (read-zip-entries input)
-
-        _        (when-let [max (::bfc/import-max-zip-entries cfg)]
-                   (when (> (count entries) max)
-                     (ex/raise :type :validation
-                               :code :too-many-zip-entries
-                               :hint (str "zip file has too many entries: " (count entries))
-                               :max max
-                               :found (count entries))))
-
        cfg      (-> cfg
                     (assoc ::entries entries)
                     (assoc ::manifest manifest)
@@ -94,11 +94,7 @@

   ;; SSRF protection
   :ssrf-allowed-hosts #{}
-   :ssrf-extra-blocked-cidrs #{}
-
-   ;; Binfile import limits
-   :binfile-import-max-object-size (* 1024 1024 100) ;; 100 MiB
-   :binfile-import-max-zip-entries (* 500 1000)})    ;; 500,000
+   :ssrf-extra-blocked-cidrs #{}})

 (def schema:config
  (do #_sm/optional-keys
@@ -155,10 +151,6 @@
    [:media-processing-service-uri {:optional true} ::sm/uri]
    [:media-processing-service-timeout {:optional true} ::sm/int]

-    ;; Binfile import limits (PENPOT_BINFILE_IMPORT_*)
-    [:binfile-import-max-object-size {:optional true} ::sm/int]
-    [:binfile-import-max-zip-entries {:optional true} ::sm/int]
-
    [:deletion-delay {:optional true} ::ct/duration]
    [:file-clean-delay {:optional true} ::ct/duration]
    [:telemetry-enabled {:optional true} ::sm/boolean]
@@ -31,8 +31,8 @@
   com.zaxxer.hikari.HikariDataSource
   com.zaxxer.hikari.HikariPoolMXBean
   com.zaxxer.hikari.metrics.prometheus.PrometheusMetricsTrackerFactory
-   io.whitfin.siphash.SipHash
-   io.whitfin.siphash.SipHashContext
+   io.whitfin.siphash.SipHasher
+   io.whitfin.siphash.SipHasherContainer
   java.io.InputStream
   java.io.OutputStream
   java.sql.Connection
@@ -701,12 +701,12 @@
 ;; --- Locks

 (def ^:private siphash-state
-  (SipHash/context
-    (uuid/get-bytes uuid/zero)))
+  (SipHasher/container
+   (uuid/get-bytes uuid/zero)))

 (defn uuid->hash-code
  [o]
-  (.hash ^SipHashContext siphash-state
+  (.hash ^SipHasherContainer siphash-state
         ^bytes (uuid/get-bytes o)))

 (defn- xact-check-param
@@ -15,7 +15,6 @@
  (:require
   [app.common.schema :as sm]
   [app.util.ssrf :as ssrf]
-   [app.worker :as-alias wrk]
   [cuerdas.core :as str]
   [integrant.core :as ig]
   [java-http-clj.core :as http])
@@ -24,8 +23,6 @@
   java.net.URI))

 (def default-max-redirects 5)
-(def default-connect-timeout 30000)
-(def default-request-timeout 30000)

 (defn client?
  [o]
@@ -36,17 +33,15 @@
  :pred client?})

 (defmethod ig/init-key ::client
-  [_ {:keys [::wrk/executor]}]
-  (http/build-client {:connect-timeout default-connect-timeout
-                      :executor executor
+  [_ _]
+  (http/build-client {:connect-timeout 30000
                      :follow-redirects :never}))

 (defn send!
  ([client req] (send! client req {}))
  ([client req {:keys [response-type] :or {response-type :string}}]
   (assert (client? client) "expected valid http client")
-   (http/send (merge {:timeout default-request-timeout} req)
-              {:client client :as response-type})))
+   (http/send req {:client client :as response-type})))

 (defn- resolve-client
  [params]
@@ -322,9 +322,7 @@
                                ::bfc/overwrite false
                                ::bfc/profile-id profile-id
                                ::bfc/project-id project-id
-                                ::bfc/input path
-                                ::bfc/import-max-object-size (cf/get :binfile-import-max-object-size)
-                                ::bfc/import-max-zip-entries (cf/get :binfile-import-max-zip-entries))]
+                                ::bfc/input path)]
          (bf.v3/import-files! cfg)
          {::yres/status  200
           ::yres/headers {"content-type" "text/plain"}
@@ -360,9 +358,7 @@
                        ::bfc/profile-id profile-id
                        ::bfc/project-id project-id
                        ::bfc/input path
-                        ::bfc/features (cfeat/get-team-enabled-features cf/flags team)
-                        ::bfc/import-max-object-size (cf/get :binfile-import-max-object-size)
-                        ::bfc/import-max-zip-entries (cf/get :binfile-import-max-zip-entries))]
+                        ::bfc/features (cfeat/get-team-enabled-features cf/flags team))]

      (if (= format :binfile-v3)
        (bf.v3/import-files! cfg)
@@ -200,7 +200,7 @@
   {::db/pool (ig/ref ::db/pool)}

   ::http.client/client
-   {::wrk/executor (ig/ref ::wrk/executor)}
+   {}

   ::session/manager
   {::db/pool (ig/ref ::db/pool)}
@@ -392,8 +392,6 @@

     :delete-object
     (ig/ref :app.tasks.delete-object/handler)
-     :demo-purge
-     (ig/ref :app.tasks.demo-purge/handler)
     :process-webhook-event
     (ig/ref ::webhooks/process-event-handler)
     :run-webhook
@@ -431,9 +429,6 @@
   :app.tasks.delete-object/handler
   {::db/pool (ig/ref ::db/pool)}

-   :app.tasks.demo-purge/handler
-   {::db/pool (ig/ref ::db/pool)}
-
   :app.tasks.file-gc/handler
   {::db/pool     (ig/ref ::db/pool)
    ::sto/storage (ig/ref ::sto/storage)}
@@ -75,10 +75,10 @@
                           {:method method
                            :uri uri
                            :body body
-                            :headers headers
-                            :timeout timeout}
+                            :headers headers}
                           {:response-type :input-stream
-                            :skip-ssrf-check? true})
+                            :skip-ssrf-check? true
+                            :timeout timeout})
            status (:status resp)]
        (when (not (<= 200 status 299))
          (let [body (:body resp)]
@@ -93,9 +93,7 @@
            (assoc ::bfc/features (cfeat/get-team-enabled-features cf/flags team))
            (assoc ::bfc/project-id project-id)
            (assoc ::bfc/profile-id profile-id)
-            (assoc ::bfc/name name)
-            (assoc ::bfc/import-max-object-size (cf/get :binfile-import-max-object-size))
-            (assoc ::bfc/import-max-zip-entries (cf/get :binfile-import-max-zip-entries)))
+            (assoc ::bfc/name name))

        input-path (:path file)
        owned?     (some? upload-id)
@@ -231,11 +231,8 @@
   ::sm/params schema:get-comment-threads}
  [cfg {:keys [::rpc/profile-id file-id share-id] :as params}]
  (db/run! cfg (fn [{:keys [::db/conn] :as cfg}]
-                 (let [perms (files/check-comment-permissions! cfg profile-id file-id share-id)
-                       threads (get-comment-threads conn profile-id file-id)]
-                   (if (= :share-link (:type perms))
-                     (filterv #(contains? (:pages perms) (:page-id %)) threads)
-                     threads)))))
+                 (files/check-comment-permissions! cfg profile-id file-id share-id)
+                 (get-comment-threads conn profile-id file-id))))

 (defn- get-comment-threads-sql
  [where]
@@ -332,15 +329,9 @@
   ::sm/params schema:get-comment-thread}
  [cfg {:keys [::rpc/profile-id file-id id share-id] :as params}]
  (db/run! cfg (fn [{:keys [::db/conn] :as cfg}]
-                 (let [perms  (files/check-comment-permissions! cfg profile-id file-id share-id)
-                       thread (some-> (db/exec-one! conn [sql:get-comment-thread profile-id file-id id])
-                                      (decode-row))]
-                   (when (and thread (= :share-link (:type perms)))
-                     (when-not (contains? (:pages perms) (:page-id thread))
-                       (ex/raise :type :not-found
-                                 :code :object-not-found
-                                 :hint "not found")))
-                   thread))))
+                 (files/check-comment-permissions! cfg profile-id file-id share-id)
+                 (some-> (db/exec-one! conn [sql:get-comment-thread profile-id file-id id])
+                         (decode-row)))))

 ;; --- COMMAND: Retrieve Comments

@@ -357,13 +348,8 @@
   ::sm/params schema:get-comments}
  [cfg {:keys [::rpc/profile-id thread-id share-id]}]
  (db/run! cfg (fn [{:keys [::db/conn] :as cfg}]
-                 (let [{:keys [file-id page-id]} (get-comment-thread conn thread-id)
-                       perms (files/check-comment-permissions! cfg profile-id file-id share-id)]
-                   (when (and (= :share-link (:type perms))
-                              (not (contains? (:pages perms) page-id)))
-                     (ex/raise :type :not-found
-                               :code :object-not-found
-                               :hint "not found"))
+                 (let [{:keys [file-id]} (get-comment-thread conn thread-id)]
+                   (files/check-comment-permissions! cfg profile-id file-id share-id)
                   (get-comments conn thread-id)))))

 (def sql:get-comments
@@ -390,26 +376,18 @@

 (def ^:private sql:file-comment-users
  "WITH available_profiles AS (
-     SELECT DISTINCT c.owner_id AS id
-     FROM comment c
-     JOIN comment_thread ct
-       ON ct.id = c.thread_id
-    WHERE ct.file_id = ?::uuid
-  ),
-  profile_ids AS (
-    SELECT id FROM available_profiles
-    UNION
-    SELECT ?::uuid
+     SELECT DISTINCT owner_id AS id
+       FROM comment
+      WHERE thread_id IN (SELECT id FROM comment_thread WHERE file_id=?)
  )
  SELECT p.id,
         p.email,
         p.fullname AS name,
-         p.fullname,
+         p.fullname AS fullname,
         p.photo_id,
         p.is_active
-    FROM profile p
-    JOIN profile_ids AS x
-      ON x.id = p.id;")
+    FROM profile AS p
+   WHERE p.id IN (SELECT id FROM available_profiles) OR p.id=?")

 (defn get-file-comments-users
  [conn file-id profile-id]
@@ -7,10 +7,9 @@
 (ns app.rpc.commands.demo
  "A demo specific mutations."
  (:require
-   [app.auth :refer [derive-password-weak]]
+   [app.auth :refer [derive-password]]
   [app.common.exceptions :as ex]
-   [app.common.schema :as sm]
-   [app.common.uuid :as uuid]
+   [app.common.time :as ct]
   [app.config :as cf]
   [app.db :as db]
   [app.loggers.audit :as audit]
@@ -18,33 +17,25 @@
   [app.rpc.commands.auth :as auth]
   [app.rpc.doc :as-alias doc]
   [app.util.services :as sv]
-   [app.worker :as wrk]
   [buddy.core.codecs :as bc]
   [buddy.core.nonce :as bn]))

-(def ^:private
-  schema:create-demo-profile
-  [:map
-   [:skip-onboarding {:optional true} ::sm/boolean]])
-
 (sv/defmethod ::create-demo-profile
  "A command that is responsible of creating a demo purpose
  profile. It only works if the `demo-users` flag is enabled in the
  configuration."
  {::rpc/auth false
   ::doc/added "1.15"
-   ::doc/changes [["1.15" "This method is migrated from mutations to commands."]
-                  ["2.18" "Add optional `skip-onboarding` param. When true, the profile is created with `onboarding-viewed` and `release-notes-viewed` (current version) set, skipping the onboarding flow."]]
-   ::sm/params schema:create-demo-profile}
-  [cfg {:keys [skip-onboarding]}]
+   ::doc/changes ["1.15" "This method is migrated from mutations to commands."]}
+  [cfg _]

  (when-not (contains? cf/flags :demo-users)
    (ex/raise :type :validation
              :code :demo-users-not-allowed
              :hint "Demo users are disabled by config."))

-  (let [sem      (uuid/next)
-        email    (str "demo-" sem "@demo.example.com")
+  (let [sem      (System/currentTimeMillis)
+        email    (str "demo-" sem ".demo@example.com")
        fullname (str "Demo User " sem)

        password (-> (bn/random-bytes 16)
@@ -55,23 +46,13 @@
                  :fullname fullname
                  :is-active true
                  :is-demo true
-                  :password (derive-password-weak password)
-                  :props (cond-> {}
-                           skip-onboarding (assoc :onboarding-viewed true
-                                                  ;; Redundant today: auth/create-profile
-                                                  ;; overwrites this with the current
-                                                  ;; version, kept so the skip does not
-                                                  ;; depend on that default.
-                                                  :release-notes-viewed (:main cf/version)))}
+                  :deleted-at (ct/in-future (cf/get-deletion-delay))
+                  :password (derive-password password)
+                  :props {}}
        profile  (db/tx-run! cfg (fn [cfg]
                                   (->> (auth/create-profile cfg params)
                                        (auth/create-profile-rels cfg))))]
-
-    (wrk/submit! (-> cfg
-                     (assoc ::wrk/task :demo-purge)
-                     (assoc ::wrk/delay (cf/get-deletion-delay))
-                     (assoc ::wrk/params {:profile-id (:id profile)})))
-
    (with-meta {:email email
                :password password}
      {::audit/profile-id (:id profile)})))
+
@@ -95,23 +95,18 @@
 (def check-read-permissions!
  (perms/make-check-fn has-read-permissions?))

-;; A user has comment permissions if:
-;; - For :membership type: they have read permissions OR explicit comment permissions
-;; - For :share-link type: they must have explicit comment permissions (who-comment=all)
-;;   This prevents share-link holders with who-comment=team from bypassing the restriction
+;; A user has comment permissions if she has read permissions, or
+;; explicit comment permissions through the share-id

 (defn check-comment-permissions!
  [cfg profile-id file-id share-id]
-  (let [perms    (perms/get-file-read-permissions cfg profile-id file-id share-id)
-        allowed? (if (= :share-link (:type perms))
-                   (has-comment-permissions? perms)
-                   (or (has-read-permissions? perms)
-                       (has-comment-permissions? perms)))]
-    (when-not allowed?
+  (let [perms       (perms/get-file-read-permissions cfg profile-id file-id share-id)
+        can-read    (has-read-permissions? perms)
+        can-comment (has-comment-permissions? perms)]
+    (when-not (or can-read can-comment)
      (ex/raise :type :not-found
                :code :object-not-found
-                :hint "not found"))
-    perms))
+                :hint "not found"))))

 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
 ;; QUERY COMMANDS
@@ -241,18 +236,6 @@
  (some-> (db/get cfg :file-data {:file-id file-id :id fragment-id :type "fragment"})
          (update :data blob/decode)))

-(defn- check-fragment-scope!
-  "Checks that the fragment is reachable from the pages authorized by
-  the share-link. Raises a :not-found exception if the fragment is not reachable."
-  [cfg file-id fragment-id pages]
-  (let [fdata (-> (bfc/get-file cfg file-id :read-only? true)
-                  (get :data)
-                  (update :pages-index select-keys pages))]
-    (when-not (contains? (feat.fdata/get-used-pointer-ids fdata) fragment-id)
-      (ex/raise :type :not-found
-                :code :object-not-found
-                :hint "object not found"))))
-
 (sv/defmethod ::get-file-fragment
  "Retrieve a file fragment by its ID. Only authenticated users."
  {::doc/added "1.17"
@@ -262,9 +245,11 @@
  [cfg {:keys [::rpc/profile-id file-id fragment-id share-id]}]
  (db/run! cfg (fn [cfg]
                 (let [perms (perms/get-file-read-permissions cfg profile-id file-id share-id)]
-                   (check-read-permissions! perms)
                   (when (= :share-link (:type perms))
-                     (check-fragment-scope! cfg file-id fragment-id (:pages perms)))
+                     (ex/raise :type :not-found
+                               :code :object-not-found
+                               :hint "object not found"))
+                   (check-read-permissions! perms)
                   (-> (get-file-fragment cfg file-id fragment-id)
                       (rph/with-http-cache long-cache-duration))))))

@@ -426,9 +426,7 @@
                     (assoc ::bfc/project-id project-id)
                     (assoc ::bfc/profile-id profile-id)
                     (assoc ::bfc/input template)
-                     (assoc ::bfc/features (cfeat/get-team-enabled-features cf/flags team))
-                     (assoc ::bfc/import-max-object-size (cf/get :binfile-import-max-object-size))
-                     (assoc ::bfc/import-max-zip-entries (cf/get :binfile-import-max-zip-entries)))
+                     (assoc ::bfc/features (cfeat/get-team-enabled-features cf/flags team)))

        result   (if (= format :binfile-v3)
                   (bf.v3/import-files! cfg)
@@ -141,7 +141,9 @@
 (defn get-profile
  "Get profile by id. Throws not-found exception if no profile found."
  [conn id & {:as opts}]
-  (-> (db/get-by-id conn :profile id opts)
+  ;; NOTE: We need to set ::db/remove-deleted to false because demo profiles
+  ;; are created with a set deleted-at value
+  (-> (db/get-by-id conn :profile id (assoc opts ::db/remove-deleted false))
      (decode-row)))

 ;; --- MUTATION: Update Profile (own)
@@ -944,10 +944,8 @@
   ::sm/params schema:delete-team-member
   ::db/transaction true}
  [{:keys [::db/conn ::mbus/msgbus] :as cfg} {:keys [::rpc/profile-id team-id member-id] :as params}]
-  (let [team    (get-team conn :profile-id profile-id :team-id team-id)
-        perms   (get-permissions conn profile-id team-id)
-        members (get-team-members conn team-id)
-        member  (d/seek #(= member-id (:id %)) members)]
+  (let [team  (get-team conn :profile-id profile-id :team-id team-id)
+        perms (get-permissions conn profile-id team-id)]
    (when-not (or (:is-owner perms)
                  (:is-admin perms))
      (ex/raise :type :validation
@@ -957,15 +955,6 @@
      (ex/raise :type :validation
                :code :cant-remove-yourself))

-    (when-not member
-      (ex/raise :type :not-found
-                :code :member-does-not-exist))
-
-    (when (and (:is-owner member)
-               (not (:is-owner perms)))
-      (ex/raise :type :validation
-                :code :cant-remove-owner))
-
    (db/delete! conn :team-profile-rel {:profile-id member-id
                                        :team-id team-id})

@@ -235,8 +235,9 @@
                       :organization-name (:name organization)
                       :member-email (:email-to invitation)
                       :member-id (:id member)
-                       :role role
-                       :user-who-send-invitation (str profile-id)}
+                       :role role}
+                organization
+                (assoc :user-who-send-invitation (str profile-id))

                (not organization)
                (assoc :team-belongs-to-organization (boolean team-organization-id)
@@ -308,9 +308,7 @@
                     (assoc :name "accept-organization-invitation")
                     (assoc :props
                            (-> props
-                                (assoc :organization-id organization-id-on-add
-                                       :user-id (:id profile)
-                                       :user-who-send-invitation (:created-by invitation))
+                                (assoc :organization-id organization-id-on-add)
                                (audit/clean-props))))))

              (cond-> (assoc claims :state :created)
@@ -327,8 +325,6 @@
                            (assoc :organization-id organization-id-on-add
                                   :organization-member-add-source organization-add-source
                                   :belongs-to-team-on-add (boolean team-id)
-                                   :user-id (:id profile)
-                                   :user-who-send-invitation (:created-by invitation)
                                   :organization-member-count-before
                                   organization-member-count-before)
                            (audit/clean-props))}))))))
@@ -56,7 +56,7 @@
      (assoc :can-read true)))

 (defn- get-view-only-bundle
-  [{:keys [::db/conn] :as cfg} {:keys [profile-id file-id share-id ::perms] :as params}]
+  [{:keys [::db/conn] :as cfg} {:keys [profile-id file-id ::perms] :as params}]
  (let [file    (bfc/get-file cfg file-id)

        project (db/get conn :project
@@ -89,18 +89,16 @@
                     (mapv (fn [{:keys [id] :as lib}]
                             (merge lib (bfc/get-file cfg id)))))

-        links   (cond->> (->> (db/query conn :share-link {:file-id file-id})
-                              (mapv (fn [row]
-                                      (-> row
-                                          (update :pages db/decode-pgarray #{})
-                                          ;; NOTE: the flags are deprecated but are still present
-                                          ;; on the table on old rows. The flags are pgarray and
-                                          ;; for avoid decoding it (because they are no longer used
-                                          ;; on frontend) we just dissoc the column attribute from
-                                          ;; row.
-                                          (dissoc :flags)))))
-                  (= :share-link (:type perms))
-                  (filterv #(= (:id %) share-id)))
+        links   (->> (db/query conn :share-link {:file-id file-id})
+                     (mapv (fn [row]
+                             (-> row
+                                 (update :pages db/decode-pgarray #{})
+                                 ;; NOTE: the flags are deprecated but are still present
+                                 ;; on the table on old rows. The flags are pgarray and
+                                 ;; for avoid decoding it (because they are no longer used
+                                 ;; on frontend) we just dissoc the column attribute from
+                                 ;; row.
+                                 (dissoc :flags)))))

        fonts   (db/query conn :team-font-variant
                          {:team-id (:id team)
@@ -41,7 +41,6 @@
   [app.rpc.notifications :as notifications]
   [app.storage :as sto]
   [app.util.services :as sv]
-   [app.util.ssrf :as ssrf]
   [app.worker :as wrk]
   [cuerdas.core :as str]))

@@ -961,18 +960,13 @@ RETURNING id, deleted_at;")
 (sv/defmethod ::check-organization-sso
  "Validate an organization SSO configuration by generating a login redirect URL.
  Nitrate calls this while configuring SSO to verify client credentials and OIDC
-  discovery before saving the settings. The issuer URL is nitrate-supplied
-  (customer-configured), so it is checked against the SSRF blocklist before
-  any outbound request is attempted."
+  discovery before saving the settings."
  {::doc/added "2.18"
   ::sm/params cto/schema:nitrate-sso
   ::sm/result schema:check-organization-sso-result
   ::rpc/auth false}
  [cfg params]
-  (let [issuer (oidc/organization-sso-discovery-uri params)]
-    {:valid (boolean (and issuer
-                          (ssrf/safe-url? issuer)
-                          (oidc/is-organization-sso-config-valid? cfg params)))}))
+  {:valid (oidc/is-organization-sso-config-valid? cfg params)})

 ;; ---- API: notify-organization-sso-change
 (sv/defmethod ::notify-organization-sso-change
@@ -1051,18 +1045,3 @@ RETURNING id, deleted_at;")
                (update acc :created conj email)))))
        {:created [] :skipped []}
        emails)))))
-
-;; ---- API: get-air-gapped
-
-(def ^:private schema:get-air-gapped-result
-  [:map
-   [:air-gapped ::sm/boolean]])
-
-(sv/defmethod ::get-air-gapped
-  "Returns whether this Penpot instance runs in air-gapped mode."
-  {::doc/added "2.18"
-   ::sm/params [:map]
-   ::sm/result schema:get-air-gapped-result
-   ::rpc/auth false}
-  [_cfg _params]
-  {:air-gapped (contains? cf/flags :air-gapped-conf)})
@@ -1,41 +0,0 @@
-;; This Source Code Form is subject to the terms of the Mozilla Public
-;; License, v. 2.0. If a copy of the MPL was not distributed with this
-;; file, You can obtain one at http://mozilla.org/MPL/2.0/.
-;;
-;; Copyright (c) KALEIDOS INC Sucursal en España SL
-
-(ns app.tasks.demo-purge
-  "Task handler for delayed demo profile deletion. Submitted at demo
-   creation time with a delay matching the configured deletion-delay."
-  (:require
-   [app.common.logging :as l]
-   [app.common.time :as ct]
-   [app.db :as db]
-   [app.worker :as wrk]
-   [integrant.core :as ig]))
-
-(defmethod ig/assert-key ::handler
-  [_ params]
-  (assert (db/pool? (::db/pool params)) "expected a valid database pool"))
-
-(defmethod ig/init-key ::handler
-  [_ cfg]
-  (fn [{:keys [props]}]
-    (let [profile-id (get props :profile-id)
-          now        (ct/now)]
-
-      (l/trc :hint "demo-purge" :profile-id (str profile-id))
-
-      ;; Mark the profile for immediate deletion
-      (db/tx-run! cfg
-                  (fn [{:keys [::db/conn] :as cfg}]
-                    (db/update! conn :profile
-                                {:deleted-at now}
-                                {:id profile-id}
-                                {::db/return-keys false})
-                    (wrk/submit!
-                     (-> cfg
-                         (assoc ::wrk/task :delete-object)
-                         (assoc ::wrk/params {:object :profile
-                                              :deleted-at now
-                                              :id profile-id}))))))))
@@ -13,7 +13,6 @@
   [app.db :as db]
   [app.features.fdata :as fdata]
   [app.storage :as sto]
-   [app.tasks.delete-object :as dobj]
   [integrant.core :as ig]))

 (def ^:private sql:get-profiles
@@ -34,11 +33,6 @@
                 ;; Mark as deleted the storage object
                 (some->> photo-id (sto/touch-object! storage))

-                 ;; Cascade soft-delete to owned teams, projects, files, etc.
-                 (dobj/delete-object cfg {:object :profile
-                                          :id id
-                                          :deleted-at timestamp})
-
                 (let [affected (-> (db/delete! conn :profile {:id id})
                                    (db/get-update-count))]
                   (+ total affected)))
@@ -17,6 +17,7 @@
   [app.http.client :as http]
   [app.main :as-alias main]
   [app.setup :as-alias setup]
+   [app.util.blob :as blob]
   [app.util.json :as json]
   [integrant.core :as ig]
   [promesa.exec :as px]))
@@ -247,16 +248,20 @@
    :props      (or (some-> props db/decode-transit-pgobject) {})
    :context    (or (some-> context db/decode-transit-pgobject) {})}))

+(defn- encode-batch
+  "Encode a sequence of event maps into a fressian+zstd base64 string
+  suitable for JSON transport."
+  ^String [events]
+  (blob/encode-str events {:version 4}))
+
 (defn send-event-batch
  "Send a single batch of events to the telemetry endpoint. Returns
-  true on success. The events are sent as a plain vector of event
-  maps; the JSON encoder handles UUID and temporal types natively and
-  the receiver coerces them back to proper types."
+  true on success."
  [{:keys [::setup/props] :as cfg} batch]
  (let [payload {:type :telemetry-events
                 :version (:full cf/version)
                 :instance-id (:instance-id props)
-                 :events (vec batch)}
+                 :events (encode-batch batch)}
        request {:method  :post
                 :uri     (cf/get :telemetry-uri)
                 :headers {"content-type" "application/json"}
@@ -5,12 +5,7 @@
 ;; Copyright (c) KALEIDOS INC Sucursal en España SL

 (ns app.util.ssrf
-  "URL/host validation to prevent Server-Side Request Forgery.
-
-   The blocklist covers the standard JVM InetAddress classifications plus
-   explicit ranges: IPv6 ULA, IPv4-mapped loopback, cloud metadata,
-   operator-supplied CIDRs and the IPv6 transition mechanisms NAT64, 6to4
-   and Teredo."
+  "URL/host validation to prevent Server-Side Request Forgery."
  (:require
   [app.common.exceptions :as ex]
   [app.common.logging :as l]
@@ -127,20 +122,6 @@
         ;; Check the embedded IPv4 is loopback (127.x.x.x)
         (= (bit-and (aget bs 12) 0xFF) 127))))

-(defn- transition-prefix
-  "Classify a 16-byte IPv6 address into its transition mechanism:
-   :nat64 (64:ff9b::/96), :6to4 (2002::/16), :teredo (2001:0000::/32) or nil."
-  [^bytes bs]
-  (let [b0 (bit-and (aget bs 0) 0xFF)
-        b1 (bit-and (aget bs 1) 0xFF)
-        b2 (bit-and (aget bs 2) 0xFF)
-        b3 (bit-and (aget bs 3) 0xFF)]
-    (cond
-      (and (= b0 0x00) (= b1 0x64) (= b2 0xFF) (= b3 0x9B)) :nat64
-      (and (= b0 0x20) (= b1 0x02))                         :6to4
-      (and (= b0 0x20) (= b1 0x01) (= b2 0x00) (= b3 0x00)) :teredo
-      :else nil)))
-
 (defn- blocked-address?
  "Check if an InetAddress should be blocked. Returns true if blocked."
  [^InetAddress addr]
@@ -160,15 +141,12 @@
   ;; Cloud metadata IPs (exact match)
   (contains? cloud-metadata-ips (.getHostAddress addr))

-   ;; Extra blocked CIDRs (IPv4 only) and IPv6 transition mechanisms
+   ;; Extra blocked CIDRs (IPv4 only)
   (let [bs (.getAddress addr)]
     (if (= (alength bs) 4)
       (or (some #(in-cidr4? bs %) extra-blocked-ranges)
           (some #(in-cidr4? bs %) extra-blocked-cidrs))
-       ;; IPv6 transition mechanisms (NAT64/6to4/Teredo): the range is
-       ;; rejected outright.
-       (boolean (when (= (alength bs) 16)
-                  (transition-prefix bs)))))))
+       false))))

 (defn resolve-host
  "Resolve a hostname to all InetAddress objects. Wraps InetAddress/getAllByName
@@ -185,10 +163,8 @@
    - host must resolve to at least one address, and
    - **every** resolved address must NOT be in the blocklist
      (loopback, link-local, site-local, multicast, any-local,
-      cloud-metadata 169.254.169.254, IPv6 ULA fc00::/7, IPv6 transition
-      mechanisms NAT64 64:ff9b::/96, 6to4 2002::/16 and Teredo
-      2001:0000::/32, IPv4-mapped IPv6 of any blocked IPv4,
-      plus operator-supplied CIDRs).
+      cloud-metadata 169.254.169.254, IPv6 ULA fc00::/7, IPv4-mapped
+       IPv6 of any blocked IPv4, plus operator-supplied CIDRs).
   When the host is an IP literal (decimal/octal/hex/IPv6) it is
   normalized via `com.google.common.net.InetAddresses` before the
   check.
@@ -23,7 +23,6 @@
   [app.storage :as sto]
   [app.storage.tmp :as tmp]
   [backend-tests.helpers :as th]
-   [backend-tests.storage-test :as stt]
   [clojure.test :as t]
   [cuerdas.core :as str]
   [datoteka.fs :as fs]
@@ -253,88 +252,3 @@
          ;; With the guard, it raises :validation :max-file-size-reached.
          (t/is (= :validation (:type out)))
          (t/is (= :max-file-size-reached (:code out))))))))
-
-(t/deftest import-rejects-too-many-zip-entries
-  ;; import must reject ZIP files exceeding max-zip-entries
-  (let [profile (th/create-profile* 1)
-        file    (prepare-simple-file profile)
-        output  (tmp/tempfile :suffix ".zip")]
-
-    (v3/export-files!
-     (-> th/*system*
-         (assoc ::bfc/ids #{(:id file)})
-         (assoc ::bfc/embed-assets false)
-         (assoc ::bfc/include-libraries false))
-     (io/output-stream output))
-
-    ;; Import with max-zip-entries=1 — the exported ZIP has more entries
-    (let [cfg (-> th/*system*
-                  (assoc ::bfc/project-id (:default-project-id profile))
-                  (assoc ::bfc/profile-id (:id profile))
-                  (assoc ::bfc/input output)
-                  (assoc ::bfc/import-max-zip-entries 1))
-          out (try
-                (v3/import-files! cfg)
-                :no-error
-                (catch Throwable e
-                  (let [d (or (ex-data e) (some-> (ex-cause e) ex-data))]
-                    d)))]
-      (t/is (= :validation (:type out)))
-      (t/is (= :too-many-zip-entries (:code out))))))
-
-(defn- prepare-file-with-media
-  "Creates a file with a media object backed by a real storage object,
-  so that v3 export produces objects/ entries."
-  [profile]
-  (let [storage (-> (:app.storage/storage th/*system*)
-                    (stt/configure-storage-backend))
-
-        sobject (sto/put-object! storage {::sto/content (sto/content "media-bytes")
-                                          :content-type "image/svg+xml"
-                                          :bucket "file-media-object"})
-
-        file    (th/create-file* 1 {:profile-id (:id profile)
-                                    :project-id (:default-project-id profile)
-                                    :is-shared false})
-
-        mobj    (th/create-file-media-object* {:file-id (:id file)
-                                               :is-local true
-                                               :media-id (:id sobject)})]
-    (update-file!
-     :file-id (:id file)
-     :profile-id (:id profile)
-     :revn 0
-     :vern 0
-     :changes
-     [{:type :add-media
-       :object mobj}])
-
-    (dissoc file :data)))
-
-(t/deftest import-rejects-oversized-object
-  ;; import must reject storage objects exceeding max-object-size
-  (let [profile (th/create-profile* 1)
-        file    (prepare-file-with-media profile)
-        output  (tmp/tempfile :suffix ".zip")]
-
-    (v3/export-files!
-     (-> th/*system*
-         (assoc ::bfc/ids #{(:id file)})
-         (assoc ::bfc/embed-assets false)
-         (assoc ::bfc/include-libraries false))
-     (io/output-stream output))
-
-    ;; Import with max-object-size=1 — the media object will exceed this
-    (let [cfg (-> th/*system*
-                  (assoc ::bfc/project-id (:default-project-id profile))
-                  (assoc ::bfc/profile-id (:id profile))
-                  (assoc ::bfc/input output)
-                  (assoc ::bfc/import-max-object-size 1))
-          out (try
-                (v3/import-files! cfg)
-                :no-error
-                (catch Throwable e
-                  (let [d (or (ex-data e) (some-> (ex-cause e) ex-data))]
-                    d)))]
-      (t/is (= :validation (:type out)))
-      (t/is (= :max-file-size-reached (:code out))))))