docs: align context help with Agent Context Infrastructure

[moonlight16]

Summary

Update the rossoctl README and context command help to describe the feature as Agent Context Infrastructure.

The command remains rossoctl context.

Why

The existing word “context” can be confused with:

1. an LLM context window containing tokens for a model request; or
2. a rossoctl configuration context selecting a server and namespace.

rossoctl context instead manages resources used by agents, including workspaces, memory, knowledge, and artifacts.

“Memory Context Infrastructure” was considered, but it incorrectly suggests that the feature is limited to memory. “Agent Context Infrastructure” distinguishes the capability from other kinds of context while matching its existing broader scope.

Terminology

• Agent Context Infrastructure: the capability
• Context Service: the backend component
• context: the resource and CLI command

Why the interfaces retain context

“Agent Context Infrastructure” names the overall capability, not an individual resource.

rossoctl context manages concrete context resources. A resource-oriented command is easier to understand and remember than rossoctl aci, which would expose an architectural acronym in the user interface.

Context Service remains the backend component name, leaving room for the broader infrastructure to include additional components over time.

Scope

This is a terminology and help-text change only. It does not rename commands or change API requests or behavior.

Validation

• go test ./cmd
• git diff --check