Rolino fixed changes

The Contact page now sends private vulnerability reports directly to Rolino's GitHub advisory form.

Unknown Rolino API v1 routes now return a real JSON 404 with a stable error code, recovery hint, and request ID, while page 404s link agents to the sitemap, llms.txt, developer index, and agent guide.

Public Organization data now includes factual support contacts and an Ontario, Canada postal region, which makes Rolino's operator and contact details easier for agents and search engines to verify.

Admin customer search results now keep person details, workspace access, status, and support controls aligned without a horizontal scrollbar.

Google Business Profile reconnect attempts now keep an existing connection active when authorization is cancelled or fails, and provider setup pages show the correct OAuth result and recovery message.

The TikTok mockup now shows the correct commercial-content label immediately when disclosure settings change.

Malformed signup-source requests are now rejected without recording a permanent survey skip.

Publishing connection setup now rejects external or cross-brand recovery addresses before OAuth starts, including provider configuration failures.

Onboarding now validates edited brand details before creation and shows save failures on the screen where they occur.

Onboarding now shows the shared yellow corner glow behind its card, matching the signed-in workspace background.

Starting onboarding under a different account or workspace now resets the wizard to the first step instead of retaining a previous completion screen.

Publishing-network authorization now preserves its safe onboarding return address, so a successful connection returns to the channel step instead of opening Integrations.

Brand creation now allows more time for its database transaction, which prevents slow but valid onboarding saves from expiring before commit.

The application shell now loads its initial theme without triggering a client-rendered script warning, and onboarding progress remains readable while updated translations load during development.

Transactional emails now load the Rolino mascot from the public email brand URL, keep header badges on one line, and use a compact header tagline without awkward orphaned words.

Onboarding navigation no longer reports a blocking-prerender warning, its progress indicator now uses valid list structure, and brand creation no longer uses workspace wording.

Creating an additional brand no longer replaces the workspace's original onboarding completion date.

Home now lets users edit a scheduled future cadence safely, keeps cadence fields in sync when they switch brands, aligns cross-time-zone totals by local week, uses the correct attention icon, and fills both dashboard side columns with useful work.

The Team page no longer adds a second “workspace” after workspace names that already contain it.

Workspace page transitions no longer reveal the outgoing page beneath incoming content, and Agent Access no longer repeats the active workspace name above its title.

Blog calendar dates with more than one item now show every card and block ambiguous moves instead of hiding content.

Landing-page calls to action can now enter the legacy dashboard route without an Instant-navigation validation error, while signed-out login callback data streams behind a stable sign-in shell.

Stale Blog schedules now clear their old publish time and show a needs-attention state when the approved content or image bundle changes before publication.

CLI authorization now declares its required signed-session boundary so browser permission windows open without a Cache Components Instant warning.

Blog revision approval now uses stable content hashing across database JSON storage and accepts existing generated revisions without weakening exact-content checks. Approval errors also give the user the specific safe recovery reason.

Failed Blog featured-image jobs now stop appearing queued, explain the saved failure reason when available, block duplicate requests while active, and safely retry both older and current job formats by reusing the exact failed job.

Failed Blog article drafts now provide a visible retry action with progress and notification feedback, and safely reuse the exact failed generation job instead of leaving the article at a dead end.

Blog Studio write actions now use consistent progress states, repeat-click protection, success notifications, and safe error feedback across planning, article editing, images, publication, site import, credentials, and publishing destinations.

Creating an article from a Blog plan now shows progress, blocks repeat clicks, opens the queued article, and refreshes automatically until its editable draft is ready.

Blog plan acceptance now updates the open idea immediately and safely handles repeated submissions instead of showing a policy error.