Marketplace

Gusto jobs and compensation, garnishments, recurring reimbursements, and employee salary estimates. Generated from Gusto's complete 2026-06-15 App Integrations reference inventory: every admitted method/path is checked against its own official Markdown-wrapped OpenAPI fragment, with raw page and extracted-contract hashes retained in the audit fixture. A single openapi_source is intentionally omitted because Gusto publishes split per-endpoint fragments whose server is the demo origin; pinning one fragment would falsely claim production-wide coverage. This leaf is isolated to CompanyAccessAuth operations and uses per-company OAuth with rotating refresh tokens; system access tokens cannot authorize it. The X-Gusto-API-Version header is fixed to 2026-06-15. Every documented scope is declared and reads are uncached; sensitive payroll and HR reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Mutations are grant-off and approval-gated, explicit-null and structurally unsafe request bodies fall back to bounded body_raw, and JSON unsafe integers remain exact strings. No work-entity Source is declared because the App Integrations surface exposes no semantically honest task, note, or project entity.

Gusto contractor profiles, payment methods, and company contractor-payment history. Generated from Gusto's complete 2026-06-15 App Integrations reference inventory: every admitted method/path is checked against its own official Markdown-wrapped OpenAPI fragment, with raw page and extracted-contract hashes retained in the audit fixture. A single openapi_source is intentionally omitted because Gusto publishes split per-endpoint fragments whose server is the demo origin; pinning one fragment would falsely claim production-wide coverage. This leaf is isolated to CompanyAccessAuth operations and uses per-company OAuth with rotating refresh tokens; system access tokens cannot authorize it. The X-Gusto-API-Version header is fixed to 2026-06-15. Every documented scope is declared and reads are uncached; sensitive payroll and HR reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Mutations are grant-off and approval-gated, explicit-null and structurally unsafe request bodies fall back to bounded body_raw, and JSON unsafe integers remain exact strings. No work-entity Source is declared because the App Integrations surface exposes no semantically honest task, note, or project entity.

Gusto employee directories and profiles, employment history, terminations, rehires, and effective-dated home and work addresses. Generated from Gusto's complete 2026-06-15 App Integrations reference inventory: every admitted method/path is checked against its own official Markdown-wrapped OpenAPI fragment, with raw page and extracted-contract hashes retained in the audit fixture. A single openapi_source is intentionally omitted because Gusto publishes split per-endpoint fragments whose server is the demo origin; pinning one fragment would falsely claim production-wide coverage. This leaf is isolated to CompanyAccessAuth operations and uses per-company OAuth with rotating refresh tokens; system access tokens cannot authorize it. The X-Gusto-API-Version header is fixed to 2026-06-15. Every documented scope is declared and reads are uncached; sensitive payroll and HR reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Mutations are grant-off and approval-gated, explicit-null and structurally unsafe request bodies fall back to bounded body_raw, and JSON unsafe integers remain exact strings. No work-entity Source is declared because the App Integrations surface exposes no semantically honest task, note, or project entity.

Gusto earning types, pay schedules and periods, payroll preparation and updates, time sheets and payroll syncs, and asynchronous reports. Generated from Gusto's complete 2026-06-15 App Integrations reference inventory: every admitted method/path is checked against its own official Markdown-wrapped OpenAPI fragment, with raw page and extracted-contract hashes retained in the audit fixture. A single openapi_source is intentionally omitted because Gusto publishes split per-endpoint fragments whose server is the demo origin; pinning one fragment would falsely claim production-wide coverage. This leaf is isolated to CompanyAccessAuth operations and uses per-company OAuth with rotating refresh tokens; system access tokens cannot authorize it. The X-Gusto-API-Version header is fixed to 2026-06-15. Every documented scope is declared and reads are uncached; sensitive payroll and HR reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Mutations are grant-off and approval-gated, explicit-null and structurally unsafe request bodies fall back to bounded body_raw, and JSON unsafe integers remain exact strings. No work-entity Source is declared because the App Integrations surface exposes no semantically honest task, note, or project entity.

Gusto system-token company provisioning and disconnection, occupation search, event polling, and webhook subscription administration. Generated from Gusto's complete 2026-06-15 App Integrations reference inventory: every admitted method/path is checked against its own official Markdown-wrapped OpenAPI fragment, with raw page and extracted-contract hashes retained in the audit fixture. A single openapi_source is intentionally omitted because Gusto publishes split per-endpoint fragments whose server is the demo origin; pinning one fragment would falsely claim production-wide coverage. This leaf is isolated to SystemAccessAuth operations and requires a separately enrolled short-lived Gusto system bearer; company OAuth tokens cannot authorize it. The X-Gusto-API-Version header is fixed to 2026-06-15. Every documented scope is declared and reads are uncached; sensitive payroll and HR reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Mutations are grant-off and approval-gated, explicit-null and structurally unsafe request bodies fall back to bounded body_raw, and JSON unsafe integers remain exact strings. No work-entity Source is declared because the App Integrations surface exposes no semantically honest task, note, or project entity.

V3 bounded gzip inspection capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local gzip CLI ingredient exposes fixed operations for readiness, gzip stream integrity testing, compact gzip metadata listing, and verbose gzip metadata listing. The pack deliberately does not expose compression or decompression output because this gzip implementation writes compressed/decompressed bytes to stdout or mutates source-adjacent files; neither fits the current file-ref output contract without shell redirection. File operations accept one gzip path or materialized file_ref, capture only metadata or exit status, and expose no stdout payload bytes, source-adjacent writes, recursive mode, suffix override, force mode, original-name restore, arbitrary flags, caller-supplied environment override, stdin, output-file write, or shell wrapper. Requires gzip on PATH.

V3 deterministic Dockerfile lint capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local hadolint CLI ingredient exposes bounded project operations for readiness and Dockerfile lint diagnostics. Lints run from an explicit project directory cwd supplied at execution time, check one trusted local Dockerfile path, and return JSON diagnostics via the dockerfile.lint catalog operation. Fixed-function and reproducible: no arbitrary hadolint flags, no caller-supplied config path, no ignore-rule hole, no trusted-registry override, no shell wrapper, no Docker image execution, and no network egress. Lint findings are represented as JSON output instead of failing the op; real invocation errors still fail. Requires hadolint on PATH. Local and no-egress.

API capability pack for bounded Harvest API v2 operations against https://api.harvestapp.com/v2 only. Reads company settings, the current user, clients, projects, tasks, and time entries for daily solo-business time tracking. Writes cover approval-gated client, project, task, and time-entry create/update/start/restart/stop operations for ordinary timesheet setup and cleanup. Enroll a Harvest personal access token or OAuth access token connection as bearer auth; no credential is embedded in the manifest. Each operation requires the Harvest account id as the documented Harvest-Account-Id request header. The pack intentionally excludes invoice/estimate/expense/report APIs, users, deletion, approvals, admin configuration, project assignments, external-reference deletion, and arbitrary API passthrough.

V3 Helm CLI capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local helm CLI ingredient exposes bounded Kubernetes chart operations for readiness, strict chart linting, and local manifest rendering. Project operations run from an explicit project directory cwd supplied at execution time, accept only a trusted relative local chart path, avoid caller-supplied Helm flags, avoid shell wrappers, and never expose install, upgrade, uninstall, rollback, repo, dependency build/update, package, push, pull, registry credentials, kubeconfig, kube-context, namespace, values files, set overrides, cluster validation, or cluster mutation. Lint findings and render diagnostics are returned as inspectable text. Requires helm on PATH.

API capability pack for bounded Help Scout Inbox API v2 operations. Enroll a Help Scout OAuth2 bearer connection named helpscout for https://api.helpscout.net/v2. The pack reads inboxes, folders, conversations, conversation threads, customers, users, teams, tags, and conversation-volume reports, and bundles support workflows for inbox triage, conversation review, customer replies/internal notes, and conversation intake. Writes are approval-gated and limited to creating one conversation, adding one customer reply, or adding one internal note at a time. Deletes, attachment upload/download, tag mutation, custom-field replacement, workflow execution or updates, user provisioning, webhook mutation, Docs API, Beacon/chat APIs, mailbox/admin settings, exports, bulk mutation, and arbitrary Help Scout endpoints are intentionally not exposed. No credential is embedded in the manifest.

Workflow pack for Recued-sent Help Scout public replies. It composes the Help Scout capability pack with a closure ledger: send one public conversation reply through the existing Help Scout approval gate, set a configured Help Scout status such as pending in the same reply, persist only the connection/conversation reply-watch linkage in data.shared, and let a scheduled watcher re-read that exact conversation until Help Scout reports closed/spam or an owner-actionable status such as active/open. This pack does not replace Help Scout Workflows, manual workflows, inbox rules, mailbox/admin settings, webhook automation, native notifications, or helpdesk queue rules; it adds Recued-visible closure state for conversations Recued replied to.

API capability pack for bounded Heroku Platform API operations against https://api.heroku.com only. Enroll a Heroku OAuth or API-token bearer connection named heroku; no credential is embedded in this manifest. The pack reads account metadata, apps, dynos, formations, releases, builds, domains, pipelines, pipeline couplings, teams, spaces, regions, stacks, dyno sizes, and app add-on inventory for deployment operations, runtime investigation, release readiness, rollback review, and infrastructure inventory. Approval-gated writes are limited to creating one app, creating one build from one source blob URL, canceling one build, creating one domain, restarting or stopping selected dynos/formations, scaling one formation, and rolling back one release. The pack intentionally excludes app/domain/team/space/pipeline/add-on deletion, config-var value reads or writes, account mutation/deletion, billing and invoices, OAuth token/client/grant administration, SSH keys, team membership/invitations/permissions, add-on provisioning and plan mutation, private-space networking changes, log-session URL creation, log-drain mutation, app webhooks, ACM mutation, app transfer, arbitrary one-off dyno command creation, and arbitrary Heroku API passthrough.

One-install Hetzner Cloud front door over four bounded domain packs and 17 non-chat, uncached, approval-free read workflows. It inventories all 189 official operations across 151 paths, admits all 177 active operations, and records exactly 12 provider-deprecated exclusions. The official OpenAPI pins https://api.hetzner.cloud/v1 and explicit APIToken Bearer security on every operation. Runtime calls use the origin-only https://api.hetzner.cloud base plus explicit /v1 paths, with path_alias.wire_prefix preserving documentary proof. The selected encrypted token is project-scoped and credentials never enter pack arguments. All 76 request bodies are required bounded body_raw JSON objects. All 167 JSON responses preserve unsafe integers; ten 204 responses claim no body. All 37 exact page/per_page collections walk at the documented maximum of 50 records. Five one-time server and console credential responses remain directly callable but are labeled secret and excluded from workflows. Reads are uncached and require no approval, all mutations are destructive and require approval, and no provider failure is silently retried. Storage Boxes at api.hetzner.com, generic S3 Object Storage, and link-local server metadata are separate origin or transport families rather than silently widened capabilities. Infrastructure resources are not claimed as work-entity Sources.

Hetzner Cloud servers, server actions, images, ISOs, server types, locations, placement groups, and SSH keys. Generated from Hetzner's byte- and hash-locked official OpenAPI 3.1.2 document (9ca6b542a057…) at https://docs.hetzner.cloud/cloud.spec.json. This leaf carries 56 of 177 active operations. Its origin-only https://api.hetzner.cloud base and explicit /v1 wire paths are reconciled to the document by path_alias.wire_prefix. Every operation has explicit APIToken Bearer security; the selected encrypted connection is project-scoped and credentials never become operation arguments. All 76 documented bodies are required bounded verbatim JSON objects. JSON responses preserve unsafe integers and empty 204 responses claim no body. Five one-time credential responses are labeled secret and excluded from reusable workflows. All 37 exact page/per_page collections paginate at the documented maximum of 50 records per request. Reads are uncached and require no approval, every mutation requires approval and is marked destructive, and provider failures receive no hidden retry. No infrastructure resource is misrepresented as a task, note, or user-work project Source.

Hetzner Cloud zones, record sets, DNS actions, pricing, and global action lookup. Generated from Hetzner's byte- and hash-locked official OpenAPI 3.1.2 document (9ca6b542a057…) at https://docs.hetzner.cloud/cloud.spec.json. This leaf carries 27 of 177 active operations. Its origin-only https://api.hetzner.cloud base and explicit /v1 wire paths are reconciled to the document by path_alias.wire_prefix. Every operation has explicit APIToken Bearer security; the selected encrypted connection is project-scoped and credentials never become operation arguments. All 76 documented bodies are required bounded verbatim JSON objects. JSON responses preserve unsafe integers and empty 204 responses claim no body. Five one-time credential responses are labeled secret and excluded from reusable workflows. All 37 exact page/per_page collections paginate at the documented maximum of 50 records per request. Reads are uncached and require no approval, every mutation requires approval and is marked destructive, and provider failures receive no hidden retry. No infrastructure resource is misrepresented as a task, note, or user-work project Source.

Hetzner Cloud networks, firewalls, load balancers, floating IPs, primary IPs, and their asynchronous actions. Generated from Hetzner's byte- and hash-locked official OpenAPI 3.1.2 document (9ca6b542a057…) at https://docs.hetzner.cloud/cloud.spec.json. This leaf carries 73 of 177 active operations. Its origin-only https://api.hetzner.cloud base and explicit /v1 wire paths are reconciled to the document by path_alias.wire_prefix. Every operation has explicit APIToken Bearer security; the selected encrypted connection is project-scoped and credentials never become operation arguments. All 76 documented bodies are required bounded verbatim JSON objects. JSON responses preserve unsafe integers and empty 204 responses claim no body. Five one-time credential responses are labeled secret and excluded from reusable workflows. All 37 exact page/per_page collections paginate at the documented maximum of 50 records per request. Reads are uncached and require no approval, every mutation requires approval and is marked destructive, and provider failures receive no hidden retry. No infrastructure resource is misrepresented as a task, note, or user-work project Source.

Hetzner Cloud block volumes, certificates, issuance retries, and resource-scoped asynchronous actions. Generated from Hetzner's byte- and hash-locked official OpenAPI 3.1.2 document (9ca6b542a057…) at https://docs.hetzner.cloud/cloud.spec.json. This leaf carries 21 of 177 active operations. Its origin-only https://api.hetzner.cloud base and explicit /v1 wire paths are reconciled to the document by path_alias.wire_prefix. Every operation has explicit APIToken Bearer security; the selected encrypted connection is project-scoped and credentials never become operation arguments. All 76 documented bodies are required bounded verbatim JSON objects. JSON responses preserve unsafe integers and empty 204 responses claim no body. Five one-time credential responses are labeled secret and excluded from reusable workflows. All 37 exact page/per_page collections paginate at the documented maximum of 50 records per request. Reads are uncached and require no approval, every mutation requires approval and is marked destructive, and provider failures receive no hidden retry. No infrastructure resource is misrepresented as a task, note, or user-work project Source.

HiBob attendance summaries and entries, clock operations, projects, clients, and project tasks. Generated from HiBob's complete callable outbound surface in the official machine-readable endpoint index: each route is checked against its own official embedded OpenAPI fragment, with raw page and extracted-contract hashes retained in the audit fixture. Inbound webhook payload pages are recorded separately rather than misrepresented as callable operations. A single openapi_source is intentionally omitted because HiBob publishes separate Markdown-wrapped fragments rather than one fetchable OpenAPI document; pinning one fragment would falsely claim coverage for the rest. Reads are uncached and permission-scoped; sensitive HR, compensation, banking, document, report, performance, and hiring reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation is grant-off and approval-gated. JSON unsafe integers remain exact strings. No work-entity Source is declared because the official task and project contracts do not yet prove both a mandatory stable identity and a mandatory version signal.

HiBob document folders, employee document inventories, URL-based uploads, and document deletion. Generated from HiBob's complete callable outbound surface in the official machine-readable endpoint index: each route is checked against its own official embedded OpenAPI fragment, with raw page and extracted-contract hashes retained in the audit fixture. Inbound webhook payload pages are recorded separately rather than misrepresented as callable operations. A single openapi_source is intentionally omitted because HiBob publishes separate Markdown-wrapped fragments rather than one fetchable OpenAPI document; pinning one fragment would falsely claim coverage for the rest. Reads are uncached and permission-scoped; sensitive HR, compensation, banking, document, report, performance, and hiring reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation is grant-off and approval-gated. JSON unsafe integers remain exact strings. 3 binary multipart upload routes are explicitly excluded; URL-based document uploads remain available. No work-entity Source is declared because the official task and project contracts do not yet prove both a mandatory stable identity and a mandatory version signal.

HiBob employment and work history, compensation, equity, variable payments, training, bank accounts, and custom tables. Generated from HiBob's complete callable outbound surface in the official machine-readable endpoint index: each route is checked against its own official embedded OpenAPI fragment, with raw page and extracted-contract hashes retained in the audit fixture. Inbound webhook payload pages are recorded separately rather than misrepresented as callable operations. A single openapi_source is intentionally omitted because HiBob publishes separate Markdown-wrapped fragments rather than one fetchable OpenAPI document; pinning one fragment would falsely claim coverage for the rest. Reads are uncached and permission-scoped; sensitive HR, compensation, banking, document, report, performance, and hiring reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation is grant-off and approval-gated. JSON unsafe integers remain exact strings. No work-entity Source is declared because the official task and project contracts do not yet prove both a mandatory stable identity and a mandatory version signal.

HiBob goal metadata and cycles, goal and key-result search, creation, progress updates, and deletion. Generated from HiBob's complete callable outbound surface in the official machine-readable endpoint index: each route is checked against its own official embedded OpenAPI fragment, with raw page and extracted-contract hashes retained in the audit fixture. Inbound webhook payload pages are recorded separately rather than misrepresented as callable operations. A single openapi_source is intentionally omitted because HiBob publishes separate Markdown-wrapped fragments rather than one fetchable OpenAPI document; pinning one fragment would falsely claim coverage for the rest. Reads are uncached and permission-scoped; sensitive HR, compensation, banking, document, report, performance, and hiring reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation is grant-off and approval-gated. JSON unsafe integers remain exact strings. No work-entity Source is declared because the official task and project contracts do not yet prove both a mandatory stable identity and a mandatory version signal.

HiBob job openings, candidates and qualifications, applications, job ads, interviews, evaluations, and offers. Generated from HiBob's complete callable outbound surface in the official machine-readable endpoint index: each route is checked against its own official embedded OpenAPI fragment, with raw page and extracted-contract hashes retained in the audit fixture. Inbound webhook payload pages are recorded separately rather than misrepresented as callable operations. A single openapi_source is intentionally omitted because HiBob publishes separate Markdown-wrapped fragments rather than one fetchable OpenAPI document; pinning one fragment would falsely claim coverage for the rest. Reads are uncached and permission-scoped; sensitive HR, compensation, banking, document, report, performance, and hiring reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation is grant-off and approval-gated. JSON unsafe integers remain exact strings. No work-entity Source is declared because the official task and project contracts do not yet prove both a mandatory stable identity and a mandatory version signal.

HiBob job profiles, roles, families, family groups, and their metadata. Generated from HiBob's complete callable outbound surface in the official machine-readable endpoint index: each route is checked against its own official embedded OpenAPI fragment, with raw page and extracted-contract hashes retained in the audit fixture. Inbound webhook payload pages are recorded separately rather than misrepresented as callable operations. A single openapi_source is intentionally omitted because HiBob publishes separate Markdown-wrapped fragments rather than one fetchable OpenAPI document; pinning one fragment would falsely claim coverage for the rest. Reads are uncached and permission-scoped; sensitive HR, compensation, banking, document, report, performance, and hiring reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation is grant-off and approval-gated. JSON unsafe integers remain exact strings. No work-entity Source is declared because the official task and project contracts do not yet prove both a mandatory stable identity and a mandatory version signal.

HiBob learning-provider registration, training-content synchronization, archival, and xAPI statements. Generated from HiBob's complete callable outbound surface in the official machine-readable endpoint index: each route is checked against its own official embedded OpenAPI fragment, with raw page and extracted-contract hashes retained in the audit fixture. Inbound webhook payload pages are recorded separately rather than misrepresented as callable operations. A single openapi_source is intentionally omitted because HiBob publishes separate Markdown-wrapped fragments rather than one fetchable OpenAPI document; pinning one fragment would falsely claim coverage for the rest. Reads are uncached and permission-scoped; sensitive HR, compensation, banking, document, report, performance, and hiring reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation is grant-off and approval-gated. JSON unsafe integers remain exact strings. No work-entity Source is declared because the official task and project contracts do not yet prove both a mandatory stable identity and a mandatory version signal.

One-install Freshdesk suite with 232 of 234 unique documented operations from the hash-locked official API reference. The 25-operation compatibility root preserves all four existing workflows, while four bounded dependency packs expose ticketing and collaboration, people and companies, knowledge and community, and administrative automation. Two CSV import routes fail closed because the current REST transport cannot encode multipart file parts. The official HTML is generation evidence rather than an OpenAPI pin; all reads are uncached and require no approval, every new mutation is approval-gated, JSON request gaps use operation-scoped body_raw, documented pagination is bounded, and JSON integers are parsed losslessly.

API capability pack for bounded Front Core API operations against https://api2.frontapp.com only. Enroll a front connection as a bearer token or OAuth bearer token; no credential is embedded in this manifest. The pack reads token identity, teammates, teams, inboxes, channels, contacts, accounts, conversations, messages, comments, tags, links, statuses, rules, views, custom fields, knowledge bases, knowledge base articles/categories, and message templates for daily shared-inbox, support, and customer-ops workflows. It adds a read-only, cursor-walking task Source for conversation work and bundles a scheduled inbox triage digest, an AI-assisted conversation investigation brief, an approval-gated customer reply workflow, and an always-confirm conversation status workflow. Approval-gated writes are limited to contact/account maintenance, account-contact membership, notes, conversation creation/update/assignment/replies/comments/followers/tags/reminders/seen status, tag and link maintenance, knowledge base content/category/article updates, and message-template maintenance. Conversation updates are always-confirm destructive operations because the same endpoint accepts deleted and spam statuses. Permanent entity-delete endpoints, attachment downloads/uploads, analytics exports/reports, custom-channel inbound/imported message ingestion, inbox/channel/admin permission changes, teammate/group/team provisioning, webhooks, application triggers, rule automation mutation, signature administration, shifts/time off, bulk imports, and arbitrary Front endpoints are intentionally not exposed.

Workflow pack for Recued-sent Front customer replies. It composes the Front capability pack with a reopen ledger: send one customer reply through the existing Front approval gate, persist only the connection/conversation/event-baseline linkage in data.shared, and let a scheduled watcher re-read that exact conversation and latest events until Front reports archived/spam/trashed/deleted, a resolved ticket category, or a newer owner-actionable event such as inbound, reopen, or delivery error. This pack does not replace Front Rules, reminders, time-goal rules, required tagging, native notifications, inbox routing, webhooks, application triggers, or teammate workflows; it adds Recued-visible closure/reopen state for conversations Recued replied to.

V3 bounded GitHub CLI read capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local gh CLI ingredient exposes fixed operations for client readiness, GitHub.com auth status, repository summary, issue list/view, pull request list/view, and latest release metadata. Remote operations require approval because they use the executor's existing gh configuration and authentication, contact GitHub.com, and can reveal private repository metadata, issue/PR bodies, labels, authors, release metadata, account names, token scopes, or network path. The pack scopes repository selectors to github.com/{owner}/{repo}, pins JSON field lists, caps list limits at 100, and exposes no gh api, create/edit/delete/merge/comment/review commands, web browser launch, arbitrary jq/template expressions, arbitrary host selection, caller-supplied gh flags, environment override, stdin, output-file write, or shell wrapper. Requires gh on PATH and an appropriate GitHub CLI authentication state for private resources.

V3 deterministic PDF rendering and compaction capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local Ghostscript CLI ingredient exposes readiness, bounded PDF compaction through pdfwrite, and first-page PNG rendering. Fixed-function and reproducible: the executor materializes the source PDF and owns the throwaway output directory, while Ghostscript writes fixed output files that are captured as result.file_ref. Write-tier but approval=never: Ghostscript writes only under an engine-managed output dir, runs with -dSAFER, exposes no arbitrary flags, no PostScript snippets, no password argument, no printer routing, no URL fetch, and never streams PDF bytes through op-step values. Requires the gs binary on PATH (Debian/Ubuntu: apt install ghostscript; macOS: brew install ghostscript). Local and no-egress. Use qpdf for structural PDF rewrites/linearization; use Ghostscript here for raster previews and lossy/loss-aware pdfwrite compaction.

V3 bounded local Git repository insight pack. By-value connector composition (service_kind=cli, no separate ingredient): one local git CLI ingredient exposes bounded project operations for readiness, repository status, changed-file rows, recent commit history, and tracked working-tree patches. Repo operations run from one explicit repository directory cwd supplied at execution time and use fixed catalog operations. Bundles scheduled recipes for a daily repo brief and a work-hours dirty-tree watch, so users can install the pack and immediately wire useful recurring Git checks. The pack never runs arbitrary git subcommands, never invokes a shell, never talks to remotes, and never exposes fetch/pull/push/clone. Path-based by design: the user points at a trusted local repository path. Requires git on PATH (Debian/Ubuntu: apt install git; macOS: git is commonly installed with developer tools). Local and no-egress.

V3 deterministic no-index diff capability pack. By-value connector composition (service_kind=cli, no separate ingredient): the local git CLI compares two source files with git diff --no-index and writes a patch file via the file.diff_no_index catalog operation. Fixed-function and reproducible: the executor materializes an ordered file_ref array into discrete argv elements, owns the throwaway output directory, git writes a fixed diff.patch result, and exit codes 0 (no differences) and 1 (differences found) are both successful. Requires git on PATH (Debian/Ubuntu: apt install git; macOS: git is commonly installed with developer tools). Local and no-egress.

One-install GitBook front door over five bounded domain packs and eleven operating workflows. It admits all 333 user-token JSON or bodyless operations from the current 355-operation official OpenAPI contract. The explicit exclusions are 17 internal, staff, integration, or installation-token-only routes and five SSE streaming routes that the static JSON REST composition cannot represent. Coverage includes organizations, members and permissions, spaces and page content, change requests and comments, published sites, analytics and content intelligence, integrations, and hosted OpenAPI specifications. A documentary read-only note Source mirrors top-level pages from one configured space, hydrates every listed page by id, and uses hash-only change detection because the page union exposes no mandatory version field. Enroll a GitBook personal access token as a bearer credential and store the Source target space id in connection config as space_id. Reads are uncached and marked sensitive-read except the Source list/read pair; all mutations are grant-off and require approval every run. The five SSE endpoints remain available through GitBook's native SDK rather than this JSON pack.

GitBook spaces, current and historical page trees, documents, files, search, comments, change requests, reviews, Git Sync, and import operations. Generated from GitBook's hash-anchored official OpenAPI 3.1 contract at the fixed https://api.gitbook.com/v1 base. Enroll a personal access token as a bearer credential. Every ordinary read is uncached and marked sensitive-read; only the installed read-only top-level-page Source list/read pair is unmarked. Every mutation is grant-off and requires approval every run. Unsafe plain JSON integer literals are preserved as exact decimal strings.

GitBook site context, scans, findings, topics, questions, analytics, and non-streaming organization intelligence operations. Generated from GitBook's hash-anchored official OpenAPI 3.1 contract at the fixed https://api.gitbook.com/v1 base. Enroll a personal access token as a bearer credential. Every ordinary read is uncached and marked sensitive-read; only the installed read-only top-level-page Source list/read pair is unmarked. Every mutation is grant-off and requires approval every run. Unsafe plain JSON integer literals are preserved as exact decimal strings.

GitBook organizations, collections, members, invites, teams, permissions, SSO, translations, glossary, and user operations. Generated from GitBook's hash-anchored official OpenAPI 3.1 contract at the fixed https://api.gitbook.com/v1 base. Enroll a personal access token as a bearer credential. Every ordinary read is uncached and marked sensitive-read; only the installed read-only top-level-page Source list/read pair is unmarked. Every mutation is grant-off and requires approval every run. Unsafe plain JSON integer literals are preserved as exact decimal strings.

GitBook integrations, installations, integration events, URL resolution, hosted OpenAPI specifications and versions, and system metadata operations. Generated from GitBook's hash-anchored official OpenAPI 3.1 contract at the fixed https://api.gitbook.com/v1 base. Enroll a personal access token as a bearer credential. Every ordinary read is uncached and marked sensitive-read; only the installed read-only top-level-page Source list/read pair is unmarked. Every mutation is grant-off and requires approval every run. Unsafe plain JSON integer literals are preserved as exact decimal strings.

GitBook published sites, structure, sections, spaces, customization, publishing auth, redirects, share links, permissions, channels, MCP servers, and advertising operations. Generated from GitBook's hash-anchored official OpenAPI 3.1 contract at the fixed https://api.gitbook.com/v1 base. Enroll a personal access token as a bearer credential. Every ordinary read is uncached and marked sensitive-read; only the installed read-only top-level-page Source list/read pair is unmarked. Every mutation is grant-off and requires approval every run. Unsafe plain JSON integer literals are preserved as exact decimal strings.

Workflow pack for Recued-created GitHub issues. It composes the GitHub capability pack with a closure ledger: create one owner-approved issue in one repository, persist only the connection/repository/issue linkage in data.shared, and let a scheduled watcher re-read that exact issue until GitHub reports it closed. This pack does not replace GitHub issue state controls, issue views, project boards, milestones, native notifications, webhooks, pull request review, or general issue reporting; it adds Recued-visible closure state for issues Recued created.

Workflow pack for Recued-created GitHub issue comments. It composes the GitHub capability pack with a closure ledger: add one owner-approved Markdown comment to an existing GitHub issue, persist only the connection/repository/issue/comment linkage in data.shared, and let a scheduled watcher re-read that exact issue until GitHub reports it closed. This pack does not replace GitHub issue comments, native notifications, issue state controls, project boards, milestones, webhooks, or general issue reporting; it adds Recued-visible closure state for issue comments Recued created.

Workflow pack that closes the loop between exception-scoped GitHub Actions failures and owner-approved Linear follow-up work. It depends on the GitHub and Linear capability packs, detects one recent unhandled failed workflow run at a time, writes a data.shared proposal, notifies the owner, provides a manual action recipe that either creates the Linear issue and links it back to the GitHub workflow run or dismisses the proposal, and watches created Linear issues until they reach a terminal state. It excludes pull-request-attached runs by default because Linear Reviews already surfaces PR checks and CI-failure notifications. It does not replace GitHub Actions notifications, GitHub workflow logs, rerun controls, branch protection, Linear's GitHub integration, Linear PR automation, or GitHub issue syncing; use it only when those normal paths are insufficient and Recued-visible cross-system closure state is needed.

GitHub Actions workflows, runs, jobs, artifacts, caches, runners, environments, variables, and organization or repository policy. Generated from GitHub's immutable first-party 2026-03-10 OpenAPI contract; every mutation is grant-off and approval-gated, sensitive reads are marked sensitive-read, JSON integers remain exact, and provider Link pagination is followed within engine caps.

GitHub Actions workflows, runs, jobs, artifacts, caches, runners, environments, variables, and organization or repository policy. Generated from GitHub's immutable first-party 2026-03-10 OpenAPI contract; every mutation is grant-off and approval-gated, sensitive reads are marked sensitive-read, JSON integers remain exact, and provider Link pagination is followed within engine caps.

GitHub Copilot, Copilot Spaces, coding agents, agent tasks, Codespaces, hosted compute, machines, exports, and access policy. Generated from GitHub's immutable first-party 2026-03-10 OpenAPI contract; every mutation is grant-off and approval-gated, sensitive reads are marked sensitive-read, JSON integers remain exact, and provider Link pagination is followed within engine caps.

GitHub Copilot, Copilot Spaces, coding agents, agent tasks, Codespaces, hosted compute, machines, exports, and access policy. Generated from GitHub's immutable first-party 2026-03-10 OpenAPI contract; every mutation is grant-off and approval-gated, sensitive reads are marked sensitive-read, JSON integers remain exact, and provider Link pagination is followed within engine caps.

GitHub issues, pull requests, checks, Projects v2 fields, items, views, comments, reviews, labels, and milestones. Generated from GitHub's immutable first-party 2026-03-10 OpenAPI contract; every mutation is grant-off and approval-gated, sensitive reads are marked sensitive-read, JSON integers remain exact, and provider Link pagination is followed within engine caps.

GitHub issues, pull requests, checks, Projects v2 fields, items, views, comments, reviews, labels, and milestones. Generated from GitHub's immutable first-party 2026-03-10 OpenAPI contract; every mutation is grant-off and approval-gated, sensitive reads are marked sensitive-read, JSON integers remain exact, and provider Link pagination is followed within engine caps.

GitHub low-level Git data, gists, packages, package versions, organization migrations, and user migrations. Generated from GitHub's immutable first-party 2026-03-10 OpenAPI contract; every mutation is grant-off and approval-gated, sensitive reads are marked sensitive-read, JSON integers remain exact, and provider Link pagination is followed within engine caps.

GitHub users, applications, installations, notifications, starring, watching, interactions, reactions, and public activity. Generated from GitHub's immutable first-party 2026-03-10 OpenAPI contract; every mutation is grant-off and approval-gated, sensitive reads are marked sensitive-read, JSON integers remain exact, and provider Link pagination is followed within engine caps.