docs(rfc): RFC-011 — rename "context" → "profile"

[aaltshuler]

Renames the context concept in RFC-011 to profile.

Why

"context" was borrowed from kubectl, but it now collides with agent/LLM
"context" — a real source of confusion. profile is the established term for
"a named, selectable bundle of config defaults" (AWS-CLI precedent: --profile,
AWS_PROFILE, [profile name]), and reads cleanly as --profile prod /
OMNIGRAPH_PROFILE / profiles: / profile list|show.

Scope

Doc-only — the concept was unshipped (it existed only in RFC-011). No code,
no migration. scope (the resolved addressing target that a profile populates)
is intentionally unchanged — only the named-bundle term is renamed.

All 35 occurrences were the concept (none was prose "in this context"), renamed
case-correctly: --context→--profile, OMNIGRAPH_CONTEXT→OMNIGRAPH_PROFILE,
contexts:→profiles:, current_context→current_profile, headings
Context→Profile.

Verification

scripts/check-agents-md.sh green; all RFC links resolve; zero remaining
"context".

🤖 Generated with Claude Code

Greptile Summary

Renames the "context" concept to "profile" throughout RFC-011 and its index entry in docs/dev/index.md. The concept was unshipped, so this is a pure documentation change with no code or migration impact.

• All 35 occurrences renamed case-correctly: --context→--profile, OMNIGRAPH_CONTEXT→OMNIGRAPH_PROFILE, contexts:→profiles:, current_context→current_profile, headings and prose updated throughout rfc-011-cli-refactoring.md.
• Related repos (omnigraph-ts, omnigraph-ui, omnigraph-cookbooks) carry no stale references to the old term, consistent with the feature being unshipped.
• The scope concept (the resolved runtime target that a profile populates) is intentionally unchanged.

Confidence Score: 5/5

Documentation-only rename of an unshipped concept; no code, config schema, or binary is touched.

Every occurrence of the renamed concept in both changed files has been updated consistently. Related repos carry no stale references. The single prose use of "context" left in docs/dev/index.md (line 88, "requires that context unless…") is correctly untouched — it is ordinary English, not the renamed concept.

No files require special attention.

Important Files Changed

Filename	Overview
docs/dev/index.md	Single-line update to the RFC-011 table entry, replacing "contexts" with "profiles" — correct and complete.
docs/dev/rfc-011-cli-refactoring.md	35 occurrences of the "context" concept (flags, env vars, config keys, headings, prose) uniformly renamed to "profile"; no remaining "context" occurrences in the RFC, and related repos carry no stale references to the old term.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[CLI Command] --> B{Scope resolution}
    B --> |"--server / --cluster / --store"| C[Primitive address]
    B --> |"--profile name\nor OMNIGRAPH_PROFILE"| D[Named profile\nin operator config]
    B --> |"flat defaults"| E[Operator config defaults]
    C --> F{Capability x Scope}
    D --> F
    E --> F
    F --> |"server scope + any/served"| G["Served path\n(HTTP + Cedar policy)"]
    F --> |"cluster scope + direct/control"| H["Direct path\n(privileged, bucket creds)"]
    F --> |"store scope + any/direct"| I["Direct path\n(local-dev / break-glass)"]
    F --> |"local verb"| J["No graph/scope resolved"]

Loading

_{Reviews (1): Last reviewed commit: "docs(rfc): RFC-011 — rename "context" → ..." | Re-trigger Greptile}