Repository navigation
fix: list a run hmz exec holds as going in hmz web and /epics - #370
Merged
Merged
Conversation
A run another process holds -- `hmz exec`, which no host speaks for -- was listed as `unfinished` in `hmz web` and as `was left unfinished` on `/epics` for as long as it ran, as though it had been killed. The runtime already knew: a run holds its epic's `.held` lock while it goes. `going()` now says so in public, `Epics.going` beside it, and both interfaces read it: the web says such a run is `running` and offers no Resume or Export of it, and `/epics` says it `is still going`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
futrime
force-pushed
the
fix/exec-runs-going
branch
from
October 12, 2026 15:03
14204a9 to
7d77c92
Compare
futrime
enabled auto-merge
October 12, 2026 15:07
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Found in release acceptance of
main@d7f732e9: whilehmz execruns an epic,hmz weblisted it as○ unfinishedwith 0 sessions (/api/runssaid"how": "unfinished"), and the terminal interface's/epicssaidwas left unfinished— the words for a run killed where it stood.specs/web.mdrequires each run be shown as "how each ended or that it is going".The runtime already knew: a run holds an exclusive
flockon its epic's.heldwhile it goes, and_going()read it — but only to refuse--resume.Changes
hmz.runtime.epic.going()(was_going) andEpics.going(): whether an epic's run is held now, by this process or another.hmz web: a run going readsrunningwhether a host holds it (held, followed live and stoppable) or another process does; the menus offer no Resume or Export of it./epics: such a run readsis still going.goingadded to the API listings inspecs/runtime/SPEC.mdandspecs/runtime/doing.md— the fix needs it public, so the listing is changed to match (one line each).docs/reference/tui.md(which documented the old behaviour),docs/reference/web.md,docs/user/web.md.Tests
going()andEpics.going()true while held and false after;row()saysrunningfor a run going but not held./api/runsand/api/runs/<name>sayrunningfor an epic another holder keeps open,doneonce it ends;/epicssaysis still going. Both integration tests fail without the fix.🤖 Generated with Claude Code