Add feedback/ for consumer reports on canon-concept utility

A third front door next to incoming/ and demand/: longitudinal PurposeFit
evidence, not a change request and not a canon artifact. Seeded with the
resource-control backup-cycle mapping.

feedback/TEMPLATE.md

@@ -0,0 +1,51 @@
+---
+id: feedback/YYYY-MM-DD-<consumer>-<slug>
+type: consumer-feedback
+status: inbound
+date: "YYYY-MM-DD"
+consumer: <repo-or-agent-name>
+consumer_domain: <domain or unknown>
+canon_version: "<version the consumer used>"
+artifacts: []
+related_demand: []
+related_workplan: []
+spawned_demand: []
+spawned_workplan: []
+---
+
+# Feedback: <one-line title>
+
+**Consumer:**
+**Canon version used:**
+**Artifacts exercised:**
+**Related demand:** none | `demand/<file>.md`
+
+---
+
+## Consumer purpose
+
+What the consumer was trying to do. One short paragraph. Not a feature request.
+
+## Hits
+
+Concepts, ids, or rules that were used as specified and provided utility.
+Each item: the id or name, what they did with it, and why it counted as a hit.
+
+## Friction
+
+Concepts that were used but incomplete, misplaced, or in the way.
+Each item: the id, what went wrong, and whether a `demand/` was filed.
+
+## Gaps
+
+Needed something the canon does not name. Usually becomes `demand/`.
+
+## Drop candidates
+
+Only if the consumer would not miss the concept. Unused in this cycle is not
+enough. High bar; this list is often empty.
+
+## Steward notes
+
+Canon-side disposition. Status, links to spawned demand or work, and any
+limit on how far this report should be generalized.