feat(kit): audit context + artifact leg, driver-agents pin bump (v1.8.0) - #24

🏁 Script executed:

#!/usr/bin/env bash
set -euo pipefail

gh version
if gh help api 2>&1 | grep -q -- '--timeout'; then
  echo "Use the CLI timeout explicitly."
else
  echo "Keep timeout(1) around each gh api call."
fi

Repository: DriverDigital/workflows

Length of output: 281

🏁 Script executed:

#!/usr/bin/env bash
set -euo pipefail

echo "Candidate file:"
fd -a 'claude\.yml$' . | sed 's#^\./##' | head -20

echo
echo "Relevant lines around GitHub API calls:"
FILE="$(fd 'claude\.yml$' templates/github | head -1)"
if [ -n "${FILE:-}" ]; then
  wc -l "$FILE"
  sed -n '240,275p' "$FILE" | cat -n -v
fi

echo
echo "Search for timeout handling in workflow:"
rg -n "TIMEOUT|timeout|gh api|gh graphql|gh api " templates/github/claude.yml || true

echo
echo "Check whether gh help api mentions '--timeout' in help text:"
gh help api 2>&1 | sed -n '1,220p' | grep -n -- '--timeout' || true

Repository: DriverDigital/workflows

Length of output: 4570

🌐 Web query:

GitHub CLI gh api default timeout no timeout documentation

💡 Result:

The GitHub CLI gh api command does not provide a flag or configuration option to explicitly set or disable a request timeout [1][2][3]. The official documentation for gh api includes various flags for controlling headers, methods, pagination, and caching, but it does not mention a timeout parameter [1][3]. Because gh api uses the standard Go net/http client internally [4][5], it relies on the default timeout behaviors of that library or the underlying system environment. There is no supported way to specify "no timeout" via the command line for gh api. If you encounter timeout errors, they are typically handled at the network or system level rather than through the gh interface [6].

Citations:

• 1: https://cli.github.com/manual/gh_api
• 2: https://man.archlinux.org/man/gh-api.1.en.txt
• 3: https://cli.github.com/manual/gh_help_reference
• 4: https://github.com/cli/cli/blob/3ad29588b8bf9f2390be652f46ee4ef75b875b03/api/http_client.go
• 5: https://github.com/cli/cli/blob/5d3c2ba5691f4cb8388710c578eeeadf216eec96/api/client.go
• 6: error using api: Post "https://api.github.com/graphql": net/http: TLS handshake timeout cli/cli#1761

🌐 Web query:

GitHub CLI cli cli 2.96.0 api http_client.go request timeout DialTimeout

💡 Result:

In the GitHub CLI (gh), HTTP request handling—including timeouts and connection behavior—is orchestrated through the api package, specifically utilizing api/http_client.go [1][2][3]. The api/http_client.go file does not define a custom DialTimeout directly within its own logic; instead, it leverages the standard library net/http client via a wrapper provided by ghAPI (the CLI's internal API client library) [1][2]. The NewHTTPClient function initializes this client with various configuration options, such as authentication, logging, and caching [1][4]. When a network connection fails, such as during a dial tcp operation, the error is typically bubbled up from the underlying Go net/http transport [5]. Because the GitHub CLI relies on standard Go HTTP clients, connection-level timeouts (like DialTimeout) and request-level timeouts are governed by the http.Client configuration [6]. Key aspects of how the CLI handles timeouts include: 1. Standard Library Behavior: The http.Client used by the CLI inherits standard Go behavior where a Timeout field (if set) covers the entire request lifecycle, including connection, redirect, and reading the response body [6]. 2. Error Handling: The CLI has evolved to handle timeouts more explicitly to avoid confusing users. For example, recent improvements have introduced specific TimeoutError types or improved error messages to distinguish between genuine timeouts and other failures like authentication issues or 5XX server errors [7][8][9]. 3. Proxy and Network Issues: Many reported "connection timeout" errors in the GitHub CLI are often attributable to local network environments, such as proxy configurations or, in some cases, failures in local keyring/authentication lookups that mimic network failures [7][5]. If you are investigating a specific timeout issue, it is recommended to check the environment for proxy settings or authentication failures, as these are common sources of "i/o timeout" or "dial tcp" errors [7][5].

Citations:

• 1: https://github.com/cli/cli/blob/3ad29588b8bf9f2390be652f46ee4ef75b875b03/api/http_client.go
• 2: https://github.com/cli/cli/blob/5d3c2ba5691f4cb8388710c578eeeadf216eec96/api/http_client.go
• 3: https://github.com/cli/cli/tree/trunk/api
• 4: https://fossies.org/linux/gh-cli/api/http_client.go
• 5: Github api : connection timeout cli/cli#8328
• 6: https://go.googlesource.com/go/+/master/src/net/http/client.go
• 7: gh api silently sends unauthenticated requests when keychain access fails cli/cli#13317
• 8: Add timeout error in gh auth status cli/cli#8337
• 9: codespace: Handle HTTP request retry interruption cli/cli#7846

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== locate file =="
git ls-files | grep -F 'templates/github/claude.yml' || true

echo "== relevant lines =="
if [ -f templates/github/claude.yml ]; then
  nl -ba templates/github/claude.yml | sed -n '220,285p'
fi

echo "== search UFO/UUID and SHOPIFY_AUDIT_CONTEXT usages =="
rg -n "UUID_RE|closingIssuesReferences|SHOPIFY_AUDIT_CONTEXT|bon[sS]ai|Bonsai|uuid=" templates/github/claude.yml .github . 2>/dev/null | head -200

Repository: DriverDigital/workflows

Length of output: 268

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== file excerpt using awk =="
awk '{printf "%6d:%s\n", NR, $0}' templates/github/claude.yml | sed -n '220,285p'

echo "== search UFO/UUID/audit context references =="
grep -n "UUID_RE\|closingIssuesReferences\|SHOPIFY_AUDIT_CONTEXT\|Bonsai\|bosai\|uuid=" templates/github/claude.yml || true

Repository: DriverDigital/workflows

Length of output: 10094

🌐 Web query:

GitHub GraphQL closingIssuesReferences first nodes issue pullRequest query

💡 Result:

The closingIssuesReferences field in the GitHub GraphQL API is a connection that retrieves a list of issues that may be closed by a specific pull request [1][2]. It is available on the PullRequest object and provides a way to programmatically identify linked issues without relying on regex parsing of pull request bodies [3][4]. Example GraphQL Query To fetch the issues closed by a pull request, you can use the following structure [5][6]: query GetClosingIssues($owner: String!, $repo: String!, $prNumber: Int!) { repository(owner: $owner, name: $repo) { pullRequest(number: $prNumber) { closingIssuesReferences(first: 100) { nodes { number title url repository { name owner { login } } } pageInfo { hasNextPage endCursor } } } } } Key Details Connection Type: It returns an IssueConnection [1]. Pagination: As a connection, it supports pagination arguments such as first, last, after, and before [1][2]. Arguments: first/last: Required to limit the number of nodes returned [1]. userLinkedOnly (Boolean): An optional argument that, if set to true, returns only issues that were manually linked to the pull request [1]. Node Fields: You can request various fields for each issue, including number, title, id, url, and repository information [7][8]. This field is commonly used in GitHub Actions and automation scripts (such as those using the GitHub CLI or custom JavaScript workflows) to automate labeling, tracking, or validating pull requests based on the issues they are intended to close [3][6][9].

Citations:

• 1: https://docs.github.com/en/graphql/reference/pulls
• 2: https://docs.github.com/en/enterprise-cloud@latest/graphql/reference/pulls
• 3: Simplify closing-pr.js with closingIssuesReferences GraphQL API mlflow/mlflow#21912
• 4: Support GraphQL closingIssuesReferences and closedByPullRequestsReferences PyGithub/PyGithub#3482
• 5: Expose issues linked-to/closed-by in `gh pr view`? cli/cli#7097
• 6: Add field to retrieve linked issues (closingIssuesReferences) in gh pr view <number>  cli/cli#10529
• 7: https://github.com/cli/cli/blob/trunk/api/query_builder.go
• 8: [gh pr view] Support closingIssuesReferences JSON field cli/cli#10544
• 9: https://github.com/mondeja/pr-linked-issues-action

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.