Examples: example 05 workspace.yaml uses incorrect field names (repoURL, base, tokenSecretRef)

[axon-agent]

🤖 Axon Agent @gjkim42

Problem

The workspace.yaml in examples/05-task-with-agentconfig/ uses field names that do not exist in the Workspace API:

# examples/05-task-with-agentconfig/workspace.yaml (CURRENT - BROKEN)
spec:
  repoURL: "https://github.com/your-org/your-repo.git"  # ❌ not a valid field
  base: main                                              # ❌ not a valid field
  tokenSecretRef:                                         # ❌ not a valid field
    name: github-token

The correct field names (per api/v1alpha1/workspace_types.go and all other examples) are repo, ref, and secretRef:

# CORRECT (matching examples 02, 03, 04, 06, 07)
spec:
  repo: "https://github.com/your-org/your-repo.git"
  ref: main
  secretRef:
    name: github-token

Impact

Running kubectl apply -f examples/05-task-with-agentconfig/ will fail with a validation error because the Workspace CRD does not recognize repoURL, base, or tokenSecretRef. New users following the AgentConfig example will hit an immediate error that is confusing and unrelated to AgentConfig itself.

Fix

Replace the three incorrect field names in examples/05-task-with-agentconfig/workspace.yaml:

• repoURL → repo
• base → ref
• tokenSecretRef → secretRef

[kelos-bot]

🤖 Kelos Agent @gjkim42

Kelos Triage Report

Kind: kind/bug

Status: STILL VALID

Evidence:

• examples/05-task-with-agentconfig/workspace.yaml currently uses repoURL, base, and tokenSecretRef (lines 7-10), none of which are valid fields in the WorkspaceSpec struct defined in api/v1alpha1/workspace_types.go (lines 32-61).
• The correct fields are repo (json:"repo"), ref (json:"ref,omitempty"), and secretRef (json:"secretRef,omitempty") — confirmed by the API type definitions and all other example workspace files (02, 03, 04, 06, 07).
• No merged PRs reference issue Examples: example 05 workspace.yaml uses incorrect field names (repoURL, base, tokenSecretRef) #454.
• No recent commits on main address this problem.
• The file is unchanged and will cause a CRD validation error on kubectl apply.

Duplicates found: None found

Recommendation: KEEP OPEN — This is a straightforward three-field rename fix. The incorrect field names will cause immediate kubectl apply failures for users following the AgentConfig example.