[DO NOT MERGE]: unstable to hotfixes, Q1 major release

[marcellamaki]

!IMPORTANT!

ensure_versioned_databases_exist and create_channel_versions migration commands should be added to Makefile's deploy-migrate command just before merging this PR.

Summary

…

Vuetify → KDS Migration

Tracking issue: #5060

This overview sets the scope of regression testing needed before release. The refactoring work replaces Vuetify components with Kolibri Design System (KDS) components across Studio. For each workflow, we're primarily focused on interactions and functionality — making sure nothing broke in the migration. Some minor visual differences are expected and noted below.

For detailed context on any specific change, issue links are included per section. When in doubt about whether something is a regression or an intentional change, check the linked issues.

General notes:

• Compare production vs. unstable
• All modals will have some visual differences due to switching to KDS — this is expected and not a concern (see the Settings section for a visual example). Focus on whether the modal opens, functions correctly, and closes correctly.
• Radina: a11y testing across all workflows is very welcome as time allows.

---

1. Settings (/settings)

We're regression testing all 3 tabs. The priority is interactions and functionality.

What changed: Page layout, offline alert bar, and several components across the Account and Storage tabs were migrated from Vuetify to KDS.

Account tab:

• Change password form — test that the form opens, validation works, and a password can be changed successfully
• Copy token input — test copy interaction
• "Failed to delete account" alert — trigger and confirm it displays correctly
• "Data export started" alert — trigger and confirm it displays

Storage tab:

• Storage overview loader — confirm it shows correctly while loading
• "Request more space" form — test the slide transition opening, form validation (error banner), and successful submission
• "About licenses" modal — open it and confirm all links inside are functional

General:

• Offline alert bar — confirm it appears correctly when offline
• All buttons, links, and interactive elements across the page

Visual differences: Modals (e.g., "About licenses", "Request more space") will look slightly different from production due to KDS styling. Functionality is the priority.

Related issues: #5061, #5062, #5063, #5064, #5080, #5081, #5082, #5092, #5095, #5123, #5127, #5132

2. Channels (/channels)

Several distinct sub-areas were touched here. Test each sub-area as a workflow.

What changed: Channel cards across all channel listing views, channel detail pages, channel collections, the Content Library, error pages, and several modals were all migrated.

2a. Channel listing views (My Channels, Starred, View-only)

• Channel cards render correctly in all three views (My Channels, Starred, View-only)
• Top-level buttons (e.g., create channel, search) work as expected
• Offline alert bar appears when offline
• Channel card interactions: open a channel, star/unstar, and any context menu or overflow actions

Related issues: #5218, #5219, #5227, #5524, #5525

2b. Channel detail page

• Channel detail page layout and content load correctly
• Edit channel details — confirm buttons work and changes save
• Channel collection options (dropdown or context menu actions on a collection)
• Invitations — send an invite, confirm UI for pending/accepted states
• Channel collections table — confirm it renders and is interactive

Visual differences: Modals on the channel detail page (e.g., unsaved changes) will look slightly different.

Related issues: #5217, #5474, #5484, #5485, #5529, #5530

2c. New collection / Unsaved changes

• Create a new collection — confirm buttons work, collection name input and validation behaves correctly (test empty submission and character limits)
• Collection channels loader — confirm loading state displays
• "Unsaved changes" modal — navigate away with unsaved changes and confirm modal appears and both actions (discard / keep editing) work

Visual differences: "Unsaved changes" modal will look slightly different from production.

Related issues: #5243, #5244, #5298, #5299

2d. Content Library

• Content Library catalog page loads correctly
• Cards render correctly
• Buttons, links, and dropdown interactions work
• Side panel opens and closes correctly
• FAQ page ("Frequently asked questions") renders and links work
• "About collections" modal — open and confirm links are functional

Visual differences: "About collections" modal will look slightly different.

Related issues: #5234, #5471, #5502, #5526, #5528

2e. Error pages

• "Channel not found" — trigger by navigating to an invalid channel URL
• "Page not found" — trigger with a bad route
• "Something went wrong" — if triggerable, confirm rendering
• "Did you forget to sign in?" — confirm this renders when accessing a protected channel while logged out

Related issues: #5235, #5295, #5296, #5297

3. Channel Editor

The channel editor had the most changes across this migration — many dialogs and action buttons throughout the editing workflow were updated. Test these as you would a normal editing session, but make a point to trigger each dialog.

What changed: Buttons and dialogs throughout the editing workflow — move, upload, questions, import, and several confirmation dialogs.

Organize / Move:

• Move modal — open it, confirm buttons work, and create a new folder from within the modal (the "create new folder" dialog inside Move)

Upload:

• Upload files — confirm upload buttons work and the upload flow completes
• Upload in progress dialog — confirm it displays during upload
• Save failed dialog — confirm it displays on a save failure (may need to simulate)

Questions:

• Questions tab — confirm buttons work
• Change question type — confirm the confirmation dialog appears and both actions (confirm / cancel) work

Content actions:

• Finish button — confirm it works and the "Incomplete resource" modal appears when applicable
• Permanently delete resource — confirm the confirmation dialog appears and deletion works
• Alert dialog — confirm it appears and responds correctly

Related tab:

• Confirm buttons and links in the Related tab are functional
• Add previous / next step buttons work

File preview:

• View fullscreen and exit fullscreen buttons work

Import from channels:

• Buttons and links in Import from Channels work
• Saved searches — save a search, confirm the saved search dialogs work (save, view, delete)

Navigation / errors:

• "Channel not found" error page renders correctly in the editor context

Visual differences: All dialogs/modals in the channel editor (move, upload, confirm delete, change question type, etc.) will look slightly different from production.

Related issues: #5355, #5375, #5376, #5377, #5378, #5379, #5420, #5421, #5422, #5423, #5442, #5443, #5444, #5470, #5472, #5473

4. Accounts

These are the pre-login and account lifecycle pages. Testing is straightforward — confirm all interactive elements function correctly.

What changed: Buttons and links on the sign-in, account created, and account deleted pages; various informative pages.

• Sign-in page — confirm all buttons and links work (sign in, forgot password link, create account link)
• Account created page — confirm the page renders and any buttons/links function
• Account deleted page — confirm the page renders and any buttons/links function
• Informative pages (e.g., activation failed, reset password) — confirm these render correctly and interactive elements work

Related issues: #5352, #5353, #5534, #5631, #5632, #5633, #5636, #5637

5. Administration (/administration)

Admin-only pages. Confirm all management actions and their confirmation dialogs work end-to-end.

What changed: Buttons and confirmation dialogs for user and channel management actions; the send email dialog.

Users:

• Disk space popup — trigger from the Users table (storage icon or similar) and confirm it opens/displays correctly
• Deactivate user — trigger confirmation dialog, confirm both actions work
• Delete user — trigger confirmation dialog, confirm both actions work
• Add / remove admin privileges — trigger dialogs and confirm both actions work

Channels:

• Delete channel — trigger confirmation dialog and confirm
• Restore channel — trigger confirmation dialog and confirm
• Toggle visibility — trigger confirmation dialog and confirm

Email:

• Send email dialog — trigger, confirm it opens, and test sending

Visual differences: All confirmation dialogs and the send email dialog will look slightly different from production.

Related issues: #5354, #5410, #5411, #5425, #5441

6. Policy modals

Policy modals

• Trigger policy modals wherever they appear (e.g., Terms of Service, Privacy Policy links in footer or sign-in)
• Confirm they open, render content, and close correctly
• Confirm any links within the modals are functional* (note, pending is the DCMA form fix-- which as of 9 March is only in hotfixes)

Visual differences: Policy modals will look slightly different from production.

Related issues: #5651

Easy Sharing of Community Channels (ESoCC)

Tracking issue: learningequality/kolibri-ecosystem#42

Overview

This document sets the scope of QA testing for the Easy Sharing of Community Channels feature — a set of new workflows that allow channel editors to submit channels for inclusion in a Community Library, and admins to review and approve those submissions.

The four primary workflows are:

1. Publishing a channel draft version for review and testing in Kolibri
2. Submitting a channel to the Community Library
3. Admin review and approval of submissions
4. Channel editor notifications

General notes:

• Test on unstable
• These workflows are interconnected — a full pass works best by following a submission from creation (as a channel editor) through to approval or flagging (as an admin) and then checking the resulting notification (as an editor)
• The draft publish feature (Introducing Content Curation #1 below) is gated behind the test_dev_feature feature flag — confirm it is enabled before testing that workflow
• Radina: a11y testing is very welcome, especially around focus trapping in side panels and keyboard navigation in the notifications page

---

This feature focuses on two user types — channel editors (regular Studio users who create and manage channels) and Studio admins (internal Learning Equality staff who review submissions). Since aspects of the workflows are interdependent, setting up two accounts to start may make testing more efficient.

• Account A: channel editor — a regular Studio user with edit access to at least one published channel
• Account B: admin — a Studio admin account

(I tried to test the UX with just one admin account and definitely confused myself 😓 )

You can test draft channel publishing workflow separately (Section 1), since it's pretty self-contained.

Community channels (suggested) testing flow:

1. As Account A, submit a channel to the Community Library (Section 2)
2. As Account B, find the submission in the admin channels table and review it — approve one submission and flag another with a note (Section 3)
3. As Account A, check that notifications appear and reflect the correct status (Section 4)

(This will probably have to be repeated for several different scenarios such as publishing a channel while a submission is still under review, approving vs. not, etc.)

---

1. Draft channel publishing

Channel editors can now publish a new version of a channel as a "draft" — this allows the new version to be tested in Kolibri without publishing it as the live version for users. Draft versions get their own token for import into Kolibri.

Note: This workflow requires the test_dev_feature feature flag to be enabled.

Publishing a draft:

• Open a channel with unpublished changes — this can be a channel with an existing live version (make some edits to re-enable publishing) or a channel that has never been published (pre-v1)
• Open the publish side panel — confirm there is now an option to publish as a draft (in addition to the standard publish)
• Publish as a draft — confirm the task completes successfully
• Confirm the draft token appears in the channel UI after publishing
• Confirm the draft version does not replace or affect the current live/published version when looking for the channel in the Kolibri UI — note: if the change includes a channel title update, the title may reflect the draft version due to a known issue (kolibri#6354)
• Copy the draft token and import the channel into Kolibri using that token — confirm the draft version of the channel is importable and reflects the changes made

Version history in publish side panel:

• Open the publish side panel — confirm a "See all versions" button is present
• Click it — confirm the version history expands inline and shows prior publish notes in context
• Collapse the version history — confirm it closes correctly

After publishing a channel that already has a Community Library submission:

• After completing a standard publish, confirm a modal appears prompting the editor to resubmit to the Community Library
• Click "Resubmit" — confirm it opens the Submit to Community Library side panel
• Dismiss the modal — confirm it does not reappear until the next relevant publish

Related issues: #4471, #5172, #5192, #5209, #5460, #5461, #5463, #5567, #5617, #5629

---

2. Submitting a channel to the Community Library

Channel editors can submit a published channel for inclusion in the Community Library. The submission includes metadata (country, subject), and the system runs a license audit to flag any content that may not be distributable.

Accessing the submission panel:

• Open a channel you have edit access to that has been published — confirm a "Share" button is visible in the channel header/toolbar
• Open a channel you only have view access to — confirm the Share button is not visible
• Click Share on the editable channel — confirm the "Submit to Community Library" side panel opens

To test the license audit warning states, you'll need a published channel that contains at least one resource with an "All Rights Reserved" license. Add such a resource, publish the channel, then open the submission panel — the audit should flag it.

Filling out the submission form:

• Confirm the panel shows the current channel version being submitted
• Fill in the country and description fields — confirm both are interactive
• Confirm that languages and subjects are auto-populated based on the channel's resources (these are not user-inputted)
• Confirm form validation works: attempt to submit with required fields empty
• Confirm the license audit runs and its results are displayed (a success notice if all licenses are valid; a warning notice listing any invalid licenses)
• If special permissions are flagged, confirm they appear as a checklist — confirm the Submit button remains disabled until all boxes are checked
• Submit the channel — confirm the submission completes and the panel updates to reflect pending status

Subsequent submissions and state messaging:

• Open the panel on a channel with a pending submission — confirm an info message is shown indicating the submission is still under review
• Open the panel on a channel whose last submission was flagged — confirm the flagged status and reason are displayed
• If the channel is actively being published when the panel is open, confirm a loader displays rather than stale or broken data

After publishing a channel that already has a Community Library submission:

• After completing a publish, confirm a modal appears prompting the editor to resubmit to the Community Library
• Click "Resubmit" — confirm it opens the Submit to Community Library side panel
• Dismiss the modal — confirm it does not reappear until the next relevant publish

Deleting a channel that is live in the Community Library:

• Attempt to delete a channel that has already been approved and is live in the Community Library — confirm a warning appears in the delete modal explaining that the channel will remain in the Community Library even after deletion
• Confirm that completing the deletion does not remove the channel from the Community Library

Related issues: #5159, #5145, #5157, #5158, #5169, #5262, #5448, #5449, #5450, #5451, #5452, #5453, #5459, #5568

---

3. Admin review and approval workflows

What this is: The admin channels table has been updated to surface Community Library submission status, and a new review flow allows admins to approve, flag, or add notes to submissions.

Admin channels table (/administration/channels):

• Log in as an admin and navigate to the admin channels table
• Confirm a "Community status" column is present on the table
• Confirm the "All channels" filter is available and working
• Filter by community status — confirm filtering returns correct results
• Confirm that deleted channels do not appear erroneously in community library views

Community Library details page:

• In the admin channels table, find a channel that has a submission — confirm a status chip is visible in the "Community status" column
• Click the chip — confirm it navigates to the Community Library details page for that channel
• Confirm the page shows channel details and submission activity history, sorted most recent first
• Confirm the activity history section can be collapsed and expanded
• Confirm the channel details card can be collapsed and expanded
• If there are multiple submissions for a channel, confirm all appear in the history

Review side panel:

• Open the review side panel for a pending submission — confirm submission metadata (country, subject, license audit results) is displayed
• Approve the submission — confirm the channel status updates and the channel is added to the Community Library
• Confirm the approved channel does not appear in Kolibri as part of the standard Kolibri Library (Community Library channels should remain separate)
• Open a different pending submission and flag it — confirm the flagged status is saved
• When flagging, add an explanatory note to the channel editor — confirm the note saves and is visible

Related issues: #5173, #5170, #5171, #5191, #5208, #5250, #5251, #5263, #5301, #5302, #5455, #5580, #5581, #5627

---

4. Channel editor notifications

What this is: When an admin approves or flags a submission, the submitting channel editor receives a notification. A red dot appears on their username and in the sidebar, and a notifications page shows the submission status and any feedback from the admin.

Setup — use separate accounts: This workflow requires actions from two different roles. We recommend testing with two separate browser sessions (or one normal + one incognito window) to avoid confusion:

• Account A: channel editor — a regular Studio user who has edit access to a channel and has made a Community Library submission
• Account B: admin — a Studio admin who will approve or flag that submission

Trying to do both from the same account makes the UX difficult to follow and can mask issues.

Note: The notifications page shows all submissions across all channels the user is an editor of, and all resolutions (approvals/rejections) for those submissions.

Red dot / notification indicator:

• As Account A (channel editor), submit a channel to the Community Library
• As Account B (admin), approve or flag that submission
• Back in Account A, reload the page — confirm a red dot appears on the username in the top nav
• Confirm the red dot also appears in the sidebar
• Access the notifications page via either the username menu or the sidebar link — confirm both entry points work
• Confirm the red dot clears after clicking the "Clear all" button on the notifications page (the red dot does not clear simply from viewing the page)

Notification recipients:

• As Account A, submit a channel to the Community Library — confirm that other editors on the same channel (i.e. not the submitter) also receive a notification that the channel has been submitted for review
• As Account B, resolve a submission (approve or flag) — confirm that all editors of that channel receive a notification, not only the editor who created the submission

Notifications page:

• Confirm the notifications page loads correctly
• Reload the page — confirm the notifications page persists (it is implemented as an immersive page)
• Confirm an approved submission appears with an "approved" status
• Have Account B flag a submission with an explanatory note — confirm the flagged status and the admin's note are visible in Account A's notifications
• Confirm keyboard navigation through the notifications list is logical and matches the visual order

Related issues: #5174, #5456, #5457, #5458

---

AI usage

Significant Claude help in drafting QA team guidance

Add an explicit permissions block at the workflow root in .github/workflows/i18n-download.yml so the default token is constrained for all jobs.
Best minimal fix without changing current behavior:

• Add:
  • contents: read (recommended minimum baseline)
• Because this workflow creates a pull request and may push/update a branch through the PR action, include:
  • pull-requests: write
  • contents: write

Placing this at the top-level applies to the existing download job and keeps the workflow behavior intact while removing implicit permission defaults.

Add an explicit permissions block to the workflow, ideally at the root so it applies to all jobs unless overridden. For this workflow, the minimal safe baseline is contents: read, which is sufficient for actions/checkout and does not grant unnecessary write access.

In .github/workflows/i18n-upload.yml, insert the following directly under the on: section (before jobs:), keeping existing logic unchanged:

• permissions:
• contents: read

No additional imports, methods, or definitions are needed (YAML workflow config only).