@rolino/cli 0.3.0 → 0.5.0-beta.0

package/CHANGELOG.md

@@ -1,5 +1,59 @@
 # @rolino/cli
 
+## 0.5.0-beta.0
+
+### Minor Changes
+
+- 4f9e790: Add the optional `blog:manage` capability and synchronized agent-first Blog
+  setup, import, cadence planning, plan review, article creation, confirmed
+  connection provisioning, and safe verification operations.
+- 1edd1e7: Add published Blog Studio delivery contracts and the server-only Next.js 16 Blog Studio package.
+- 74a13ea: Expose immediate versus scheduled delivery and destination lifecycle stages,
+  preserve YouTube visibility for immediate publishing, and clarify remote
+  schedule confirmation across public clients.
+- 4a893dd: Add provider-neutral Blog publishing destinations, safe delivery inspection,
+  and exact destination binding across public agent interfaces.
+- 843a1db: Add the exact optional `seo:read` capability and bounded read-only SEO
+  opportunity and weekly-report parity across public agent contracts, clients,
+  CLI commands, and closed-world MCP tools. SEO reads now use the version 3 task
+  contract with the exact Ready, Research, or Rejected decision, selected format,
+  complete deliverables, bounded evidence, safe URLs, limitations, and no-publish
+  rules. Public output uses readable topic names and separate topic-relevance and
+  action-readiness confidence. Research tasks compare all supported formats and
+  must validate or reject the finding before a separate draft action is allowed.
+
+### Patch Changes
+
+- Updated dependencies [4f9e790]
+- Updated dependencies [1edd1e7]
+- Updated dependencies [74a13ea]
+- Updated dependencies [4a893dd]
+- Updated dependencies [843a1db]
+  - @rolino/contracts@0.5.0-beta.0
+  - @rolino/sdk@0.5.0-beta.0
+  - @rolino/local-auth@0.5.0-beta.0
+
+## Unreleased
+
+### Minor Changes
+
+- Add Blog destination discovery, delivery inspection, and exact destination selection for publication commands.
+
+## 0.4.0
+
+### Minor Changes
+
+- 6d5cefc: Add LinkedIn native video capability, limits, and delivery-options parity across public agent surfaces.
+- 4149259: Add platform-aware media-adjustment readiness actions and align LinkedIn publishing guidance across agent packages.
+
+### Patch Changes
+
+- Updated dependencies [6d5cefc]
+- Updated dependencies [4149259]
+  - @rolino/contracts@0.4.0
+  - @rolino/sdk@0.4.0
+  - @rolino/local-auth@0.4.0
+
 ## 0.3.0
 
 ### Minor Changes

package/README.md

@@ -51,16 +51,34 @@ rolino posts publish execute POST_ID --project PROJECT_ID --expected-version VER
 rolino integrations health --project PROJECT_ID
 rolino integrations delivery-options --project PROJECT_ID --provider TIKTOK|LINKEDIN
 rolino calendar list --project PROJECT_ID [--from ISO_DATE --to ISO_DATE] [--limit 50] [--cursor CURSOR]
-rolino doctor
+rolino seo opportunities list --project PROJECT_ID [--limit 20] [--cursor CURSOR] [--kind KIND] [--impact HIGH|MEDIUM|LOW]
+rolino seo opportunities show OPPORTUNITY_ID --project PROJECT_ID
+rolino seo reports list --project PROJECT_ID [--limit 10] [--cursor CURSOR] [--status COMPLETE|PARTIAL]
+rolino seo reports show REPORT_ID --project PROJECT_ID
+rolino blog destinations providers --project PROJECT_ID
+rolino blog destinations list --project PROJECT_ID
+rolino blog destinations deliveries --project PROJECT_ID [--article ARTICLE_ID]
+rolino doctor
 ```
 
 Interactive login opens the configured Rolino instance in a browser, obtains
 explicit workspace approval, and exchanges a single-use code with PKCE S256.
 The approval screen always includes identity and workspace reads and lets the
 user independently opt into project creation, draft writing, confirmed
-scheduling, and confirmed immediate publishing. Optional permissions start off,
+scheduling, confirmed immediate publishing, and read-only SEO Intelligence.
+The SEO option explains that it permits reading opportunities, evidence,
+complete tasks, and weekly reports. It cannot run analysis or change SEO settings.
+Opportunity detail prints the exact decision, selected format, target,
+deliverables, research, safe URLs, separate topic-relevance and action-readiness
+confidence, limitations, and no-publish rules. A Ready
+task can request complete final deliverables for review. A Research task must
+select only `RESEARCH_TASK`, compare all reasonable formats without a preferred
+final format, and return `VALIDATED` with a complete next task or `REJECTED`
+with evidence. It cannot create a final draft in the same action.
+Optional permissions start off,
 and existing credentials never gain a newly selected permission. Revoke and
-reauthorize an existing connection to grant project creation. The bearer
+reauthorize an existing connection to grant project creation or `seo:read`.
+Existing credentials never receive `seo:read` automatically. The bearer
 credential never passes through a browser URL. Saved credentials are scoped by
 base URL and stored in the operating-system configuration directory;
 `ROLINO_CONFIG_DIR` overrides that location. `auth logout` revokes the calling
@@ -107,9 +125,11 @@ rolino posts create --project PROJECT_ID --caption "Launch description" --platfo
 ```
 
 Google may restrict uploads from unaudited API projects to Private. Rolino does
-not infer audit approval from configuration. A scheduled YouTube post must
-target Public; confirmed scheduling starts its private resumable upload
-immediately so processing can finish before the target time.
+not infer audit approval from configuration. `posts publish` preserves the
+chosen Public, Unlisted, or Private visibility and does not create a schedule.
+A future `posts schedule` delivery must target Public; confirmed scheduling
+starts its private resumable upload immediately so processing can finish before
+the target time.
 
 TikTok drafts require account-specific choices. Refresh them immediately before
 preparing the draft:
@@ -134,18 +154,23 @@ images. Use `--bluesky-caption` for a destination-specific override of up to
 rolino posts create --project PROJECT_ID --caption "Shared launch" --platform BLUESKY --bluesky-caption "Launch day 🦋" --yes
 ```
 
-LinkedIn drafts can be text-only or include up to ten stored JPEG/PNG images.
-Refresh the connected member and server policy before preparing the draft, and
-use `--linkedin-caption` for a destination override:
+LinkedIn drafts can be text-only, include up to ten stored JPEG/PNG images, or
+contain exactly one stored MP4 without mixing images and video. Native video
+must be 75 KB to 500 MB and 3 seconds to 30 minutes. Refresh the connected
+member and server policy before preparing the draft, and use
+`--linkedin-caption` for a destination override:
 
 ```text
 rolino integrations delivery-options --project PROJECT_ID --provider LINKEDIN
 rolino posts create --project PROJECT_ID --caption "Shared launch" --platform LINKEDIN --linkedin-caption "Launch day for our LinkedIn network" --media IMAGE_ASSET_ID --yes
+rolino posts create --project PROJECT_ID --caption "Product demo" --platform LINKEDIN --media VIDEO_ASSET_ID --yes
 ```
 
 The connected OAuth member is the author; the developer app's associated
-Company Page is not a publishing target. If final post creation has an unknown
-outcome, inspect that member's LinkedIn feed before retrying.
+Company Page is not a publishing target. Native video publish and schedule
+execution remains in preparation until LinkedIn confirms upload and processing.
+If final post creation has an unknown outcome, inspect that member's LinkedIn
+feed before retrying.
 
 Project creation also requires interactive confirmation or `--yes`. It
 atomically saves a project and its paired brand, but does not start research,
@@ -165,8 +190,10 @@ server confirmation.
 
 When YouTube is selected, the preview states whether confirmed execution starts
 or resumes early private preparation. A schedule execution may return
-`PENDING` while YouTube confirms a remote schedule change; that result is not a
-published state, and the same idempotency key is safe to replay.
+`PENDING` with phase `REMOTE_SCHEDULE_CONFIRMATION` after the upload completes
+while YouTube acknowledges the requested Public publish time. The video remains
+private, no second publish action is required, and the same idempotency key is
+safe to replay.
 
 Immediate publishing uses the same server-enforced pattern. `posts publish
 preview` validates the current version, exact destination set, readiness, live
@@ -177,8 +204,9 @@ delivery; Rolino's worker performs provider calls and reconciles ambiguous
 network results so an unsafe retry cannot duplicate a post. Use
 `ROLINO_CONFIRMATION_TOKEN` for scripts instead of putting the token in process
 arguments. YouTube remains `PREPARING` while its resumable upload and provider
-processing are incomplete; only provider-confirmed visibility becomes
-published.
+processing are incomplete. The preview identifies the delivery as `IMMEDIATE`,
+shows the exact visibility, and confirms that no schedule will be created; only
+provider-confirmed visibility becomes published.
 
 The CLI cannot enable YouTube, Bluesky, or LinkedIn, or infer provider approval.
 Those are server-side deployment controls. Self-hosted operators should
@@ -224,3 +252,36 @@ issues through the repository's
 [security policy](https://github.com/deifos/rolino/security/policy).
 
 `@rolino/cli` is available under the MIT License.
+## Agent-first Blog Studio setup
+
+Authorize the optional `blog:manage` capability separately from Blog reading,
+draft writing, and approved-revision publishing. Existing credentials never
+gain it automatically. Start every setup with:
+
+```bash
+rolino --agent blog setup status --project PROJECT_ID
+```
+
+The `blog site`, `blog plan`, `blog article`, `blog connection`, and
+`blog destinations` command groups mirror the versioned API. Use these safe
+publishing reads before setup or publication:
+
+```bash
+rolino --agent blog destinations providers --project PROJECT_ID
+rolino --agent blog destinations list --project PROJECT_ID
+rolino --agent blog destinations deliveries --project PROJECT_ID
+rolino --agent blog destinations deliveries --project PROJECT_ID --article ARTICLE_ID
+```
+
+The provider catalog requires `blog:manage`. It returns only providers enabled
+for the workspace, safe capabilities, and official documentation. Destination
+and delivery-attempt reads require `blog:read`. They omit draft content,
+prompts, evidence, secrets, and raw provider responses. A returned remote URL
+is not proof that a queued or failed delivery is live.
+
+Mutations require a stable idempotency key.
+Connection provisioning also requires preview, explicit confirmation, and
+execute. A first successful execute can return a delivery token or webhook
+secret once; save it only in server-side environment configuration. Replays
+do not reveal it again. Blog publication remains the separate approved exact
+revision preview/execute workflow.