GitDocket v0.6.4

GitDocket 0.6.4

Highlights

• Explicit work inventory questions use complete filtered task lists directly, while overview remains the bounded orientation view. Agents reuse fetched results when only selecting fields or formatting an answer.
• Overview and epic-list reads batch committed task evidence through Git, reducing process overhead while preserving source freshness, inventory completeness and explicit incomplete-evidence reporting.
• The retained exact-search index uses compact numeric postings and unique word lists to reduce construction work and allocations while preserving ranking, snippets, complete link neighborhoods and older readers during edits.
• Pickup conflict handling checks applicable host, user, session and project authority before asking for worktree approval. Already-authorized isolation proceeds without another question; missing authority receives one concrete request with the recommended next action first.
• Workspace conflicts and overlapping edits are handled separately. Epic supervision continues independent ready work while affected edits wait for ownership or authorization, with clearer blocker messages.
• Epic review requests name the result and the action approval enables, reuse plain-language acceptance for the same scope, and keep required source explanations brief without repeating skill routing.
• The published 0.6.3 workflow bodies remain frozen as upgrade merge bases. Historical, customized and stale adopters receive the updated instructions or an explicit review requirement.

Verification

• Publication receipt: attached registry.json (SHA-256 bad80b1f33f9e0b76ca649f09994a0a52d380d987d49806b054a24397c6ca04b)
• npm trusted-publisher provenance:
• @gitdocket/core@0.6.4
• @gitdocket/web@0.6.4
• @gitdocket/bin-darwin-arm64@0.6.4
• @gitdocket/bin-darwin-x64@0.6.4
• @gitdocket/bin-linux-arm64@0.6.4
• @gitdocket/bin-linux-x64@0.6.4
• @gitdocket/cli@0.6.4
• @gitdocket/mcp@0.6.4

GitDocket v0.6.3

GitDocket 0.6.3

Highlights

Tasks and Epics can keep a concise, replaceable # Current state checkpoint. Agent overview and compact pickup show bounded checkpoint excerpts with source identity, while status, readiness, dependencies and rollups remain authoritative engine fields.

The existing CLI and MCP document editor can read or replace one named level-one section at a whole-source version. Other content and metadata stay intact; stale saves conflict, equivalent saves avoid churn, and full-body reads and edits remain available.

Workflows prefer checkpoint replacement over repeated progress narration. Logs remain optional for useful milestones and decision context; Git preserves committed chronology. Agents choose consolidation content and preserve uncommitted originals. The engine adds no automatic summarization or pruning.

Included engine cleanups

This release also includes the engine cleanup work carried by 0.6.2: atomic task edits and complete creation, reusable source versions, compact write and pickup receipts, and a bounded agent overview with explicit source continuations.

• Guarded worktree targeting, foreign-closeout warnings and reviewed reconciliation help surface conflicting or missing tracking changes without silently changing acceptance or merging application code.
• Focused lint summaries and verified unchanged index/cache reuse reduce repeated output and refresh work. Shipped workflows reuse loaded instructions and run discovery/lint once after each completed documentation batch when the evidence still applies.
• Explicit supplied-trace diagnostics expose Docket command/read patterns and context contribution while preserving unknown host usage and avoiding automatic session capture.
• Website command-copy controls and canonical maintenance changes are included. The detailed 0.6.2 notes retain the original compatibility boundaries and measured replay limits.

Compatibility

Legacy work items need no migration. Workflow upgrades retain historical merge bases and project customizations, with stale or divergent instructions still requiring review. The assigned 0.6.2 workflow bodies remain frozen; these changes are included in 0.6.3.

Verification

• Tests, native execution, installed smoke and release qualification were skipped at the owner's explicit request. Artifact checksums, package metadata and trusted-publisher provenance were verified.
• Publication receipt: attached registry.json (SHA-256 c5e80b5848f561f27ba798188fd5853557fbb5d2df8b2bb8e5c46452137d6a28)
• npm trusted-publisher provenance:
• @gitdocket/core@0.6.3
• @gitdocket/web@0.6.3
• @gitdocket/bin-darwin-arm64@0.6.3
• @gitdocket/bin-darwin-x64@0.6.3
• @gitdocket/bin-linux-arm64@0.6.3
• @gitdocket/bin-linux-x64@0.6.3
• @gitdocket/cli@0.6.3
• @gitdocket/mcp@0.6.3

GitDocket v0.6.1

GitDocket 0.6.1

GitDocket 0.6.1 lets a named Epic pickup enter Epic supervision without changing the Epic's status or selecting a child task. It hardens Board sorting and makes connected-tool planning easier to discover on the website. It also refreshes the pinned release tools used to build and qualify distribution artifacts.

Named Epic pickup

• docket task start <EPIC-ID> --json now returns a typed route to Epic supervision, including the Epic's authoritative identity and manager title. The human CLI explains the handoff.
• The route leaves the Epic, child tasks and active-task marker unchanged. Ordinary Task pickup and actual command failures keep their existing behavior.
• The Docket pickup workflow follows that route while retaining its active-task conflict, closed-item reopening and manager-title rules. A project that already has 0.6.0 instructions can review and apply the new workflow with docket upgrade.

Board sorting

• Malformed saved Board sort settings now fall back to the default instead of breaking the view. The paged Board API rejects unsupported sort modes with HTTP 400, and an unused count helper was removed.

Connected-tool planning example

• The website illustrates how an extension can use an agent's existing authorized connection to read a Notion list, cite source items and draft a project plan for review. It links to Beacon's retained local MCP evidence and makes clear that no Notion connector, ready-made workflow or live Notion validation is included.

Release tooling

• Release compilation and qualification use pinned Bun 1.4.2 and npm 11.20.0. The minimum Bun version for source development and the core and web libraries remains 1.3.14.
• The release test harness allows more time for installed CLI checks under x64 emulation and prints the subprocess result when a check fails.

Verification

• Publication receipt: attached registry.json (SHA-256 5483d0ea2af02345604c82d469690d1a7dcc0d97645edafb94db78c79912e2a3)
• npm trusted-publisher provenance:
• @gitdocket/core@0.6.1
• @gitdocket/web@0.6.1
• @gitdocket/bin-darwin-arm64@0.6.1
• @gitdocket/bin-darwin-x64@0.6.1
• @gitdocket/bin-linux-arm64@0.6.1
• @gitdocket/bin-linux-x64@0.6.1
• @gitdocket/cli@0.6.1
• @gitdocket/mcp@0.6.1

GitDocket v0.6.0

GitDocket 0.6.0

GitDocket 0.6.0 adds wiki authoring, accepted Decision records, Mermaid diagrams and a combined view of task progress across linked Git worktrees. It also makes parallel tracked work explicit and moves Linux release qualification into local Docker.

Write and reorganize project knowledge

• Create Reference, Spec and Playbook pages with Wiki → New page in the browser, the docket-wiki agent workflow, or the new CLI/MCP document operations. Browser drafts retain their content through navigation, reload and save errors in the same tab; preview and collision checks help you review a page before saving.
• Read and revise complete documents with version checks. A stale edit or an occupied creation path fails without overwriting newer content. Wiki authoring does not start tracked work or select project guidance.
• Plan and apply wiki moves with docket document move-plan and move-apply. Docket repairs supported Markdown links and fragments, preserves relative outbound targets and refreshes the index. Changed source invalidates a plan; interrupted writes retain a recovery journal for move-recover. Unsupported or external references are reported for explicit reconciliation.
• Record an accepted choice with docket decision create or MCP decision_create. Decisions have Context, Decision and Consequences sections and a configurable ids.decision_prefix (default DEC). ID allocation is coordinated across linked worktrees. docket task create --type now accepts Task or Epic; use the dedicated Decision command for decisions.

See work across branches

docket task progress [ID] --json, MCP task_progress, and browser task, board and epic views expose saved task changes from accessible linked worktrees and committed versions in locally available refs. Observations identify their source, incomplete coverage, conflicts and integration evidence. Tasks found only elsewhere remain read-only in the current checkout.

Recorded status and observed progress stay distinct. A branch can report “done” while its changes await integration; matching status after a squash or cherry-pick alone does not prove integration. Dependencies still use the current checkout's recorded state. Reads do not fetch, merge or copy task files, and pickup markers do not claim an agent is running.

Starting a different task in an occupied checkout now returns active-task-conflict, naming both tasks and suggesting an explicit hand-off or a separate linked worktree. Agent guidance checks the branch, starting commit and task availability before isolation. Worktree creation requires explicit authorization unless the request, session or project guidance already grants it.

Projects can opt into reopening closed Tasks or Epics with workflow.reopen_closed: [Task, Epic]. Reopening returns closed work to the queue, requires a reason and preserves the earlier disposition in history. Existing projects retain terminal closed states unless configured; completed done work stays terminal.

Render diagrams locally

Fenced mermaid blocks render as diagrams in Markdown pages and editor previews. Diagram code remains editable Markdown. Mermaid loads only when needed from bundled local assets, including in standalone installations without external network access. Strict rendering, contained errors and source fallback keep a failing diagram from breaking adjacent content.

Release and installation reliability

The release operator now has commands for isolated workspaces, qualification, candidate review packets, bounded waits, owner login and promotion. Receipts retain source identities, checksums, completed steps and resume instructions. Publication verifies the coordinated package set under staged before owner promotion to latest, preserving accepted writes during registry propagation delays.

Linux ARM64 and x64 release qualification runs in local Ubuntu 24.04 Docker containers, including npm/Homebrew lifecycle checks and historical, customized and stale project upgrades. macOS checks remain local, with Intel execution through Rosetta. Receipts identify Docker emulation and Rosetta assistance. Automatic standalone builds on pushes and pull requests are removed; ordinary Linux CI and trusted publication remain on GitHub Actions.

Install and upgrade

brew install gitdocket/tap/gitdocket
docket --version
docket-mcp --version

Existing Homebrew users can run brew update followed by brew upgrade gitdocket. The project formula supplies standalone CLI/MCP executables for macOS 15+ and Homebrew-compatible glibc Linux on ARM64 and x64. It requires Git, with no separate Bun, Node or npm installation. Windows and musl/Alpine are not qualified.

Node 22+ users can instead run npm install -g --include=optional @gitdocket/cli@0.6.0 @gitdocket/mcp@0.6.0. All eight coordinated packages use 0.6.0; core/web libraries and source development remain Bun-based.

After updating executables, review docket upgrade --dry-run --json in each project, then apply docket upgrade and reconcile reported conflicts or retained differences. Package installation does not rewrite project instructions. Published workflow merge bases remain preserved. Restart an existing agent session if its skill inventory predates the new wiki workflow.

Verification

• Publication receipt: attached registry.json (SHA-256 db3246a69fd14b006d262531ac446a767b9d26c5cbc224689912275d7635c9c4)
• npm trusted-publisher provenance:
• @gitdocket/core@0.6.0
• @gitdocket/web@0.6.0
• @gitdocket/bin-darwin-arm64@0.6.0
• @gitdocket/bin-darwin-x64@0.6.0
• @gitdocket/bin-linux-arm64@0.6.0
• @gitdocket/bin-linux-x64@0.6.0
• @gitdocket/cli@0.6.0
• @gitdocket/mcp@0.6.0

GitDocket v0.5.0

GitDocket 0.5.0

GitDocket 0.5.0 adds Cursor as a first-class harness, restores and expands opt-in local usage telemetry, and ships the compact homepage install control. It preserves the published 0.4.1, 0.4.0, 0.3.1, 0.3.0, 0.2.1 and 0.1.1 workflow merge bases.

Cursor beside Claude and Codex

• Initialize Cursor with docket init --agent cursor. That writes .cursor/skills/docket-*/SKILL.md pointers and, when docket-mcp is on PATH, registers docket in .cursor/mcp.json without clobbering Claude, Codex, or an existing custom Cursor MCP entry.
• Combined --agent cursor --agent claude --agent codex installs remain additive. Cursor does not rewrite .mcp.json, Claude settings, or Codex TOML.
• Pickup and epic-manager titles use Cursor's rename_chat on the calling conversation. Epic supervision on Cursor stays serial in that session; isolated worker/worktree orchestration is not claimed.
• After init writes a new project server, enable it once in Customize → MCPs (Command Palette: Open MCPs). Init cannot complete that host approval.
• docket upgrade regenerates stale marked Cursor skill stubs, skips hand-authored Cursor files, and does not rewrite .cursor/mcp.json.

Public install and harness docs name Cursor beside Claude and Codex. Canonical workflows stay host-neutral; Cursor tool names stay in the adapter layer and generated skills.

Local usage telemetry

Opt-in local collection now covers ordinary MCP tool calls, known actor/host values at verified CLI/MCP/Serve boundaries, and checkout-local workflow tokens from docket task start that later CLI commands in that checkout can attach. Independent MCP and Serve callers still pass workflow/actor/host explicitly; a long-lived MCP process does not join unrelated work.

Reports add recent 24-hour and seven-day windows beside the full retained sample, a versioned coverage inventory, and content-free search/save/failure outcomes. Editor open/preview/save, extension discovery/lifecycle, and MCP workflow_extensions are inventoried from 0.5.0. Silence is not treated as unused. Telemetry remains local, content-free and off by default.

Website and install copy

The homepage Homebrew command is a compact chip rather than a full-width bar, with supported platforms and the npm alternative on one quiet line. Site docs that teach --agent include Cursor. These pages go live with public main after Homebrew and npm 0.5.0 installs pass.

Installation

brew install gitdocket/tap/gitdocket
docket --version
docket-mcp --version

The project-maintained formula installs standalone CLI/MCP executables, embedded browser resources and retained upgrade history. No separate Bun, Node or npm installation is needed. Release qualification combines Ubuntu 24.04 ARM64/x64 checks in Linux-only GitHub Actions with local Mac ARM64 and Rosetta-assisted Intel checks; receipts record the actual Mac OS and assistance. The formula supports macOS 15+ and Homebrew-compatible glibc Linux on those architectures. Windows is not supported.

Node 22+ users can instead run npm install -g --include=optional @gitdocket/cli@0.5.0 @gitdocket/mcp@0.5.0. The existing npm names launch exact-version platform packages containing the same binaries as Homebrew. The core/web libraries remain Bun-based. Source development and the Beacon example app still require Bun.

Use your package manager to update the executables. In each project, review docket upgrade --dry-run --json before applying docket upgrade and resolving any reported conflicts or retained differences. Package installation, updating and removal preserve project bundles; they do not reconcile project instructions automatically. If switching from npm/Bun, inspect command precedence and custom MCP paths using the migration guide.

All eight coordinated npm packages use 0.5.0. Claude adapters are generated; Claude behavior remains unqualified where authentication is unavailable. Isolated Cursor worker orchestration remains out of scope.

Verification

• Publication receipt: attached registry.json (SHA-256 6af411c504d1cb4a085da3edb768eaa4d200cf171b5c0111acbc032c4e37210f)
• npm trusted-publisher provenance:
• @gitdocket/core@0.5.0
• @gitdocket/web@0.5.0
• @gitdocket/bin-darwin-arm64@0.5.0
• @gitdocket/bin-darwin-x64@0.5.0
• @gitdocket/bin-linux-arm64@0.5.0
• @gitdocket/bin-linux-x64@0.5.0
• @gitdocket/cli@0.5.0
• @gitdocket/mcp@0.5.0

GitDocket v0.4.1

GitDocket 0.4.1

GitDocket 0.4.1 installs both commands with one Homebrew command and adds reusable project workflows. It preserves the published 0.3.1 and partially published 0.4.0 workflow merge bases.

Teams can inspect and install versioned local Markdown packages, configure project choices, discover qualified workflows, update packages independently of GitDocket, and disable or remove them while retaining project records. Conservative reconciliation exposes local edits, incompatible content and interrupted operations. Mechanical validation reports its limits without executing package code.

The extension guide and Beacon example demonstrate a product-delivery process from reviewed request to verified local handoff, with reusable decisions for later work. A second incident-review package demonstrates independent authoring and composition. Optional recipes use tools already exposed by the agent host, including MCP; the host owns connections and credentials. Custom UI/statuses, executable plugins and background synchronization remain outside this version.

Qualification includes actual Codex sessions, real browser downloads, local synthetic MCP success/failure/uncertainty, fresh-session recovery, historical/customized upgrades, and macOS/Linux package checks. Claude adapters are generated, but Claude behavior remains unqualified in the tested environment because authentication was unavailable. Synthetic review and provider fixtures are not human approval or live delivery.

This candidate also fixes Git updates in linked worktrees on Linux when a missing private refs directory deferred its filesystem error until iteration. Direct watcher and Serve regressions verify shared refs, detached HEAD changes and packed refs without increasing timeouts.

Installation

brew install gitdocket/tap/gitdocket
docket --version
docket-mcp --version

The project-maintained formula installs standalone CLI/MCP executables, embedded browser resources and retained upgrade history. No separate Bun, Node or npm installation is needed. Release qualification combines Ubuntu 24.04 ARM64/x64 checks in Linux-only GitHub Actions with local Mac ARM64 and Rosetta-assisted Intel checks; receipts record the actual Mac OS and assistance. The formula supports macOS 15+ and Homebrew-compatible glibc Linux on those architectures. Windows is not supported.

Node 22+ users can instead run npm install -g --include=optional @gitdocket/cli@0.4.1 @gitdocket/mcp@0.4.1. The existing npm names now launch exact-version platform packages containing the same binaries as Homebrew. The core/web libraries remain Bun-based. Source development and the Beacon example app still require Bun.

Use your package manager to update the executables. In each project, review docket upgrade --dry-run --json before applying docket upgrade and resolving any reported conflicts or retained differences. Package installation, updating and removal preserve project bundles; they do not reconcile project instructions automatically. If switching from npm/Bun, inspect command precedence and custom MCP paths using the migration guide.

Qualification exercises both installation routes, npm/npx, browser resources, actual MCP tooling, historical/customized/stale project upgrades, Homebrew reinstall/revision upgrade/uninstall, and failed checksum/download recovery. Release artifacts include source identity, licenses, checksums and native verification receipts. All eight coordinated npm packages use 0.4.1.

Markdown authoring guidance now preserves unwrapped paragraphs and simple list items, and lint reports accidental hard wrapping. Existing project content is never silently reformatted.

Publication recovery

This patch release completes the installation launch after 0.4.0 publication stopped during npm registry propagation. The publisher now waits up to ten minutes for version, provenance and tag visibility, bounds each metadata lookup and records accepted writes and verification progress immediately. Regression checks cover delayed visibility, safe resumption and immutable conflicts. The existing 0.4.0 tag and published packages remain unchanged.

Verification

• Publication receipt: attached registry.json (SHA-256 1c2943dbf61ef1366fb3019c386af74ebbf8a59626efcfed9d1818462fe427f4)
• npm trusted-publisher provenance:
• @gitdocket/core@0.4.1
• @gitdocket/web@0.4.1
• @gitdocket/bin-darwin-arm64@0.4.1
• @gitdocket/bin-darwin-x64@0.4.1
• @gitdocket/bin-linux-arm64@0.4.1
• @gitdocket/bin-linux-x64@0.4.1
• @gitdocket/cli@0.4.1
• @gitdocket/mcp@0.4.1

GitDocket v0.3.1

GitDocket 0.3.1

GitDocket 0.3.1 makes retained workflow differences explicit during upgrades and gives the website’s documentation headings more breathing room.

Upgrade review

docket upgrade now labels retained workflow differences review in human output and returns a reviewRequired path list in JSON, with reviewRequired: true on affected items. This includes clean merges and unchanged files whose origin already matches the current version. A current stamp or conflict-free merge does not prove that current instructions arrived: compare retained differences with the shipped workflow and preserve confirmed project requirements.

The JSON action continues to describe the file operation. Review items preserve project-owned text and do not change the exit status; merge conflicts still return a nonzero status.

Historical upgrade checks now run in the normal test suite and against installed candidate packages during release qualification. They cover clean historical workflows, deliberate customization, stale version stamps, incomplete conflict resolution, repeat upgrades and preservation of authored guidance. Published 0.3.0 workflow bodies remain frozen as merge bases.

Website spacing

Documentation section headings now have consistent space above them: 48px on desktop and 40px on mobile, with smaller subheading gaps. The shared stylesheet handles both wrapped sections and headings directly in the page, avoiding cramped transitions or doubled spacing. All eight pages were checked at desktop and narrow mobile widths.

Upgrade

bun add --global @gitdocket/cli@0.3.1 @gitdocket/mcp@0.3.1

Restart Serve processes and reconnect MCP clients. In each existing project, run docket upgrade --dry-run, review the plan, then run docket upgrade. Reconcile conflicts and retained differences before treating the upgrade as complete, then run docket index and docket lint. This release does not automatically replace project-owned workflow differences.

All four packages (core, web, cli, and mcp) use version 0.3.1. No project-document migration is required.

Verification

• Publication receipt: attached registry.json (SHA-256 5ed4eada5244a3dc547276090b3450992a0ec923505a030063eb5c60b0dbf741)
• npm trusted-publisher provenance:
• @gitdocket/core@0.3.1
• @gitdocket/web@0.3.1
• @gitdocket/cli@0.3.1
• @gitdocket/mcp@0.3.1

GitDocket v0.3.0

GitDocket 0.3.0

GitDocket 0.3.0 adds saved project guidance, a shared browser editor, and a simpler path from one useful task to a fresh agent session that can use what the project learned.

Saved project guidance

• Save standards and scoped procedures in ordinary linked Markdown, then ask your agent to inspect, revise or retire them.
• Use the new Project guidance destination to manage instructions and procedure links through the browser. Removing a guidance link preserves the shared source document.
• Make relevant guidance discoverable before direct or tracked implementation through repository instructions, native adapter files, task context, and the new project_guidance MCP tool or docket guidance command.
• Preserve project-owned guidance and local instructions through initialization and upgrades.

Guidance is optional. Saving a procedure does not authorize its execution, and saving an instruction does not guarantee that an already-running agent has read or applied it. Agents are instructed to reread after explicit changes or before the next piece of work. Controlled fresh-session checks demonstrated saved rules applied to implementation; native client and authentication limits remain documented.

Edit authored documents in the browser

• Edit titles, descriptions and complete Markdown bodies across tasks, epics, specs, references, playbooks, decisions, workflows and custom concepts with one shared editor.
• Preview changes, save explicitly, and recover same-tab drafts after navigation or reload where browser storage is available.
• Detect changed source versions, retain the draft, and review and reconcile the latest source before retrying.
• Distinguish local saves, optional successful commits, and source saved with a failed commit. Unrelated staged work remains intact.

Generic content edits preserve IDs, lifecycle state, provenance and evidence fields. Editing an acceptance checkbox does not complete a task. Generated views and reserved introduction, briefing and log sources retain their existing workflows. Draft recovery is best-effort; closing the tab or losing storage can lose a draft. Complete-source editing supports Markdown files up to 256 KiB, with documented limits for arbitrary external writers.

Start smaller and carry knowledge forward

• Begin with one standalone task; specs, epics, a populated wiki and saved guidance are optional.
• Follow the revised homepage, one-task tutorial and everyday-use guide to inspect what changed, why, and what was checked.
• See a retained demonstration where a separate fresh agent uses a task-recorded decision and a browser-edited convention to plan later work.
• Get clearer recovery instructions for missing or stale briefings, local-save explanations, and completion/follow-up guidance.
• Open and share tasks and epics through stable ticket-number URLs that survive title changes.

The demonstration distinguishes scripted work from controlled agent execution. Agent-proxy comprehension checks are not human customer research, and a completed status alone does not establish correctness.

Upgrade

Requires Bun 1.3.14 or newer on macOS or Linux:

bun add --global @gitdocket/cli@0.3.0 @gitdocket/mcp@0.3.0
docket --version

Restart Serve processes and reconnect MCP clients. In each existing project, run docket upgrade, review local workflow customizations or conflicts, then run docket index and docket lint. The workflow ledger preserves the exact published 0.2.1 and 0.1.1 bodies as upgrade merge bases; 0.3.0 carries the new guidance and planning workflows. No project-document migration is required.

All four packages (core, web, cli, and mcp) use version 0.3.0. Telemetry remains opt-in and local. Existing large-project performance qualification and usage pilots remain open; this release adds no latency or memory SLA.

Verification

• Publication receipt: attached registry.json (SHA-256 02e4a97b453a9063250139cc0de644e469865ce33ffd3aae1a44261e148a596f)
• npm trusted-publisher provenance:
• @gitdocket/core@0.3.0
• @gitdocket/web@0.3.0
• @gitdocket/cli@0.3.0
• @gitdocket/mcp@0.3.0

GitDocket v0.2.1

GitDocket 0.2.1

GitDocket 0.2.1 brings faster repeated reads, a redesigned local workspace, opt-in local telemetry, and a shorter website with focused reference docs.

Faster project navigation and agent reads

• Reuses parsed concepts, exact search indexes, Serve snapshots, and Git evidence across repeated reads instead of repeatedly rebuilding the project.
• Adds bounded pages for browser collections and source/history retrieval, while preserving complete CLI/MCP exports when requested.
• Keeps persistent MCP reads warm and coordinates task writes across processes.
• Adds the source_page MCP tool and docket source command for bounded Markdown reads with source hashes and continuation cursors.

These changes improve ordinary browsing and agent workflows. Cold starts, large exports, and very large project memory costs still need further qualification; this release does not promise a latency or memory SLA.

A clearer local workspace

• Makes Home and Board the first navigation destinations, with a compact board overview and project re-entry context on Home.
• Adds a document-focused Wiki workspace and clearer reading, metadata, navigation, and pagination across work views.
• Improves board controls, filtering, collapsed empty columns, epic editing, and responsive layouts while keeping Markdown and Git authoritative.

Local telemetry, explicitly opt-in

Telemetry is off by default and enabled separately for each checkout:

docket telemetry enable
docket telemetry status
docket telemetry report

Observations stay on the local computer, outside the repository. Docket never uploads them. The allowlisted records cover operation counts, timings, errors, and sampled runtime memory; they exclude document contents, prompts, search terms, task IDs, and file paths. Reports show sample and coverage limits.

Use docket telemetry disable to stop collection and docket telemetry delete to remove the current checkout's enrollment and retained observations. Exports you create remain yours to manage.

Website and reference

The homepage is shorter and shows the current interface. On-site docs cover setup, CLI commands, MCP workflows and input schemas, and a small reference for the local browser API. The scripted Harbor example retains inspectable CLI evidence and replay instructions.

Release validation

This release also fixes a macOS-specific test temporary path and aligns the macOS/Linux CI toolchain with the publication workflow. The earlier v0.2.0 tag stopped at preflight before publishing packages; 0.2.1 supersedes that candidate.

Upgrade

Requires Bun 1.3.14 or newer on macOS or Linux:

bun add --global @gitdocket/cli@0.2.1 @gitdocket/mcp@0.2.1
docket --version

Restart running Serve processes and reconnect MCP clients to load the new code. In each existing project, run docket upgrade, review any local workflow customizations or conflicts, then run docket index and docket lint. The released 0.1.1 workflow bodies remain the upgrade merge base.

All four packages (core, web, cli, and mcp) use version 0.2.1. Telemetry remains disabled until explicitly enabled for that checkout.

Verification

• Publication receipt: attached registry.json (SHA-256 adbda1ac760717df404af523a4e0d3583b35dbeec4839e7871bc94ef2f7e6acb)
• npm trusted-publisher provenance:
• @gitdocket/core@0.2.1
• @gitdocket/web@0.2.1
• @gitdocket/cli@0.2.1
• @gitdocket/mcp@0.2.1

GitDocket v0.1.1

GitDocket 0.1.1

Highlights

• Coordinates sequential task and epic IDs across linked Git worktrees, including uncommitted sibling-worktree concepts, while retaining explicit duplicate recovery for separate clones.
• Adds bounded, provenance-bearing evidence for task-linked commits on local branches and worktrees without letting another checkout override canonical status, readiness, or authored project context.
• Makes opt-in Serve commits resilient to concurrent HEAD and index changes through isolated commit trees, repository-operation refusal, hooks, signing, and compare-and-swap publication.
• Adds deterministic candidate planning, fail-closed public staging, and an exact local-tarball product smoke before publication.
• Adds approval-gated, tokenless npm publication under a holding tag with safe recovery for partial package and dist-tag states.
• Completes a coherent registry release with verified provenance, a registry-only product smoke, and a first-class GitHub Release receipt.

Verification

• Publication receipt: attached registry.json (SHA-256 40b019d11596f52586411d1fd64cea4032d194a3638a10ecffd84195607b4a2c)
• npm trusted-publisher provenance:
• @gitdocket/core@0.1.1
• @gitdocket/web@0.1.1
• @gitdocket/cli@0.1.1
• @gitdocket/mcp@0.1.1