@researai/deepscientist 1.5.5 → 1.5.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@researai/deepscientist",
-  "version": "1.5.5",
+  "version": "1.5.6",
   "description": "Local-first research operating system with a Python runtime and npm launcher",
   "license": "MIT",
   "files": [

package/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "deepscientist"
-version = "1.5.5"
+version = "1.5.6"
 description = "DeepScientist Core skeleton"
 readme = "README.md"
 requires-python = ">=3.11"

package/src/deepscientist/__init__.py

@@ -5,4 +5,4 @@ __all__ = ["__version__"]
 try:
     __version__ = _package_version("deepscientist")
 except PackageNotFoundError:  # pragma: no cover - source checkout fallback
-    __version__ = "1.5.5"
+    __version__ = "1.5.6"

package/src/deepscientist/prompts/builder.py

@@ -745,7 +745,7 @@ class PromptBuilder:
             "- response_pattern: say what changed -> say what it means -> say what happens next",
             "- interaction_protocol: first message may be plain conversation; after that, treat artifact.interact threads and mailbox polls as the main continuity spine across TUI, web, and connectors",
             "- mailbox_protocol: artifact.interact(include_recent_inbound_messages=True) is the queued human-message mailbox; when it returns user text, treat that input as higher priority than background subtasks until it has been acknowledged",
-            "- acknowledgment_protocol: after artifact.interact returns any human message, immediately call artifact.interact(...) again to confirm receipt; if answerable, answer directly, otherwise state the short plan, nearest checkpoint, and that the current background subtask is paused",
+            "- acknowledgment_protocol: after artifact.interact returns any human message, immediately send one substantive artifact.interact(...) follow-up; if the active connector runtime already emitted a transport-level receipt acknowledgement, do not send a redundant receipt-only message; if answerable, answer directly, otherwise state the short plan, nearest checkpoint, and that the current background subtask is paused",
             "- progress_protocol: emit artifact.interact(kind='progress', reply_mode='threaded', ...) at real human-meaningful checkpoints; if no natural checkpoint appears during active user-relevant work, send a concise keepalive before you drift beyond roughly 10 to 30 tool calls without a user-visible update",
             "- smoke_then_detach_protocol: for baseline reproduction, main experiments, and analysis experiments, first validate the command path with a bounded smoke test; once the smoke test passes, launch the real long run with bash_exec(mode='detach', ...) and usually leave timeout_seconds unset rather than guessing a fake deadline",
             "- progress_first_monitoring_protocol: when supervising a long-running bash_exec session, judge health by forward progress rather than by whether the final artifact has already appeared within a short window",

package/src/deepscientist/quest/service.py

@@ -2813,8 +2813,8 @@ class QuestService:
                 ),
                 self.localized_copy(
                     quest_root=quest_root,
-                    zh="- 立即再调用一次 artifact.interact(...)，明确告知你已经收到这些用户消息。",
-                    en="- Immediately call artifact.interact(...) again to confirm that you received these user messages.",
+                    zh="- 立即发送一条有实际内容的 follow-up artifact.interact(...)；如果当前 connector 的运行时已经替你发过即时回执，就不要再重复发送一条只有“已收到/处理中”的确认。",
+                    en="- Immediately send one substantive follow-up artifact.interact(...); if the active connector runtime already sent the transport-level receipt acknowledgement, do not send a redundant receipt-only message such as 'received' or 'processing'.",
                 ),
                 self.localized_copy(
                     quest_root=quest_root,

package/src/prompts/connectors/qq.md

@@ -3,6 +3,8 @@
 - connector_contract_id: qq
 - connector_contract_scope: loaded only when QQ is the active or bound external connector for this quest
 - connector_contract_goal: use `artifact.interact(...)` as the main durable user-visible thread on QQ instead of exposing raw internal runner or tool chatter
+- qq_runtime_ack_rule: the QQ bridge itself emits the immediate transport-level receipt acknowledgement before the model turn starts
+- qq_no_duplicate_ack_rule: do not waste your first model response or first `artifact.interact(...)` call on a redundant receipt-only acknowledgement such as "received", "已收到", or "I am processing" when the bridge already sent that
 - qq_reply_style: keep QQ replies concise, milestone-first, respectful, and easy to scan on a phone
 - qq_reply_length_rule: for ordinary QQ progress updates, normally use only 2 to 4 short sentences, or 3 short bullets at most
 - qq_summary_first_rule: start with the conclusion the user cares about, then what it means, then the next action
@@ -16,6 +18,7 @@
 - qq_default_text_rule: plain text is the default and safest QQ mode
 - qq_absolute_path_rule: when you request native QQ image or file delivery via an attachment `path`, prefer an absolute path
 - qq_failure_rule: if `artifact.interact(...)` returns `attachment_issues` or `delivery_results` errors, treat that as a real delivery failure and adapt before assuming the user received the media
+- qq_first_followup_rule: after a new inbound QQ message, your first substantive follow-up should either answer directly or give the first meaningful checkpoint and next action, not a second bare acknowledgement
 
 ## QQ Runtime Capabilities
 

package/src/prompts/system.md

@@ -1027,7 +1027,8 @@ For `artifact.interact(...)` specifically:
 - ordinary user-facing progress updates should read like a short collaborator message, not like a monitoring transcript, execution diary, or internal postmortem
 - when `artifact.interact(...)` returns queued user requirements, treat that mailbox payload as the latest user instruction bundle
 - if queued user requirements were returned, treat them as higher priority than the current background subtask until you have acknowledged them
-- immediately follow a non-empty mailbox poll with another `artifact.interact(...)` update that confirms receipt
+- immediately follow a non-empty mailbox poll with one substantive `artifact.interact(...)` follow-up update
+  - if the active connector runtime already emitted a transport-level receipt acknowledgement before your turn, do not send a redundant receipt-only update such as "received" or "processing"
   - if the request is directly answerable, answer it in that immediate follow-up update
   - otherwise say the current subtask is being paused, give a short execution plan plus nearest report-back point, then complete the user request first
 - after completing that interrupting user request, send another `artifact.interact(...)` update with the full result before resuming older work

package/src/tui/package.json

@@ -1,6 +1,6 @@
 {
   "name": "deepscientist-tui",
-  "version": "1.5.5",
+  "version": "1.5.6",
   "private": true,
   "type": "module",
   "main": "dist/index.js",