The dashboard routes review-state cards with its own copy of the card-location rule #773

New issue

Open

opened 2026-10-08 08:34:30 +00:00 by claude · 3 comments

claude commented

2026-10-08 08:34:30 +00:00

Member

The dashboard routes cards with its own copy of the rule — dashboard/jvm/src/application/ReviewStateService.scala resolveStatePath (:158-191); decide whether it should call ReviewStateLocation.cardLocations (it hides error text and reads the pointer with its own function). Found in IW-712 analysis, decision 6.

- [ ] The dashboard routes cards with its own copy of the rule — `dashboard/jvm/src/application/ReviewStateService.scala` `resolveStatePath` (:158-191); decide whether it should call `ReviewStateLocation.cardLocations` (it hides error text and reads the pointer with its own function). Found in IW-712 analysis, decision 6.

mph referenced this issue from a commit

2026-10-08 08:36:37 +00:00

chore(IW-712): file follow-ups to the tracker

claude referenced this issue

2026-10-08 08:36:48 +00:00

IW-712: review-state card location: route on the key kind, report pointer read errors, keep the routing pure #774

claude commented

2026-10-10 19:16:56 +00:00

Author

Member

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

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

claude added the

agent-ready

label

2026-10-10 19:16:56 +00:00

claude commented

2026-10-15 17:26:32 +00:00

Author

Member

Implement: needs-human
Reason: batch-implement exit 1 — the kanon plugin did not compile against the iw-cli core of the current main, so no phase ran

The core forge calls now return TrackerError (#778, #780). The installed kanon plugin (lib/batch/ForgeCatchUp.scala:143) still expects String. This is not specific to this issue: every issue on a branch with the current main stops at the same place until the plugin follows the core change. No batch-implement.log was written; these are the last lines of the command output:

[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

Implement: needs-human Reason: batch-implement exit 1 — the kanon plugin did not compile against the iw-cli core of the current main, so no phase ran The core forge calls now return `TrackerError` (#778, #780). The installed kanon plugin (`lib/batch/ForgeCatchUp.scala:143`) still expects `String`. This is not specific to this issue: every issue on a branch with the current main stops at the same place until the plugin follows the core change. No `batch-implement.log` was written; these are the last lines of the command output: ``` [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 ```

claude added

needs-human

and removed

agent-ready

labels

2026-10-15 17:26:32 +00:00

claude commented

2026-10-16 17:10:44 +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:44 +00:00