Update to Riverside

Changed files

Choose a file to see its text changes. Binary or large files show metadata only.

.app.json →

.codex-plugin/plugin.json →

.mcp.json →

CHANGELOG.md →

LICENSE →

README.md →

SECURITY.md →

agents/openai.yaml →

assets/logo.png →

docs/cursor-testing.md →

skills/content-discovery/SKILL.md →

skills/content-discovery/references/cross-skill-handoffs.md →

skills/content-discovery/references/hierarchy-navigation.md →

skills/podcast-hosting/SKILL.md →

skills/podcast-hosting/agents/openai.yaml →

skills/setup/SKILL.md →

skills/social-publishing/SKILL.md →

skills/social-publishing/agents/openai.yaml →

skills/social-publishing/references/results-and-recovery.md →

skills/social-publishing/references/scheduling-and-draft-export.md →

skills/social-publishing/references/upload-status.md →

skills/video-editing/SKILL.md →

skills/social-publishing/references/results-and-recovery.md

Lines starting with − were removed; lines starting with + were added. Other lines provide context.

--- before
+++ after
@@ -1,48 +1,81 @@
-# Results and recovery
+# Results, management and recovery
 
-Outcome interpretation, retry admissibility, and error-specific recovery after a
-publish is processing, partial, or failed, or after a timeout, transport failure,
-missing result, or any other unknown outcome. The main skill file's safety
-contract still governs every follow-up here.
-
-## Classify the outcome
-
-- **Processing or accepted for later completion:** explain that processing is
-  underway and the post should follow automatically. Relay a returned
-  user-facing message when present; do not expose a raw internal status or
-  resend the call.
-- **Timeout, transport failure, missing response, or unknown result:** say that
-  submission could have happened but cannot be confirmed. Stop. With no
-  idempotency key or authoritative status readback, retrying could duplicate a
-  live post.
-- **Explicit per-target failure:** fetch fresh platform guidance and evaluate
-  the retry gate below. A failure on one target does not undo or change another
-  target's result.
-
-## Retry gate
-
-A retry is admissible only when both the returned failure and current
-`social_get_publishing_guidelines` recovery guidance explicitly establish that
-no post was created and that retrying this failure is safe. Never retry a
-success, processing result, partial or ambiguous result, timeout, transport
-failure, or unknown outcome.
-
-Passing this gate makes a retry eligible; it does not authorize the call. Return
-to the main preview and obtain the required new confirmation, whether or not the
-payload changed. If the same explicit failure repeats after one clean retry,
-stop and report the platform's result.
-
-## Error-specific recovery
-
-Use the fresh live guidance for the failure in hand rather than a remembered
-error-code catalogue.
-
-- **Export required:** re-run the main routing table; this outcome matches its
-  scheduling-and-draft-export row, which supplies current compose choices.
-  Retry only if the explicit failure passes the retry gate, and return to the
-  main preview because the payload changed.
-- **Metadata or media rejected:** correct only what the live guidance and
-  returned failure identify, then return to the main preview and confirmation.
-- **YouTube copyright / Content-ID signal:** use video-editing's
-  `editing_get_export_publish_data` to inspect the edit's media and surface a
-  flagged match instead of retrying over it.
+## Find and inspect
+
+`social_list_uploads` needs studio/production ids. Default is the next 30 days;
+use past dates for published posts. Page with `offset`/`hasMore`; window totals
+are before platform/status filters, not filtered-row totals.
+
+Read `social_get_upload` before mutations. Independently check `editable`,
+`mediaEditable`, `cancellable`: rendering may allow only cancellation; failed
+may allow only editing. Match the account with connected platforms. Only
+`COMPLETED` proves live. Relay returned `postUrl`; null does not prove failure.
+Do not invent Facebook URLs.
+
+## Update or cancel
+
+Preview current account/platform, content, schedule, change and consequences;
+confirm each mutation. Refresh/reconfirm if material values changed.
+
+- `social_update_upload` requires `editable`. Send changing fields only and the
+  matching platform object; returned `content` is not an input template and
+  nulls cannot be sent back. `publishNow` posts immediately and cannot be undone;
+  never combine it with future `scheduledAt`. Use the main scheduling route.
+- Media changes require `mediaEditable`. Video cannot be removed or converted
+  to images, or vice versa. `assets` replaces all images; `[]` removes them only
+  on text-only platforms. X replies and LinkedIn comments replace whole lists:
+  start with current entries, preserve unchanged ones and X reply ids, and
+  preview deletions explicitly.
+- `social_cancel_upload` requires `cancellable`; it permanently removes the
+  post from Content Planner, with no restore or platform deletion. Success is
+  confirmed by its own response. Do not read back: cancelled ids now return
+  an authorization error.
+
+Live edits/removal happen on the platform. Never blindly repeat uncertain
+mutations, especially publish-now/cancellation.
+
+## Accounts
+
+Resolve required studio id/slug and production id through content-discovery.
+`social_connect_social_account` gives a user consent link. After they report
+completion, read connected platforms and compare ids
+with `connectedPlatformAccountIds`. If that snapshot is null, list accounts and
+ask which was added. If none appeared, ask about the browser result before a
+fresh link. Never poll by restarting connections. `isAddingAccount` selects an
+additional Instagram/X account; omit `returnTo` unless a current Riverside URL
+is known.
+
+Before `social_disconnect_social_account`, read accounts, name the target and
+warn that all its scheduled uploads are permanently cancelled; get explicit
+confirmation. For Facebook, every Page under that login is disconnected: name
+all affected Pages first. Other logins stay connected. Reconnection does not
+restore cancelled uploads.
+
+## Analytics
+
+`social_get_upload_analytics` reads a published post found by listing. Pass
+known `studioId` to diagnose permissions. Relay `asOf`; counts are not live. `hasData: false`, null metrics/days mean unavailable,
+never zero. Daily values are already differenced: do not sum/difference them.
+`frozen` means collection ended. `MISSING_ANALYTICS_SCOPE` requires reconnecting,
+not read retries. In listing views, missing fields mean lookup failed; null
+means no collected/available count.
+
+## Recovery
+
+Processing: report without resending. Timeout/transport failure/unusable result:
+stop publishing. Listing may investigate, but no matching row cannot prove no
+post; there is no idempotency key.
+
+For explicit failures, fetch fresh guidance. Both failure and guidance must
+prove no post and safe retry before a fresh upload is eligible. Never retry
+success, processing, partial/unknown outcomes. Preview/confirm again; stop if
+the failure repeats after one clean retry.
+
+Prefer in-place recovery. Re-read status/capabilities. `UNKNOWN`/missing failure
+category needs platform or Support verification before republishing. Expired
+connections may revive scheduled posts after reconnect: no new publish or
+`publishNow` until its fresh outcome is reconciled. Other confirmed failures may
+use eligible in-place update with the confirmation contract above.
+
+Export-required matches the draft-export route. Fix only identified metadata/
+media errors, then preview/confirm again. Keep the main YouTube copyright gate.