feedback-rejection-flowlisted

# Feedback Rejection Flow This skill loads at the rejection-handling point; rejection detection, correction-record write scope, reuse conditions, and the budget probe stay always-on in the FO contract. ## Feedback Rejection Flow When a feedback stage recommends REJECTED: 1. Read the rejected stage's `feedback-to` target — the stage that receives the fix request, not the reviewer. 2. Read the already-authorized workflow package: rejected snapshot, finding evidence, existing workflow classifications, FO-authorized dispositions, and concrete revise assignment. If the distinct authorization or assignment is missing, hold at the active workflow's review-finding checkpoint; routing is ineligible. 3. Invoke `«context-budget»()`. If the old ensign is over budget or the source is unavailable, shut down and fresh-dispatch; if no probe is declared, proceed to reuse below. 4. Route the authorized package unchanged to the target stage in the same worktree using `«addressable-worker»` when the existing handle is addressable and reuse conditions pass; otherwise shut down and fresh-dispatch. The routed message carries the concrete assignment, not an acknowledgment request or a new classification request. Do not treat the immediate routing response as completion: wait for the reused worker's next `«completion-signal»` when it is on the critical path, and attribute completion by mailbox content, task path, or durable workflow state. 5. After correction completes, wait until the worker entr