German shortcut names, groups, tooltips, filtering, counts, and hero labels now come from a deterministic validated catalog with encoding-corruption guards.
The hero overlay snapshot now follows the active website theme on clean load and later manual or system-theme changes.
Current release status
FluentOverlay's first public product release is v1.0. Public docs should describe the launch app as one coherent release instead of implying that later minor version labels have already shipped.
The website demo now mirrors the candidate local-only Template Composer interaction for Prompt and Snippet entries that contain variables: multiline fields, live preview, unchanged copy, and composed copy after every value is non-blank.
The demo's schema-4 feature-proof registry now covers 15 desktop capabilities. Shortcut activation and ordinary Knowledge copy use explicit Pro explanation surfaces instead of pretending that a browser can send native keys or expose complete private content; variable Prompt and Snippet examples keep the representative Template Composer.
Holding Ctrl, Alt, Shift, or Win highlights matching visible Shortcut rows without overriding browser behavior. A localized footer note makes the session boundary explicit: temporary demo changes reset on reload.
The browser receives only opaque target IDs and two representative demo templates. Exact desktop source templates, authoring bodies, entered values, and persistence remain outside the public payload.
The desktop candidate also adds accessible semantic rows and group headers, distinct search-miss and empty-content recovery, deterministic current-tab Search v2 across Shortcuts and Knowledge, and a live current-app shortcut-source snapshot inside the existing Where shortcuts come from User Guide topic. The candidate removes the permanent Source header action and keeps provenance out of individual rows.
A follow-up separates durable row selection from transient hover, favourite-action, and held-key visuals, and removes global selected-tab binding fan-out from retained tab presenters. Clean desktop rendered-frame and resource-plateau measurements still gate any public tab-performance claim.
Pro MCP gains explicit-target, read-only content queries for listing, searching, and bounded detail retrieval. Every call rechecks enablement and entitlement; built-ins are available when enabled, while personal, edited, and installed content stays behind a separate default-off consent toggle. MCP execution and live foreground inspection remain out of scope.
Shortcut-resolution policy, bounded diagnostic I/O, and one-pass UI Automation context capture improve hot-path ownership without adding network or model work. The built-in Knowledge audit retained all 383 stable IDs and improved two weak cards across all six locales without touching user content.
This is a coordinated v1.1 candidate record, not a released product claim. Marketing and shipped-capability copy must wait for matching desktop release metadata.
Website publication also remains blocked until the sibling desktop release records Template Composer as shipped through tests, accessibility, all desktop locales, changelog, release metadata, and product truth.
v1.0 product-truth and integrity update — 13 July 2026
Release metadata now comes from the desktop app's canonical project version and matching changelog record: v1.0, Initial Release, stable channel.
The desktop foundation pass repaired localized text and added deterministic UTF-8, resource, pack, placeholder, and executable-field checks. It did not modify user-created, user-edited, or installed content.
Current product copy now states the local-first boundary directly: opening the overlay and searching local content require no cloud AI service, API key, or in-app chat panel.
Free and Pro remain the current product tiers. Pro+ is only an exploratory, unannounced label with no assigned feature bundle, price, or release date.
v1.0 launch baseline
Overlay foundation, live menu reading, fuzzy search, synonym-backed shortcut recall, bundled shortcut packs, and JSON-based custom or community pack loading.
Free discovery plus Pro execution, favourites, personal shortcuts, Pack Editor workflows, PDF and Markdown export, saved views, presentation modes, and workflow authoring.
Theme, density, opacity, accent, trigger, tab management, custom tab, per-app rule, and layout controls that make the overlay feel adaptable without changing the release label.
Six UI locales, Windows 10/11 x64 targeting, local-first storage, per-app caching, multi-monitor polish, warm-path performance work, and direct desktop distribution.
MCP structure authoring through an external host and Community Marketplace app bundles are part of the v1.0 launch story. Read-only content queries are implemented only in the unreleased candidate; MCP execution remains future work.
Preparing
A clearer in-app update path, release-note surface, and update manifest contract are being prepared so future releases can be noticed and installed cleanly.
Help, bug-report, review, Store, MSI, and managed-feed routes should only move from preparing to shipped when the relevant path is actually ready.
Future minor version headings should appear in docs only after the release exists in product truth and release artifacts.
Exploring
Unified cross-tab search, BYOK search, local learning or practice, PWA mapping, MCP execution, browser and web-app awareness, and live context remain explicit future work without an announced tier.
Workflow or pack generation and a contextual assistant are also exploratory ideas, not announced Pro+ entitlements.
Shortcut Truth Sync is planned as a stricter version of custom shortcuts: create or edit a shortcut in the overlay, write it to a supported app/system shortcut source, then re-read that source so the overlay matches the real binding. Today's custom shortcuts remain local overlay overrides.
Passive learning, practice-style coaching, team distribution, mobile or voice experiments, and deeper automation ideas remain exploratory until they strengthen the core overlay instead of distracting from it.
How to read future-facing notes here
Launch, install, and shipped-behavior guides should continue to describe what people can use today.
Preparing and exploring notes belong in the changelog or roadmap sections, where planned work can stay explicit without rewriting the core docs as if it already exists.
If a future direction becomes product-real later, the task-first setup and usage guides can expand from the released version record.
