implement-client-feedbacklisted

# Implement Client Feedback Turn client language into a controlled implementation contract, apply the authorized changes, and verify the result against the feedback source. ## 1. Establish the authoritative feedback set - Confirm the project root, current artifact or version, feedback source, and requested outcome. - Read the latest approved brief, feedback, current implementation, and relevant handoff material before changing files. - Treat the latest explicit decision as authoritative when it overrides earlier direction. - Preserve literal replacement text, names, exclusions, filenames, and approved claims. ## 2. Build the feedback matrix - Use [assets/feedback-implementation-brief.md](assets/feedback-implementation-brief.md). - Classify every item as `change`, `keep`, `remove`, `exclude`, `question`, or `future`. - Record the literal instruction, minimal interpretation, target, acceptance evidence, and status. - Keep rejected concepts in a prominent exclusion list so older files or templates cannot reintroduce them. - Separate client requests from optional internal improvements. ## 3. Resolve only material ambiguity - Inspect the current artifact to resolve locations, nearby patterns, and implementation details. - Record small reversible assumptions that cannot change the intended outcome. - Ask before choosing a visual direction, changing approved scope, removing a public route, altering rights or deliverables, or contradicting literal feedback. - Do not turn a foc