BerryUIKI · Nov 7, 2026 · Nov 7, 2026 · Nov 7, 2026 · Nov 7, 2026
diff --git a/README.md b/README.md
@@ -243,10 +243,10 @@ Output: `src-tauri/target/release/bundle/`
 <picture>
   <source media="(prefers-color-scheme: dark)" srcset="docs/screenshots/roadmap_status_dark.svg">
   <source media="(prefers-color-scheme: light)" srcset="docs/screenshots/roadmap_status_light.svg">
-  <img alt="Omera roadmap status at v0.5.0: thirteen milestones complete, video and model-ecosystem milestones partially complete, and milestones 17–19 planned" src="docs/screenshots/roadmap_status_dark.svg" width="100%">
+  <img alt="Omera roadmap status at v0.6.0: fourteen milestones complete, video and ComfyUI studio milestones in progress, and milestones 18–19 planned" src="docs/screenshots/roadmap_status_dark.svg" width="100%">
 </picture>
 
-**Milestone 15 (video)** and **Milestone 16 (Flux.1 / SD3.5 + Civitai)** are partially complete. The remaining items are resolution/codec/motion-score facets and the ComfyUI workflow visualizer. Milestone 20 (image compression) is delivered; Milestones 17–19 cover real-time ComfyUI workflows, the LAN web companion and color analytics.
+**Milestone 15 (video)** needs resolution, codec and motion-score facets, and **Milestone 17 (ComfyUI studio)** still needs remote output transfer and reconnect history replay. Milestone 20 (image compression) is delivered; Milestones 18–19 cover the LAN web companion and color analytics.
 
 📖 See [docs/ROADMAP.md](docs/ROADMAP.md) for the full checklist.
 

diff --git a/docs/DELIVERY_ROADMAP.md b/docs/DELIVERY_ROADMAP.md
@@ -1,6 +1,6 @@
 # Omera delivery roadmap
 
-> **Historical delivery plan.** Phase 5 stabilization is the current phase; see [ROADMAP.md](ROADMAP.md) and [STABILIZATION_EXECUTION.md](STABILIZATION_EXECUTION.md).
+> **Historical delivery plan.** Phases 0–4 are complete and Phase 5 stabilization is the current phase; see [ROADMAP.md](ROADMAP.md) and [STABILIZATION_EXECUTION.md](STABILIZATION_EXECUTION.md). The only release gate still open is installed-update acceptance in [#256](https://github.com/BerryUIKI/Omera/issues/256).
 
 This roadmap separates lead-owned safety work from general-engineer implementation. Detailed task cards and issue links are in [ENGINEERING_HANDOFF.md](ENGINEERING_HANDOFF.md). No dates are promised before dependencies and validation are complete.
 
@@ -54,19 +54,26 @@ Exit: required automated checks and platform/manual matrix pass; release blocker
 
 ## Phase 5 — Stabilization and 1.0 review (in progress)
 
-The current October review task sequence and acceptance ledger is
-[STABILIZATION_EXECUTION.md](STABILIZATION_EXECUTION.md). September baseline and
-assignment snapshots are historical; use current approved `dev` for fixes.
+The October review task sequence and acceptance ledger is
+[STABILIZATION_EXECUTION.md](STABILIZATION_EXECUTION.md). All of its rows except
+[#256](https://github.com/BerryUIKI/Omera/issues/256) are closed, as are the six
+GUI refinement packages in [GUI_REFINEMENT.md](GUI_REFINEMENT.md). September
+baseline and assignment snapshots are historical; use current approved `dev` for
+fixes.
 
 All pre-1.0 releases retain legacy detection and supported import. Keep cleanup optional. Resolve verified migration problems before removing compatibility paths. Decide the 1.0 import policy explicitly and document it; never use version 1.0 as permission to erase legacy data. Remote collaboration remains a separate product decision after stabilization.
 
 ### Stabilization Gates for 1.0 Readiness:
 
+Status: gates 1–3 are implemented and exercised by CI and the signed release
+pipeline; gate 4's query and layout boundaries are met, while its measured
+storage-evolution work is still pending in [STORAGE_EVOLUTION.md](STORAGE_EVOLUTION.md).
+
 1. **Installer and Desktop Integration**:
    - Windows NSIS installer configures Start Menu folder (`Omera`), native 7-language installer localization (`tauri.conf.json`), optional desktop shortcut creation (`$(createDesktop)`), pre-install process termination and uninstall cleanup (`hooks.nsh`), and in-app desktop shortcut management (`commands::create_desktop_shortcut`), ensuring consistent system indexing and user preference adherence.
    - macOS DMG/App bundle and Linux AppImage/deb/rpm packages continuously built and verified via GitHub Actions release matrix.
 2. **In-App Update Resilience**:
-   - `src/utils/updater.ts` implements automated fallback from GitHub REST API (rate-limited) to HTML 302 tag redirection and canonical release asset matching, ensuring seamless update notifications from v0.4.1/v0.4.2 onward.
+   - `src/utils/updater.ts` falls back from the GitHub REST API to the `releases/latest` redirect when the API rate-limits, behind the native `fetch_update_metadata` command, and matches assets by OS and architecture. Signature verification remains mandatory and fails closed.
 3. **Data Safety and Migration Verification**:
    - Append-only migrations (`omera-storage`) preserve historical schemas.
    - Legacy Berry database discovery and WAL preservation validated without touching source files.

diff --git a/docs/MULTI_DATABASE_COLLABORATION_RFC.md b/docs/MULTI_DATABASE_COLLABORATION_RFC.md
@@ -2,7 +2,7 @@
 
 - **Author**: Omera Architecture Group
 - **Status**: Deferred proposal; not an implemented or supported runtime backend
-- **Target Release**: v0.4.0+
+- **Target Release**: None scheduled; deferred past 1.0 pending measurement
 - **Keywords**: MySQL 8.0, PostgreSQL 14+, Storage Abstraction, Keyset Cursor, Multi-User Collaboration, Cross-Platform Root Mapping
 
 ---

diff --git a/docs/OMERA_MIGRATION.md b/docs/OMERA_MIGRATION.md
@@ -1,6 +1,6 @@
 # Omera identity and pre-1.0 migration contract
 
-Status: accepted product direction; implementation and release verification pending.
+Status: implemented in R0–R6 and verified per [OMERA_RENAME_STATUS.md](OMERA_RENAME_STATUS.md); this document remains the data-safety contract for changes to it.
 
 Ownership: lead maintainer/Codex. General engineers consume the migration contracts and implement presentation only after the safety services are ready. See [ENGINEERING_HANDOFF.md](ENGINEERING_HANDOFF.md).
 
@@ -51,6 +51,13 @@ Require renewed confirmation if the source changed after migration. Use OS trash
 
 ## Delivery and verification
 
+Items 1–4 are complete: the services exist (`src-tauri/src/legacy_migration.rs`
+provides status, preview, staged execution, receipts, cleanup preview/confirm
+and defer), the runtime identity is activated, and the required suites run in
+CI. Item 5's fault matrix and item 6's real-installer next-update path remain
+release acceptance work, and the installed-update matrix stays open in
+[#256](https://github.com/BerryUIKI/Omera/issues/256).
+
 1. Update documentation and track migration/release/storage tasks in GitHub issues.
 2. Implement and test migration/cleanup services before switching the runtime identity.
 3. Rename application, packages, crates, UI strings, settings, database, CI, and release artifacts; allow legacy strings only in migration code, fixtures, and historical records.

diff --git a/docs/OMERA_RENAME_STATUS.md b/docs/OMERA_RENAME_STATUS.md
@@ -1,6 +1,8 @@
 # Omera rename: current context and next actions
 
-Updated: 2026-09-24. This is a handoff snapshot, not a release-readiness statement. For the full work inventory and dependency gates, read [OMERA_RENAME_EXECUTION.md](OMERA_RENAME_EXECUTION.md); for data safety, read [OMERA_MIGRATION.md](OMERA_MIGRATION.md).
+> **Historical snapshot (2026-09-24).** R0–R6 are complete and [#134](https://github.com/BerryUIKI/Omera/issues/134) is closed. The identity, crate, database, settings and credential-service rename is live in released builds; the obligation that remains is standing pre-1.0 legacy discovery and supported import, described in [OMERA_MIGRATION.md](OMERA_MIGRATION.md). Not a release-readiness statement.
+
+For the full work inventory and dependency gates, read [OMERA_RENAME_EXECUTION.md](OMERA_RENAME_EXECUTION.md); for data safety, read [OMERA_MIGRATION.md](OMERA_MIGRATION.md).
 
 ## Verified repository state
 

diff --git a/docs/PERFORMANCE.md b/docs/PERFORMANCE.md
@@ -345,8 +345,10 @@ Installer size is a publication gate, checked before detached signing/upload and
 again against downloaded installers before a draft release can become public.
 `scripts/installer-budget.mjs` caps NSIS EXE and macOS DMG at 25 MiB, MSI/DEB/RPM
 at 40 MiB and Linux AppImage at 120 MiB (its portable runtime is included).
-The public v0.5.2 baselines were 16.95 MiB EXE, 33.29 MiB MSI, 18.08 MiB DMG,
-32.04 MiB DEB/RPM and 100.72 MiB AppImage. These limits allow bounded growth;
+The public v0.6.0 baselines were 17.10 MiB EXE, 33.56 MiB MSI, 18.34 MiB DMG,
+32.34 MiB DEB, 32.34 MiB RPM and 100.96 MiB AppImage. The published v0.5.2
+baselines were 16.95 MiB EXE, 33.29 MiB MSI, 18.08 MiB DMG, 32.04 MiB DEB/RPM
+and 100.72 MiB AppImage. These limits allow bounded growth;
 exceeding one requires reducing the artifact before publication. The workflow
 viewer uses existing Vue/HTML/SVG; no graph editor runtime, ComfyUI server or
 model weights are bundled for the studio features.

diff --git a/docs/RELEASE_NOTES.md b/docs/RELEASE_NOTES.md
@@ -13,7 +13,7 @@ before release; the app does not send notes to a translation service.
 2. Run `node scripts/generate-release-notes.mjs --check`. CI and release preflight
    both reject missing versions, empty translations, and malformed boundaries.
 3. Preview the exact GitHub body with
-   `node scripts/generate-release-notes.mjs v0.5.1 --output <preview-file>`.
+   `node scripts/generate-release-notes.mjs v0.6.0 --output <preview-file>`.
 
 The release workflow generates its final GitHub body from this catalog. English
 is visible first, and each other language is in a labeled disclosure. Each

diff --git a/docs/RELEASING.md b/docs/RELEASING.md
@@ -6,7 +6,7 @@ The target product is Omera, identifier `com.berryuiki.omera`, canonical reposit
 
 Before publishing, follow [OMERA_MIGRATION.md](OMERA_MIGRATION.md). Verify migration to `omera.db`, `omera_*` settings and the Omera credential service; platform installer replacement; signed OS/architecture-specific updates; and the subsequent Omera update. Test upgrades that skip intermediate releases. Keep legacy data until validated migration and explicit cleanup confirmation. Never reset application/schema versions or publish an unverified rename build.
 
-Implementation branches start from and target `dev`; approved release integration reaches `main`. Signing key provisioning and actual installer upgrade tests are release gates. v0.5.0 was prepared and published on 2026-10-26 with signed Windows, macOS and Linux assets. The installed-update matrix remains pending under [#256](https://github.com/BerryUIKI/Omera/issues/256); release preparation and published signed artifacts do not by themselves establish native acceptance. Record candidate package/signing results separately and retain the required approving review on `main`. A changed macOS Bundle ID requires checking provisioning and App Store distribution as a new identity.
+Implementation branches start from and target `dev`; approved release integration reaches `main`. Signing key provisioning and actual installer upgrade tests are release gates. [v0.6.0](https://github.com/BerryUIKI/Omera/releases/tag/v0.6.0) is the latest published release (2026-11-03) with signed Windows, macOS and Linux assets, following v0.5.2. The installed-update matrix remains pending under [#256](https://github.com/BerryUIKI/Omera/issues/256); release preparation and published signed artifacts do not by themselves establish native acceptance. Record candidate package/signing results separately and retain the required approving review on `main`. A changed macOS Bundle ID requires checking provisioning and App Store distribution as a new identity.
 
 This guide describes the release process, versioning conventions, and build artifact management for **Omera**.
 
@@ -95,10 +95,10 @@ git checkout main
 git pull origin main
 
 # 2. Tag the release commit
-git tag v0.5.0
+git tag v0.6.0
 
 # 3. Push the tag to GitHub
-git push origin v0.5.0
+git push origin v0.6.0
 ```
 
 The workflow checks synchronized versions and requires the tag to be integrated

diff --git a/docs/ROADMAP.md b/docs/ROADMAP.md
@@ -5,7 +5,7 @@ This roadmap documents completed milestones and future engineering goals for **O
 <picture>
   <source media="(prefers-color-scheme: dark)" srcset="screenshots/roadmap_status_dark.svg">
   <source media="(prefers-color-scheme: light)" srcset="screenshots/roadmap_status_light.svg">
-  <img alt="Omera roadmap status at v0.5.0: thirteen milestones complete, video and model-ecosystem milestones partially complete, and milestones 17–19 planned" src="screenshots/roadmap_status_dark.svg" width="100%">
+  <img alt="Omera roadmap status at v0.6.0: fourteen milestones complete, video and ComfyUI studio milestones in progress, and milestones 18–19 planned" src="screenshots/roadmap_status_dark.svg" width="100%">
 </picture>
 
 ---
@@ -151,10 +151,10 @@ is opt-in completion-driven indexing of an explicitly selected local output fold
 
 Execution order and ownership: [DELIVERY_ROADMAP.md](DELIVERY_ROADMAP.md) and [ENGINEERING_HANDOFF.md](ENGINEERING_HANDOFF.md). High-impact migration, persistence and release work stays with the lead; ordinary UI, parser and bounded performance tasks are prepared for general implementation engineers.
 
-- [ ] Complete [OMERA_MIGRATION.md](OMERA_MIGRATION.md): full identity rename, pre-1.0 legacy discovery, staged migration, and separately confirmed cleanup.
-- [ ] Validate signed updates and platform installer transitions, including skipped bridge releases. v0.5.0 is published with signed assets; the native installed-update matrix remains open in [#256](https://github.com/BerryUIKI/Omera/issues/256).
+- [x] Complete [OMERA_MIGRATION.md](OMERA_MIGRATION.md): full identity rename, pre-1.0 legacy discovery, staged migration, and separately confirmed cleanup. R0–R6 are complete and [#134](https://github.com/BerryUIKI/Omera/issues/134) is closed. The remaining obligation is standing pre-1.0 compatibility: every release before 1.0.0 keeps legacy discovery and supported import, and cleanup stays a separate explicit user decision.
+- [ ] Validate signed updates and platform installer transitions, including skipped bridge releases. [v0.6.0](https://github.com/BerryUIKI/Omera/releases/tag/v0.6.0) is published with signed assets, so the installed-update matrix in [#256](https://github.com/BerryUIKI/Omera/issues/256) is now executable against two consecutive signed stable releases (v0.5.2 → v0.6.0). It remains open until installed-to-next-version acceptance is recorded per platform.
 - [x] Complete review issues #98–#117 with regression coverage. All twenty issues are closed as completed and their regression suites run in CI.
-- [ ] Measure and implement [STORAGE_EVOLUTION.md](STORAGE_EVOLUTION.md) without rewriting applied migrations.
+- [ ] Measure and implement [STORAGE_EVOLUTION.md](STORAGE_EVOLUTION.md) without rewriting applied migrations. Baseline benchmarks currently cover gallery pagination and directory fingerprinting only; filtering, full-text search and sidebar aggregation still need p50/p95 measurements before any schema or index change.
 
 ### 🟡 Milestone 15: Video & Animation AIGC Ingestion & Playback (core features complete; extended facets pending)
 
@@ -164,7 +164,7 @@ Delivered in the v0.4.x line. The remaining facet work is limited to resolution,
 - [x] **Video Thumbnail Generation & Hover Scrubbing**: Capture frame thumbnails and scrub through video frames while hovering cards in Grid and Waterfall views.
 - [x] **Fullscreen Lightbox Video Player**: Seamless loop toggle, playback speed selector (0.25x–2x), frame-by-frame stepping (`.` / `,`), audio toggle, and sidecar prompt/workflow inspection.
 - [x] **Duration & Frame-Rate Facets**: Filter videos by duration range and frame rate, with an Images/Videos media-type filter.
-- [ ] **Remaining Video Facets**: Resolution, container-codec and motion-score filters are not implemented yet.
+- [ ] **Remaining Video Facets**: Resolution, container-codec and motion-score filters are not implemented yet. `width`, `height` and `video_codec` are already extracted into asset metadata and the existing duration/FPS facet pattern in `SearchCriteria`, `build_search_query`, `src/utils/search.ts` and `FilterDrawer.vue` is the wiring point. Motion score needs a new derived metric and its own schema decision.
 
 ### ✅ Milestone 16: Next-Gen Model Architectures & Ecosystem (complete)
 
@@ -174,10 +174,10 @@ Flux.1 / SD3.5 parsing and Civitai integration shipped in v0.5.0. The interactiv
 - [x] **Civitai Direct API Integration**: Remote model reverse lookups by AutoV2/SHA256, cached preview cards, version update badges, and one-click merge of trained trigger words into the local LoRA catalog.
 - [x] **ComfyUI Workflow Visualizer Enhancements**: On-demand interactive workflow graph viewer with prompt, sampler, ControlNet and LoRA categories, selection, search, keyboard navigation, connected-edge highlighting and pan/zoom.
 
-### 🟡 Milestone 17: Bi-Directional ComfyUI Studio, Live Queue & Prompt Diff (2 of 3 complete)
+### 🟡 Milestone 17: Bi-Directional ComfyUI Studio, Live Queue & Prompt Diff (3 of 3 complete; pipeline depth pending)
 - [x] **Real-Time ComfyUI WebSocket Monitor**: Explicit native HTTP/WebSocket connection, reconnect and bounded queue/history reconciliation; node progress, queue order, outcomes and VRAM in the studio, with status bar and Activity summaries. Qualified with local protocol fixtures only.
-- [ ] **Zero-Latency Ingestion Pipeline**: Stream newly generated images directly into Omera database and UI memory via IPC upon workflow completion, eliminating filesystem polling delay.
-  - Implemented packages: opt-in loopback completion events index a registered linked output folder or copy named outputs through an enabled copy-only pipeline, preserving sources and sidecars. Move/cleanup, remote outputs and reconnect history catch-up remain pending; see [COMFY_STUDIO.md](COMFY_STUDIO.md).
+- [x] **Completion-Driven Ingestion (first package)**: Opt-in loopback completion events index a registered linked output folder or copy named outputs through an enabled copy-only pipeline, preserving sources and sidecars. See [COMFY_STUDIO.md](COMFY_STUDIO.md).
+  - Still pending: remote output transfer, reconnect history replay (outputs missed while disconnected), video/custom-node output descriptors, move pipelines and cleanup, and queue-worker isolation.
 - [x] **Prompt Diff & Matrix Workbench**: Select A/B images in comparison mode; compare positive/negative and optional dual text-encoder prompts, explicit weights `(keyword:1.2)`, seeds, models, samplers and other generation parameters. Full details load on demand; long text has bounded section fallback and display limits.
 
 ### 🎯 Milestone 18: Local LAN Web Companion (Omera Remote)

diff --git a/docs/STABILIZATION_EXECUTION.md b/docs/STABILIZATION_EXECUTION.md
@@ -1,11 +1,16 @@
 # Remaining review fixes
 
-Updated: 2026-10-12. Integration target: `dev`; `main` remains release-only.
+Updated: 2026-11-07. Integration target: `dev`; `main` remains release-only.
 
-This execution ledger supersedes the historical September dispatch status for the
-October review reports. The handoff ownership boundaries, migration safeguards,
-and release qualification requirements still apply. An implemented feature is
-not evidence of native or platform qualification.
+This ledger covers the October 2026 review reports. Rows 0–15 are closed with
+merged regression coverage. Row 16 (#256) is the only item still open: its
+automated and production-signing work is merged, while installed-to-next-version
+acceptance per platform remains a release gate. The GUI refinement packages that
+followed this ledger are recorded in [GUI_REFINEMENT.md](GUI_REFINEMENT.md).
+
+The handoff ownership boundaries, migration safeguards, and release
+qualification requirements still apply. An implemented feature is not evidence
+of native or platform qualification.
 
 ## Sequence and acceptance
 

diff --git a/docs/TASK_ASSIGNMENT_BOARD.md b/docs/TASK_ASSIGNMENT_BOARD.md
@@ -1,6 +1,8 @@
 # Engineering assignment board
 
 > **Historical (2026-09-23).** Superseded by [ROADMAP.md](ROADMAP.md) and [STABILIZATION_EXECUTION.md](STABILIZATION_EXECUTION.md). Use the current approved `dev` and open GitHub issues for dispatch.
+>
+> **Every issue referenced below is closed.** #102, #107, #110, #118, #124, #128, #134, #135 and #137 are all resolved, and #119–#133 were reconciled through the October stabilization ledger. #256 is the only open issue. This page is kept only for the ownership reasoning behind each role boundary, not as a dispatch list.
 
 Updated: 2026-09-23. Named people can be assigned by the product owner; role labels below are proposed work packages, not claims that someone is already working.