Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Publish a surface-neutral client for Cloudflare WordPress provisioning

Open
  • Is something wrong?
#2,080 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript, wordpress
Domain
api, backend, cli

Research direction

Start with parent issue #1970 and the related producer interoperability proof in #1974, then trace the raw HTTP contract described here. Compare the TypeScript client, CLI, Ability projection, and contract-test entry points once they exist; done means one fixture produces matching canonical receipts across all supported surfaces without direct infrastructure access.

Written by the indexing model from the issue text.

Description

Parent: #1970

Goal

Make the same provisioning contract easy to call from WP Build, Studio, CLI, Agents API, ChatGPT, CI, and plain HTTP without embedding product behavior in the Cloudflare runtime.

Scope

  • versioned TypeScript client over artifact staging, create, polling, imports, claims, renewal, and deletion
  • streaming digest computation and bounded artifact upload
  • idempotency-key generation/persistence supplied explicitly by the caller boundary
  • typed operation progress, retry, terminal receipt, and error schemas
  • CLI commands and a generic WordPress Ability/Agents API projection using the same client contract
  • portable examples for service accounts and interactive callers
  • webhook/event adapter contract only after durable queue identities exist

Acceptance criteria

  • Every supported surface uses the same public HTTP schemas and immutable artifact bytes.
  • Clients never require direct R2, D1, Cloudflare account, or Worker deployment access.
  • Retry after timeout converges through the original idempotency key.
  • A caller can resume polling from persisted site/operation URLs after process restart.
  • Secrets are injected by the surrounding surface and never written to artifacts, logs, or receipts.
  • Contract tests run one fixture through raw HTTP, TypeScript client, CLI, and Ability projection and compare receipts byte-for-byte where ordering is canonical.
  • WP Build and Studio producer outputs remain adapter-neutral.

Related

  • #1974 producer interoperability proof

AI assistance

OpenAI GPT-5.6 Sol via OpenCode separated the universal HTTP contract from surface adapters and drafted this client slice with Chris Huber.

Dominant language
TypeScript
Stars
17
Forks
4
Avg merge
1h 39m
Merged PRs (30d)
45

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Automattic/wp-codebox

All issues in Automattic/wp-codebox

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.