-
Notifications
You must be signed in to change notification settings - Fork 14
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
- Status: Open.#656 In pipefy/ai-toolkit;
- Status: Open.#655 In pipefy/ai-toolkit;
- Status: Open.#654 In pipefy/ai-toolkit;
- Status: Open.#653 In pipefy/ai-toolkit;
- Status: Open.#652 In pipefy/ai-toolkit;
destructiveHint has no stated meaning, and 62% of write tools omit it
documentationDocs, skills, README, or in-repo guides only (no runtime change)Docs, skills, README, or in-repo guides only (no runtime change)questionClarification needed; not yet a confirmed bug or featureClarification needed; not yet a confirmed bug or featureStatus: Open.#645 In pipefy/ai-toolkit;[Bug]: create_ipaas_connection is the only write tool that omits readOnlyHint
bugDefect: incorrect or broken behavior vs documented contractDefect: incorrect or broken behavior vs documented contractgood first issueScoped for a first-time contributor; acceptance criteria are clearScoped for a first-time contributor; acceptance criteria are clearStatus: Open.#644 In pipefy/ai-toolkit;[Bug]: two LLM-provider tools annotate destructiveHint=False against their own documented effect
bugDefect: incorrect or broken behavior vs documented contractDefect: incorrect or broken behavior vs documented contractStatus: Open.#643 In pipefy/ai-toolkit;[Bug]: execute_graphql omits destructiveHint although it gates its own mutations
bugDefect: incorrect or broken behavior vs documented contractDefect: incorrect or broken behavior vs documented contractStatus: Open.#642 In pipefy/ai-toolkit;Errors: business-validation failures return bare "is invalid" (API-bound)
bugDefect: incorrect or broken behavior vs documented contractDefect: incorrect or broken behavior vs documented contractreliabilityCorrectness under failure: retries, idempotency, false errors, resilienceCorrectness under failure: retries, idempotency, false errors, resilienceStatus: Open.Writes: no idempotency key, so retry after ambiguous failure is unsafe (API-bound)
enhancementNew capability or intentional behavior change (not a bugfix)New capability or intentional behavior change (not a bugfix)reliabilityCorrectness under failure: retries, idempotency, false errors, resilienceCorrectness under failure: retries, idempotency, false errors, resilienceStatus: Open.Pipes: description and anyone_can_create_card readable but not writable (API-bound)
enhancementNew capability or intentional behavior change (not a bugfix)New capability or intentional behavior change (not a bugfix)Status: Open.