@clickminded/coauthor-cli 0.0.48 → 0.0.50

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.48",
3
+ "version": "0.0.50",
4
4
  "type": "module",
5
5
  "bin": {
6
6
  "coauthor": "dist/index.js",
@@ -50,7 +50,7 @@ SEO mode is rolling out gradually; accounts outside it get `feature_unavailable`
50
50
  core_promise?: string
51
51
  format?: string
52
52
  reading_commitment?: null | {
53
- kind: "preset" | "custom"
53
+ kind: "preset" | "custom" | "outline"
54
54
  preset_id?: null | "quick_read" | "balanced_post" | "deep_dive"
55
55
  source: "user_explicit" | "user_choice" | "assistant_inferred" | "system_default"
56
56
  }
@@ -102,7 +102,7 @@ SEO mode is rolling out gradually; accounts outside it get `feature_unavailable`
102
102
  }
103
103
  ```
104
104
 
105
- - Use `reading_commitment.kind: "preset"` with a preset id for quick length choices; use `"custom"` with explicit `length_guidance` when the user gives a custom range.
105
+ - Leave `reading_commitment` out when the user didn't state a length: CoAuthor saves `{ "kind": "outline" }` and the outline sizes the post (each section about as long as it needs, near what ranks for a search post). Use `"preset"` with a preset id only when the user picked a length tier, and `"custom"` with explicit `length_guidance` when they gave a range.
106
106
  - Use top-level `canonical_entities`, `outline_seed`, `style_rules`, `must_not_change`, `structure_preference`, and `confidence_notes`. A legacy nested `handoff` object may be normalized, but top-level fields are clearer for agents.
107
107
  ## Field guide
108
108
 
@@ -111,7 +111,7 @@ SEO mode is rolling out gradually; accounts outside it get `feature_unavailable`
111
111
  - `target_audience`: Who the piece is for, including their sophistication, context, objections, and buying or reading intent.
112
112
  - `core_promise`: The reader outcome. Phrase it as what the reader will understand, decide, or be able to do after reading.
113
113
  - `format`: Human-readable format label, such as `blog post`, `guide`, `listicle`, `case study`, or `long-form SEO comparison guide`.
114
- - `reading_commitment`: Use a preset when the user picked or implied a length tier. Use `custom` plus `length_guidance` when the user gave a specific range.
114
+ - `reading_commitment`: Omit it unless the user stated a length; the outline then sizes the post (`kind: "outline"`, no `length_guidance`). Use a preset when the user picked a length tier. Use `custom` plus `length_guidance` when the user gave a specific range.
115
115
  - `length_guidance`: Word-count bounds. Use positive integers or `null`; keep `min_words <= target_words <= max_words` when known.
116
116
  - `audience_knowledge_assumptions`: What the reader already knows, so the draft does not over-explain or under-explain.
117
117
  - `desired_reader_experience`: How the finished piece should feel to read, such as fast and scannable, authoritative and comprehensive, funny but informative, or practical and no-fluff.
@@ -141,7 +141,6 @@ SEO mode is rolling out gradually; accounts outside it get `feature_unavailable`
141
141
  "target_audience": "Owners of 3-15 person accounting and bookkeeping firms who run month-end close for small-business clients.",
142
142
  "core_promise": "Readers leave with a five-step intake process and a client message template they can use this month.",
143
143
  "format": "how-to guide",
144
- "reading_commitment": { "kind": "preset", "preset_id": "balanced_post", "source": "user_explicit" },
145
144
  "audience_knowledge_assumptions": "Knows close procedures and common accounting software; has not formalized client intake.",
146
145
  "must_include": ["A day-by-day close calendar", "A copy-paste client reminder email", "How to handle clients who send documents late"],
147
146
  "must_avoid": ["Software vendor comparisons", "Generic productivity advice"],
@@ -26,7 +26,7 @@ coauthor post-details set <id> --seo-title "..." --description "..." --slug "...
26
26
 
27
27
  For SEO posts on a profile with a website, `post_details.incoming_link_suggestions` lists existing pages on the user's site that could link to the new post: `{status, suggestions: [{url, title, anchor, sentence}]}`. `status` is `ready`, `none`, or `index_not_ready` (the site was still being indexed when the draft was written; links appear on the next post). It is read-only. After the post is published, offer the user the sentences to add on those pages, linking the anchor text to the new post's URL. It is `null` for other posts.
28
28
 
29
- For SEO posts, `post-details show` also returns `seo`: the target `keyword`, its `market`, `seo_research_credits`, and a `checks` list computed from the current draft and title. Each check has an `id`, a `status` (`pass`, `warn`, `fail`, or `skip` when there is nothing to measure) and a plain `detail`. The ids are `keyword_in_title`, `keyword_in_intro` (first 100 words), `secondary_in_h2`, `table_stakes`, `angle_section`, `questions_answered`, `internal_link`, `outbound_sources` and `length`. A `fail` on the title is worth fixing before publishing: edit it with `project rename`. A `warn` on `keyword_in_intro` is fine when the keyword wouldn't read naturally in the opening, so don't force it in. `questions_answered` is optional: it reports `pass` or `skip`, never `warn`. `seo` is `null` for other posts.
29
+ For SEO posts, `post-details show` also returns `seo`: the target `keyword`, its `market`, `seo_research_credits`, and a `checks` list computed from the current draft and title. Each check has an `id`, a `status` (`pass`, `warn`, `fail`, or `skip` when there is nothing to measure) and a plain `detail`. The ids are `keyword_in_title`, `keyword_in_intro` (first 100 words), `secondary_in_h2`, `table_stakes`, `angle_section`, `questions_answered`, `internal_link`, `outbound_sources` and `length`. A `fail` on the title is worth fixing before publishing: edit it with `project rename`. A `warn` on `keyword_in_intro` is fine when the keyword wouldn't read naturally in the opening, so don't force it in. `secondary_in_h2` and `questions_answered` are optional: they report `pass` or `skip`, never `warn`. `seo` is `null` for other posts.
30
30
 
31
31
  `post_details` also records where the post went: `search_keyword` (the search it was written for), `export_ref` (the last export's destination reference, for example `{destination: "wordpress", wordpress_post_id}`), and `published_url` / `published_at`, which are set only when an export reports the post is live. WordPress exports are always drafts, so they record `export_ref` only.
32
32
 
@@ -129,7 +129,7 @@ SEO mode is rolling out gradually; accounts outside it get `feature_unavailable`
129
129
  core_promise?: string
130
130
  format?: string
131
131
  reading_commitment?: null | {
132
- kind: "preset" | "custom"
132
+ kind: "preset" | "custom" | "outline"
133
133
  preset_id?: null | "quick_read" | "balanced_post" | "deep_dive"
134
134
  source: "user_explicit" | "user_choice" | "assistant_inferred" | "system_default"
135
135
  }
@@ -181,7 +181,7 @@ SEO mode is rolling out gradually; accounts outside it get `feature_unavailable`
181
181
  }
182
182
  ```
183
183
 
184
- - Use `reading_commitment.kind: "preset"` with a preset id for quick length choices; use `"custom"` with explicit `length_guidance` when the user gives a custom range.
184
+ - Leave `reading_commitment` out when the user didn't state a length: CoAuthor saves `{ "kind": "outline" }` and the outline sizes the post (each section about as long as it needs, near what ranks for a search post). Use `"preset"` with a preset id only when the user picked a length tier, and `"custom"` with explicit `length_guidance` when they gave a range.
185
185
  - Use top-level `canonical_entities`, `outline_seed`, `style_rules`, `must_not_change`, `structure_preference`, and `confidence_notes`. A legacy nested `handoff` object may be normalized, but top-level fields are clearer for agents.
186
186
  ### Field guide
187
187
 
@@ -190,7 +190,7 @@ SEO mode is rolling out gradually; accounts outside it get `feature_unavailable`
190
190
  - `target_audience`: Who the piece is for, including their sophistication, context, objections, and buying or reading intent.
191
191
  - `core_promise`: The reader outcome. Phrase it as what the reader will understand, decide, or be able to do after reading.
192
192
  - `format`: Human-readable format label, such as `blog post`, `guide`, `listicle`, `case study`, or `long-form SEO comparison guide`.
193
- - `reading_commitment`: Use a preset when the user picked or implied a length tier. Use `custom` plus `length_guidance` when the user gave a specific range.
193
+ - `reading_commitment`: Omit it unless the user stated a length; the outline then sizes the post (`kind: "outline"`, no `length_guidance`). Use a preset when the user picked a length tier. Use `custom` plus `length_guidance` when the user gave a specific range.
194
194
  - `length_guidance`: Word-count bounds. Use positive integers or `null`; keep `min_words <= target_words <= max_words` when known.
195
195
  - `audience_knowledge_assumptions`: What the reader already knows, so the draft does not over-explain or under-explain.
196
196
  - `desired_reader_experience`: How the finished piece should feel to read, such as fast and scannable, authoritative and comprehensive, funny but informative, or practical and no-fluff.
@@ -220,7 +220,6 @@ SEO mode is rolling out gradually; accounts outside it get `feature_unavailable`
220
220
  "target_audience": "Owners of 3-15 person accounting and bookkeeping firms who run month-end close for small-business clients.",
221
221
  "core_promise": "Readers leave with a five-step intake process and a client message template they can use this month.",
222
222
  "format": "how-to guide",
223
- "reading_commitment": { "kind": "preset", "preset_id": "balanced_post", "source": "user_explicit" },
224
223
  "audience_knowledge_assumptions": "Knows close procedures and common accounting software; has not formalized client intake.",
225
224
  "must_include": ["A day-by-day close calendar", "A copy-paste client reminder email", "How to handle clients who send documents late"],
226
225
  "must_avoid": ["Software vendor comparisons", "Generic productivity advice"],
@@ -406,7 +405,7 @@ coauthor post-details set <id> --seo-title "..." --description "..." --slug "...
406
405
 
407
406
  For SEO posts on a profile with a website, `post_details.incoming_link_suggestions` lists existing pages on the user's site that could link to the new post: `{status, suggestions: [{url, title, anchor, sentence}]}`. `status` is `ready`, `none`, or `index_not_ready` (the site was still being indexed when the draft was written; links appear on the next post). It is read-only. After the post is published, offer the user the sentences to add on those pages, linking the anchor text to the new post's URL. It is `null` for other posts.
408
407
 
409
- For SEO posts, `post-details show` also returns `seo`: the target `keyword`, its `market`, `seo_research_credits`, and a `checks` list computed from the current draft and title. Each check has an `id`, a `status` (`pass`, `warn`, `fail`, or `skip` when there is nothing to measure) and a plain `detail`. The ids are `keyword_in_title`, `keyword_in_intro` (first 100 words), `secondary_in_h2`, `table_stakes`, `angle_section`, `questions_answered`, `internal_link`, `outbound_sources` and `length`. A `fail` on the title is worth fixing before publishing: edit it with `project rename`. A `warn` on `keyword_in_intro` is fine when the keyword wouldn't read naturally in the opening, so don't force it in. `questions_answered` is optional: it reports `pass` or `skip`, never `warn`. `seo` is `null` for other posts.
408
+ For SEO posts, `post-details show` also returns `seo`: the target `keyword`, its `market`, `seo_research_credits`, and a `checks` list computed from the current draft and title. Each check has an `id`, a `status` (`pass`, `warn`, `fail`, or `skip` when there is nothing to measure) and a plain `detail`. The ids are `keyword_in_title`, `keyword_in_intro` (first 100 words), `secondary_in_h2`, `table_stakes`, `angle_section`, `questions_answered`, `internal_link`, `outbound_sources` and `length`. A `fail` on the title is worth fixing before publishing: edit it with `project rename`. A `warn` on `keyword_in_intro` is fine when the keyword wouldn't read naturally in the opening, so don't force it in. `secondary_in_h2` and `questions_answered` are optional: they report `pass` or `skip`, never `warn`. `seo` is `null` for other posts.
410
409
 
411
410
  `post_details` also records where the post went: `search_keyword` (the search it was written for), `export_ref` (the last export's destination reference, for example `{destination: "wordpress", wordpress_post_id}`), and `published_url` / `published_at`, which are set only when an export reports the post is live. WordPress exports are always drafts, so they record `export_ref` only.
412
411