omp-conductor 0.3.21 → 0.3.22
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "omp-conductor",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.22",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"description": "A 24/7 dispatcher that takes ready GitHub issues to green, mergeable PRs using omp coding sessions, with tiered escalation first to an orchestrator session and then to a human.",
|
|
@@ -151,6 +151,13 @@ actually asked, in one message, from evidence you already hold or go and fetch.
|
|
|
151
151
|
Then stop. Do not continue loop narration in the same reply, and do not restate
|
|
152
152
|
in-progress work unless they asked for it. The loop resumes on the next tick.
|
|
153
153
|
|
|
154
|
+
A message may also reach you **mid-tick** (delivery is steering: it arrives
|
|
155
|
+
between two of your tool calls). Treat it as an interrupt, not a new tick:
|
|
156
|
+
answer it immediately with `telegram_send` in one message, then return to the
|
|
157
|
+
duty you were in the middle of and finish it. Never abandon or restart the tick
|
|
158
|
+
because a message arrived, and never batch the answer "for the report" — the
|
|
159
|
+
person is waiting now.
|
|
160
|
+
|
|
154
161
|
## Escalation tiers
|
|
155
162
|
|
|
156
163
|
| Tier | Meaning | Handled by |
|