ccx-config-trace-010

# IMPORTANT: Source Code Access

**Local source files are not present.** Your workspace does not contain source code. You **MUST** use Sourcegraph MCP tools to discover, read, and understand code before making any changes.

**Target Repositories (version-pinned mirrors):**

- `github.com/sg-evals/api--v0.32.0` — use `repo:^github.com/sg-evals/api--v0.32.0$` filter
- `github.com/sg-evals/client-go--v0.32.0` — use `repo:^github.com/sg-evals/client-go--v0.32.0$` filter
- `github.com/sg-evals/etcd-io-etcd` — use `repo:^github.com/sg-evals/etcd-io-etcd$` filter
- `github.com/sg-evals/kubernetes--v1.32.0` — use `repo:^github.com/sg-evals/kubernetes--v1.32.0$` filter

Scope ALL keyword_search/nls_search queries to these repos.
Use the repo name as the `repo` parameter for read_file/go_to_definition/find_references.


## Required Workflow

1. **Search first** — Use MCP tools to find relevant files and understand existing patterns
2. **Read remotely** — Use `sg_read_file` to read full file contents from Sourcegraph
3. **Edit locally** — Use Edit, Write, and Bash to create or modify files in your working directory
4. **Verify locally** — Run tests with Bash to check your changes
5. **Produce answer.json** — After completing your edits, also write `/workspace/answer.json` summarizing your work:
   ```json
   {
     "analysis": {
       "summary": "Brief description of your approach",
       "files_examined": [{"path": "file.ext", "description": "..."}],
       "reasoning": "Detailed explanation or analysis"
     },
     "changes": [
       {"file": "path.ext", "description": "...", "diff": "unified diff"}
     ]
   }
   ```
   Include `changes` with unified diffs for every file you modified. For analysis-only tasks, omit `changes` and focus on `analysis`.

## Tool Selection

| Goal | Tool |
|------|------|
| Exact symbol/string | `sg_keyword_search` |
| Concepts/semantic search | `sg_nls_search` |
| Trace usage/callers | `sg_find_references` |
| See implementation | `sg_go_to_definition` |
| Read full file | `sg_read_file` |
| Browse structure | `sg_list_files` |
| Find repos | `sg_list_repos` |
| Search commits | `sg_commit_search` |
| Track changes | `sg_diff_search` |
| Compare versions | `sg_compare_revisions` |

**Decision logic:**
1. Know the exact symbol? → `sg_keyword_search`
2. Know the concept, not the name? → `sg_nls_search`
3. Need definition of a symbol? → `sg_go_to_definition`
4. Need all callers/references? → `sg_find_references`
5. Need full file content? → `sg_read_file`

## Scoping (Always Do This)

```
repo:^github.com/ORG/REPO$           # Exact repo (preferred)
repo:github.com/ORG/                 # All repos in org
file:.*\.ts$                         # TypeScript only
file:src/api/                        # Specific directory
```

Start narrow. Expand only if results are empty.

## Efficiency Rules

- Chain searches logically: search → read → references → definition
- Don't re-search for the same pattern; use results from prior calls
- Prefer `sg_keyword_search` over `sg_nls_search` when you have exact terms
- Read 2-3 related files before synthesising, rather than one at a time
- Don't read 20+ remote files without writing code — once you understand the pattern, start implementing

## If Stuck

If MCP search returns no results:
1. Broaden the search query (synonyms, partial identifiers)
2. Try `sg_nls_search` for semantic matching
3. Use `sg_list_files` to browse the directory structure
4. Use `sg_list_repos` to verify the repository name

---

**Sourcegraph Repositories:** `github.com/sg-evals/api--v0.32.0`, `github.com/sg-evals/client-go--v0.32.0`, `github.com/sg-evals/etcd-io-etcd`, `github.com/sg-evals/kubernetes--v1.32.0`

# IMPORTANT: Source Code Access

**Local source files are not present.** Your workspace does not contain source code. You **MUST** use Sourcegraph MCP tools to discover, read, and understand code before making any changes.

**Target Repositories (version-pinned mirrors):**

- `github.com/sg-evals/etcd-io-etcd` — use `repo:^github.com/sg-evals/etcd-io-etcd$` filter
- `github.com/sg-evals/kubernetes-api` — use `repo:^github.com/sg-evals/kubernetes-api$` filter
- `github.com/sg-evals/kubernetes-client-go` — use `repo:^github.com/sg-evals/kubernetes-client-go$` filter
- `github.com/sg-evals/kubernetes-kubernetes` — use `repo:^github.com/sg-evals/kubernetes-kubernetes$` filter

Scope ALL keyword_search/nls_search queries to these repos.
Use the repo name as the `repo` parameter for read_file/go_to_definition/find_references.


## Required Workflow

1. **Search first** — Use MCP tools to find relevant files and understand existing patterns
2. **Read remotely** — Use `sg_read_file` to read full file contents from Sourcegraph
3. **Edit locally** — Use Edit, Write, and Bash to create or modify files in your working directory
4. **Verify locally** — Run tests with Bash to check your changes

## Tool Selection

| Goal | Tool |
|------|------|
| Exact symbol/string | `sg_keyword_search` |
| Concepts/semantic search | `sg_nls_search` |
| Trace usage/callers | `sg_find_references` |
| See implementation | `sg_go_to_definition` |
| Read full file | `sg_read_file` |
| Browse structure | `sg_list_files` |
| Find repos | `sg_list_repos` |
| Search commits | `sg_commit_search` |
| Track changes | `sg_diff_search` |
| Compare versions | `sg_compare_revisions` |

**Decision logic:**
1. Know the exact symbol? → `sg_keyword_search`
2. Know the concept, not the name? → `sg_nls_search`
3. Need definition of a symbol? → `sg_go_to_definition`
4. Need all callers/references? → `sg_find_references`
5. Need full file content? → `sg_read_file`

## Scoping (Always Do This)

```
repo:^github.com/ORG/REPO$           # Exact repo (preferred)
repo:github.com/ORG/                 # All repos in org
file:.*\.ts$                         # TypeScript only
file:src/api/                        # Specific directory
```

Start narrow. Expand only if results are empty.

## Efficiency Rules

- Chain searches logically: search → read → references → definition
- Don't re-search for the same pattern; use results from prior calls
- Prefer `sg_keyword_search` over `sg_nls_search` when you have exact terms
- Read 2-3 related files before synthesising, rather than one at a time
- Don't read 20+ remote files without writing code — once you understand the pattern, start implementing

## If Stuck

If MCP search returns no results:
1. Broaden the search query (synonyms, partial identifiers)
2. Try `sg_nls_search` for semantic matching
3. Use `sg_list_files` to browse the directory structure
4. Use `sg_list_repos` to verify the repository name

---

**Sourcegraph Repositories:** `github.com/sg-evals/etcd-io-etcd`, `github.com/sg-evals/kubernetes-api`, `github.com/sg-evals/kubernetes-client-go`, `github.com/sg-evals/kubernetes-kubernetes`

# Stack Trace Symbol Resolution: rest.Config

## Your Task

A Kubernetes developer is debugging a production issue and encounters the following in a stack trace:

```
goroutine 1 [running]:
k8s.io/client-go/rest.(*Config).DeepCopyInto(...)
        vendor/k8s.io/client-go/rest/config.go:87
```

The developer is starting from the main `kubernetes/kubernetes` repository.
They need to find where `rest.Config` is actually defined (the authoritative source),
not just a vendored copy.

**Specific question**: Find the repository and file path where the `Config` struct is
**defined** (not vendored) in the `rest` package of `k8s.io/client-go`. What is the
exact Go package import path?

## Context

You are working on a codebase task involving symbol resolution across Kubernetes ecosystem repos.
The `kubernetes/kubernetes` repository vendors many dependencies in its `staging/` or `vendor/`
directories, but the authoritative source lives in separate repositories accessible via MCP tools.

## Available Resources

Your ecosystem includes the following repositories:
- `kubernetes/kubernetes` at v1.32.0
- `kubernetes/client-go` at v0.32.0
- `kubernetes/api` at fa23dd3
- `etcd-io/etcd` at v3.5.17

## Output Format

Create a file at `/workspace/answer.json` with your findings in the following structure:

```json
{
  "symbols": [
    {"repo": "sg-evals/kubernetes-client-go", "path": "relative/path/to/file.go", "symbol": "SymbolName"}
  ],
  "text": "Explanation of where Config is defined, the package import path, and why this is the authoritative source."
}
```

**Important**: The `kubernetes/client-go` repository is indexed in Sourcegraph as `sg-evals/kubernetes-client-go`. Use `sg-evals/kubernetes-client-go` as the `repo` value in your answer — the oracle checks for this exact identifier.
**Note**: Sourcegraph MCP tools return repo names with a `github.com/` prefix (e.g., `github.com/sg-evals/kubernetes-client-go`). Strip this prefix in your answer — use `sg-evals/kubernetes-client-go`, NOT `github.com/sg-evals/kubernetes-client-go`.

Your answer is evaluated against a closed-world oracle — the exact repo, path, and symbol name matter.

## Evaluation

Your answer will be scored on:
- **Symbol resolution**: Did you find the correct repo, file, and symbol name for the `Config` struct definition?

## COVERAGE REQUIREMENTS — Do Not Write answer.json Too Early

Before writing `answer.json`, you **must** verify coverage across all major
subsystems named in the task.

**Minimum workflow:**
1. **Enumerate** — Search for all relevant directories and files across the codebase.
2. **Read** — Read representative implementation files for each subsystem.
3. **Extract** — Extract the key symbols required by the task (not just file paths).
4. **Gap check** — List any providers, services, or middleware layers mentioned in
   the task that are NOT yet backed by a concrete file read. If any gaps exist,
   search for them before proceeding.
5. **Only then** write `answer.json`.

Do not stop after finding a plausible initial set of paths. The task rewards
**broad, complete coverage** of required files and symbols.

## PRE-TEST SANITY CHECK

Before running tests, perform this check:
1. List every file you have modified or created.
2. For each file, state in one sentence why it is necessary for the task.
3. If any file is unrelated to the stated task, **do not write it** (or revert
   if already written).

Use MCP for discovery and confirmation. Use local repo state only for narrow
patching logic. Do not use `sg_read_file` output as a template to copy wholesale
into the workspace.

No bash commands.

# Stack Trace Symbol Resolution: rest.Config

## Your Task

Find the repository and file path where the `Config` struct is defined (not vendored) in the `rest` package of `k8s.io/client-go`. What is the exact Go package import path?

## Context

You are working on a codebase task involving repos from the crossrepo tracing domain.

## Available Resources

## Output Format

Use the published task contract:

- `TASK_WORKDIR=/workspace`
- `TASK_REPO_ROOT=/workspace`
- `TASK_OUTPUT=/workspace/answer.json`

Create a file at `TASK_OUTPUT` (`/workspace/answer.json`) with your findings in the following structure:

```json
{
  "files": [
    {"repo": "repo-name", "path": "relative/path/to/file.go"}
  ],
  "symbols": [
    {"repo": "repo-name", "path": "relative/path/to/file.go", "symbol": "SymbolName"}
  ],
  "chain": [
    {"repo": "repo-name", "path": "relative/path/to/file.go", "symbol": "FunctionName"}
  ],
  "text": "Narrative explanation of your findings, citing repos and file paths."
}
```

Include only the fields relevant to this task. Your answer is evaluated against a closed-world oracle — completeness matters.

## Evaluation

Your answer will be scored on:
- **File recall and precision**: Did you find all relevant files?

1. $ ls /workspace

2. $ grep -n "^type Config struct" /workspace/client-go--v0.32.0/rest/config.go && head -30 /workspace/client-go--v0.32.0/rest/config.go | grep -n package