v0.8.0 — GitHub Issues tracker backend

[v0.8.0] — 2026-06-23 · GitHub Issues tracker backend

Added

• Pluggable tracker backends — GitHub Issues support (with a GitLab-ready seam). The
  read/write skills (/next, /resume, /status, /digest, /handoff, /improve) now
  target Jira or GitHub Issues, selected per-repo: an explicit tracker: in
  .bitacora.yml (or ~/.claude/bitacora.yml) wins, otherwise the backend is inferred
  from the git remote host. New resolve-tracker.sh resolves jira | github | gitlab;
  new bitacora-tracker.sh is a uniform CLI adapter over the gh CLI (verbs
  list-mine/view/comments/comment/edit-body/whoami/doctor, emitting
  normalized JSON). A new tracker-adapter skill documents the verb reference and the
  per-backend capability table. On GitHub, /next is naturally repo-scoped, and
  /digest epic rollup degrades gracefully (rolls up by sub-issues, else milestone)
  and names the basis it used. Requires the gh CLI installed and authenticated.
  (#117, #128)

Changed

• The [CTX] format is now tracker-agnostic. validate-ctx.sh remains the single
  format gate across all backends and reads tracker-neutral — URL-wrapping is required on
  every family (GitHub-flavored markdown would autolink bare URLs, but the shared gate
  still requires wrapping for cross-tracker consistency; behavior unchanged).
• /bit:* alias help text generalized from Jira-only to Jira · GitHub · GitLab;
  the plugin/marketplace descriptions and keywords likewise broadened.

Note

• The GitLab adapter column (glab) is stubbed (the seam is built); GitLab support
  ships in a follow-up release.