Spellcast v0.4.12

Spellcast 0.4.12 — completion notification visibility and read sync

Completion notifications now stay visible when the pointer enters or leaves a card. Opening the matching Codex task can also clear its notification when Spellcast missed the brief unread state.

• Show the completion window through Tauri so its stored visibility agrees with the Windows window. Pointer pass-through changes no longer reapply a stale hidden state.
• Keep observed unread-to-read transitions immediate. For a missed transition, accept a stable Codex snapshot saved after completion once the three-second notification propagation grace has passed.
• Preserve unread notifications, later turns, unavailable or stale snapshots, changed account/host scopes, and tasks whose metadata has not arrived yet. Existing unread observations retain their meaning during the schema upgrade.

Validation

• Completion-related Rust tests: 28 passed, 1 existing ignored test.
• Full local Windows test run: 200 workspace tests passed; 121 desktop library tests passed, with 2 ignored tests.
• Isolated Windows native regression: 22 checks passed, covering pointer pass-through, focus, hide/show, missed read transitions, and retention of a new completion after an older read snapshot.
• The pointer disappearance fix was checked on the actual Windows desktop. The missed-read path was checked with isolated notification/state fixtures; a new live Codex completion-to-click cycle was not observed after installing that fix.
• Package builds run from the tagged commit in GitHub Actions. The local unfinished Canvas changes are not part of this release.

Running the native regression on Windows

Build a separate test identity before running npm run check:completion-visibility:

$env:TAURI_CONFIG = '{"identifier":"com.spellcast.visibility-test","app":{"windows":[{"label":"main","title":"Spellcast visibility test","visible":false}]}}'
cargo build --manifest-path src-tauri/Cargo.toml --bin spellcast
Remove-Item Env:TAURI_CONFIG
npm run check:completion-visibility

The test uses isolated databases and the actual native window commands without moving the system pointer. It refuses an executable with the normal app identity, so it cannot accidentally attach to the installed app's single-instance window. Rebuild with the normal configuration before using the debug executable for ordinary development.

Spellcast v0.4.11

Full Changelog: v0.4.10...v0.4.11

Spellcast v0.4.10

Full Changelog: v0.4.9...v0.4.10

Spellcast v0.4.9 (superseded by v0.4.10)

What's Changed

• Humanize Spellcast README copy (EN + ZH) by @Vanyangyang in #15

Full Changelog: v0.4.8...v0.4.9

Spellcast v0.4.8

Full Changelog: v0.4.7...v0.4.8

Spellcast v0.4.7

Full Changelog: v0.4.6...v0.4.7

Spellcast v0.4.6

What's Changed

• Polish README hero: tofu glyphs, title gradient, simpler motion by @Vanyangyang in #10
• README hero: wand-only loop, drop caption and dots by @Vanyangyang in #11
• Polish README hero wand and recast the aside loop by @Vanyangyang in #12
• Add Grok Build aside-bubble GIF to README How it looks by @Vanyangyang in #13
• Remove Grok Build vs Codex shot disclaimers from READMEs by @Vanyangyang in #14

Full Changelog: v0.4.5...v0.4.6

Spellcast v0.4.5

What's Changed

• Add Linux AppImage and .deb packaging for Spellcast by @Vanyangyang in #4
• README: How it looks walkthrough (Codex asides, early preview) by @Vanyangyang in #3
• README: Grok Build floating bubble and completion notice by @Vanyangyang in #5
• README: add hero wand animation after the title by @Vanyangyang in #6
• README: one story hero GIF after the title by @Vanyangyang in #8
• README: add Product Hunt featured badge (EN + ZH) by @Vanyangyang in #9

Full Changelog: v0.4.3...v0.4.5

Spellcast 0.4.4

Spellcast 0.4.4 — Codex-only setup, Grok Build later

Windows is the only tested platform.

Changes

• Settings install is Codex-only. The Grok Build button stays visible but disabled, with copy that it will be added in a future version. The desktop complete-setup commands refuse a Grok install so they cannot write ~/.grok.
• Hook/Skill merge helpers stay in the library for that later release: they only touch Spellcast’s own MCP table, skills/spellcast, and a Stop group in hooks/spellcast.json, and they refuse invalid user JSON.

Verification

• cargo test --manifest-path src-tauri/Cargo.toml --lib unsupported_clients
• npm run check:i18n, npm run check:complete-setup-ui, npm run check:complete-setup-preview
• Local Windows NSIS install of this build

Spellcast 0.4.2 — Canvas workbench and Grok Build

Spellcast 0.4.2 — Canvas workbench and Grok Build

Windows only tested. The macOS .dmg files are unsigned CI packaging output that nobody has run; they are not guaranteed to work. Expect Gatekeeper warnings.

• Same product as 0.4.0: editable Canvas workbench plus Grok Build as a first-class host (MCP + Skill).
• 0.4.2 only unblocks macOS CI: complete-setup no longer treats system prefixes /var and /tmp as hostile reparse points, so plugin trees under TempDir (/var/folders/...) can install. User profiles under /Users were already fine.

Notes: https://github.com/Vanyangyang/spellcast/blob/main/docs/releases/0.4.2.md
Workbench notes: https://github.com/Vanyangyang/spellcast/blob/main/docs/releases/0.4.0.md