@kosuke-ai/kosuke 1.2.3619 → 1.3.3622

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/CHANGELOG.md CHANGED
@@ -1,5 +1,9 @@
1
1
  # Changelog
2
2
 
3
+ ## 1.3.3622
4
+
5
+ - `sensei messages send --file-ids` sends up to 10 workspace File ids with a teammate message; the recipient's card shows each one. A Personal File, another workspace's File, a folder, a deleted or an expired File is refused with 400 naming each, and nothing is sent.
6
+
3
7
  ## 1.2.3619
4
8
 
5
9
  - The system cron settings accept and list `weekly-card`, the Friday "Your week in Kosuke" card members can turn off like the other system crons. The app's icon set has a trophy and a flame, the icons the Overview's new Leaderboard uses for first place and merge streaks.
@@ -6,7 +6,7 @@ export const operation = {
6
6
  "messages",
7
7
  "send"
8
8
  ],
9
- "summary": "Send a message to a member's Sensei. Any sender can: you, your Sensei, a Cron Run, a session's agent, or a project's deploy agent; the sender is read from the credential. Their Sensei shows it on a card that says who sent it, with the action that fits, and they are notified as for any card. Name the project with projectId, and optionally the Chat Session (sessionId) or pull request (pullRequest, with projectId) it is about; a sessionId alone names its project. memberId is required: the id a Member mention carries or `kosuke workspaces members list` prints, never a guess between members who share a name. key is a slug such as merge-plan, ticket-<slug> or qa-guide, and text, up to 60,000 characters, is everything the member needs, so it can hold a ticket prompt or a whole Project QA Guide. title, why (one line: why this member), paths (the repository paths it is about) and link (a Sensei path starting with / or an https URL the card opens) are optional. The same key with new text or a new link updates the open card and raises the revision; the same again writes nothing. Pass ifRevision, the revision an earlier send answered, to be refused with MESSAGE_CHANGED when it moved on. When a member sent it, the recipient's approve, edit, reject or reply comes back to the thread it was sent from. Answers id, revision, updated and the recipient: say who it went to. Keys and text by kind: ticket-<slug of the title>, whose text is \"File the ticket <title> in <project>'s Backlog.\" then the reason and the description; start-<slug>, only for an unassigned or the member's own ticket while nothing of theirs builds or waits on them; delete-<slug> with its evidence; merge-<slug> with the merged text and each task's promptRevision; cron-<slug> with its prompt, crontab and projects; merge-plan with each pull request's number, head SHA and action. Before a ticket message, read the open tasks (`tasks list --include-prompt`): send nothing for work a session already covers, and name the Todo task that covers part of it in text. A 400 VALIDATION_ERROR wrote nothing: fix the fields in details and send again with the same key and memberId. Any other refusal is final: send to nobody else instead. An unknown outcome (a timeout, a 5xx) is never sent again. Pass the body with --body or --body-file.",
9
+ "summary": "Send a message to a member's Sensei. Any sender can: you, your Sensei, a Cron Run, a session's agent, or a project's deploy agent; the sender is read from the credential. Their Sensei shows it on a card that says who sent it, with the action that fits, and they are notified as for any card. Name the project with projectId, and optionally the Chat Session (sessionId) or pull request (pullRequest, with projectId) it is about; a sessionId alone names its project. memberId is required: the id a Member mention carries or `kosuke workspaces members list` prints, never a guess between members who share a name. key is a slug such as merge-plan, ticket-<slug> or qa-guide, and text, up to 60,000 characters, is everything the member needs, so it can hold a ticket prompt or a whole Project QA Guide. title, why (one line: why this member), paths (the repository paths it is about) and link (a Sensei path starting with / or an https URL the card opens) are optional. fileIds, up to ten ids of the workspace's Files (`files get <workspaceId> <fileId>`), show on the recipient's card; a file the member attached, or a Personal File they ask to send, is saved to the workspace's Files first. A Personal File id, another workspace's File, a folder or an expired File is refused with 400, naming each, and then nothing is sent. The same key with new text, link or attached Files updates the open card and raises the revision; the same again writes nothing. Pass ifRevision, the revision an earlier send answered, to be refused with MESSAGE_CHANGED when it moved on. When a member sent it, the recipient's approve, edit, reject or reply comes back to the thread it was sent from. Answers id, revision, updated and the recipient: say who it went to. Keys and text by kind: ticket-<slug of the title>, whose text is \"File the ticket <title> in <project>'s Backlog.\" then the reason and the description; start-<slug>, only for an unassigned or the member's own ticket while nothing of theirs builds or waits on them; delete-<slug> with its evidence; merge-<slug> with the merged text and each task's promptRevision; cron-<slug> with its prompt, crontab and projects; merge-plan with each pull request's number, head SHA and action. Before a ticket message, read the open tasks (`tasks list --include-prompt`): send nothing for work a session already covers, and name the Todo task that covers part of it in text. A 400 VALIDATION_ERROR wrote nothing: fix the fields in details and send again with the same key and memberId. Any other refusal is final: send to nobody else instead. An unknown outcome (a timeout, a 5xx) is never sent again. Pass the body with --body or --body-file.",
10
10
  "pathParams": [],
11
11
  "query": [],
12
12
  "body": {
@@ -82,6 +82,14 @@ export const operation = {
82
82
  "required": false,
83
83
  "description": "Where the card should open: a path inside Sensei starting with /, or an https URL."
84
84
  },
85
+ {
86
+ "name": "fileIds",
87
+ "flag": "file-ids",
88
+ "kind": "json",
89
+ "required": false,
90
+ "description": "Workspace Files to send with it, by id as `kosuke files get <workspaceId> <fileId>` shows them, up to 10: Files of the message's workspace, which the recipient's card shows. A file the member attached to their message, or a Personal File the member asks to send, is saved to the workspace's Files first (`kosuke files set <workspaceId>`) and goes by that File's id; a Personal File id itself is refused.",
91
+ "shape": "string[] (max 10)"
92
+ },
85
93
  {
86
94
  "name": "ifRevision",
87
95
  "flag": "if-revision",
package/openapi.json CHANGED
@@ -27790,7 +27790,7 @@
27790
27790
  "/api/sensei/teammate-messages": {
27791
27791
  "post": {
27792
27792
  "operationId": "senseiMessagesSend",
27793
- "summary": "Send a message to a member's Sensei. Any sender can: you, your Sensei, a Cron Run, a session's agent, or a project's deploy agent; the sender is read from the credential. Their Sensei shows it on a card that says who sent it, with the action that fits, and they are notified as for any card. Name the project with projectId, and optionally the Chat Session (sessionId) or pull request (pullRequest, with projectId) it is about; a sessionId alone names its project. memberId is required: the id a Member mention carries or `kosuke workspaces members list` prints, never a guess between members who share a name. key is a slug such as merge-plan, ticket-<slug> or qa-guide, and text, up to 60,000 characters, is everything the member needs, so it can hold a ticket prompt or a whole Project QA Guide. title, why (one line: why this member), paths (the repository paths it is about) and link (a Sensei path starting with / or an https URL the card opens) are optional. The same key with new text or a new link updates the open card and raises the revision; the same again writes nothing. Pass ifRevision, the revision an earlier send answered, to be refused with MESSAGE_CHANGED when it moved on. When a member sent it, the recipient's approve, edit, reject or reply comes back to the thread it was sent from. Answers id, revision, updated and the recipient: say who it went to. Keys and text by kind: ticket-<slug of the title>, whose text is \"File the ticket <title> in <project>'s Backlog.\" then the reason and the description; start-<slug>, only for an unassigned or the member's own ticket while nothing of theirs builds or waits on them; delete-<slug> with its evidence; merge-<slug> with the merged text and each task's promptRevision; cron-<slug> with its prompt, crontab and projects; merge-plan with each pull request's number, head SHA and action. Before a ticket message, read the open tasks (`tasks list --include-prompt`): send nothing for work a session already covers, and name the Todo task that covers part of it in text. A 400 VALIDATION_ERROR wrote nothing: fix the fields in details and send again with the same key and memberId. Any other refusal is final: send to nobody else instead. An unknown outcome (a timeout, a 5xx) is never sent again. Pass the body with --body or --body-file.",
27793
+ "summary": "Send a message to a member's Sensei. Any sender can: you, your Sensei, a Cron Run, a session's agent, or a project's deploy agent; the sender is read from the credential. Their Sensei shows it on a card that says who sent it, with the action that fits, and they are notified as for any card. Name the project with projectId, and optionally the Chat Session (sessionId) or pull request (pullRequest, with projectId) it is about; a sessionId alone names its project. memberId is required: the id a Member mention carries or `kosuke workspaces members list` prints, never a guess between members who share a name. key is a slug such as merge-plan, ticket-<slug> or qa-guide, and text, up to 60,000 characters, is everything the member needs, so it can hold a ticket prompt or a whole Project QA Guide. title, why (one line: why this member), paths (the repository paths it is about) and link (a Sensei path starting with / or an https URL the card opens) are optional. fileIds, up to ten ids of the workspace's Files (`files get <workspaceId> <fileId>`), show on the recipient's card; a file the member attached, or a Personal File they ask to send, is saved to the workspace's Files first. A Personal File id, another workspace's File, a folder or an expired File is refused with 400, naming each, and then nothing is sent. The same key with new text, link or attached Files updates the open card and raises the revision; the same again writes nothing. Pass ifRevision, the revision an earlier send answered, to be refused with MESSAGE_CHANGED when it moved on. When a member sent it, the recipient's approve, edit, reject or reply comes back to the thread it was sent from. Answers id, revision, updated and the recipient: say who it went to. Keys and text by kind: ticket-<slug of the title>, whose text is \"File the ticket <title> in <project>'s Backlog.\" then the reason and the description; start-<slug>, only for an unassigned or the member's own ticket while nothing of theirs builds or waits on them; delete-<slug> with its evidence; merge-<slug> with the merged text and each task's promptRevision; cron-<slug> with its prompt, crontab and projects; merge-plan with each pull request's number, head SHA and action. Before a ticket message, read the open tasks (`tasks list --include-prompt`): send nothing for work a session already covers, and name the Todo task that covers part of it in text. A 400 VALIDATION_ERROR wrote nothing: fix the fields in details and send again with the same key and memberId. Any other refusal is final: send to nobody else instead. An unknown outcome (a timeout, a 5xx) is never sent again. Pass the body with --body or --body-file.",
27794
27794
  "tags": ["sensei"],
27795
27795
  "x-kosuke-command": ["sensei", "messages", "send"],
27796
27796
  "x-kosuke-sandbox-token": true,
@@ -27865,6 +27865,16 @@
27865
27865
  "type": "string",
27866
27866
  "maxLength": 2000
27867
27867
  },
27868
+ "fileIds": {
27869
+ "description": "Workspace Files to send with it, by id as `kosuke files get <workspaceId> <fileId>` shows them, up to 10: Files of the message's workspace, which the recipient's card shows. A file the member attached to their message, or a Personal File the member asks to send, is saved to the workspace's Files first (`kosuke files set <workspaceId>`) and goes by that File's id; a Personal File id itself is refused.",
27870
+ "maxItems": 10,
27871
+ "type": "array",
27872
+ "items": {
27873
+ "type": "string",
27874
+ "format": "uuid",
27875
+ "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
27876
+ }
27877
+ },
27868
27878
  "ifRevision": {
27869
27879
  "description": "The revision an earlier send answered. Refused with MESSAGE_CHANGED when the message moved past it.",
27870
27880
  "type": "integer",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@kosuke-ai/kosuke",
3
- "version": "1.2.3619",
3
+ "version": "1.3.3622",
4
4
  "description": "Sensei platform CLI. The client customers install to drive app.kosuke.ai from their own machine.",
5
5
  "license": "MIT",
6
6
  "repository": {
@@ -43,10 +43,10 @@
43
43
  "minimatch": "^11.0.1"
44
44
  },
45
45
  "kosukeRelease": {
46
- "sourceCommit": "c381840338c5361257fa5083a4e87c64d66f629c",
47
- "sourceIdentity": "5defc7e10bac4c379ee5a94d26df8f10080463b9cfe1e24afac672d4dc8702ff",
46
+ "sourceCommit": "61581d4d5281500f2e0661be93622cc48fe65d9c",
47
+ "sourceIdentity": "45b50589e30588ba1961767f8cadc0883d7866a9514a99268abd162e341bc26b",
48
48
  "fragments": [
49
- "trophy-flame-icons-gz5dqd.json"
49
+ "teammate-message-attachments-b3emig.json"
50
50
  ]
51
51
  }
52
52
  }