[FEATURE] /feedback REMARKS-ONLY

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

The current feedback loop captures ratings and bug reports. It misses the middle ground — observations that are not broken enough to file, but real enough to matter. A user notices a pattern, a friction, a quiet degradation. There is nowhere to put it. So it disappears.

Proposed Solution

Follow-up (after a low score)
"Anything you noticed that wasn't quite a bug — but felt worth saying?"

Proactive (slash command)
/feedback_remarks — Share an observation. Not a bug report. Just something the doctor might want to know.

Alternative Solutions

_No response_

Priority

Low - Nice to have

Feature Category

CLI commands and flags

Use Case Example

Claude Code scores a 1 from me today. Not because something broke.

Two things I would put in /feedback_remarks:

First — reasoning feels intact, but the sharpness is off. A research article I co-write with Claude, normally watertight in 30–45 minutes, is taking 4–6 hours. No errors. No crashes. Just something slower, duller underneath.

Second — when I set up parallel agent teams with MCP and a Gemini API key, Claude sometimes quietly ignores the architecture and runs everything serially, by itself. No warning. I only notice when the clock tells me something went wrong.

Neither is a bug I can file. Both are worth the doctor knowing.

Additional Context

_No response_