agent-transport-system 0.7.29 → 0.7.30

package/dist/ats.js

@@ -27,7 +27,7 @@ import wrapAnsi from "wrap-ansi";
 import { Box, Container, Editor, Key, ProcessTerminal, TUI, Text, getEditorKeybindings, matchesKey } from "@mariozechner/pi-tui";
 
 //#region package.json
-var version = "0.7.29";
+var version = "0.7.30";
 var package_default = {
 	$schema: "https://www.schemastore.org/package.json",
 	name: "agent-transport-system",
@@ -37674,7 +37674,7 @@ function buildDispatchPromptWithBootstrap(input) {
 	const sections = [];
 	if (input.shouldInjectBootstrap && isEntryBriefEnabled(input)) sections.push(renderEntryBriefSection(input));
 	if ((input.spaceContractSnapshot?.dispatchBrief ?? "default") !== "none") sections.push(renderDispatchBriefSection(input));
-	sections.push(["Current message:", prompt].join("\n"));
+	sections.push(["Current Wake message:", prompt].join("\n"));
 	return sections.filter(Boolean).join("\n\n");
 }
 function buildDispatchBootstrapTemplateFacts(input) {
@@ -37787,6 +37787,7 @@ function buildActionGuidanceLines(input) {
 		spaceId: input.spaceId
 	})}\`.`);
 	if (input.threadContext) lines.push("- This dispatch belongs to a thread. Public replies should stay in that thread unless explicitly asked to reply in the main Space.");
+	lines.push("- Source alignment: Treat this Wake message as the current source. If you use other Space messages, private context, memory, or tools, keep each source mapped to the action and reply it supports.", "- Delivery intent: If the user asks you to deliver work to another Agent Profile, use Handoff or Reply + handoff. A plain reply or a bare @name does not deliver executable work.", "- Reply placement: Reply where the current request should continue. Thread Wakes default to the current thread; only move the reply when the user explicitly asks.", "- Context sources: ATS metadata is infrastructure context, not proof of what a human or agent is doing. Use Space context, private context, memory, and tools when appropriate; avoid exposing secrets, credentials, private files, or high-risk sensitive data unless the owner clearly authorizes it.");
 	lines.push("- If the current message mentions multiple targets, handle only the part assigned to you unless it explicitly asks you to synthesize for the group.");
 	lines.push("- Wake asks another Agent Profile to act. Reference and CC are context only. Bare @names in prose do not create executable work.", "- For a normal reply to this Wake, do not add target flags. Use target flags only when this Wake asks you to hand off, reference, or CC another profile.");
 	lines.push(`- Need action details? Run \`${buildSpaceActionCommand(input, "help")}\`. Only if every Space Action command fails, use \`${buildPromptSpaceActionCommand(input)}\` for fallback JSON.`);
@@ -41793,10 +41794,12 @@ function buildStructuredActionRepairPrompt(input) {
 			previousOutput,
 			"```"
 		] : [],
+		"This is a bounded repair of the public delivery action only. Do not redo the user's work.",
 		"Do not change the user's intent.",
+		"Preserve source alignment: keep the corrected action tied to the same current Wake and reply target.",
+		"If the user's intent was to make another Agent Profile act, use Wake or Reply + handoff target semantics. A plain reply or bare @name is not executable delivery.",
 		"ATS only consumes your final answer and at most one valid trailing ```ats-space-action``` JSON block.",
 		"If an ATS Space Action CLI command is available, run that command instead of printing fallback JSON.",
-		"Return the corrected final answer again.",
 		publicationRequirement.repairRequirementLine,
 		...SPACE_ACTION_TARGET_GUIDANCE_LINES,
 		...normalizeOptionalText$49(input.currentReplyToSignalId) ? [`post_message.messageEnvelope.replyToSignalId must match the current dispatch reply target: ${normalizeOptionalText$49(input.currentReplyToSignalId)}.`] : [],
@@ -84604,6 +84607,7 @@ const PROMPT_GUIDE_CATALOG = {
 				"Use `reply` for the normal final answer.",
 				"Use `wake` or `reply --wake` only when handing off work to another Agent Profile.",
 				"Use `--reference` or `--cc` when another profile should be mentioned for context but should not start work.",
+				"Keep each reply aligned to the source message it answers. If you use other Space messages, private context, memory, or tools, make sure the visible outcome still maps to the right source.",
 				"Use `status` only for final-safe status outcomes, not ongoing progress.",
 				"Use `ats-space-action` structured blocks only as a fallback when the CLI action command is unavailable."
 			],
@@ -84621,7 +84625,9 @@ const PROMPT_GUIDE_CATALOG = {
 				"`<DISPATCH_ACTION_CLI>` is a placeholder in guides, not a literal command.",
 				"Fallback JSON is last resort: only if every Space Action CLI command fails, run `ats prompt space-action --raw` and use one trailing `ats-space-action` block.",
 				"Wake targets must be Agent Profiles available for Wake in the current Space.",
+				"If a user asks you to deliver work to another Agent Profile, a plain reply is not enough; use `wake` or `reply --wake` so executable work is created.",
 				"Bare @names in prose are not execution targets in the agent path; use target flags for Wake, Reference, or CC semantics.",
+				"ATS metadata is infrastructure context, not proof of what a human or agent is doing. Use Space context, private context, memory, and tools when appropriate; avoid exposing secrets, credentials, private files, or high-risk sensitive data unless the owner clearly authorizes it.",
 				"`working` is not accepted here because status actions are final visible outcomes in the current contract."
 			]
 		}