append-roadmap-feedbacklisted

# Append Roadmap Feedback Record one descendant discovery as the next append-only record in the parent thread's `roadmap-feedback.md`. You own only this bounded side effect: allocating the next record number, validating the record shape, and appending without disturbing anything already in the file. The caller owns the evidence and the judgment that the discovery matters; you own the numbering, the shape, and the impact gate below. ## Precondition and refusal Act only when the caller supplies all of: - **Parent roadmap reference** — the parent Roadmap thread whose `roadmap-feedback.md` receives the record. - **Source** — the child thread that produced the discovery. - **Affects** — the named future child briefs, shared constraints, overall direction, or a possible new child the discovery bears on. - **Context** — self-contained evidence and the assumption or boundary the discovery challenges. - **Impact** — why later work may need to change. - **Recommendation** — an advisory next action. If any field is missing, refuse, name exactly what is missing, and write nothing. Never fabricate a field to complete a record. ## The impact gate Append only a discovery that bears on one of the Affects categories above. Reject content that is only a local implementation note, a local surprise, or report material with no such cross-child or direction-level bearing — tell the caller that material belongs in the child's own implementation report, and write nothing. A `Recommendation` i