Dashboard card loses information after HTMX refresh #197
Labels
No labels
agent-ready
bug
contract
documentation
duplicate
enhancement
good first issue
help wanted
invalid
needs-human
needs-input
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
iterative-works/iw-cli#197
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
After an HTMX polling refresh, the worktree card loses some information that was present on the initial page load — notably the git worktree state. The card appears to use a different (or incomplete) rendering path for the refreshed content compared to the initial render.
Expected Behavior
The card should display identical information before and after refresh. All data visible on initial load (including git worktree state) must also appear in the HTMX-refreshed fragment.
Investigation Needed
Intake: agent-ready
Workflow: diagnostic
Reason: all gates passed
Analysis: project-management/issues/IW-197/analysis.md on branch IW-197
Implement: needs-human
Reason: batch-implement exit 1 — the kanon plugin does not compile against the iw-cli core on this branch, so no phase started
iw-cli
mainchanged the tracker port to returnTrackerError(#778, #780). The installed kanon plugin still expectsStringinlib/batch/ForgeCatchUp.scala. This blocks every implement run in iw-cli, not only this issue. Update the kanon plugin to theTrackerErrorport, then release this issue toagent-readyagain. There was nobatch-implement.log; these are the last lines of the command output: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.