Local prompts not working in CLI despite documented support

Checks

• I have searched github.com/aws/amazon-q-developer-cli/issues and there are no duplicates of my issue
• I have run q doctor in the affected terminal session
• I have run q restart and replicated the issue again

Operating system

macOS 14.6.1 (23G93)

Expected behaviour

Based on the Amazon Q IDE documentation:
Local prompts should be stored in ~/.aws/amazonq/prompts/ (or similar location)
Prompts should be accessible via @prompt-name syntax
/prompts command should list local prompts alongside MCP prompts

Q generated bug report attached

bug-report-local-prompts.md

Actual behaviour

/prompts list only shows MCP prompts, ignoring local files
@prompt-name returns "Prompt not found" for all local prompts
No error messages or debug information about local prompt loading

Steps to reproduce

Create prompt file: ~/.aws/amazonq/prompts/test-prompt.md
Add content: "You are a helpful assistant."
Run: q chat
Try: @test-prompt
Result: "Prompt test-prompt not found"

Environment

<This will be visible to anyone. Do not include personal or sensitive information>

[q-details]
version = "1.12.3"
hash = "65aa9285fc7ec3716215386a89d3a626500a25a7"
date = "2025-07-03T01:14:12.212107Z (5d ago)"
variant = "full"

[system-info]
os = "macOS 14.6.1 (23G93)"
chip = "Apple M1"
total-cores = 8
memory = "8.00 GB"

[environment]
cwd = "/Users/USER/Projects/mcp-servers"
cli-path = "/Users/USER/Projects/mcp-servers"
os = "Mac"
shell-path = "/Applications/Amazon Q.app/Contents/MacOS/qchat"
install-method = "brew"

[env-vars]
PATH = "/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Users/USER/.local/bin:/Users/USER/.local/bin:/Users/USER/.local/bin"
Q_SET_PARENT_CHECK = "1"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "dev.warp.Warp-Stable"

Inizia leggendo i punti di ingresso della CLI per il caricamento dei prompt e per il comando /prompts, quindi verifica come @prompt-name risolve i nomi dei prompt. L’issue fornisce una riproduzione usando ~/.aws/amazonq/prompts/test-prompt.md; eseguila e confronta il comportamento dei prompt locali con le aspettative documentate. Il lavoro è completato quando i prompt locali compaiono in /prompts e possono essere usati con @prompt-name.