feedback / inbox
§01Send it straight to the bench.
Bugs, feature requests, questions, or a note about what’s broken — this form drops into the same inbox the developer actually reads. Replies go back to the email you provide.
feedback / form
§02The form, routed directly.
feedback / routing.manifest
actionsend feedback or suggestion
channelemail to developer
ticketing_systemnone
autopilotnever
email_usereply only, never shared
feedback / lifecycle.manifest
01_receivedlands in developer inbox
02_triagehuman review, not bot
03_responsesame thread, not canned
04_roadmapshapes next build
05_closureyou see it shipped
feedback / what_happens_next
§03What happens after you hit send.
Every message is read by the developer. No automated triage, no ticket queue — just a direct line to the person who writes the code. Replies come back in the same thread.
§04Ready to send it in.
Every message gets a real reply. The form above goes straight to the developer’s inbox — no ticket system, no chatbot, no queue.
feedback / submit.manifest
destinationdeveloper inbox
reply_guaranteedyes, same thread
accounts_requirednever
statusform ready