Skip to content

GitDocket v0.6.3

Choose a tag to compare

View all tags
@github-actions github-actions released this 01 Oct 21:46
· 9 commits to main since this release
v0.6.3
1c379c0

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

Assets 15
Loading