List workflow stage threads

[almirsarajcic]

Adds hey workflow stage view <workflow-id> <stage-id> for listing every thread in a stage.

Depends on basecamp/hey-sdk#141.

---

Summary by cubic

Adds hey workflow stage view <workflow-id> <stage-id> to list threads in a workflow stage. Previously, the CLI had no way to inspect a stage's threads.

New Features

• Table output shows thread ID, subject, and email count.
• JSON output includes stage metadata and each thread's topic_id for hey thread read.
• --ids-only and --count support scripting.

Dependencies

• Pins github.com/almirsarajcic/hey-sdk/go with a replace directive until the upstream SDK exposes stage topics.

^{Written for commit 6d60874. Summary will update on new commits.}

[cubic-dev-ai]

All reported issues were addressed

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

1 issue found across 6 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="go.mod">
<violation number="1" location="go.mod:131">
P2: Merging pins the released CLI to an individual's personal fork (`github.com/almirsarajcic/hey-sdk/go`) via `replace` in go.mod. A personal fork is outside the org's control — the pinned tag can be moved, deleted, or its contents changed, which silently changes what every build and published binary ships. Prefer depending on the upstream SDK once basecamp/hey-sdk PR 141 lands, and consider not merging the `replace` to a personal fork in the meantime.</violation>
</file>

<sub>Requires human review: Auto-approval blocked because this review re-detected 1 unresolved issue already reported by Cubic.
Tip: Review your code locally with the cubic CLI to iterate faster.

Re-trigger cubic</sub>

[cubic-dev-ai]

P2: Merging pins the released CLI to an individual's personal fork (github.com/almirsarajcic/hey-sdk/go) via replace in go.mod. A personal fork is outside the org's control — the pinned tag can be moved, deleted, or its contents changed, which silently changes what every build and published binary ships. Prefer depending on the upstream SDK once basecamp/hey-sdk PR 141 lands, and consider not merging the replace to a personal fork in the meantime.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At go.mod, line 131:
<comment>Merging pins the released CLI to an individual's personal fork (`github.com/almirsarajcic/hey-sdk/go`) via `replace` in go.mod. A personal fork is outside the org's control — the pinned tag can be moved, deleted, or its contents changed, which silently changes what every build and published binary ships. Prefer depending on the upstream SDK once basecamp/hey-sdk PR 141 lands, and consider not merging the `replace` to a personal fork in the meantime.</comment>
<file context>
@@ -127,3 +127,5 @@ require (
k8s.io/klog/v2 v2.140.0 // indirect
)
+
+replace github.com/basecamp/hey-sdk/go => github.com/almirsarajcic/hey-sdk/go v0.28.2-0.20260901124435-ada48dc17209
</file context>