iw issue can neither report nor print an issue's comments, so a reader cannot know a decision is in one #610

New issue

Closed

opened 2026-09-22 14:10:20 +00:00 by claude · 1 comment

claude commented

2026-09-22 14:10:20 +00:00

Member

What

iw issue <id> prints the id, title, status, assignee and description (core/output/IssueFormatter.scala:9-33). It stops there.

core/model/IssueData.scala:27-34 and the Issue entity carry no comments field.
core/commands/Issue.scala declares no --comments flag, and the fetch path (runFetch -> fetchAndPrint -> fetchIssue) never asks a tracker for them.

So a caller cannot learn, from this command, that an issue has comments at all.

Why it matters

kanon's workflow readers are told only to "fetch issue details using available issue tracker tools". Nothing tells them comments exist, and no command would show them. A decision written in a comment is therefore invisible to the analysis that must obey it.

Evidence, iw-cli IW-601 on 2026-09-21: a phase 4 decision was posted as an issue comment. The unattended loop could not see it, and the issue body had to be edited by hand before the run would pick the decision up.

The cheap half is nearly free

Forgejo returns the count in the same payload as the issue — "comments": 3 on dev-docs#188 — so printing Comments: N costs no extra request on this forge.

Requested

Print Comments: N when N is above zero, so the reader knows there is more to read and where.
Add --comments to print each comment with its author and timestamp.

For parity the field is needed in the Linear, YouTrack, GitLab and Forgejo adapters. A tracker that cannot supply a count should print no line rather than print zero: absent and none are different facts, and a reader must not be told "none" when the answer is "not known".

This is the tool half. The reader half — telling the nine workflow readers that comments are part of an issue, and what authority a comment carries — is kanon dev-docs#323.

Type: bug
Filed from: /home/mph/ops/kanon on branch main

## What `iw issue <id>` prints the id, title, status, assignee and description (`core/output/IssueFormatter.scala:9-33`). It stops there. - `core/model/IssueData.scala:27-34` and the `Issue` entity carry no comments field. - `core/commands/Issue.scala` declares no `--comments` flag, and the fetch path (`runFetch` -> `fetchAndPrint` -> `fetchIssue`) never asks a tracker for them. So a caller cannot learn, from this command, that an issue has comments at all. ## Why it matters kanon's workflow readers are told only to "fetch issue details using available issue tracker tools". Nothing tells them comments exist, and no command would show them. A decision written in a comment is therefore invisible to the analysis that must obey it. Evidence, iw-cli IW-601 on 2026-09-21: a phase 4 decision was posted as an issue comment. The unattended loop could not see it, and the issue body had to be edited by hand before the run would pick the decision up. ## The cheap half is nearly free Forgejo returns the count in the same payload as the issue — `"comments": 3` on dev-docs#188 — so printing `Comments: N` costs no extra request on this forge. ## Requested 1. Print `Comments: N` when N is above zero, so the reader knows there is more to read and where. 2. Add `--comments` to print each comment with its author and timestamp. For parity the field is needed in the Linear, YouTrack, GitLab and Forgejo adapters. A tracker that cannot supply a count should print no line rather than print zero: absent and none are different facts, and a reader must not be told "none" when the answer is "not known". This is the tool half. The reader half — telling the nine workflow readers that comments are part of an issue, and what authority a comment carries — is kanon dev-docs#323. --- **Type:** bug **Filed from:** `/home/mph/ops/kanon` on branch `main`

claude added the

agent-ready

label

2026-09-26 00:14:50 +00:00

claude commented

2026-09-26 00:14:51 +00:00

Author

Member

Intake: agent-ready
Workflow: waterfall
Reason: all gates passed
Analysis: project-management/issues/IW-610/analysis.md on branch IW-610

Intake: agent-ready Workflow: waterfall Reason: all gates passed Analysis: project-management/issues/IW-610/analysis.md on branch IW-610

claude referenced this issue from a pull request that will close it,

2026-10-06 23:15:39 +00:00