Docs: CLI reference omits 'agentconfigs' resource type and '--phase'/--all flags from kelos get/delete

[kelos-bot]

🤖 Kelos User Agent @gjkim42

Problem

As a new user following the documentation, I discovered that the CLI reference in both README.md and docs/reference.md is incomplete relative to what the CLI actually supports. Three features are silently absent:

1. kelos get agentconfig is undocumented

Both the README and docs/reference.md describe kelos get as:

kelos get <resource> [name]  List resources or view a specific resource (tasks, taskspawners, workspaces)

But the CLI also supports agentconfig / agentconfigs / ac as a resource type (see internal/cli/get_agentconfig.go). A new user who creates an AgentConfig via kelos create agentconfig has no way to know from the docs that they can list it with kelos get agentconfig.

Similarly, kelos delete agentconfig is implemented but not mentioned anywhere in the CLI reference (the docs show tasks, taskspawners, workspaces only).

2. kelos get task --phase filter is undocumented

The kelos get task command supports a --phase flag for filtering tasks by phase (Pending, Running, Waiting, Succeeded, Failed), implemented in internal/cli/get.go. This flag does not appear in the kelos get flags section of docs/reference.md:

### `kelos get` Flags
- `--output, -o`: Output format (yaml or json)
- `--detail, -d`: Show detailed information for a specific resource
- `--all-namespaces, -A`: List resources across all namespaces

This is particularly useful for monitoring running tasks (kelos get task --phase Running).

3. kelos delete --all flag is undocumented

The kelos delete task, kelos delete workspace, kelos delete taskspawner, and kelos delete agentconfig subcommands all support --all to delete every resource of that type in the namespace. This flag is not mentioned anywhere in the CLI reference.

Impact

These are features a new user would never discover from the docs. They'd either resort to trial-and-error or kubectl directly — defeating the purpose of having a kelos CLI.

Suggested Fix

Update docs/reference.md and README.md:

1. Add agentconfigs to the resource types listed for kelos get and kelos delete
2. Add --phase to the kelos get flags section (task-specific, e.g. --phase: Filter tasks by phase — Pending, Running, Waiting, Succeeded, Failed — kelos get task only)
3. Add --all to a kelos delete flags section (delete all resources of the specified type in the namespace)

[kelos-bot]

🤖 Kelos Agent @gjkim42

Kelos Triage Report

Kind: kind/docs
Priority: priority/important-longterm — Documentation gap for existing features; affects new-user adoption but not urgent and not blocking.
Actor: actor/kelos — Concrete, scoped doc edits to docs/reference.md and README.md; acceptance is objectively verifiable. Note: superseded by duplicates below.

Status: DUPLICATE

Evidence:

• Verified the reported gaps exist on main:
  • kelos get agentconfig is implemented in internal/cli/get_agentconfig.go but docs/reference.md (line 346) lists only tasks, taskspawners, workspaces.
  • --phase flag is registered in internal/cli/get.go:195 (StringSliceVar(&phases, "phase", ...)) but absent from the kelos get Flags section (lines 391–395).
  • --all flag is implemented for task/workspace/taskspawner (internal/cli/delete.go:42,110,178) and agentconfig (internal/cli/delete_agentconfig.go:24) but no kelos delete flags section exists in the reference.
• No merged PRs reference Docs: CLI reference omits 'agentconfigs' resource type and '--phase'/--all flags from kelos get/delete #1048; no commits on main address it.

Duplicates found:

• Docs: 'kelos get tasks --phase' flag and 'kelos get agentconfigs' command undocumented in CLI reference #767 — "Docs: 'kelos get tasks --phase' flag and 'kelos get agentconfigs' command undocumented in CLI reference" — covers items (1) and (2) of this issue verbatim.
• Docs: 'kelos delete --all' and supported resource types undocumented in CLI reference #773 — "Docs: 'kelos delete --all' and supported resource types undocumented in CLI reference" — covers item (3) of this issue verbatim, including the agentconfig resource-type omission for delete.

Together, #767 + #773 fully cover the scope of #1048.

Recommendation: CLOSE as duplicate of #767 and #773. The maintainer may prefer to keep #1048 open if they want a single bundled doc PR; otherwise close and let the two existing issues track the work.