Merge main and retain Fetch recovery release notes

This commit is contained in:
vorotamoroz committed 2026-11-09 11:54:40 +00:00
commit cf57a19ec4
11 files changed
+594 -1

No files matched your search

+13
View File
@@ -86,6 +86,7 @@ npm run test:e2e:obsidian:focused -- local-file-retry
npm run test:e2e:obsidian:focused -- folder-batch
npm run test:e2e:obsidian:focused -- security-seed-reconnect
npm run test:e2e:obsidian:focused -- couchdb-http-cache
npm run test:e2e:obsidian:focused -- fetch-on-demand-chunks
npm run test:e2e:obsidian:focused -- replication-status
npm run test:e2e:obsidian:focused -- sync-guard
```
@@ -399,6 +400,18 @@ Set `E2E_OBSIDIAN_ARTIFACT_ROOT` to a directory containing the exact release `ma
When these checks pass for the release artefacts, BRAT acceptance can be limited to installation or update, enabling the plug-in, and a cold start. Check any other changes included in that release using their own regression scenarios. The diagnostic export checks verify report payloads; they do not exercise the operating system's clipboard or download implementation on iOS or Android.
### Fetch with on-demand Chunks
`fetch-on-demand-chunks` checks Standard Fetch finalisation for an existing Vault
when native Request API selection makes Fast Setup fall back from Streaming
replication. It uses encrypted CouchDB, obfuscated paths, internal Metadata
encryption, Markdown and attachment files, and on-demand Chunk retrieval. The
scenario requires local Chunks to be absent before the strict scan, then checks
remote delivery, exact file bytes, unchanged Metadata revisions, provenance,
readiness, and released suspension after finalisation. It covers the shared
failure path reported in #1329 and #1332; a Linux Obsidian run does not establish
verification on the reporter's iPadOS/WebKit device.
### Environment variables
- `OBSIDIAN_BINARY`: explicit Obsidian executable path.