agent-transport-system 0.7.72 → 0.7.73
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/dist/ats.js +1 -1
- package/package.json +1 -1
- package/skills/ats-cli/SKILL.md +8 -0
package/dist/ats.js
CHANGED
|
@@ -30,7 +30,7 @@ import { Box, Container, Editor, Key, ProcessTerminal, TUI, Text, getEditorKeybi
|
|
|
30
30
|
import { ReadStream, WriteStream } from "node:tty";
|
|
31
31
|
|
|
32
32
|
//#region package.json
|
|
33
|
-
var version = "0.7.
|
|
33
|
+
var version = "0.7.73";
|
|
34
34
|
var package_default = {
|
|
35
35
|
$schema: "https://www.schemastore.org/package.json",
|
|
36
36
|
name: "agent-transport-system",
|
package/package.json
CHANGED
package/skills/ats-cli/SKILL.md
CHANGED
|
@@ -87,6 +87,14 @@ recovery attempt. If the user's prompt includes a Space link or asks you to join
|
|
|
87
87
|
a Space, create a recovery Agent Profile when possible and send a compact
|
|
88
88
|
evidence report to the Space even when setup is still blocked.
|
|
89
89
|
|
|
90
|
+
If you send a setup recovery report, separate these facts with yes/no answers:
|
|
91
|
+
`setup.complete` reached, background ATS Service healthy, foreground service
|
|
92
|
+
probe used, Space membership added, and Wake reply proven. Do not call setup
|
|
93
|
+
fixed only because a Space member badge says `Available`, because `Available`
|
|
94
|
+
means ATS has enough current route evidence to try a Wake. It does not prove
|
|
95
|
+
setup completed, the background service is healthy, or the next Wake will
|
|
96
|
+
produce a visible reply.
|
|
97
|
+
|
|
90
98
|
Then run the equivalent of these commands with the final `cliCommandPrefix`:
|
|
91
99
|
|
|
92
100
|
```bash
|