gentle-ai-provider-defect-report
Trigger: Gentle AI provider defect, report a gentle-ai defect, gentle-ai invocation failure or refusal, provider-defect consent handoff. Classify, ask consent, privacy-scrub, and report or comment on gentle-ai issues.
Try your first task
A source-grounded starter task has not been verified for this skill yet.
SKILL.md
name: gentle-ai-provider-defect-reportdescription: "Trigger: Gentle AI provider defect, report a gentle-ai defect, gentle-ai invocation failure or refusal, provider-defect consent handoff. Classify, ask consent, privacy-scrub, and report or comment on gentle-ai issues."license: Apache-2.0metadata: author: gentleman-programming version: "1.0"Activation Contract
Load from the orchestrator's provider-defect classification stub (orchestrator-prompts.md) only when a Gentle AI invocation produced the failure. This skill owns the complete Gentle AI provider defect handoff: consent, privacy, duplicate lookup, uncertainty, and resume.
Hard Rules
- When it is ours, never offer to switch to, inspect, modify, or directly repair the Gentle AI repository from that workflow. If an upstream envelope offers direct repair, do not silently mutate it: reject it as semantically inadmissible and issue this separate orchestrator-owned handoff envelope.
Decision Gates
Before losslessly relaying any blocking choice envelope, classify its semantic admissibility. The test is what produced the failure, not what the work was doing when it happened. Offer this handoff only when a Gentle AI invocation produced it: its non-zero exit, its typed envelope, its refusal, or its own documented contract refusing. A Gentle AI workflow merely hosting a failure is not enough, because the client runtime carries out the work: a delegated task failing inside that runtime is that runtime's defect even when our contract prescribed the task.
When anything else produced it, there is no report and no handoff. That includes the model provider (context limits reached, rate limits, a refusal to process an input), the client runtime (a session that must be restarted, a crashed or empty sub-agent result, a dispatcher that never dispatched), the environment, and the user's own repository state. Do not name the component you believe is responsible, do not suggest where else to file it, and do not ask. Say plainly what blocked the work in the ordinary conversation, then continue or stop as the workflow dictates. A report system that files other projects' defects stops meaning anything when it files ours.
Pending consent has no response deadline. consent-binding-already-consumed is a local lifecycle outcome, not a Gentle AI provider defect. An unknown consent binding is reportable only when independent evidence proves a fresh, same-session, unconsumed binding was lost. Never infer that evidence from the old combined stale-binding message.
| Situation | Action |
|---|---|
| Anything other than a Gentle AI invocation produced it | No report, no handoff; say what blocked the work and continue or stop |
consent-binding-already-consumed, or an unknown binding without that independent evidence | Not a provider defect |
| A Gentle AI invocation produced it | Run the Execution Steps |
Execution Steps
- Ask the user first, in the active orchestrator conversation language, for explicit consent to report the apparent defect. Present one single-select blocking envelope with exactly three semantic choices in this order. Its exact internal answer tokens are
report_and_continue,continue_without_reporting,stop_here. Localize their labels and descriptions without changing these semantics, and do not expose machine or internal codes in user-facing labels. - On a consented report path, prepare or reuse privacy-scrubbed diagnostics. Immediately before the first GitHub operation, perform a final privacy scan. This scan precedes the definitive lookup, report creation, and occurrence comment. Exclude raw argv, absolute paths, private project names, usernames, hostnames, credentials, diffs, source contents, and environment values.
- Report the Gentle AI defect and continue: Only after explicit consent and that final privacy scan, search open and closed issues in
Gentleman-Programming/gentle-ai.- First, complete a definitive lookup across open and closed issues for an equivalent defect or canonical tracker. Equivalent means the same observable defect and affected contract, backed by concrete evidence rather than title similarity alone; a canonical tracker owns the causal class. A definitive lookup is a completed open+closed lookup with a classifiable result; incomplete, error, or unknown is not definitive.
- Only a definitive lookup may branch to GitHub mutation. If no equivalent exists, create a new automated provider-defect report.
- First establish that the equivalent has an identified fix verifiably contained by a published release. Then determine the installed build and derive its evidence channel only from its build string: the contract's recognized prerelease tags are
-rc.and-main.; every other build is stable. That release is a relevant published fix only when it is in the installed build's evidence channel. A main-only commit, local/source build, unmerged PR, or unsupported assertion is not published-fix evidence, including for prerelease or main builds. - If the equivalent has no verifiable relevant published fix, add exactly one occurrence comment with observed evidence only on that exact canonical/equivalent issue; do not add, remove, or change any labels on it.
- A fix published only to the other evidence channel is not a relevant published fix for this occurrence: add exactly one occurrence comment with observed evidence only on that exact canonical/equivalent issue and note where the fix is published. Do not recommend switching channels; channel choice is the user's. Do not add, remove, or change any labels on that issue.
- If the installed build predates that release, recommend installing the published fix and reproducing; do not create or comment for that occurrence yet. If the installed build demonstrably contains the fix and still reproduces, treat it as a possible regression: reproduction on a build proven to contain that fix; comment on a suitable canonical tracker, or create a linked regression issue when that tracker is unsuitable. Never reopen automatically.
- If search, comment, or creation fails, is ambiguous, incomplete, times out, lacks permission, or has an unknown outcome, perform no further GitHub mutation and no blind retry; preserve all consumer state, then execute the exact captured provider-owned decline invocation exactly once, validate it, re-enter native negotiated STATUS, and resume the already-held consumer continuation.
- Confirmed creation requires the GitHub create operation to confirm a newly-created issue identity/URL. Never infer creation from output text alone. If creation fails, is ambiguous, incomplete, times out, lacks permission, or has an unknown outcome, preserve all consumer state; do not search, comment, update, or retry creation until the exact created issue identity is resolved, then use the uncertainty continuation below.
- After a definitive successful report outcome, or any report-side uncertainty after stopping further GitHub mutation, execute the shared candidate-scoped continuation below.
- Continue without reporting: Perform no GitHub search, write, comment, or label, and no report-side privacy scan is required. Execute the shared candidate-scoped continuation below.
- Stop here: Perform no GitHub operation and no decline invocation; preserve all consumer state and STOP.
- Report the Gentle AI defect and continue: Only after explicit consent and that final privacy scan, search open and closed issues in
- Both continue choices execute that exact captured decline invocation exactly once: use only the exact captured provider-owned
choices[answer="declined"].invocationfrom thegentle-ai.review-integration.consent/v3envelope. Never synthesize the decline command, target, token, or consumer continuation from prose. - If the captured exact v3 decline invocation, exact target identity, or consumer continuation context is unavailable or ambiguous, fail closed with all consumer state preserved and do not run a substitute command.
- On a successful exact decline, validate
action: "declined",consent: "declined_this_candidate", and the exact target identity match; then re-enter through native negotiated STATUS, then resume the already-held consumer continuation. - The result carries no lineage or receipt; ordinary delivery is unmanaged by the candidate choice, and the next candidate asks again.
- Unless the user explicitly asks, do not invoke
gentle-ai review mode disableat clone or global scope or turn RDD off or on within this handoff. - Resume after an installed published fix or an explicit maintainer-authorized, documented native recovery or reset that the runtime contract supports; then re-enter through native status. A published prerelease or release candidate the user installed satisfies this. Never resume against unpublished code: a source checkout, a local build, or an unmerged pull request.
Output Contract
Report observed evidence, not an unconfirmed root cause. Include or reuse sanitized version/build, OS/architecture/client, the operation shape without secrets, bounded attempts and outcomes, failure envelopes, mutation outcome, expected and actual behavior, a minimal reproduction, safe opaque reason/revision identifiers, and preserved-state evidence.
References
assets/orchestrator-prompts.md— Lossless Blocking Prompts (native route, fallback, answer validation) used to present the consent envelope.