JishuDB v0.7.5

JishuDB v0.7.5

Status: Desktop-only stable release preparation.

JishuDB v0.7.5 completes the WorkBuddy OAuth connection flow for the macOS
ARM64 and Windows x64 Desktop distributions. It also includes the current
Desktop authentication-motion, Agent installer, model-onboarding, and Notes
migration reliability fixes. This release does not publish or promote
Homebrew, native service, Linux container, or Docker artifacts.

WorkBuddy OAuth

• Adds OAuth dynamic client registration for WorkBuddy clients and binds each
  registered client to its declared scope and callback.
• Accepts the validated workbuddy://workbuddy/mcp/.../oauth/callback redirect
  only for dynamically registered clients while preserving strict loopback or
  HTTPS redirects for metadata-based clients.
• Provides an in-flow login and consent experience when the browser has no
  existing JishuDB human session.
• Protects unauthenticated consent completion with an expiring,
  installation-bound proof and validates the request origin.
• Preserves PKCE S256, exact redirect checks, rotating refresh tokens,
  refresh-family replay revocation, and explicit grant revocation.

Compatibility and reliability

• Preserves Service Bearers, manually created jkm_ tokens, and stdio as
  separate compatibility paths.
• Keeps authentication motion responsive and includes the latest immutable
  release provenance checks used by the Agent installers.
• Reuses the active Desktop migration transaction during Notes repair to avoid
  a nested SQLite writer transaction.

Distribution boundary

• Publishes the existing explicit unsigned macOS DMG and Windows per-user NSIS
  contracts; no publisher identity, notarization, or SmartScreen reputation is
  claimed.
• Requires exact protected-tag and source-revision checks. Stable promotion
  remains a separate workflow after macOS and Windows acceptance.

JishuDB v0.7.4

JishuDB v0.7.4

Status: Desktop-only stable release preparation.

JishuDB v0.7.4 adds the verified Agent installation Skill and standards-based
HTTP MCP OAuth to the macOS ARM64 and Windows x64 Desktop distributions. It
also keeps folder synchronization restart recovery responsive and validates
the safe internal symlinks required by the packaged macOS application. This
release does not publish or promote Homebrew, native service, Linux container,
or Docker artifacts.

Desktop OAuth

• Enables MCP OAuth only through the controlled Desktop service launcher while
  native and headless services remain opt-in and disabled by default.
• Publishes protected-resource and authorization-server discovery for the
  loopback Desktop MCP endpoint.
• Requires explicit browser consent, exact redirect validation, and PKCE S256.
• Uses rotating refresh tokens, refresh-family replay revocation, explicit
  grant revocation, and fail-closed installation-identity reconciliation.
• Preserves existing Service Bearers, manually created jkm_ tokens, and stdio
  behavior as separate compatibility paths.

Agent installation

• Adds self-contained JishuDB Skill 0.1.2 for supported Agents.
• Selects only stable immutable releases with exact API asset digests, adjacent
  checksums, candidate manifests, and source-revision verification.
• Installs macOS Desktop per-user to ~/Applications/JishuDB.app without
  elevation after one reviewed Agent transaction approval.
• Allows only relative application-bundle symlinks whose resolved targets stay
  inside the verified bundle; absolute, dangling, and escaping links fail
  closed before copy and are rechecked after staging and installation.
• Retains operating-system publisher prompts, first-administrator creation,
  browser consent, secret entry, and client trust as user-presence gates.

Restart reliability

• Retries transient SQLite writer contention on the one-second folder-sync
  coordinator loop instead of turning it into a 30-second root-error backoff.
• Preserves the existing error state and recovery behavior for non-transient
  scanner failures.

Distribution boundary

• Publishes the existing explicit unsigned macOS DMG and Windows per-user NSIS
  contracts; no publisher identity, notarization, or SmartScreen reputation is
  claimed.
• Requires the public GitHub prerelease and final stable release to report
  immutable: true before the Agent installer accepts it.

JishuDB v0.7.3

JishuDB v0.7.3

Status: Desktop-only stable release preparation.

JishuDB v0.7.3 adds the verified Agent installation Skill and standards-based
HTTP MCP OAuth to the macOS ARM64 and Windows x64 Desktop distributions. It
also keeps folder synchronization restart recovery responsive when startup
scanning briefly contends for the SQLite writer. This release does not publish
or promote Homebrew, native service, Linux container, or Docker artifacts.

Desktop OAuth

• Enables MCP OAuth only through the controlled Desktop service launcher while
  native and headless services remain opt-in and disabled by default.
• Publishes protected-resource and authorization-server discovery for the
  loopback Desktop MCP endpoint.
• Requires explicit browser consent, exact redirect validation, and PKCE S256.
• Uses rotating refresh tokens, refresh-family replay revocation, explicit
  grant revocation, and fail-closed installation-identity reconciliation.
• Preserves existing Service Bearers, manually created jkm_ tokens, and stdio
  behavior as separate compatibility paths.

Agent installation

• Adds a self-contained JishuDB Skill for supported Agents.
• Selects only stable immutable releases with exact API asset digests, adjacent
  checksums, candidate manifests, and source-revision verification.
• Installs macOS Desktop per-user to ~/Applications/JishuDB.app without
  elevation after one reviewed Agent transaction approval.
• Retains operating-system publisher prompts, first-administrator creation,
  browser consent, secret entry, and client trust as user-presence gates.

Restart reliability

• Retries transient SQLite writer contention on the one-second folder-sync
  coordinator loop instead of turning it into a 30-second root-error backoff.
• Preserves the existing error state and recovery behavior for non-transient
  scanner failures.

Distribution boundary

• Publishes the existing explicit unsigned macOS DMG and Windows per-user NSIS
  contracts; no publisher identity, notarization, or SmartScreen reputation is
  claimed.
• Requires the public GitHub prerelease and final stable release to report
  immutable: true before the Agent installer accepts it.

JishuDB v0.7.0

JishuDB v0.7.0

Status: release candidate preparation.

JishuDB v0.7.0 improves model onboarding, authenticated agent access, upload
safety, and multilingual knowledge workflows while retaining the established
protected release and explicit unsigned Desktop security contracts.

User experience

• Adds direct model cards for text, image, and cloud-provider switching, with
  clearer active-model and connection details.
• Rejects unsupported uploads before reading or sending file contents, and
  links an unavailable chat composer directly to model settings.
• Adds bilingual AI summaries and returns the summary matching the selected UI
  language.
• Improves guided Ollama setup and resets incomplete cloud-provider form state
  when settings close.
• Adds a domestic model-mirror fallback for model onboarding.

Agent and model connectivity

• Adds MCP connection management and exposes the native LAN MCP endpoint for
  approved local-network clients.
• Keeps token reveal actions attached to the connection that owns the token.
• Rejects empty API keys when a new cloud provider is configured.
• Improves MiniMax VLM/OCR request compatibility and diagnostics.

Release platforms

• Linux container: protected ARM64 image with provenance, SBOM, ingestion,
  retrieval, and local reranker smoke gates.
• macOS native: Apple Silicon runtime archive and Homebrew Formula through the
  protected native distribution workflow.
• macOS Desktop: unsigned Apple Silicon DMG requiring manual Gatekeeper
  approval.
• Windows Desktop: unsigned Windows 11 x64 per-user installer requiring manual
  SmartScreen approval.

The Desktop candidates must come from the same protected v0.7.0 tag, source
revision, and workflow attempt. They remain a prerelease until the exact DMG
and Windows installer pass independent machine and checksum verification. No
existing release asset or tag is replaced.

JishuDB v0.6.3

JishuDB v0.6.3

Status: release candidate preparation.

JishuDB v0.6.3 improves first-run setup, content recovery, and agent access
while retaining the v0.6.2 distribution and unsigned Desktop security
contracts.

User experience

• Adds guided local and cloud model setup with validation that blocks invalid
  cloud credentials from being saved.
• Adds MCP connection management and enables authenticated HTTP MCP access for
  approved local and LAN clients.
• Supports direct agent uploads and makes content upload, folder sync, and
  failed-ingest recovery more actionable.
• Improves Notes and Content identity synchronization, conversation history,
  and knowledge inventory answers.
• Makes Feishu onboarding progress and recovery guidance reflect the actual
  connection state.
• Improves Windows first-run recovery, folder synchronization, installation,
  and Desktop lifecycle handling.
• Keeps automatic AI Wiki generation disabled by default.

Release platforms

• macOS Desktop: unsigned Apple Silicon DMG.
• Windows Desktop: unsigned Windows 11 x64 per-user installer.
• Linux container: the protected v0.6.3 tag drives the release image
  workflow.
• macOS native: Apple Silicon runtime archive and Homebrew Formula published
  through the protected native distribution workflow.

The Desktop candidates must come from the same protected tag, source revision,
and workflow attempt. They remain a prerelease until the exact DMG and Windows
installer pass their independent smoke gates. No existing release asset or tag
is replaced.

JishuDB v0.6.2

JishuDB v0.6.2

Status: release candidate preparation.

JishuDB v0.6.2 fixes the Desktop first-use route while retaining the v0.6.1
distribution and security contracts.

User experience

• Starts the seven-step first-use tutorial immediately after a new
  administrator is created.
• Does not redirect a fresh Desktop instance to model settings before the
  tutorial.
• Remembers completion or an explicit skip, and resumes the tutorial after an
  interrupted first launch.
• Keeps the tutorial available from Settings → About → Getting started.
• Restores copy actions for connection URLs, pairing codes, tokens, and client
  configuration JSON in the sandboxed Desktop renderer without broadening
  Electron permissions.

Release platforms

• macOS Desktop: unsigned Apple Silicon DMG.
• Windows Desktop: unsigned Windows 11 x64 per-user installer.
• Linux container: the protected v0.6.2 tag drives the release image
  workflow.
• macOS native: Apple Silicon runtime archive and Homebrew Formula published
  through the protected native distribution workflow.

The Desktop candidates must come from the same protected tag, source revision,
and workflow attempt. They remain a prerelease until the exact DMG and Windows
installer pass their independent smoke gates. No existing release asset or tag
is replaced.

JishuDB v0.6.1

JishuDB v0.6.1

Status: release candidate preparation.

JishuDB v0.6.1 is the first shared-version Desktop release candidate for
unsigned macOS ARM64 and Windows 11 x64 packages. It forward-fixes the aborted
v0.6.0 publication by encoding the shared workflow-attempt provenance with one
canonical integer type. The protected v0.6.1 tag, full source revision,
adjacent checksums, and platform candidate manifests are the authoritative
artifact identity.

User experience

• Adds the guided card tutorial for the knowledge workflow.
• Adds the new-user welcome experience on the authentication path.
• Delivers the compact content workspace, refined source-management flows,
  improved source previews, and citation navigation.
• Keeps the knowledge-base AI Wiki, per-file summaries, content ingestion,
  retrieval, notes, and local MCP tools in the shared application.

Desktop platforms

macOS

• Apple Silicon (arm64) only.
• Requires macOS 13.3 or newer.
• Distributed as
  jishudb-desktop-0.6.1-unsigned-darwin-arm64.dmg.
• Uses unsigned-dmg-v1 and unsigned-local-user-presence-v1.
• Has no Developer ID identity, notarization, or stapled ticket. The first open
  requires the documented macOS manual-open flow.

Windows

• Windows 11 x64 only; minimum supported build is 10.0.19045.
• Distributed as JishuDB-Windows-x64-0.6.1-Setup.exe.
• Uses the current-user per-user-nsis-v1 installer and
  windows-fresh-install-v1 authorization contract.
• Has no Authenticode publisher identity. Windows may show Unknown Publisher or
  Microsoft Defender SmartScreen guidance; this release does not claim
  publisher authentication or SmartScreen reputation.
• Does not install a Windows Service, modify the system PATH, add a firewall
  rule, or require administrator installation.

Artifact verification

Both platform artifacts are built from the same protected tag and workflow
attempt. Each artifact is published with an adjacent SHA-256 file and immutable
candidate manifest. Verify the checksum before installation. A checksum,
revision, version, runtime-lock, or candidate mismatch invalidates the release
evidence.

The Windows and macOS candidates are one release unit. The public prerelease
must remain a prerelease until the exact DMG passes the Mac Air gate and the
exact installer passes the controlled Windows 11 install, lifecycle, MCP,
upgrade, uninstall-data-preservation, and recovery gates. Either-platform
failure blocks stable promotion.

Known limitations

• Desktop updates are manual; no automatic updater is included.
• macOS Intel and Windows ARM64 are not supported.
• Windows Folder Sync, Windows Hello recovery, remote/LAN Agent exposure, and
  Windows application signing are outside this interim release.
• The local MCP endpoint remains loopback-only by default.

No existing tag or release asset is replaced in place. Publication, promotion,
and withdrawal retain the immutable checksums and candidate evidence.

JishuDB v0.4.2

JishuDB v0.4.2

JishuDB v0.4.2 is the forward-only source version for the next native/Homebrew
and macOS Desktop release attempt. The channels use the same protected source
tag and full revision, but they remain independently published and promoted.

The public native/Homebrew v0.4.1 release remains immutable historical
release evidence. This release does not delete, recreate, or replace that tag,
its assets, or its Formula history. No public Desktop v0.4.1 release was
created.

Desktop packaging fix

The Desktop resource configuration now copies the manifest-bound
web/assets/handbook/.gitkeep through an explicit file mapping. This avoids an
electron-builder directory-walk rule that otherwise drops .gitkeep before
resource filters run and causes the mounted runtime inventory to differ from
DESKTOP-RUNTIME.json.

The fix preserves the strict packaged-runtime inventory gate. It does not add
an exception to the verifier, ignore missing files, or weaken checksum and
symlink validation.

Unsigned macOS artifacts

The Apple Silicon native runtime archive and Desktop DMG remain unsigned Apple
artifacts. They have no Developer ID publisher identity and are not notarized
or stapled. The Desktop app uses the declared unsigned-dmg-v1 distribution
mode, unsigned-local-user-presence-v1 authorization mode, and deterministic
ad-hoc integrity seals for runtime Mach-O files followed by the complete app
bundle. Those seals provide structural integrity only; they do not authenticate
JishuDB as the publisher.

For a Desktop DMG, verify the adjacent SHA-256 and candidate metadata before
use. A normal first open is expected to require the documented macOS manual-open
flow. Do not weaken macOS security settings globally.

Release evidence

• GitHub and GitLab protected v0.4.2 tags must resolve to the same full source
  revision before either channel is dispatched.
• Native/Homebrew and Desktop candidates must each pass their own immutable
  artifact, checksum, public-download, and Mac Air gates before promotion.
• A successful native release does not imply that a Desktop DMG exists, and a
  Desktop release never promotes the Homebrew Formula.
• Neither channel replaces an existing tag or release asset in place.