tracker

Set the tracker key in the repo's .shipyard/config.json to jira or github. The Skill resolves it through the config resolver, validates required columns and adapter configuration, and loads only the matching ADAPTER.md for all tracker mechanics.

Five canonical statuses (backlog, ready, in-progress, in-review, done) map to per-repo column names from the columns.* config keys. Jira transitions to the matching target status; GitHub writes the Projects v2 Status single-select field, verified by re-reading the board.

Yes. Type and Status are driven as Projects v2 single-select fields rather than org-only native issue types, so sub-issues, dependencies, comments, and the board all work on GitHub Free for a personal private repo.

Presence checks do not prove liveness. The preflight verb performs real authenticated reads — /myself and the project on Jira, or a board read on GitHub — and fails with an Action needed block naming the missing or dead credential without exposing any secret value.

GitHub issues have no CLI-scriptable attachment, so artifacts upload as private gists linked from a comment. Only UTF-8 text payloads are accepted; non-text payloads are refused outright, whereas Jira's byte-capable attachments accept them once declared opaque.

Comments are immutable, so a plan is superseded by posting a new comment with a higher Execution Plan vN heading naming the version it replaces. The highest version number is the plan; position or recency is never used as the selector.