dkitchen 0.2.0__tar.gz → 0.2.2__tar.gz

{dkitchen-0.2.0/src/dkitchen.egg-info → dkitchen-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dkitchen
-Version: 0.2.0
+Version: 0.2.2
 Summary: A multi-agent workflow for research repos, with the ding CLI for messaging and waking agent sessions
 Author: 917Dhj
 License-Expression: MIT
@@ -30,11 +30,27 @@ Provides-Extra: dev
 Requires-Dist: pytest>=8; extra == "dev"
 Dynamic: license-file
 
-# dkitchen
+<p align="center">
+  <img src="https://raw.githubusercontent.com/917Dhj/dkitchen/main/docs/assets/dkitchen.png" width="240" alt="Two pixel-art robot chefs: the big one rings a service bell, the small one answers with a pan">
+</p>
 
-**English** | [简体中文](https://github.com/917Dhj/dkitchen/blob/main/README.zh-CN.md)
+<h1 align="center">dkitchen</h1>
 
-**You decide what to cook. Your agents run the kitchen.** 🧑‍🍳
+<p align="center">
+  <b>English</b> | <a href="https://github.com/917Dhj/dkitchen/blob/main/README.zh-CN.md">简体中文</a>
+</p>
+
+<p align="center">
+  <b>You decide what to cook. Your agents run the kitchen.</b> 🧑‍🍳
+</p>
+
+<p align="center">
+  <a href="https://pypi.org/project/dkitchen/"><img src="https://img.shields.io/pypi/v/dkitchen" alt="PyPI"></a>
+  <a href="https://pypi.org/project/dkitchen/"><img src="https://img.shields.io/pypi/pyversions/dkitchen" alt="Python"></a>
+  <a href="https://github.com/917Dhj/dkitchen/actions/workflows/tests.yml"><img src="https://github.com/917Dhj/dkitchen/actions/workflows/tests.yml/badge.svg" alt="Tests"></a>
+  <a href="https://github.com/917Dhj/dkitchen/blob/main/LICENSE"><img src="https://img.shields.io/github/license/917Dhj/dkitchen" alt="License"></a>
+  <a href="https://x.com/dahuoji09"><img src="https://img.shields.io/badge/follow-%40dahuoji09-000000?logo=x" alt="X: @dahuoji09"></a>
+</p>
 
 dkitchen is the multi-agent workflow I use every day to run my research repo. It gives a set of Claude Code and Codex sessions fixed stations, a shared way to hand off work through GitHub issues, clear rules for when to stop and ask you, and the tools that tie it together. You keep the decisions only you can make: what to research, what to try, what to spend.
 
@@ -50,6 +66,10 @@ dkitchen sets up your agents the same way. You are the head chef.
 
 ## 🧑‍🍳 The kitchen
 
+<p align="center">
+  <img src="https://raw.githubusercontent.com/917Dhj/dkitchen/main/docs/assets/kitchen.gif" width="100%" alt="A pixel-art kitchen: you talk a design through with the designer, the verifier checks the ticket, the orchestrator rings the bell to start a Codex executor on free GPUs, reviews and merges a PR, and brings you one decision to approve">
+</p>
+
 | Station | In a kitchen | What it does | Runs on |
 | --- | --- | --- | --- |
 | 👑 **You** | Head chef | Choose the direction, approve designs and budgets, decide what the results mean for your paper. | You |

{dkitchen-0.2.0 → dkitchen-0.2.2}/README.md

@@ -1,8 +1,24 @@
-# dkitchen
+<p align="center">
+  <img src="https://raw.githubusercontent.com/917Dhj/dkitchen/main/docs/assets/dkitchen.png" width="240" alt="Two pixel-art robot chefs: the big one rings a service bell, the small one answers with a pan">
+</p>
 
-**English** | [简体中文](https://github.com/917Dhj/dkitchen/blob/main/README.zh-CN.md)
+<h1 align="center">dkitchen</h1>
 
-**You decide what to cook. Your agents run the kitchen.** 🧑‍🍳
+<p align="center">
+  <b>English</b> | <a href="https://github.com/917Dhj/dkitchen/blob/main/README.zh-CN.md">简体中文</a>
+</p>
+
+<p align="center">
+  <b>You decide what to cook. Your agents run the kitchen.</b> 🧑‍🍳
+</p>
+
+<p align="center">
+  <a href="https://pypi.org/project/dkitchen/"><img src="https://img.shields.io/pypi/v/dkitchen" alt="PyPI"></a>
+  <a href="https://pypi.org/project/dkitchen/"><img src="https://img.shields.io/pypi/pyversions/dkitchen" alt="Python"></a>
+  <a href="https://github.com/917Dhj/dkitchen/actions/workflows/tests.yml"><img src="https://github.com/917Dhj/dkitchen/actions/workflows/tests.yml/badge.svg" alt="Tests"></a>
+  <a href="https://github.com/917Dhj/dkitchen/blob/main/LICENSE"><img src="https://img.shields.io/github/license/917Dhj/dkitchen" alt="License"></a>
+  <a href="https://x.com/dahuoji09"><img src="https://img.shields.io/badge/follow-%40dahuoji09-000000?logo=x" alt="X: @dahuoji09"></a>
+</p>
 
 dkitchen is the multi-agent workflow I use every day to run my research repo. It gives a set of Claude Code and Codex sessions fixed stations, a shared way to hand off work through GitHub issues, clear rules for when to stop and ask you, and the tools that tie it together. You keep the decisions only you can make: what to research, what to try, what to spend.
 
@@ -18,6 +34,10 @@ dkitchen sets up your agents the same way. You are the head chef.
 
 ## 🧑‍🍳 The kitchen
 
+<p align="center">
+  <img src="https://raw.githubusercontent.com/917Dhj/dkitchen/main/docs/assets/kitchen.gif" width="100%" alt="A pixel-art kitchen: you talk a design through with the designer, the verifier checks the ticket, the orchestrator rings the bell to start a Codex executor on free GPUs, reviews and merges a PR, and brings you one decision to approve">
+</p>
+
 | Station | In a kitchen | What it does | Runs on |
 | --- | --- | --- | --- |
 | 👑 **You** | Head chef | Choose the direction, approve designs and budgets, decide what the results mean for your paper. | You |

{dkitchen-0.2.0 → dkitchen-0.2.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "dkitchen"
-version = "0.2.0"
+version = "0.2.2"
 description = "A multi-agent workflow for research repos, with the ding CLI for messaging and waking agent sessions"
 readme = "README.md"
 requires-python = ">=3.10"

{dkitchen-0.2.0 → dkitchen-0.2.2}/src/dkitchen/watch.py

@@ -6,7 +6,8 @@ Wakes on:
 - status labels being added, and newly opened PRs;
 - stale tickets: no status label, last comment an executor "in progress" older than --stale-hours,
   no running `ding run` for the ticket, and no live tmux job whose session name holds issue<N>.
-On tickets labelled awaiting-user, executor comments wake only for blocked, done, and waiting on design.
+On tickets labelled awaiting-user, executor comments wake only for blocked, done, and waiting on design,
+or when their "waiting on" names the orchestrator, designer, or verifier.
 Verifier comments never wake on their own, since the verifier also messages the orchestrator;
 they are listed in the next batch for reference.
 The state file keeps the time already reported, so rerunning the same command loses nothing.
@@ -61,14 +62,16 @@ def issue_number(url: str) -> int:
 
 
 def role(body: str, config: Config) -> str:
-    """The executor by its session line; otherwise the station named at the start of the first line; else the user."""
+    """The station named at the start of the first line; otherwise the executor by a line starting with its
+    session signature; else the user. A session signature quoted inside a line signs nothing."""
     stations = config.stations
-    if "Codex session:" in body:
-        return stations.executor
     first = next((line for line in body.splitlines() if line.strip()), "")
     first = re.sub(r"^[\s#*>]+", "", first)
-    return next((name for name in (stations.designer, stations.verifier, stations.orchestrator)
-                 if first.startswith(name)), stations.user)
+    signed = next((name for name in (stations.designer, stations.verifier, stations.orchestrator)
+                   if first.startswith(name)), None)
+    if signed:
+        return signed
+    return stations.executor if re.search(r"(?m)^[ \t]*Codex session:", body) else stations.user
 
 
 def fields(body: str, config: Config) -> dict[str, str]:
@@ -85,10 +88,11 @@ def state_and_waiting(body: str, config: Config) -> tuple[str, str]:
 def executor_wakes(body: str, waiting_user: bool, config: Config) -> bool:
     state, waiting = state_and_waiting(body, config)
     status, stations = config.status, config.stations
+    names = lambda *who: not waiting.startswith(status.none) and any(name in waiting for name in who)
+    kitchen = (stations.orchestrator, stations.designer, stations.verifier)
     if waiting_user:
-        return state in {status.blocked, status.done, status.waiting_on_design}
-    names = (stations.orchestrator, stations.designer, stations.verifier, stations.user)
-    return state != status.in_progress or (not waiting.startswith(status.none) and any(name in waiting for name in names))
+        return state in {status.blocked, status.done, status.waiting_on_design} or names(*kitchen)
+    return state != status.in_progress or names(*kitchen, stations.user)
 
 
 def summary(body: str, config: Config) -> str:

{dkitchen-0.2.0 → dkitchen-0.2.2/src/dkitchen.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dkitchen
-Version: 0.2.0
+Version: 0.2.2
 Summary: A multi-agent workflow for research repos, with the ding CLI for messaging and waking agent sessions
 Author: 917Dhj
 License-Expression: MIT
@@ -30,11 +30,27 @@ Provides-Extra: dev
 Requires-Dist: pytest>=8; extra == "dev"
 Dynamic: license-file
 
-# dkitchen
+<p align="center">
+  <img src="https://raw.githubusercontent.com/917Dhj/dkitchen/main/docs/assets/dkitchen.png" width="240" alt="Two pixel-art robot chefs: the big one rings a service bell, the small one answers with a pan">
+</p>
 
-**English** | [简体中文](https://github.com/917Dhj/dkitchen/blob/main/README.zh-CN.md)
+<h1 align="center">dkitchen</h1>
 
-**You decide what to cook. Your agents run the kitchen.** 🧑‍🍳
+<p align="center">
+  <b>English</b> | <a href="https://github.com/917Dhj/dkitchen/blob/main/README.zh-CN.md">简体中文</a>
+</p>
+
+<p align="center">
+  <b>You decide what to cook. Your agents run the kitchen.</b> 🧑‍🍳
+</p>
+
+<p align="center">
+  <a href="https://pypi.org/project/dkitchen/"><img src="https://img.shields.io/pypi/v/dkitchen" alt="PyPI"></a>
+  <a href="https://pypi.org/project/dkitchen/"><img src="https://img.shields.io/pypi/pyversions/dkitchen" alt="Python"></a>
+  <a href="https://github.com/917Dhj/dkitchen/actions/workflows/tests.yml"><img src="https://github.com/917Dhj/dkitchen/actions/workflows/tests.yml/badge.svg" alt="Tests"></a>
+  <a href="https://github.com/917Dhj/dkitchen/blob/main/LICENSE"><img src="https://img.shields.io/github/license/917Dhj/dkitchen" alt="License"></a>
+  <a href="https://x.com/dahuoji09"><img src="https://img.shields.io/badge/follow-%40dahuoji09-000000?logo=x" alt="X: @dahuoji09"></a>
+</p>
 
 dkitchen is the multi-agent workflow I use every day to run my research repo. It gives a set of Claude Code and Codex sessions fixed stations, a shared way to hand off work through GitHub issues, clear rules for when to stop and ask you, and the tools that tie it together. You keep the decisions only you can make: what to research, what to try, what to spend.
 
@@ -50,6 +66,10 @@ dkitchen sets up your agents the same way. You are the head chef.
 
 ## 🧑‍🍳 The kitchen
 
+<p align="center">
+  <img src="https://raw.githubusercontent.com/917Dhj/dkitchen/main/docs/assets/kitchen.gif" width="100%" alt="A pixel-art kitchen: you talk a design through with the designer, the verifier checks the ticket, the orchestrator rings the bell to start a Codex executor on free GPUs, reviews and merges a PR, and brings you one decision to approve">
+</p>
+
 | Station | In a kitchen | What it does | Runs on |
 | --- | --- | --- | --- |
 | 👑 **You** | Head chef | Choose the direction, approve designs and budgets, decide what the results mean for your paper. | You |

{dkitchen-0.2.0 → dkitchen-0.2.2}/tests/test_kitchen.py

@@ -206,6 +206,8 @@ def executor(block):
     ("Status: in progress\nWaiting on: Designer, for the prompt\nKey numbers: 1\nNext: wait", False, True),
     ("Status: done\nWaiting on: none\nKey numbers: 1\nNext: merge", False, True),
     ("Status: waiting on user\nWaiting on: User\nKey numbers: 1\nNext: wait", True, False),
+    ("Status: waiting on user\nWaiting on: User to approve; Orchestrator to merge PR #3\nKey numbers: 1\nNext: merge",
+     True, True),
     ("Status: blocked\nWaiting on: none\nKey numbers: 1\nNext: fix", True, True),
 ])
 def test_executor_comments_wake_by_status_and_waiting_on(tmp_path, block, waiting_user, wakes):
@@ -222,6 +224,14 @@ def test_chinese_status_words_and_full_width_colons(tmp_path):
     assert not watch.executor_wakes(executor("状态: 进行中\n在等: 无\n关键数字: 1\n下一步: 跑"), False, loaded)
 
 
+def test_an_awaiting_user_ticket_wakes_when_the_comment_also_waits_on_the_kitchen(tmp_path):
+    # #209 issuecomment-6179869282: still waiting on the user, but also asking the orchestrator to merge
+    loaded = settings(tmp_path, CHINESE)
+    body = executor("状态: 等用户\n在等: 用户批准说话人 1,329 次单次作答；总编排重审合入 PR #314\n关键数字: 0\n下一步: 合入")
+    assert watch.executor_wakes(body, True, loaded)
+    assert not watch.executor_wakes(executor("状态: 等用户\n在等: 用户批准\n关键数字: 0\n下一步: 等"), True, loaded)
+
+
 @pytest.fixture
 def tree(tmp_path):
     (tmp_path / "pkg").mkdir()
@@ -279,3 +289,14 @@ def test_log_issue_must_be_positive(capsys):
     with pytest.raises(SystemExit) as exc:
         ding.main(["log", "--item", "a", "--issue", "0"])
     assert exc.value.code == 2
+
+
+@pytest.mark.parametrize("text", [None, CHINESE])
+def test_a_quoted_session_signature_signs_nothing(tmp_path, text):
+    loaded = settings(tmp_path, text)
+    stations = loaded.stations
+    verifier = (f"## {stations.verifier}{stations.separator}#272 run request check\n\n"
+                "| request body | ok: it starts with the status block and contains `Codex session:` |\n")
+    assert watch.role(verifier, loaded) == stations.verifier
+    assert watch.role("I checked it; the body has `Codex session:` in it.", loaded) == stations.user
+    assert watch.role(executor("Status: done\nWaiting on: none\nKey numbers: 1\nNext: merge"), loaded) == stations.executor