v0.1.6

chore: release v0.1.6

v0.1.5

chore: release v0.1.5

v0.1.4

feat: log token source on startup; document config in README

The language server now logs where the token was resolved from (settings,
CODETIME_TOKEN, or ~/.codetime/config.json), or warns when none is found,
so users can confirm setup in the LSP log. README documents the token
precedence, the log line, and the corrected per-workspace build commands.
Bump to 0.1.4.

v0.1.3

feat: read token from ~/.codetime/config.json by default

Resolve the token from init options, then CODETIME_TOKEN, then the shared
~/.codetime/config.json that other CodeTime clients write — so users
already signed in elsewhere need no setup. Bump to 0.1.3.

v0.1.2

fix: isolate codetime-ls into its own workspace

The extension compiles to wasm32-wasip1, but codetime-ls pulls in
tokio/reqwest/tower-lsp which cannot build for wasm. Having it as a
workspace member made Zed's extension build (and the registry CI) fail
with "Only features ... are supported on wasm". Give codetime-ls its
own workspace so the root wasm build never touches it.

Release CI now builds it via --manifest-path; bump to 0.1.2.

v0.1.1

chore: release v0.1.1

v0.1.0

feat: add Zed extension for codetime.dev activity tracking

Port of codetime-vscode. Zed exposes no editor-event or status-bar API
to extensions, so editing activity is captured via the language server
protocol instead: the WASM extension registers and launches a native
language server (codetime-ls) that turns didOpen/didChange/didSave into
CodeTime event logs and POSTs them to the API.

Consequence: the VS Code status-bar total has no Zed equivalent and is
dropped; tracking is unaffected.