[sophiecarreras]

The repository-owned files.list conformance check could not tell whether ls --recursive was honoured: with flat names a CLI that ignores the option sends the same requests and the check still passed.

• The check now also uploads list/sub/d.txt and list/sub/e.txt.
• The recursive listing must contain both; a plain (non-recursive) ls must return the three top-level names plus the folder entry list/sub/ (read as plain text, because --json prints a folder as its first file).

Verified at the pinned B2 simulator: the real CLI 5.0.2 passes; a mutant where ls ignores --recursive fails; a mutant where ls is always recursive fails; the old check passed the ignore-option mutant. Test infrastructure only: no change to the CLI's behaviour.

🤖 Generated with Claude Code

[sophiecarreras]

Review: changes only .sdkharness/tests/conformance-file-lifecycle.py and a changelog.d fragment. The files.list check now uploads two nested names and asserts that 'ls' without --recursive collapses them into one folder entry (top-level names plus list/sub/), while the recursive listing still returns all names; the versions check correctly moves to top_level[-1]. Logic is sound. The first run had two failures unrelated to the diff: test-docker test_rm_b2id (500 internal_error 'internal incident' from the B2 service) and macos test_sync_up (socket.gaierror name resolution); unit suites passed. One rerun of the failed jobs is now fully green. Merging normally.