bug: API endpoint naming inconsistency — /send vs /prompt confusion

[OneStepAt4time]

Bug Report

Discovered by: Athena (dogfooding — API surface test)
Priority: P3 — UX inconsistency, not breaking

Description

The API has inconsistent naming for prompt-related endpoints:

• POST /v1/sessions accepts a prompt field for the initial prompt
• POST /v1/sessions/:id/send handles follow-up prompts
• POST /v1/sessions/:id/input is an alias for /send
• POST /v1/sessions/:id/prompt → 404 (does not exist)

A user (or agent) who sees prompt in the session creation body will naturally try /prompt for follow-ups. This is a discoverability issue.

Proposed fix (pick one)

1. Add /prompt as an alias for /send — lowest effort, backward compatible
2. Rename the prompt field in session creation to message — consistent with /send
3. Document the distinction clearly in API reference — minimum viable fix

Environment

• Aegis: v0.6.7-preview.1

[aegis-gh-agent]

Resolved by PR #3391 (merged on 2026-05-14).