Fixes from the rest of the live session
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 2m13s
CI / e2e (pull_request) Successful in 3m22s

- A near miss for abandon ("abort", "cancel", "drop it", ...) in an item's
  thread is asked about, and changes nothing.
- The driver is told only the operator stops or closes an item, so it
  doesn't claim to have done either.
- An issue assigned again after its item closed starts a new item that
  notes the one before (Gitea's timeline gives the assignment time);
  item_for_issue returns the latest item.
- Abandoning an issue Gitea won't close because of open dependencies says
  so, naming them.
- An agreed item isn't offered restate.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE
This commit is contained in:
dongarandClaude Opus 5.5 committed 2026-10-08 02:16:51 +00:00
1 parent 613a2a7f72
commit 0064ec7696
9 files changed
+242 -14

No files matched your search

+7 -1
View File
@@ -400,7 +400,13 @@ class Walk:
where = f"seed {self.seed}, steps {self.steps}"
store = self.world["store"]
items = self.items()
issues = [(i.scope, loop_of(i).issue) for i in items if loop_of(i).issue]
# Open items: an issue assigned again after its item closed gets a new
# one (D1), which loop.qnt doesn't model.
issues = [
(i.scope, loop_of(i).issue)
for i in items
if loop_of(i).issue and i.status == "open"
]
assert len(issues) == len(set(issues)), f"one_item_per_issue: {where}"
for item in items:
loop = loop_of(item)