@clickminded/coauthor-cli 0.0.64 → 0.0.66
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/commands.js
CHANGED
|
@@ -2303,6 +2303,8 @@ function seoPlanShowMessage(data, kind) {
|
|
|
2303
2303
|
const code = planString(plan, 'error_code');
|
|
2304
2304
|
lines.push(`The last plan run failed${code ? ` (${code})` : ''}: ${planString(plan, 'error_message') ?? 'unknown error'}. Try again with \`coauthor seo-plan generate --wait\`.${firstPlanFree ? ' Your first plan is free, so the retry uses no credits.' : ''}`);
|
|
2305
2305
|
}
|
|
2306
|
+
if (plan.is_preview === true)
|
|
2307
|
+
lines.push(`This is a free preview of the plan (the first posts and a few pages to improve). \`coauthor seo-plan generate --wait\` finishes it into the full plan${firstPlanFree ? ', which is free (your first plan)' : ''}.`);
|
|
2306
2308
|
if (view.stale === true)
|
|
2307
2309
|
lines.push('The profile\'s website or market changed since this plan was made. `coauthor seo-plan generate` updates it.');
|
|
2308
2310
|
const monthly = view.monthly_check === null || view.monthly_check === undefined ? null : planRecord(view.monthly_check);
|
package/package.json
CHANGED
|
@@ -16,6 +16,7 @@ coauthor draft revise <id> --instruction "Cut the intro to two sentences and lea
|
|
|
16
16
|
- Name the place precisely ("the paragraph after the 'Write the first line' heading") and give numbers for cuts ("under 60 words"). Vague targets get a clarifying question back, and a vague "tighten" changes little.
|
|
17
17
|
- One revision can be open on a draft at a time, and an open one blocks the user's saves in the browser. Always apply or discard it. `revision_pending` means one is already open. A revision you leave waiting for review is discarded automatically after 30 minutes (`expires_at` in `draft revision show`), so review it promptly; after that, start a new one.
|
|
18
18
|
- If `--wait` returns `still_running`, check again with `coauthor draft revision show <id> <revision-id> --json`.
|
|
19
|
+
- While a revision runs, up to 100 available credits are temporarily held for its steps. Only actual usage is charged; unused held credits are released when it finishes or stops. A hold is included in `coauthor credits <id> --json` and does not change the request's spending limit.
|
|
19
20
|
- `revise_unavailable` means this account cannot revise by instruction yet; use a direct edit.
|
|
20
21
|
|
|
21
22
|
## 2. Direct edit (exact text you already have)
|
|
@@ -34,6 +34,7 @@ coauthor seo-plan results [--profile <id>] --json
|
|
|
34
34
|
- Without `--profile` the default profile is used. Run `coauthor profile list --json` first when the user has several profiles and the request names a site or brand.
|
|
35
35
|
- `generate` returns at once with `data.plan_id`, `data.free` and `data.estimate_credits`. With `--wait` it polls until the plan is ready. After 9 minutes it exits with code 2 and `still_running`; run the same `generate ... --wait` command again to keep waiting (it joins the running plan; it does not start a second one).
|
|
36
36
|
- Many plans can be made at once, so a new plan may wait its turn. While `status` is `queued`, the status data carries `queue_position` (1 = next), `queue_eta_minutes` (a rough estimate) and `queue_paused`; the position and estimate are `null` once the plan is running or before the position is known. When `queue_paused` is `true` the plan is waiting for free plans to resume and has no estimate. Tell the user their place in line and keep waiting; the plan starts by itself.
|
|
37
|
+
- A plan can still be the free **preview** a person got from the website (`data.plan.is_preview` is `true`): it holds only the first 10 posts and a few pages to improve, with no monthly check. Running `generate` finishes it into the full plan, which counts as the user's free first plan (`first_plan_free` ignores previews). Say so when the user asks why a plan is short.
|
|
37
38
|
- `--adjust` is a short steer for this run, for example `--adjust "focus on B2B buyers, skip anything about hiring"`. Use it when the user wants a different emphasis. Competitors are found automatically; the user corrects them in the web app.
|
|
38
39
|
- `show` returns `data.plan` (`strategy_line`, `competitors_line`, `status`), `data.do_next` (the five best next moves), `data.counts_by_kind`, and `data.items` for one `--kind` (default `post`). Items are sorted as the web app shows them.
|
|
39
40
|
- A plan run that fails says why in `data.error_code` and `data.error_message` (see `references/troubleshooting.md`). Credits for a failed run are only charged for work that finished.
|
|
@@ -316,6 +316,7 @@ coauthor draft revise <id> --instruction "Cut the intro to two sentences and lea
|
|
|
316
316
|
- Name the place precisely ("the paragraph after the 'Write the first line' heading") and give numbers for cuts ("under 60 words"). Vague targets get a clarifying question back, and a vague "tighten" changes little.
|
|
317
317
|
- One revision can be open on a draft at a time, and an open one blocks the user's saves in the browser. Always apply or discard it. `revision_pending` means one is already open. A revision you leave waiting for review is discarded automatically after 30 minutes (`expires_at` in `draft revision show`), so review it promptly; after that, start a new one.
|
|
318
318
|
- If `--wait` returns `still_running`, check again with `coauthor draft revision show <id> <revision-id> --json`.
|
|
319
|
+
- While a revision runs, up to 100 available credits are temporarily held for its steps. Only actual usage is charged; unused held credits are released when it finishes or stops. A hold is included in `coauthor credits <id> --json` and does not change the request's spending limit.
|
|
319
320
|
- `revise_unavailable` means this account cannot revise by instruction yet; use a direct edit.
|
|
320
321
|
|
|
321
322
|
### 2. Direct edit (exact text you already have)
|
|
@@ -620,6 +621,7 @@ coauthor seo-plan results [--profile <id>] --json
|
|
|
620
621
|
- Without `--profile` the default profile is used. Run `coauthor profile list --json` first when the user has several profiles and the request names a site or brand.
|
|
621
622
|
- `generate` returns at once with `data.plan_id`, `data.free` and `data.estimate_credits`. With `--wait` it polls until the plan is ready. After 9 minutes it exits with code 2 and `still_running`; run the same `generate ... --wait` command again to keep waiting (it joins the running plan; it does not start a second one).
|
|
622
623
|
- Many plans can be made at once, so a new plan may wait its turn. While `status` is `queued`, the status data carries `queue_position` (1 = next), `queue_eta_minutes` (a rough estimate) and `queue_paused`; the position and estimate are `null` once the plan is running or before the position is known. When `queue_paused` is `true` the plan is waiting for free plans to resume and has no estimate. Tell the user their place in line and keep waiting; the plan starts by itself.
|
|
624
|
+
- A plan can still be the free **preview** a person got from the website (`data.plan.is_preview` is `true`): it holds only the first 10 posts and a few pages to improve, with no monthly check. Running `generate` finishes it into the full plan, which counts as the user's free first plan (`first_plan_free` ignores previews). Say so when the user asks why a plan is short.
|
|
623
625
|
- `--adjust` is a short steer for this run, for example `--adjust "focus on B2B buyers, skip anything about hiring"`. Use it when the user wants a different emphasis. Competitors are found automatically; the user corrects them in the web app.
|
|
624
626
|
- `show` returns `data.plan` (`strategy_line`, `competitors_line`, `status`), `data.do_next` (the five best next moves), `data.counts_by_kind`, and `data.items` for one `--kind` (default `post`). Items are sorted as the web app shows them.
|
|
625
627
|
- A plan run that fails says why in `data.error_code` and `data.error_message` (see `references/troubleshooting.md`). Credits for a failed run are only charged for work that finished.
|