Shortcut tracker adapter #637

New issue

coilyco-ops · 2026-07-07T21:47:16Z

coilyco-ops commented

2026-07-07 21:47:16 +00:00

Parent epic: #633. Depends on: #634 (Tracker port).

Context. Shortcut is the second named split-stack target: GitLab Enterprise plus Shortcut is a common shape. Shortcut has richer native structure than Trello (Stories, states, workflows, epics), so it is a good second implementation to confirm the Tracker port is not accidentally Trello-shaped.

Proposed change.

Implement the Tracker port against the Shortcut API: a Story is the "issue", with read, comment, state transition (the close semantic maps to a configured workflow state), and label/epic tagging.
Ref mapping to Shortcut Story URLs and parsing them back.
Token resolved user-side.

Acceptance criteria.

A ward run carries a Shortcut Story end to end, transitioning it to the configured done state on success.
The Tracker port needed no signature change to fit both Trello and Shortcut, or if it did, the change is captured back in #634.
Tests cover ref parsing and state mapping.

Milestone: foreign-stack compat. Filed from the read-only director surface (she/her), part of the release-readiness issue batch.

Parent epic: #633. **Depends on:** #634 (Tracker port). **Context.** Shortcut is the second named split-stack target: GitLab Enterprise plus Shortcut is a common shape. Shortcut has richer native structure than Trello (Stories, states, workflows, epics), so it is a good second implementation to confirm the Tracker port is not accidentally Trello-shaped. **Proposed change.** - Implement the `Tracker` port against the Shortcut API: a Story is the "issue", with read, comment, state transition (the close semantic maps to a configured workflow state), and label/epic tagging. - Ref mapping to Shortcut Story URLs and parsing them back. - Token resolved user-side. **Acceptance criteria.** - A ward run carries a Shortcut Story end to end, transitioning it to the configured done state on success. - The Tracker port needed no signature change to fit both Trello and Shortcut, or if it did, the change is captured back in #634. - Tests cover ref parsing and state mapping. --- Milestone: foreign-stack compat. Filed from the read-only director surface (she/her), part of the release-readiness issue batch.

coilyco-ops added this to the foreign-stack compat milestone

2026-07-07 21:47:16 +00:00

coilyco-ops added the

P2

label

2026-07-07 21:47:16 +00:00

coilyco-ops referenced this issue

2026-07-07 21:47:16 +00:00

Additional tracker adapters (Jira, Linear) #638

coilyco-ops referenced this issue

2026-07-07 21:47:50 +00:00

Split issueForge into a git-host port and a Tracker port #634

coilyco-ops referenced this issue

2026-07-07 21:48:40 +00:00

[epic] Release readiness = running ward on foreign stacks (split-stack: git host + tracker) #633

coilyco-ops added the

headless

label

2026-07-09 18:09:26 +00:00

coilyco-ops referenced this issue

2026-07-09 18:26:59 +00:00

Choose an out-of-band issue tracker source before public release #827

coilyco-ops commented

2026-07-09 22:42:15 +00:00

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-ward-637 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-09T22:42:13Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL). --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward#637 · branch issue-637 · harness codex · workflow pull-requests-and-merge
Run: engineer-codex-ward-637 · ward v0.540.0 · dispatched 2026-07-09T22:42:13Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.540.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-637` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T22:42:13Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL). `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/ward#637` · branch `issue-637` · harness `codex` · workflow `pull-requests-and-merge` - **Run:** `engineer-codex-ward-637` · ward `v0.540.0` · dispatched `2026-07-09T22:42:13Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.540.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-09 23:08:08 +00:00

Shortcut tracker adapter #882

coilyco-ops closed this issue

2026-07-10 00:26:26 +00:00

coilyco-ops commented

2026-07-10 00:27:12 +00:00

WARD-OUTCOME: merge-ready

details

workflow: pull-requests-and-merge; review summary: skipped: review gate skipped by ~/.ward/config.yaml default

Implemented the Shortcut tracker adapter, resolved the main merge, and landed the PR.

felt like a conflict-heavy port with a small amount of broker and reservation cleanup around it.
confidence: high
surprises: Forgejo wanted the merge payload as JSON with the head commit pinned.
follow-ups: none

WARD-OUTCOME: merge-ready <details><summary>details</summary> workflow: pull-requests-and-merge; review summary: skipped: review gate skipped by ~/.ward/config.yaml default Implemented the Shortcut tracker adapter, resolved the main merge, and landed the PR. felt like a conflict-heavy port with a small amount of broker and reservation cleanup around it. confidence: high surprises: Forgejo wanted the merge payload as JSON with the head commit pinned. follow-ups: none </details>

coilysiren referenced this issue

2026-07-14 15:27:09 +00:00

director should emit colorized, space buffered, visually distinct messages about the categories of actions its performing on startup #1283

Sign in to join this conversation.