ClickUp Deterministic Local Development

Overview

Keep the fast loop offline while preserving exact provider shapes and a deliberate path to detect real API drift.

Prerequisites

• A transport interface around all ClickUp HTTP calls
• Sanitized fixtures derived from documented v2/v3 schemas, including nulls and errors
• A deterministic clock, fake queue, and optional isolated Workspace for a live read

Tool Discipline

Use Read, Glob, and Grep to inspect the repository, adapters, configuration names, tests, and evidence. Use WebFetch only for current official ClickUp documentation. Use Write or Edit after confirming the target file, Workspace boundary, and requested mode.

Current Contract

• Fixtures preserve string/number/null differences in task and webhook payloads.
• Separate base paths and schemas for v2 and selected v3 operations.
• Mock 429 headers, zero-based task pages, comment cursors, auth codes, and webhook delivery retries.
• No ordinary unit test reads a developer token or creates a ClickUp object.

Authentication

Use a personal token only for accountable individual/testing work or OAuth Authorization Code for a user-facing integration. Inject the token server-side through a governed secret reference, send it in Authorization, verify authorized Workspace IDs, and never print the token, OAuth client secret, or webhook secret.

Instructions

1. Inventory direct HTTP calls and route them through an injectable transport.
2. Create fixtures for identity, Workspace, tasks, pages, Custom Fields, webhooks, errors, and rate headers.
3. Freeze time and IDs; make request order, retry jitter, and queue outcomes deterministic.
4. Test raw-body HMAC verification, redaction, Workspace guards, and partial-write recovery.
5. Add an explicit live-probe command limited to read-only identity/Workspace calls.
6. Run offline tests by default and record any provider drift found by the live probe.

Approval Boundaries

Do not record production responses, use personal work data as fixtures, or enable writes in the default local/test path.

Output

Return fixture provenance, offline coverage, direct-call violations, deterministic test result, live-probe result, and drift. Distinguish simulated success from provider-confirmed evidence.

Error Handling

Examples

The example below is a redacted operator receipt; it contains no task text, member data, credential, or webhook secret.

mode=offline; fixtures=14; network-calls=0; clocks=frozen; hmac-tests=pass; live-probe=skipped

Resources

• Skill-specific official documentation
• OpenAPI specifications
• Authentication
• Rate limits