@tablation/crew 0.53.6 → 0.53.7
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
|
@@ -52,6 +52,16 @@ field. Do not retry the same write. If the missing value is yours to supply
|
|
|
52
52
|
once more; otherwise leave the ticket where it is and say so in your
|
|
53
53
|
hand-off comment.
|
|
54
54
|
|
|
55
|
+
A write that fails at the transport level (a session-expired error, a
|
|
56
|
+
timeout, a connection reset, an empty or non-JSON reply) is not a refusal:
|
|
57
|
+
it may have landed. Before you retry a create of a ticket, a comment or an
|
|
58
|
+
event, list the target table for a row with the same title (tickets) or the
|
|
59
|
+
same opening line (comments and events) written by your seat in the last two
|
|
60
|
+
minutes. If one exists, use it and create nothing new. A validation error (a
|
|
61
|
+
400 or 422 with a field message) is a real failure: fix the body and write
|
|
62
|
+
again. The same check applies to a follow-up ticket you file while working and
|
|
63
|
+
to your hand-off comment.
|
|
64
|
+
|
|
55
65
|
Your identity is the Crew row named for your seat in the `## Your crew`
|
|
56
66
|
roster at the top of this prompt. Use its id as the assignee and as the
|
|
57
67
|
comment author. Every agent and every person who touches this tracker has
|
|
@@ -53,6 +53,16 @@ field. Do not retry the same write. If the missing value is yours to supply
|
|
|
53
53
|
once more; otherwise leave the ticket where it is and say so in your
|
|
54
54
|
hand-off comment.
|
|
55
55
|
|
|
56
|
+
A write that fails at the transport level (a session-expired error, a
|
|
57
|
+
timeout, a connection reset, an empty or non-JSON reply) is not a refusal:
|
|
58
|
+
it may have landed. Before you retry a create of a ticket, a comment or an
|
|
59
|
+
event, list the target table for a row with the same title (tickets) or the
|
|
60
|
+
same opening line (comments and events) written by your seat in the last two
|
|
61
|
+
minutes. If one exists, use it and create nothing new. A validation error (a
|
|
62
|
+
400 or 422 with a field message) is a real failure: fix the body and write
|
|
63
|
+
again. The same check applies to a follow-up ticket you file while working and
|
|
64
|
+
to your hand-off comment.
|
|
65
|
+
|
|
56
66
|
Your identity is the Crew row named for your seat in the `## Your crew`
|
|
57
67
|
roster at the top of this prompt. Use its id as the assignee and as the
|
|
58
68
|
comment author. Every agent and every person who touches this tracker has
|