@clickminded/coauthor-cli 0.0.79 → 0.0.80

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
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@clickminded/coauthor-cli",
3
- "version": "0.0.79",
3
+ "version": "0.0.80",
4
4
  "type": "module",
5
5
  "bin": {
6
6
  "coauthor": "dist/index.js",
@@ -8,6 +8,7 @@ Every failure prints JSON on stderr with `ok: false`, `error` (a readable messag
8
8
  | --- | --- | --- |
9
9
  | `needs_clarification` | The brief is too thin to outline well. | Answer `data.clarification_questions` from your context (ask the user only what you can't know), update the contract, run again. |
10
10
  | `timed_out` | The wait window ended; the work is still running on CoAuthor's side. | Run the resume command in `data.next_commands`, usually `coauthor workflow resume <id> --target draft --wait --json`. |
11
+ | `contract_field_too_long` | A brief field or list item is over its limit (`data.fields` lists each one: list items 600 characters, `additional_editorial_guidance` 10,000, other text fields 600 or 2,000, and 20–40 items per list). Nothing was saved. | Shorten the named fields, or split a long item into several items, and save again. |
11
12
  | `still_running` | Same, for a draft revision. | `coauthor draft revision show <id> <revision-id> --json`. |
12
13
  | `research_structuring` | Research finished and is being organized for drafting. Normal. | Keep waiting or resume toward draft. Don't rewind. |
13
14
  | `research_running_stale` | Research progress has not changed for 30+ minutes. | Check `coauthor research status <id> --json` a few minutes apart and look at `coauthor research structured <id> --json`. Rewinding (`coauthor workflow rewind <id> --target research --json`) discards the research done so far and costs credits to redo, so ask the user first. |
@@ -725,6 +725,7 @@ Every failure prints JSON on stderr with `ok: false`, `error` (a readable messag
725
725
  | --- | --- | --- |
726
726
  | `needs_clarification` | The brief is too thin to outline well. | Answer `data.clarification_questions` from your context (ask the user only what you can't know), update the contract, run again. |
727
727
  | `timed_out` | The wait window ended; the work is still running on CoAuthor's side. | Run the resume command in `data.next_commands`, usually `coauthor workflow resume <id> --target draft --wait --json`. |
728
+ | `contract_field_too_long` | A brief field or list item is over its limit (`data.fields` lists each one: list items 600 characters, `additional_editorial_guidance` 10,000, other text fields 600 or 2,000, and 20–40 items per list). Nothing was saved. | Shorten the named fields, or split a long item into several items, and save again. |
728
729
  | `still_running` | Same, for a draft revision. | `coauthor draft revision show <id> <revision-id> --json`. |
729
730
  | `research_structuring` | Research finished and is being organized for drafting. Normal. | Keep waiting or resume toward draft. Don't rewind. |
730
731
  | `research_running_stale` | Research progress has not changed for 30+ minutes. | Check `coauthor research status <id> --json` a few minutes apart and look at `coauthor research structured <id> --json`. Rewinding (`coauthor workflow rewind <id> --target research --json`) discards the research done so far and costs credits to redo, so ask the user first. |