@avallon-labs/sdk 47.5.0-staging.1084 → 48.0.0-staging.1085

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/index.d.ts CHANGED
@@ -2191,6 +2191,12 @@ type CreateInformationRequestBodyMetadata = {
2191
2191
  */
2192
2192
 
2193
2193
  type CreateInformationRequestBody = {
2194
+ /**
2195
+ * A short label for the question, so somebody scanning a queue of open requests can tell yours apart. Name what it is about, not what you need — no trailing punctuation.
2196
+ * @minLength 1
2197
+ * @maxLength 120
2198
+ */
2199
+ title: string;
2194
2200
  /**
2195
2201
  * The single fact you need, as one question. Write it for a person who is not watching this run: say what you were doing, what you could not determine, and what would let you continue.
2196
2202
  * @minLength 1
@@ -2232,6 +2238,8 @@ type InformationRequestMetadata = {
2232
2238
 
2233
2239
  interface InformationRequest {
2234
2240
  id: string;
2241
+ /** Short label the asker gave the question */
2242
+ title: string;
2235
2243
  /** What the asker needs to know */
2236
2244
  question: string;
2237
2245
  /** Null while the request is open */
@@ -12200,7 +12208,7 @@ type SecondParameter$c<T extends (...args: never) => unknown> = Parameters<T>[1]
12200
12208
  /**
12201
12209
  * Ask a person for a specific fact you cannot establish yourself.
12202
12210
 
12203
- Use this when one missing piece of information is blocking you and only a human can supply it — which claim a document belongs to, which of two policies applies, what an ambiguous reference means. Ask one answerable question per request, and write it so it stands on its own: whoever resolves it sees your question and nothing else.
12211
+ Use this when one missing piece of information is blocking you and only a human can supply it — which claim a document belongs to, which of two policies applies, what an ambiguous reference means. Ask one answerable question per request, and write it so it stands on its own: whoever resolves it sees your title and your question and nothing else.
12204
12212
 
12205
12213
  Immediately link the request to its case with `addCaseLinks` and `entity_type: "information_request"`. That is how it reaches the person working that case; unlinked, it sits in a queue nobody is looking at. Leave it unlinked only when you genuinely cannot tell which case it belongs to.
12206
12214