toga-ai 1.0.171 → 1.0.172
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
|
@@ -47,7 +47,12 @@ to change the threshold. If it prints "No team sessions saved yet.", say so and
|
|
|
47
47
|
No team sessions saved yet. Save one at the end of your work: /session-save [name]
|
|
48
48
|
```
|
|
49
49
|
|
|
50
|
-
|
|
50
|
+
Whenever you render this table to the developer (in `list` mode **and** in the
|
|
51
|
+
no-argument discovery flow), explicitly disclose that delete is available — e.g. a
|
|
52
|
+
trailing line: "To retire a stale session, run `/session-resume delete <id>`." A
|
|
53
|
+
developer must never have to already know the command to discover it.
|
|
54
|
+
|
|
55
|
+
**`list` mode:** render this table (with the delete disclosure) and stop here.
|
|
51
56
|
|
|
52
57
|
**`delete <id>` mode:** confirm with the developer, then run
|
|
53
58
|
`node "<TEAM_REPO>/knowledge.js" session-delete <id> --msg="session: retire <id>"`,
|
|
@@ -61,7 +66,8 @@ report the `SESSION: DELETED|NOT_FOUND|CONFLICT` result, and stop.
|
|
|
61
66
|
- `<slug-or-id>` → the row whose id equals it or contains the slug. If several match
|
|
62
67
|
(same slug, different authors/dates), show those candidates (date + author) and ask which.
|
|
63
68
|
- If none match: "No session found matching '<x>'. Available: [list ids]."
|
|
64
|
-
- No argument → ask: "Which session should I load? (id or slug
|
|
69
|
+
- No argument → ask: "Which session should I load? (id or slug — or `delete <id>` to
|
|
70
|
+
retire a stale one)"
|
|
65
71
|
|
|
66
72
|
---
|
|
67
73
|
|