Docs: example 07-task-pipeline README shows invalid Go template syntax for .Deps access

[kelos-bot]

🤖 Kelos Agent @gjkim42

Problem

The flow diagram in examples/07-task-pipeline/README.md (line 33) shows:

write-tests (Task, dependsOn: [scaffold])
    │  checks out the same branch
    │  reads scaffold's branch via {{.Deps.scaffold.Results.branch}}

This dot-notation syntax (.Deps.scaffold.Results.branch) is invalid Go template syntax for a map[string]interface{} value. In Go's text/template, dot notation only works for struct fields, not map keys.

Root Cause

The .Deps variable is a map[string]interface{} (see internal/controller/task_controller.go). Accessing map keys requires the index function in Go templates:

{{ index .Deps scaffold Results branch }}

If a user follows the diagram literally (instead of the correct examples below it), their prompt template will silently fall back to the raw prompt string, and the downstream Task will not receive the upstream branch name.

Impact

This is a copy-paste trap. The diagram is the first thing a user reads. If they copy the syntax from the diagram rather than scrolling to the "Key Concepts" section, their pipeline will silently fail to interpolate results.

Fix

Change line 33 of examples/07-task-pipeline/README.md from:

│  reads scaffold's branch via {{.Deps.scaffold.Results.branch}}

to:

│  reads scaffold's branch via {{index .Deps "scaffold" "Results" "branch"}}

This matches the correct syntax already used in:

• examples/07-task-pipeline/pipeline.yaml
• examples/07-task-pipeline/README.md (Key Concepts section, line 56)
• examples/07-task-pipeline/README.md (CLI Equivalent section, lines 119, 122)
• The main README.md (line 385)

[kelos-bot]

🤖 Kelos Agent @gjkim42

Kelos Triage Report

Kind: kind/docs
Priority: priority/backlog — Single-line diagram fix in an example README; correct syntax is already shown in the same file's Key Concepts section
Actor: actor/kelos — Concrete one-line documentation fix with clear before/after and objectively verifiable correctness

Status: STILL VALID

Evidence:

• Line 33 of examples/07-task-pipeline/README.md uses {{.Deps.scaffold.Results.branch}} (dot notation), which is invalid Go template syntax for map[string]interface{} values
• The controller code at internal/controller/task_controller.go:780-794 confirms .Deps is a map[string]interface{}, requiring index for key access
• The template is parsed with Option("missingkey=error") (line 787), so the dot-notation would cause template execution to fail and fall back to the raw prompt string (line 795)
• The correct {{index .Deps "scaffold" "Results" "branch"}} syntax is already used in the same README (line 56, 119, 122) and in pipeline.yaml (line 41, 67)
• No merged PRs or recent commits address this issue

Duplicates found: None found

Recommendation: KEEP OPEN — Fix line 33 to use {{index .Deps "scaffold" "Results" "branch"}} for consistency with the rest of the file