v0.5.5

Caelune / 凯露恩 v0.5.5 Release Notes

Release Status

v0.5.5 is the Chinese product-name, repository-owner, documentation, and public-surface consistency release.

Release Focus

This release aligns the Windows desktop app, source tree, documentation, website, Wiki, licensing, MCP setup guidance, and release metadata around the current Caelune / 凯露恩 product identity and the canonical EllisMorrow repository owner.

Highlights

• The Chinese desktop title and all current Chinese product copy use 凯露恩.
• README, website accessibility metadata, architecture guidance, runtime instructions, third-party notices, changelog entries, and retained release notes use the current product name.
• Copyright and current repository-owner references use EllisMorrow.
• Legacy MCP migration guidance no longer repeats a retired account identifier, while the stable omniclip.status and omniclip.search tool IDs remain unchanged.
• Both README files keep the self-updating GitHub Release badge as their only version indicator.
• GitHub Wiki and repository-page copy are prepared for the same public-name update.

Compatibility

• Existing knowledge bases, Markdown/PDF/Tika indexes, Runtime components, model caches, live-watch settings, and UI settings remain compatible.
• No model redownload, Runtime reinstall, or full index rebuild is required solely for this update.
• The Python package remains omniclip_rag, and existing MCP tool calls remain compatible.

Release Assets

• Caelune-v0.5.5-WIN-EXE.zip
  • ordinary Windows desktop GUI package
• Caelune-MCP-v0.5.5-win64.zip
  • manual MCP package for direct stdio setup
• caelune-mcp-win-x64-v0.5.5.mcpb
  • MCPB package for Registry and MCPB-aware clients

Validation Scope

• Full automated test suite: 452 tests passed.
• Current source tree and current v0.5.5 build directories contain no retired Chinese product-name or repository-owner strings.
• Clean PyInstaller builds for the GUI and MCP executables.
• Windows archive integrity and Shiboken portability checks.
• MCPB schema validation, packing, unpacking, entry-point verification, and Registry SHA256 regeneration.
• Packaged MCP entry point and CLI argument smoke check completed successfully without reading a configured knowledge base.

Privacy

• Release archives exclude local Runtime installations, model caches, knowledge-base files, indexes, logs, configuration files, credentials, Registry tokens, temporary worker payloads, and local build paths.
• Activity logs and MCP self-check output may contain private paths, knowledge-base names, or retrieved snippets. Review and remove them before sharing diagnostics publicly.

Upgrade Guidance

Extract Caelune-v0.5.5-WIN-EXE.zip to a new folder instead of overwriting an older release, then start Caelune.exe. Keep the previous application folder until the new build has opened normally and completed Runtime detection.

v0.5.4

Caelune / 凯露恩 v0.5.4 Release Notes

Release Status

v0.5.4 is the live-watch responsiveness, multi-knowledge-base fairness, and visible backlog-progress release.

Release Focus

This release makes incremental Markdown indexing react to the notes users are editing now, while still safely catching up with changes made while Caelune was closed. Large backlogs are split into fair, efficient turns and report recalculated completion estimates without weakening the existing resource limits.

Highlights

• Changes made while Caelune was closed are detected when live watch starts and are processed in bounded batches.
• Fresh editor events take priority over historical reconciliation and retained repair work.
• Multi-knowledge-base semantic indexing now uses a fair FIFO gate so one busy source cannot repeatedly monopolize the worker.
• Batches larger than three files amortize model-process startup cost while retaining the configured vector encode, RAM, and VRAM limits.
• The Activity Log identifies live updates, offline reconciliation, repair work, retries, progress, and completion.
• Backlogs containing more than three files show a per-knowledge-base ETA that is recalculated from completed end-to-end batches, including time spent waiting for a fair worker turn.
• Stale repair paths are removed, and valid historical repairs are consumed in bounded pieces after current edits.

Compatibility

• Existing knowledge bases, Markdown/PDF/Tika indexes, Runtime components, model caches, live-watch settings, and UI settings remain compatible.
• No model redownload, Runtime reinstall, or full index rebuild is required solely for this update.
• The Python package remains omniclip_rag, and the MCP tool IDs remain omniclip.status and omniclip.search.

Release Assets

• Caelune-v0.5.4-WIN-EXE.zip
  • ordinary Windows desktop GUI package
• Caelune-MCP-v0.5.4-win64.zip
  • manual MCP package for direct stdio setup
• caelune-mcp-win-x64-v0.5.4.mcpb
  • MCPB package for Registry and MCPB-aware clients

Validation Scope

• Full automated test suite: 452 tests passed.
• Focused regressions cover Watchdog add/modify/delete events, offline restart reconciliation, live-event priority, bounded repair work, fair repeated multi-vault turns, dynamic ETA updates, and UI log rendering.
• Clean PyInstaller builds for the GUI and MCP executables.
• Windows archive integrity and Shiboken portability checks.
• MCPB schema validation, packing, unpacking, and entry-point verification.
• Release-bundle privacy scan for local user paths, knowledge-base names, Runtime/model data, indexes, logs, configuration, credentials, and temporary worker payloads.

Privacy

• Release archives exclude local Runtime installations, model caches, knowledge-base files, indexes, logs, configuration files, credentials, Registry tokens, temporary worker payloads, and local build paths.
• Activity logs may contain private paths and knowledge-base names. Remove them before posting logs publicly.

Upgrade Guidance

Extract Caelune-v0.5.4-WIN-EXE.zip to a new folder instead of overwriting an older release, then start Caelune.exe. Keep the previous application folder until the new build has opened normally, completed Runtime detection, and verified live-watch processing on a small edit.

v0.5.2

Caelune / 凯露恩 v0.5.2 Release Notes

Release Status

v0.5.2 is the cross-device Runtime compatibility, source-state clarity, and Windows packaging reliability release.

Release Focus

This release addresses failures that appeared only on some Windows devices while preserving existing knowledge bases, indexes, model caches, and query behavior. It also separates source-path health from index health so users can understand why an offline source may still be searchable from its retained local index.

Highlights

• Fixed a CPU Runtime compatibility failure that could leave semantic retrieval usable but prevent BAAI/bge-reranker-v2-m3 from running with 'dict' object has no attribute 'model_type'.
• Added a targeted semantic-core repair path that updates the incompatible Transformers layer without forcing users to redownload models or rebuild indexes.
• Added Runtime package versions, system-memory snapshots, configured/selected knowledge-base counts, and active-scope state to query diagnostics for cross-device troubleshooting.
• Kept the active Markdown knowledge base aligned with saved and selected knowledge bases, preventing the Start page from incorrectly reporting that no knowledge base was selected.
• Markdown, PDF, and Tika rows now report source-path state and index state separately. A missing source with a retained index is shown as offline but still searchable.
• Disabled preflight, rebuild, and new live-watch actions for unavailable source paths while preserving safe removal and retained-index search behavior.
• Fixed an extension-source deletion reload race that could restore a deleted PDF/Tika source from stale registry state.
• Added a portable Shiboken recovery payload and early Runtime repair hook so Windows packages can recover when extraction or copy tools omit the nested shiboken6 directory.
• Version references, Windows examples, MCPB metadata, and Registry metadata are aligned to 0.5.2.

Compatibility

• Existing data roots, Markdown/PDF/Tika indexes, model caches, Runtime components, live-watch settings, and UI settings remain compatible.
• No model redownload or index rebuild is required solely for this update.
• Devices with the identified semantic-core incompatibility can use the targeted repair action, then refresh Runtime detection and restart Caelune.
• The Python package remains omniclip_rag and the MCP tool IDs remain omniclip.status and omniclip.search.

Source Removal and Cleanup

• Removing a Markdown knowledge base from the saved list keeps its independent workspace and index for safe recovery.
• Re-adding the exact same source path reconnects to that retained workspace.
• The Data-page index cleanup clears the current workspace's Markdown SQLite and LanceDB indexes; it does not remove the entire workspace or its isolated PDF/Tika indexes.
• PDF/Tika row deletion removes that source and clears only its matching extension index/state.
• Original source notes and documents are never deleted by these actions.

See the Knowledge Bases and Live Watch Wiki page for the complete bilingual explanation.

Release Assets

• Caelune-v0.5.2-WIN-EXE.zip
  • ordinary Windows desktop GUI package
• Caelune-MCP-v0.5.2-win64.zip
  • manual MCP package for direct stdio setup
• caelune-mcp-win-x64-v0.5.2.mcpb
  • MCPB package for Registry and MCPB-aware clients

Validation Scope

• Full automated test suite: 441 tests passed.
• Focused regressions cover Runtime repair, active knowledge-base recovery, source-path/index-state presentation, extension deletion, reranker compatibility classification, and Shiboken packaging fallback.
• Clean PyInstaller builds for the GUI and MCP executables.
• User verification of the packaged v0.5.2 desktop executable on the affected Windows workflow.
• MCPB schema validation, packing, unpacking, and entry-point verification.
• Release-archive integrity, required-file, privacy, and SHA-256 checks.

Privacy

• Release archives exclude local Runtime installations, model caches, knowledge-base files, indexes, logs, configuration files, credentials, Registry tokens, temporary worker payloads, and local build paths.
• Query diagnostics may contain private paths and workspace names. Remove them before posting logs publicly.

Upgrade Guidance

Extract Caelune-v0.5.2-WIN-EXE.zip to a new folder instead of overwriting an older release, then start Caelune.exe. Keep the previous application folder until the new build has opened normally, completed Runtime detection, and completed a query.

v0.5.1

Caelune / 凯露恩 v0.5.1 Release Notes

Release Status

v0.5.1 is the desktop UI clarity, onboarding, and release-metadata refinement release.

Release Focus

This release makes Caelune easier to read and operate without changing its local-first retrieval architecture, knowledge-base formats, Runtime layout, or MCP tool contracts. The desktop interface now has a clearer visual hierarchy across its supported themes, more practical bilingual guidance, and a startup experience that follows the saved application theme from the first visible window.

Highlights

• Refined the main navigation, cards, tables, buttons, input fields, focus states, status badges, and header hierarchy across the supported UI themes.
• Improved Chinese and English labels, guidance, and tooltips for first-time users while keeping expert workflows compact.
• The startup progress window now loads the saved UI theme before it is shown, avoiding a visible Windows-theme-to-app-theme switch.
• The Windows title bar now shows the release version instead of repeating the application name.
• The README files now show separate, current, full-resolution Query Console and Results and Details screenshots in Chinese and English.
• MCP initialization now reports the Caelune release version instead of the bundled MCP SDK version.
• Version references, Windows examples, MCPB metadata, and Registry metadata are aligned to 0.5.1.

Compatibility

• Existing data roots, knowledge bases, indexes, Runtime components, model caches, UI settings, and live-watch settings remain compatible.
• The Python package remains omniclip_rag and the MCP tool IDs remain omniclip.status and omniclip.search.
• No database migration, index rebuild, Runtime reinstall, or model redownload is required solely for this update.

Release Assets

• Caelune-v0.5.1-WIN-EXE.zip
  • ordinary Windows desktop GUI package
• Caelune-MCP-v0.5.1-win64.zip
  • manual MCP package for direct stdio setup
• caelune-mcp-win-x64-v0.5.1.mcpb
  • MCPB package for Registry and MCPB-aware clients

Validation Scope

• Full automated test suite plus focused Qt identity and MCP release-version regressions.
• Clean PyInstaller builds for the GUI and MCP executables.
• Packaged GUI title-bar smoke test on Windows 11.
• Valid MCP initialize request against the packaged executable.
• MCPB schema validation, packing, unpacking, and entry-point verification.
• Release-archive path, privacy, dependency-purity, and SHA-256 checks.

Privacy

• Release archives exclude local Runtime installations, model caches, knowledge-base files, indexes, logs, configuration files, credentials, Registry tokens, temporary worker payloads, and local build paths.
• Documentation screenshots contain no query results, note contents, usernames, credentials, or absolute local paths.

Upgrade Guidance

Extract Caelune-v0.5.1-WIN-EXE.zip to a new folder and start Caelune.exe. Keep the previous application folder until the new build has opened normally and completed a query; it can then be archived or removed manually.

v0.5.0

Caelune / 凯露恩 v0.5.0 Release Notes

Release Status

v0.5.0 is the product-identity migration release from OmniClip RAG / 方寸引 to Caelune / 星野.

Release Focus

This release gives the desktop app, Windows executables, MCP package, documentation, and website one consistent public identity. The migration is deliberately compatibility-first: existing users keep their selected data root, local indexes, downloaded Runtime, configuration, and MCP tool contracts.

Highlights

• The desktop title and public English product name are now Caelune.
• The Chinese product name is now 星野.
• New Windows executables are named Caelune.exe and Caelune-MCP.exe.
• Fresh installations use %APPDATA%\Caelune-default and a %APPDATA%\Caelune\bootstrap.json pointer.
• New configuration overrides use the CAELUNE_* prefix.
• The website, README files, current setup guides, package metadata, and MCP Registry metadata use the new identity.

Compatibility

• Existing %APPDATA%\OmniClip RAG environments remain recognized and are reused automatically.
• Existing bootstrap pointers, Runtime directories, and OMNICLIP_* environment overrides remain supported as legacy aliases.
• The Python import package remains omniclip_rag to avoid breaking internal imports and integrations.
• MCP tool IDs remain omniclip.status and omniclip.search so existing AI-client configurations do not break.
• The MCPB package identity is now io.github.EllisMorrow/caelune-mcp; users of the old io.github.msjsc001/omniclip-rag-mcp MCPB should remove it once before installing the renamed package.
• Stored SQLite, vector-index, marker, and log filenames are not rewritten or migrated destructively.

Release Assets

• Caelune-v0.5.0-WIN-EXE.zip
  • ordinary Windows desktop GUI package
• Caelune-MCP-v0.5.0-win64.zip
  • manual MCP package for direct stdio setup
• caelune-mcp-win-x64-v0.5.0.mcpb
  • MCPB package for Registry and MCPB-aware clients

Privacy

• Release archives exclude local Runtime installations, model caches, knowledge-base files, indexes, logs, configuration files, credentials, Registry tokens, and temporary worker payloads.
• The rename does not upload, copy, or inspect user knowledge-base content.

Upgrade Guidance

Extract the new package to a new folder and start Caelune.exe. The app will discover the previous data-root selection and Runtime when present. Keep the previous application folder until the first Caelune launch and a normal query have been verified; it can then be archived or removed manually.

v0.4.13

OmniClip RAG v0.4.13 Release Notes

Release Status

v0.4.13 is the event-driven live-watch and disposable incremental-indexing release.

Release Focus

This release removes recurring whole-vault scans from normal Markdown watchdog operation. After one startup reconciliation, live watch waits for real file events, merges repeated saves during a configurable quiet period, and processes only the affected Markdown files.

Incremental parsing, embedding, vector writes, and CUDA work now run in a disposable child process. When the batch completes or live watch is stopped, the process exits so Windows can reclaim its Commit charge, physical memory, and GPU memory.

Highlights

• Markdown watchdog mode is event-driven after startup reconciliation.
• The live-watch quiet period is configurable and defaults to 10 seconds.
• Repeated saves are coalesced into one incremental update after editing settles.
• Heavy incremental indexing runs outside the GUI process and releases resources after every batch.
• Multiple watched vaults serialize semantic update batches to avoid duplicate model loads.
• Stop requests terminate and reap active incremental workers.
• .stversions, logseq/bak, logseq/.recycle, and logseq/.tine-trash are excluded from Markdown indexing and watch events.
• Query subprocess resource cleanup and existing Markdown/PDF/Tika/MCP behavior remain unchanged.

Release Assets

• OmniClipRAG-v0.4.13-WIN-EXE.zip
  • ordinary Windows desktop GUI package; use this package for desktop testing
• OmniClipRAG-MCP-v0.4.13-win64.zip
  • manual MCP package for direct stdio setup
• omniclip-rag-mcp-win-x64-v0.4.13.mcpb
  • MCPB package for the official Registry and MCPB-aware clients

Validation Scope

• Event coalescing and configurable quiet-period regressions.
• Event-only idle-watch behavior after startup reconciliation.
• Generated Logseq history/recovery exclusion regressions.
• Disposable watch-worker lifecycle, cancellation, and process-reaping regressions.
• Multi-vault serialization and resource-batch mapping regressions.
• Synthetic real-watch smoke test using filesystem events and an actual disposable worker.
• Full automated test suite.
• Packaged GUI and MCP build audits.

Privacy and Compatibility

• Release archives exclude local Runtime installations, model caches, vault contents, indexes, logs, configuration files, credentials, Registry tokens, and temporary worker payloads.
• Existing configuration files remain compatible; the new quiet-period value defaults to 10 seconds when absent.
• Markdown, PDF, Tika, query, Runtime-layout, and MCP contracts are unchanged.
• Polling remains available only as a compatibility fallback when filesystem event monitoring cannot be used.

v0.4.12

From v0.4.9 to v0.4.12, the main issues addressed were:

• Smoother startup: Runtime detection now starts automatically, without requiring a manual refresh, and time-consuming tasks have been moved to background processes.
• Queries are less likely to crash: Queries now run in isolated processes, so even if a model or CUDA fails, the main interface remains protected and the system attempts to fall back automatically.
• More reasonable GPU and memory decisions: Instead of using a rigid memory threshold, resource availability is now evaluated dynamically based on the model, system memory, and GPU memory.
• Clearer query status: The interface now shows the current stage, such as semantic recall, fusion, and reranking, and provides actionable troubleshooting guidance.
• Cleaner interface: Queries, results, configuration, and activity logs are separated, while numeric input fields and the collapsible top layout have been improved.
• Live watchers can stop reliably: Batch stopping, individual vault stopping, and application shutdown now correctly clean up watcher processes.
• PDF/Tika operations no longer block the interface: Directory scanning, status refreshes, and index statistics now run in the background.
• Release packages are easier to identify: The standard Windows version is now clearly labeled WIN-EXE.

In simple terms, these releases gradually transformed the application from one that could feel slow at startup, crash during queries, and provide unclear status information into one with more stable startup, safer queries, more sensible GPU usage, and background tasks that no longer drag down the interface.

---

OmniClip RAG v0.4.12 Release Notes

Release Status

v0.4.12 is the adaptive Reranker-resource, visible query-stage, and query-process cleanup release.

Release Focus

This release removes the universal 10 GiB Windows Commit floor that could skip a healthy Reranker even when the machine had enough RAM and VRAM for the actual workload.

Auto now estimates the active Reranker's requirements from the measured local model weights and query batch settings, then compares that estimate with live Windows Commit headroom, available physical memory, and free CUDA memory. The Query Console exposes those measured and required values whenever Auto must skip only the optional second-pass ordering.

Highlights

• Auto uses a model-aware resource estimate instead of a universal 10 GiB Commit threshold.
• Explicit CUDA remains an intentional user override while desktop queries stay isolated from the main interface.
• The status button beside Search shows the live query stage and percentage.
• Visible stages include preparation, lexical recall, semantic recall, fusion, reranking, result finalization, context packing, copying, and fallback recovery.
• Failed queries keep a clear failed state instead of showing an earlier completed query.
• Score-threshold and result-limit fields remain immediately beside their labels on wide windows.
• Completed, cancelled, and failed query children are explicitly waited on and reaped.
• Global live-watch stop now targets every actual running vault, even if the selected-vault set changed after startup.
• Each vault exposes a non-repeatable stopping state while its worker exits.
• Initial vault scans, incremental rendering, and vector writes honor cooperative stop requests and retain repair state when interrupted.
• Application shutdown waits for live-watch workers instead of immediately discarding their bookkeeping.
• PDF/Tika directory actions keep state reloads and indexed-source summaries off the Qt UI thread.
• Repeated PDF/Tika refresh requests are coalesced, and stale background results cannot overwrite newer directory settings.

Release Assets

• OmniClipRAG-v0.4.12-WIN-EXE.zip
  • ordinary Windows desktop GUI package; the explicit WIN-EXE label makes the end-user download unambiguous
• OmniClipRAG-MCP-v0.4.12-win64.zip
  • manual MCP package for direct stdio setup
• omniclip-rag-mcp-win-x64-v0.4.12.mcpb
  • MCPB package for the official Registry and MCPB-aware clients

Validation Scope

• Focused Query Console regressions for live stage text, failed state, and numeric-control ownership.
• Adaptive Reranker resource-budget and explicit CUDA override regressions.
• Query-worker completion and cancellation reaping regressions.
• Multi-vault live-watch stop, duplicate-stop suppression, cooperative vector cancellation, and worker-exit regressions.
• PDF/Tika directory-button responsiveness, background-thread ownership, stale-result rejection, and pending state-reload regressions.
• Full automated test suite.
• Packaged GUI, MCP, and MCPB build audits.
• Packaged multi-vault query verification with CUDA vector recall and CUDA Reranker execution.

Privacy and Compatibility

• Release archives exclude local Runtime installations, model caches, vault contents, indexes, logs, configuration files, credentials, Registry tokens, and temporary query payloads.
• Markdown, PDF, Tika, index, Runtime-layout, and MCP tool contracts are unchanged.
• Auto can still skip only the optional Reranker when the model-aware estimate says current resources are insufficient.
• Explicit CPU/CUDA device selection remains available.

v0.4.11

OmniClip RAG v0.4.11 Release Notes

Release Status

v0.4.11 is the Windows Commit-pressure, native PyTorch-crash prevention, and semantic-query recovery release. The packaged Windows GUI has been exercised against a real Runtime and two existing vault indexes before publication.

Release Focus

This release keeps useful semantic retrieval available when Windows has enough resources for the CUDA embedding model but not enough Commit headroom to safely load the optional Reranker beside it.

Auto mode now preserves GPU/CUDA vector recall and skips only second-pass reranking when Commit headroom is below the measured safe loading floor. The Query Console explains what happened and gives concrete recovery steps instead of suggesting that a healthy Runtime or model must be reinstalled.

Highlights

• CUDA Markdown vector recall remains active when Auto skips the Reranker for low Commit headroom.
• Auto requires at least 10 GiB of Windows Commit headroom before loading the Reranker beside an active vector model.
• The Query Console tells users to close memory-heavy applications, keep Auto selected, enable automatic Windows paging-file management or increase the paging file, and restart Windows if needed.
• Low-Commit guidance explicitly states that Runtime and model reinstallation are not required.
• Disposable query workers no longer move large CUDA models back to CPU during shutdown.
• Query results are written before the operating system reclaims the disposable worker and its model allocations.
• If a GPU semantic process still exits natively, a fresh CPU semantic process without Reranker is attempted before the final lexical-only fallback.
• The main Qt interface remains isolated from PyTorch, SentenceTransformer, CrossEncoder, and CUDA native-process failures.

Release Assets

• OmniClipRAG-v0.4.11-win64.zip
  • desktop GUI package
• OmniClipRAG-MCP-v0.4.11-win64.zip
  • manual MCP package for direct stdio setup
• omniclip-rag-mcp-win-x64-v0.4.11.mcpb
  • MCPB package for the official Registry and MCPB-aware clients

Validation Scope

• Focused Query Console ownership regression for the low-Commit remediation text.
• Query-worker cleanup, CPU semantic recovery, and lexical last-resort regressions.
• Reranker low-Commit guard and safe model-release regressions.
• Full automated test suite.
• Packaged GUI and MCP build audits.
• MCPB validation and unpack verification.
• Real packaged multi-vault query using CUDA vector recall and returning 15 results without a native child-process crash.

Privacy and Compatibility

• Release archives exclude local Runtime installations, model caches, vault contents, indexes, logs, configuration files, credentials, Registry tokens, and temporary query payloads.
• Markdown, PDF, Tika, index, Runtime-layout, and MCP tool contracts are unchanged.
• Auto may skip only the optional Reranker under measured low-Commit conditions; vector semantic recall remains active.
• Explicit CPU/CUDA device selection behavior remains available, while Auto continues to choose the safer path from measured resources.

v0.4.10

OmniClip RAG v0.4.10 Release Notes

Release Status

v0.4.10 is the Runtime-readiness, query-isolation, CUDA diagnostics, and desktop workspace-layout release. The packaged Windows build has been exercised against a real Runtime and multi-vault configuration before publication.

Release Focus

This release prevents startup Runtime detection and native semantic-model failures from taking control of the interactive desktop process.

The query interface stays blocked while the automatic Runtime probe is active. Safe startup still skips semantic prewarming, but it no longer skips the isolated status-only probe that supplies the Start and Runtime pages with an accurate state.

Queries now run in a disposable child process. A native Windows access violation in PyTorch, SentenceTransformer, CrossEncoder, CUDA, or another compiled dependency can end that query process without terminating the Qt main window. If the semantic process exits without a result, OmniClip makes one clean lexical-only attempt in a fresh process and displays an explicit degradation warning.

Highlights

• Query buttons and the execution guard remain disabled while startup Runtime detection is active.
• Safe startup performs the isolated Runtime status probe instead of leaving a stale repair warning.
• The exact Runtime probe payload is applied to both the Start and Runtime pages.
• Single-vault and multi-vault queries execute outside the GUI process.
• Query progress and structured results cross a temporary JSON protocol whose files are removed after each query.
• Native semantic-process crashes cannot directly terminate the desktop window.
• A fresh lexical-only process provides one automatic recovery attempt.
• Closing the desktop terminates an active query process so it is not orphaned.
• Multi-vault queries continue to reuse the same embedding and reranker resources within one query.
• Auto now leaves ordinary Windows memory pressure to the operating system and intervenes only near the commit/physical-memory limit; the query still retains isolated-process and CUDA-OOM recovery protection.
• The Query console and Activity log report the measured memory values, the exact CUDA/Reranker readiness conditions, and the original Reranker exception instead of presenting an unexplained failure.
• Healthy memory snapshots no longer generate a false CPU-fallback warning, and CUDA execution is identified from the model/inference device rather than the CPU location of the returned NumPy array.
• Query Console, Results & Details, Config, and Activity Log now occupy independent top-level tabs; existing diagnostic jumps open the new Activity Log location.
• The header can be hidden completely while its Expand/Collapse action remains at the far right of the tab row, and a compact state button beside Query shows whether a query is ready, blocked, running, or complete.
• Official MCP Registry discovery now follows the current io.github.EllisMorrow/omniclip-rag-mcp namespace; the MCPB keeps its legacy internal identity so existing installations remain upgrade-compatible.

Release Assets

• OmniClipRAG-v0.4.10-win64.zip
  • desktop GUI package
• OmniClipRAG-MCP-v0.4.10-win64.zip
  • manual MCP package for direct stdio setup
• omniclip-rag-mcp-win-x64-v0.4.10.mcpb
  • MCPB package

Validation Scope

• Startup Runtime gating and safe-mode status decisions.
• Start-page Runtime state synchronization.
• Query result serialization, progress transport, and native-crash recovery coordination.
• A real source-build child-process round trip against a synthetic Markdown vault.
• Full automated test suite, packaged build audit, MCPB validation/unpack, and packaged desktop smoke testing before publication.

Privacy and Compatibility

• The release archives exclude local Runtime installations, vault contents, indexes, logs, caches, configuration files, credentials, and Registry tokens.
• The external Runtime layout, Markdown/PDF/Tika source formats, indexes, and MCP tool contracts are unchanged.
• Query recovery changes ranking behavior only when the semantic child process has already failed; normal successful semantic queries retain the configured hybrid pipeline.

v0.4.9

OmniClip RAG v0.4.9 Release Notes

Release Focus

v0.4.9 completes the Windows startup-responsiveness work and refreshes the application identity with a cleaner flat icon.

The first window now appears without parsing the full Tika format catalog or constructing the complete query service in the GUI process. Immediately after first paint, the Runtime status changes to detecting and an isolated child process performs the real validation. The initial workspace snapshot follows in another isolated process, while Markdown, extension-source, and Tika refreshes are deliberately staggered so background work does not overwhelm the interface.

Highlights

• Runtime detection starts automatically after first paint.
• The Start and Runtime pages show a truthful runtime detecting… state and update automatically when validation finishes.
• Runtime validation and initial workspace status collection run outside the GUI process.
• Markdown status, extension-source summaries, and Tika status start in a controlled sequence instead of competing at once.
• Full Tika JAR format-catalog parsing is deferred until the user opens the format picker.
• Complete-but-unverified Runtime installations are shown as installed rather than missing.
• Enabled PDF/Tika sources distinguish unbuilt state from pending status confirmation.
• The new flat ring-and-spark application icon stays clear at Windows thumbnail sizes.

Release Assets

v0.4.9 ships the same three public release asset forms:

• OmniClipRAG-v0.4.9-win64.zip
  • desktop GUI package
• OmniClipRAG-MCP-v0.4.9-win64.zip
  • manual MCP package for direct stdio setup
• omniclip-rag-mcp-win-x64-v0.4.9.mcpb
  • MCPB package for the official MCP Registry line

MCP / Registry Note

This release does not add MCP tools or change query semantics.

• The desktop ZIP, MCP ZIP, MCPB package, and Registry metadata share the same v0.4.9 version.
• Public repository and release URLs now use the canonical EllisMorrow/OmniClip-RAG path.
• The Registry server name remains io.github.msjsc001/omniclip-rag-mcp so this version updates the existing official entry instead of creating a duplicate server identity.

Validation

• Relevant startup, Runtime, extension-status, desktop-entry, localization, and MCP Registry tests pass.
• A packaged Windows startup smoke test observed no non-responsive GUI samples while Runtime detection was active.
• Release bundles are audited to exclude local workspaces, indexes, logs, caches, Runtime installations, and heavyweight semantic packages.

Notes

• Runtime installation, Markdown/PDF/Tika retrieval, and MCP tool contracts are unchanged.
• Runtime detection may still take several seconds on a cold machine, but it no longer performs heavy validation inside the GUI process.
• On a machine below the safe resource threshold, automatic Runtime validation is skipped rather than forcing background work that could degrade the interface.