Skip to content

Diagnose existing Turnstile integrations before provisioning - #108

Closed
irvinebroque wants to merge 2 commits into
mainfrom
codex/turnstile-repair
Closed

Diagnose existing Turnstile integrations before provisioning#108
irvinebroque wants to merge 2 commits into
mainfrom
codex/turnstile-repair

Conversation

@irvinebroque

@irvinebroque irvinebroque commented Sep 5, 2026

Copy link
Copy Markdown
Collaborator

A repair request without a sitekey in the prompt currently falls into widget creation. Discover existing public configuration and handler mappings first, then route to repair, migration, setup, or guarded secret recovery as the request requires.

Repairs preserve existing widgets and secret storage, avoid the Edit-scope auth probe, and leave unrelated CAPTCHA integrations alone. Expired-token recovery also stays within the selected flow instead of invoking the creation probe.

Validation: six offline routing scenarios reviewed as instruction walkthroughs; creation workflow and guarded recovery steps preserved; git diff --check passes. The skill validator reports the same pre-existing references frontmatter incompatibility. No live APIs or real secrets used.

Hosted-prompt companion: cloudflare/cloudflare-docs#33256 (draft).

Independent offline exercise of the combined authorization and repair changes: the agent fixed a form retry defect, verified fresh tokens and reset behavior with Node mocks, and reported unavailable backend validation without account access or an approval stop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant