[QA] Test oc10 - oCIS migration

[deyankiteworks]

We need to test and verify how is working the migration from an oc10 to an oCIS instance.

1. Run oc10 using Docker Compose - https://doc.owncloud.com/server/next/admin_manual/installation/docker/#docker-compose
2. Run oCIS using Docker Compose - https://owncloud.dev/clients/web/getting-started/#installation

[DeepDiver1975]

🤖 Automated issue triage by Claude Code review agent.

Triage: internal QA task (analysis-only).

This is an internal QA test-execution task — verify the oc10 → oCIS migration path by standing up both stacks via Docker Compose and running through a migration. It isn't a bug report or a user-facing feature request, so there is no single code change to make from triage alone.

A couple of notes to keep this actionable:

• The linked oCIS getting-started reference points at the web-client docs; for a self-contained migration test you'll likely want the current oCIS deployment-example compose setup as well so both ends are reproducible.
• Issue Migration with Keycloak #19 ("Migration with Keycloak") already captures concrete blockers that surface during such a test run (OIDC-over-HTTP/PKCE setup, the "must have logged in to both systems" precondition, and the OC10-username ↔ oCIS-identity mapping when Keycloak uses email as the username). Worth running this QA pass with Migration with Keycloak #19 open in parallel so findings feed back there.

Is this test pass still planned / in progress? If it's been completed or superseded, please close with a short note on the outcome.