dealer-reply-drafterlisted

# Dealer Reply Drafter One dealer reply in hand, one proposed response. Use `../orchestrator/SKILL.md` for a full buying cycle, `../inbox-triage/SKILL.md` for inbox classification, and `../close-day-checklist/SKILL.md` when signing is imminent. ## Private policy and outward offer `WALK_AWAY` (the executable policy key is `walk_away`) is the buyer's INTERNAL maximum OTD. Never disclose that number, a range derived from it, or its meaning in dealer mail, screenshots, filenames, or attachments. No negotiation round changes this rule. Do not describe a number as the buyer's ceiling or hard cap. `authorized_offer` is a separate outward proposal explicitly authorized by the buyer. An internal budget is not authorization to make an offer. The constrained renderer requires its amount to be below `walk_away`; an equal amount is blocked because this workflow never prints the private ceiling. If no offer was approved, ask for a written breakdown without proposing a price. A nonnumeric exit line is enough: "If that does not work, I will continue my search." Store real policy, quotes, message IDs, drafts and attachments only under the private companion data directory resolved by `tools/runtime_paths.py`. Missing private configuration must fail before writing. Never use a repository-relative scratch directory or public template as a runtime record. ## Procedure 1. Read the complete inbound message and relevant thread. Extract the vehicle, sale price, tax, doc, title, registration