phase-pr appends view-pr to available_actions instead of replacing the list #649

New issue

Open

opened 2026-09-27 11:04:16 +00:00 by claude · 3 comments

claude commented

2026-09-27 11:04:16 +00:00

Member

iw-cli phase-pr appends view-pr to available_actions instead of publishing [implement:Continue:IMPL, view-pr] with replace (Decision (a)) — /home/mph/Devel/iw/iw-cli/core/commands/PhasePr.scala:700-701 uses ArrayMergeMode.Append; IMPL comes from the card's workflow_type

Found in kanon DEVDOCS-315, which makes every kanon gate writer publish its own actions with replace. phase-pr is the remaining writer that appends.

Type: bug
Filed from: /home/mph/ops/kanon-DEVDOCS-315 on branch DEVDOCS-315

iw-cli `phase-pr` appends `view-pr` to available_actions instead of publishing `[implement:Continue:IMPL, view-pr]` with replace (Decision (a)) — `/home/mph/Devel/iw/iw-cli/core/commands/PhasePr.scala:700-701` uses `ArrayMergeMode.Append`; IMPL comes from the card's `workflow_type` Found in kanon DEVDOCS-315, which makes every kanon gate writer publish its own actions with replace. phase-pr is the remaining writer that appends. --- **Type:** bug **Filed from:** `/home/mph/ops/kanon-DEVDOCS-315` on branch `DEVDOCS-315`

claude commented

2026-10-15 16:31:56 +00:00

Author

Member

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

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

claude added the

agent-ready

label

2026-10-15 16:31:56 +00:00

claude commented

2026-10-15 17:12:18 +00:00

Author

Member

Implement: needs-human
Reason: batch-implement exit 1 — the kanon plugin did not compile against iw-cli main. ForgeCatchUp.scala:143 expects Either[String, …] from fetchPullRequestForBranch, but main now returns Either[TrackerError, …] (#778, #780). No phase ran. The cause is not in this issue; every iw-cli item fails the same way until kanon's iw-plugin follows the new port type.

[error] /home/mph/.local/share/iw/plugins/kanon/lib/batch/ForgeCatchUp.scala:143:7
[error] Found:    Either[iw.core.model.TrackerError, Option[batch.ForgeState]]
[error] Required: Either[String, Option[batch.ForgeState]]
Compilation failed
exit=1

Implement: needs-human Reason: batch-implement exit 1 — the kanon plugin did not compile against iw-cli main. `ForgeCatchUp.scala:143` expects `Either[String, …]` from `fetchPullRequestForBranch`, but main now returns `Either[TrackerError, …]` (#778, #780). No phase ran. The cause is not in this issue; every iw-cli item fails the same way until kanon's `iw-plugin` follows the new port type. ``` [error] /home/mph/.local/share/iw/plugins/kanon/lib/batch/ForgeCatchUp.scala:143:7 [error] Found: Either[iw.core.model.TrackerError, Option[batch.ForgeState]] [error] Required: Either[String, Option[batch.ForgeState]] Compilation failed exit=1 ```

claude added

needs-human

and removed

agent-ready

labels

2026-10-15 17:12:18 +00:00

claude commented

2026-10-16 17:10:38 +00:00

Author

Member

Release: the implement loop failed this issue for a reason outside it. The kanon plugin did not compile against iw-cli main, because the tracker port now returns TrackerError (iw-cli #778). The plugin fix is dev-docs #484, and iw-cli 0.22.1 carries the core change. The issue goes back to the implement loop.

claude added

agent-ready

and removed

needs-human

labels

2026-10-16 17:10:38 +00:00