New — five Stripo workspace tools: list emails, folders, and templates, export send-ready HTML, and read your plan quotas

What shipped

• •New tool — orbit_list_stripo_emails. Lists the generated emails in your Stripo workspace via the API — paginated, searchable, sortable, with id, name, folder, timestamps, and editor and preview URLs per email. Filtering by folder_id is recursive, so pointing it at a parent folder includes every subfolder. Until now, taking stock of a Stripo library meant scraping the cabinet UI card by card; this is one read-only call.
• •New tool — orbit_list_stripo_folders. Fetches the full recursive folder tree of your workspace, so the folder IDs you need for email-list filters come from a call instead of a URL hunt. Read-only by necessity: Stripo exposes no folder write or move API, so filing an email into a folder still happens in the cabinet UI — the tree just tells you where everything lives. The stripo-email-builder skill's stale claims that Stripo has no list or folder API are corrected to match.
• •New tool — orbit_list_stripo_templates. Lists the templates in your workspace with IDs, names, and editor and preview URLs, and auto-discovers your master template — the skeleton Orbit composes into — by flagging it as is_configured_master in the results. A quick way to confirm the template ID in your settings points at the right one.
• •New tool — orbit_export_stripo_email_html. Exports one generated email as compiled, CSS-inlined, send-ready HTML to a local file — the output you'd hand to any ESP that isn't Braze. One caveat worth respecting: Stripo meters this endpoint against your plan's export quota (roughly 300 per period), so the tool returns a file path and byte count rather than raw HTML, and it should never be run in a loop. Check orbit_get_stripo_limits before a batch. Emails only — exporting the master template would strip its gen-area marker, so the tool refuses template IDs.
• •New tool — orbit_get_stripo_limits. Reads your Stripo plan's quota counters: stored emails and templates against the plan cap (pushes fail outright at the cap), the metered HTML-export quota, and the timer allowance. Each counter reports count, limit, and remaining, with a warning once usage passes 85% — so a big compose batch or export run gets a green light before it starts instead of a surprise failure partway through.
• •Setup improvements — orbit_setup_stripo now verifies the master template's gen-area padding automatically by reading the template back over the API, a check that previously reported itself as not implemented and left a known render trap unverified. Token checking is sharper too: the REST token is validated against Stripo's purpose-built /validate endpoint — the endpoint that exists for exactly this — rather than inferred from an unrelated read.
• •Behaviour fix — the Stripo Default Folder ID setting is removed. It sat in the extension settings implying Orbit-composed emails would land in a folder of your choosing, but nothing ever consumed the value: Stripo's generation API offers no folder destination, and there is no folder-move API either. A setting that promises something the platform can't deliver is worse than no setting. Composed emails land at the root; filing them is the cabinet UI's job, and the stripo-library-cleanup skill covers it.
• •Behaviour fix — the module archived flag now tells you it can't be trusted. orbit_list_stripo_modules reports archived per module, but the value is derived from tags rather than any authoritative state, and it's wrong often enough to mislead. Every place the flag surfaces now says so and documents the reliable check instead: call with include_html:true and treat a non-null artifact_path as the live-module signal.