Validate versioned Obsidian E2E targets

[vrtmrz]

Adds explicit version qualification to the real-Obsidian E2E harness, so supported runs use reviewed assets while exploratory versions remain clearly unverified.

Summary

• add a reviewed AppImage catalogue for Obsidian 1.12.7 and 1.13.6, with exact ARM64 and x86_64 asset names and SHA-256 digests
• default managed Linux sessions to Obsidian 1.13.6 and keep downloads, extractions, and release metadata separated by version and architecture
• allow exact catalogue-external versions only through E2E_OBSIDIAN_ALLOW_UNVERIFIED_VERSION=true, label them as unverified probes, and reject that option from the validated suite
• observe the version from the active renderer, compare it with the requested target, and report its catalogue status in session readiness
• select the main Vault renderer when Obsidian opens a Settings pop-out first, and recognise the current mobile Modal header control
• document the release-qualification boundary, commands, environment controls, and packed-consumer API

Rationale

The previous installer derived AppImage names from a single pattern, reused one shared extraction directory, and did not prove that the running renderer matched the requested Obsidian version. That could silently exercise a stale binary, and the derived x86_64 filename did not match the official unsuffixed asset name. Obsidian 1.13.6 also exposed renderer-order and mobile Modal DOM assumptions in the existing harness.

The reviewed catalogue and runtime version check keep release evidence reproducible. The explicit unverified path preserves a convenient early regression probe without treating its result as support evidence.

User and developer impact

Managed Linux E2E now targets Obsidian 1.13.6 by default. E2E_OBSIDIAN_VERSION selects another exact reviewed target. A version outside the catalogue requires the explicit unverified option and cannot pass test:e2e:obsidian:validated.

Executable discovery and session start-up remain offline operations; AppImages are downloaded only by the explicit installer command.

Verification

• NODE_OPTIONS=--max-old-space-size=3072 npm run verify:workspace
• NODE_OPTIONS=--max-old-space-size=3072 npm run verify:packed-consumer
• Obsidian 1.13.6 ARM64: all 10 validated real-application E2E scenarios passed
• Obsidian 1.12.7 ARM64: all 10 validated real-application E2E scenarios passed
• Obsidian 1.13.4 ARM64: all 10 scenarios passed while reported as an unverified probe
• confirmed that an unverified version is rejected without the explicit option
• confirmed that the validated suite rejects the unverified-version option before launching Obsidian
• captured and visually reviewed the desktop lifecycle, mobile prompt, long dialogue, and grouped Notice states