From 0763617116aa4050edb5b554b50b668fc37cc9bf Mon Sep 17 00:00:00 2001 From: Roger Deng <13251150+rogerdigital@users.noreply.github.com> Date: Sun, 13 Sep 2026 20:17:29 +0800 Subject: [PATCH] docs: record clean-vault installation verification for 1.0.0 --- docs/verification/1.0.0-readiness.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/verification/1.0.0-readiness.md b/docs/verification/1.0.0-readiness.md index 23d42d2..79f45cf 100644 --- a/docs/verification/1.0.0-readiness.md +++ b/docs/verification/1.0.0-readiness.md @@ -130,7 +130,7 @@ The user subsequently confirmed that the outstanding items listed in the impleme | Desktop keyboard and drag | PASS (user-confirmed) | Full keyboard and drag acceptance confirmed by the user | | Remaining desktop visual/error matrix | PASS | Closed by the supplementary 2026-09-13 runtime pass below (flat-fixture, width, duplicate-basename, search, and creation error paths) | | One large flat folder | PASS | Closed by the supplementary 2026-09-13 runtime pass below | -| Published 1.0 assets | PASS (installation pending) | Release published with hash-verified assets; clean-vault installation spot-check prepared and tracked in the publication record below | +| Published 1.0 assets | PASS | Release published with hash-verified assets; clean-vault installation spot-check completed — see the publication record below | Windows/Linux were not available in either run; do not claim they were tested. These missing checks are release gates, not proof of a defect. @@ -187,4 +187,4 @@ Known residual: context-menu-driven inline rename error paths (invalid/collision | Published release | https://github.com/rogerdigital/smart-explorer/releases/tag/1.0.0 (published 2026-09-13 11:08:31 UTC, not a draft) | | Attached assets | `main.js` (70,532 B), `manifest.json` (318 B), `styles.css` (14,137 B) | | Download verification | All three assets downloaded from the release; SHA-256 byte-identical to the recorded candidate hashes; manifest reports 1.0.0 with min app version 1.7.2 | -| Clean-vault installation | PENDING — a clean vault with the downloaded assets pre-installed was prepared at `/tmp/se-1.0.0-clean-vault` (three notes including a wiki-link pair, plugin enabled via `community-plugins.json`, no `data.json`). The running Obsidian instance's accessibility bridge became unavailable before the browse/search/create/rename/link-update/manual-order/reload spot-check could be executed, and the machine was back in active use. Open that folder as a vault to complete the check; record the outcome here afterwards. | +| Clean-vault installation | PASS — the downloaded release assets were installed into a fresh `/tmp/se-1.0.0-clean-vault` (no `data.json`, plugin pre-enabled via `community-plugins.json`), opened in real Obsidian 1.13.7 via "Open folder as vault", and trusted. The plugin loaded at 1.0.0 and indexed 3 files; row activation opened the note with selection tracking; search "Clean" filtered to 2 of 3 with auto-expanded ancestors and the clear-filters control; inline create made `Install Check.md` (footer 3 → 4, row selected); after View → Force Reload the plugin reloaded with the 4-file count, tree state, and selection intact. Rename/link-update and manual order were not repeated here: the installed assets are byte-identical to the candidate covered by the runtime matrix above. The temporary vault and its window were removed afterwards. |