--command-profile is documented but has no effect on command surface or execution

[MattDevy]

Summary

--command-profile <serverless|stack|default> is documented in elastic --help as restricting "available commands to a deployment profile". As of v0.1.1 the flag is accepted but has no observable effect: identical command surface and identical execution behavior under all profiles.

Reproducer

$ elastic version
{"version": "0.1.1"}

$ elastic --help 2>&1 | grep -A1 'command-profile'
  --command-profile <name>    restrict available commands to a deployment
                              profile (serverless, stack, default)

# Top-level surface is identical
$ diff <(elastic --command-profile serverless help) <(elastic --command-profile stack help)
# (no diff)

# ES surface is identical (ILM is a stack-only API; serverless should hide it)
$ diff <(elastic --command-profile serverless es help) <(elastic --command-profile stack es help)
# (no diff)

# Execution is not gated either - both profiles produce the same error
$ elastic --command-profile serverless es ilm get-lifecycle --policy demo
Error: unknown option '--policy'

$ elastic --command-profile stack es ilm get-lifecycle --policy demo
Error: unknown option '--policy'

I'd expect, for example, --command-profile serverless to hide ILM, watcher, snapshot, and other stack-only namespaces from --help, or to reject invocations at runtime.

Expected behavior

Either:

• Wire up the filtering so the flag does what --help claims, or
• Mark the flag as a roadmap item / hide it from --help until it lands.

The current state is misleading: users who rely on the help text will assume the flag is doing something and may build automation around a no-op.

Environment

• elastic v0.1.1 on macOS