Problem

/ponytail-help currently says:

Default mode = full, auto-active every session.

That is misleading for GitHub Copilot CLI.

Ponytail's own portability docs say Copilot CLI is instruction-tier only, using AGENTS.md, .github/copilot-instructions.md, or ~/.copilot/copilot-instructions.md, with no /ponytail levels or lifecycle hooks. In practice, fresh Copilot CLI sessions do not receive Ponytail session-start context unless /ponytail is invoked manually or the rules are copied into a global instructions file.

Repro

Environment tested:

• GitHub Copilot CLI 1.0.63
• Ponytail plugin 4.4.0

Steps:

1. Install/load Ponytail in Copilot CLI.
2. Invoke /ponytail-help.
3. Note the help text says default mode is full and auto-active every session.
4. Start a brand-new Copilot CLI session without invoking /ponytail.
5. Inspect the new session events/system context, or ask a minimal prompt whether Ponytail instructions are active.

Observed: the new Copilot CLI session has normal Copilot instructions and sessionStart hooks, but no Ponytail instructions / full mode context.

Expected

The help text should qualify the auto-activation claim by host, e.g.:

Auto-active every session on hook-capable hosts such as Claude Code/Codex/OpenCode. GitHub Copilot CLI is instruction-tier only; run /ponytail per session, or copy the rules into ~/.copilot/copilot-instructions.md for always-on behavior.

Why this matters

The current wording makes Copilot CLI users think Ponytail is active when it is not, which changes the assistant's behavior silently.