[opendev9]

Problem

After #25 removed the legacy Compose overlay values, an existing deployment whose .env did not explicitly set CF_ENABLE_S3_STORAGE=true keeps its persisted multi routing (so old libraries stay readable), but bootstrap regenerates [cloudfile] s3_storage_enabled = false. cf_pin_default_local_storage is gated by that switch, so new libraries silently land in the default seafile-data instead of their own auto-local directory. This violates "legacy deployments keep their behavior".

Change

• library_storage.retained_legacy_switch(): true when the persisted config still has enable_storage_classes = true and s3_storage_enabled = true.
• bootstrap.write_cloudfile_seafile_conf(): when legacy backend sections are retained and that switch was on, keep s3_storage_enabled = true. Explicit CF_LIBRARY_STORAGE=auto and new installs are unaffected.
• Test regressions from fix(build): unify full dev builds and immutable receipts #26 on dev:
  • tests/test_v2_native_config.py and tests/test_v2_web_paths.py still pointed at build/v2, which fix(build): unify full dev builds and immutable receipts #26 archived; they move to docs/history/storage-build-20261020/tests/ with their paths updated (19 tests, OK).
  • test_application_assembly.test_changed_native_pin_refuses_reuse_without_creating_output set seafile-server ref to 'a'*40, which equals the new source-lock.json fixture value, so nothing changed and the refusal never fired. It now uses 'c'*40.

Validation

cd tests && python3 -m unittest discover -s . -p 'test_*.py'
Ran 144 tests — only error: test_automatic_local_storage (local host lacks pytest)
pytest test_automatic_local_storage.py   # in a venv with pytest: 19 passed
python3 -m unittest test_library_storage_config   # 17 OK, incl. 2 new legacy-switch tests

Before this PR, dev had 1 failure plus the 2 archived-test import errors (and the same pytest import error).

No deployment or image build.

🤖 Generated with Claude Code