Feedback items

Purpose: Keep each requested outcome from site feedback as one file with a permanent ID, kind, workflow state and sources, so its status can change and be referenced without hunting through dated summaries. Scenario: After an import, triage finds a new post asking for a summary field and writes docs/feedback/items/PF-20260101-F01.txt with the request and the post's URL. A second post asking the same thing adds its URL to that file's Sources: instead of creating another item. When work lands, the commit carries a Feedback: PF-... trailer and updates the item's Workflow and Evidence in the same commit; if it forgets, the next triage run finds the trailer in git log and proposes the update. ./v3 feedback check fails on a malformed file and lists any post shared by two items for review. Sources: triage procedure, record format, item (source unavailable), check (source unavailable), index (source unavailable), command (source unavailable), tests (source unavailable). Boundary: Created in feedback work restart. New feedback arrives through the feedback triage procedure, which proposes before writing; history lists what was folded in and what is not yet reconciled. Site members cannot change status; items live only in the repository, and source posts do not link back to them.