Ship the Booster

assembling and shipping

Part of: Resume Bullet Booster

Every piece exists now: the rewrite prompt, the cleanup, the verb check, the number check, the length cap, the validator with retries, and batch handling with a cost estimate. Shipping is wiring them into one command and running it on a real list. When you finish, this build lands in your Portfolio . The whole pipeline, one function Shipping isn't new code, it's the assembly. Read tasks, dedupe, rewrite each with retries, validate, and print a clean resume section: Read it top to bottom and the loop from lesson 1 of the whole track is right there: input (tasks), prompt and call (rewrite), parse (clean), verify (validate), ship (print). Every project in this track is that same skeleton with a different middle. What "done" means here Shipped doesn't mean deployed to the cloud. It means: 1. It runs from a clean start on a whole list, not just your one test task. 2. It handles the messy input, blanks, duplicates, a bullet that fails validation, without crashing. 3. Someone else could paste their tasks in and get usable bullets from your instructions alone. If those three hold, it's a real deliverable, not a demo. It lands in your Portfolio Finishing this final lesson records the build

Challenge: Assemble the Resume Section