Prepare v4.0.2

.agents/skills/changelog/SKILL.md

@@ -0,0 +1,156 @@
+---
+
+name: changelog
+description: Generate a draft CHANGELOG entry for the next release from merged GitHub pull requests. Asks the user for the target version before starting.
+----------------------------------------------------------------------------------------------------------------------------------------------------------
+
+# Skill: Generate CHANGELOG draft
+
+> **This skill produces a working draft, not a finished changelog.** The output is a starting point to make the task easier — the maintainer must review, edit and refine every entry before committing.
+
+Generate a draft entry for `CHANGELOG.md` based on the pull requests merged since the last published release.
+
+If you can modify files, insert the new entry into `CHANGELOG.md` as described below. Otherwise, output the completed block ready to be inserted manually.
+
+---
+
+## 0. Ask for the target version
+
+**Before doing anything else**, ask the user:
+
+> What will the version number and type be for this release?
+> Examples: `v4.0.0-rc2`, `v4.0.1`, `v4.1.0-beta1`
+
+Wait for the answer. Use that value verbatim for the heading — do not infer or calculate it from the existing CHANGELOG.
+
+The release date is **today's date** in `YYYY-MM-DD` format.
+
+---
+
+## 1. Find the latest published release on GitHub
+
+Fetch the latest release to get the cut-off timestamp:
+
+```sh
+gh release view --repo exelearning/mod_exeweb --json tagName,publishedAt
+```
+
+Record:
+
+* **`tagName`** — the git tag of the last release (e.g. `v4.0.0-rc1`).
+* **`publishedAt`** — the ISO timestamp used to filter merged PRs.
+
+---
+
+## 2. Collect all merged PRs since the last release
+
+```sh
+gh pr list \
+  --repo exelearning/mod_exeweb \
+  --state merged \
+  --search "merged:>YYYY-MM-DDTHH:MM:SSZ" \
+  --json number,title,body,labels,mergedAt \
+  --limit 200
+```
+
+> Replace the timestamp with the `publishedAt` value from step 1.
+
+If the result reaches the limit, continue fetching additional pages until all merged PRs have been processed.
+
+For each PR, read:
+
+* **`title`** — the PR headline.
+* **`body`** — the **full description**. This is the primary source; many PRs bundle several unrelated changes under a single title.
+* **`labels`** — supporting context only. When labels conflict with the PR body, prefer the PR body.
+* **`mergedAt`** — for verification if needed.
+
+If a PR body references issues with `Closes #NNN` or `Fixes #NNN`, fetch them too:
+
+```sh
+gh issue view NNN --repo exelearning/mod_exeweb --json title,body
+```
+
+---
+
+## 3. Write the entries
+
+Follow the **exact style** of the existing changelog entries in `CHANGELOG.md`.
+
+### Style rules
+
+* **One sentence per bullet.** Start with a capital letter; no trailing full stop.
+* Describe the **outcome for users**, not the implementation.
+
+  * ✅ `Sort iDevice: exercises with identical cards are now correctly validated`
+  * ❌ `Fixed a bug in the validation logic of SortIdevice.js`
+* Use component prefixes only when they improve clarity and match the style already used in the changelog (e.g. `TinyMCE:`, `File Manager:`).
+* Avoid technical jargon unless it is already common in the existing changelog (e.g. `blob:`, `asset://`, `SCORM`).
+* Dependency upgrades: `package-name: OLD → NEW` (lowercase, `→`, no extra words).
+* Group related entries together.
+
+### What NOT to include
+
+* Duplicate entries for the same fix.
+* Multiple translation-only bullets when they can reasonably be combined.
+* Dependency-only PRs with no user-visible effect may be grouped into a single bullet if there are many minor updates.
+* Merge commits.
+* Version-bump-only PRs.
+* Purely internal changes (CI, tests, linting, formatting) unless they have a significant user or developer impact.
+
+---
+
+## 4. Assemble the block
+
+```markdown
+## vX.Y.Z-type – YYYY-MM-DD
+
+- …
+- …
+```
+
+---
+
+## 5. Insert into `CHANGELOG.md`
+
+Insert the new block immediately after the `# CHANGELOG` heading, before the previous version entry.
+
+```markdown
+# CHANGELOG
+
+## vX.Y.Z-type – YYYY-MM-DD
+…
+…
+
+## v4.0.0-rc1 – 2026-04-07
+…
+```
+
+Do **not** modify any existing content below the insertion point.
+
+---
+
+## 6. Remind the user this is a draft
+
+After generating the entry, tell the user:
+
+> ⚠️ This is a draft. Please review every entry before committing:
+>
+> * Check that descriptions are accurate and clear for end users.
+> * Merge or remove redundant entries.
+> * Add anything the PRs may not have described explicitly.
+
+---
+
+## Reference: existing entry style
+
+```markdown
+## v4.0.1 – 2026-06-09
+
+- Show the eXeLearning "Edit" button on the activity view when "Display" is set to "In pop-up", "Open" or "New window".
+- Remove the legacy "In frame" display option and migrate existing activities to "Embed" during upgrade.
+- Fix embedded editor version detection in release packages so the correct eXeLearning version is reported.
+- Improve accessibility by updating embedded content frame titles dynamically based on the activity and page title.
+- Exclude development files from release packages.
+- Update the README to clarify Moodle compatibility, editor modes and support information.
+- Automatically install and configure the embedded editor in Playground environments.
+```

.distignore

@@ -2,6 +2,7 @@
 .github
 .gitignore
 .aider*
+.agents
 .claude
 .DS_Store
 .distignore

AGENTS.md

@@ -120,6 +120,14 @@ Uses Moodle's file API — packages stored in `mod_exeweb/package` filearea, exp
 - GitHub Actions `release.yml` triggers on git tags: fetches editor, builds, packages, uploads to GitHub Release
 - `check-editor-releases.yml` runs daily to auto-release when new editor versions appear
 
+## Agent skills (`.agents/`)
+
+The `.agents/skills/` directory contains Claude Code project skills — reusable prompt workflows invoked with `/skill-name` in the Claude Code CLI. They are development tooling only and are excluded from release packages via `.distignore`.
+
+| Skill | File | Purpose |
+|-------|------|---------|
+| `changelog` | `.agents/skills/changelog/SKILL.md` | Draft a CHANGELOG entry from merged GitHub PRs since the last release |
+
 ## Twin-plugin checks (mod_exeweb ↔ mod_exescorm)
 
 `mod_exeweb` and [`mod_exescorm`](https://github.com/exelearning/mod_exescorm) share large amounts of code, history, and bug surface (embedded editor, action bar, packaging pipeline, online callbacks, etc.). **Before closing a fix, always cross-check the sibling plugin:**

CHANGELOG.md

@@ -1,5 +1,15 @@
 # CHANGELOG
 
+## v4.0.2 – 2026-07-07
+
+- Allow saving the plugin settings page without requiring an optional package template file.
+- Fix Playground environments loading an outdated embedded editor version when `.editor-version` had already been updated.
+- Automatically keep the Playground blueprint editor URL in sync with `.editor-version` on each release.
+- Review and complete the Spanish (es) translation.
+- Review all language packs and add placeholder translations for newly introduced strings in incomplete translations.
+
+---
+
 ## v4.0.1 – 2026-06-09
 
 - Show the eXeLearning "Edit" button on the activity view when "Display" is set to "In pop-up", "Open" or "New window".