[michvllni]

Two issues from a real Dropbox sync, plus the follow-on cleanup.

1. Debug mode now offers to save the log

A debug run is read off a 30-line screen that scrolls, so by the time it reaches whatever went wrong, the version, the init log and the config summary are long gone. Photographing the screen is what a bug report ended up being made of.

Everything written to the console is now captured while debug mode is on, and the end of the run offers to write it to /3ds/3DSync/logs/debug-<stamp>.log — A saves, B discards.

The capture is fed by teeing stdout rather than by routing every printf through debugf(): libctru's console is a newlib devoptab, so a copy of it with write_r wrapped records the run exactly as it appeared. It has to be installed after the last consoleInit(), which replaces devoptab_list[STD_OUT] with its own.

• Only the first 96 KB and the last 48 KB are kept; a long run drops its middle and says in the file how much.
• debugLogSave() strips ANSI sequences and runs debugRedact() over the finished text, not per write — a token can straddle two console writes.
• The save is offered, not done: the file is plaintext on a shared SD card and the run listed every save path, so the prompt says so.

2. The spurious Dropbox API error: HTTP 409

Every sync printed a red 409 with a path/conflict/folder body between the entry header and Listing, then carried on and worked. ensureRoot() called create_folder_v2 on every run and already treated 409 as success — but _performWithRetry() printed the error before the caller ever saw the status.

_rpc() / _performWithRetry() now take an expectedStatus: the status is still returned and still explained through debugf(), but the console line is suppressed. Where the expectation turns out to be wrong, the caller prints the reason itself.

ensureRoot() now probes with get_metadata and only creates when the probe says path/not_found. Request count is a wash — the folder exists on every run but the first, so it trades a write that 409s for a read that succeeds, at the cost of one extra round trip on the first run. In exchange the steady state is read-only, and "is this a folder" comes from a .tag field rather than the wording of an error.

That also fixes a latent bug: any 409 was previously swallowed as success, so a file sitting where the sync folder belongs, a malformed Path= and a missing write permission all "succeeded" here and failed later. Dropbox separates those only by error_summary, so the reading of it lives in remoteparse.cpp as dropboxPathState() — host-testable against the real response bodies — rather than inline in the provider.

No new OAuth scope: files.metadata.read was already required by list_folder.

3. Dropbox is no longer marked experimental

Per @michvllni, tested thoroughly. isExperimental() defaults to true so a new backend cannot forget the notice, so Dropbox opts out explicitly. README table, landing page and configurator drop the badge; SMB, FTP and WebDAV keep theirs.

4. Version

APP_VERSION 0.5.1 → 0.6.0. v0.5.1 is already tagged, and this branch adds a user-facing feature and promotes a backend out of experimental, so the minor moves. Per the release process in version.h this is step one; the tag comes after this lands on master, and release.yml's Version Check fails the release if the two disagree.

5. Devcontainer — split out to #23

The gh / extension change was originally here, but pr.yml rebuilds the toolchain image from scratch whenever a PR touches docker/*Dockerfile, and pkg.devkitpro.org is currently behind a Cloudflare block (HTTP 403 on dkp-linux.db). That is a third-party outage, not a code problem, but it would keep this PR red for as long as it lasts — so it now lives in #23 and this PR takes the docker pull path again.

Testing

• make builds clean for the 3DS.
• make -C tests: 115 passed, 0 failed (was 101). Each commit builds and passes in isolation.
• 5 new debuglog cases: the capture must stay empty outside debug mode, stay bounded on a long run, reset between runs, and reach the SD card with colour codes gone and tokens masked.
• 9 new dropboxPathState cases pinning each real Dropbox response body — including that path/malformed_path and path/no_write_permission are not read as success, and that an unparseable 2xx is not treated as a verdict.

Not exercised on hardware — the devoptab tee and the SD write are the parts worth a real-console check before merge.

🤖 Generated with Claude Code