kelly-jobhuntlisted

# Kelly JobHunt Replace board-and-pray applications with a short, inspectable loop: find the companies worth writing to, find one address that will actually be read, write one email per company, and let the human approve each send. ## Subcommands The desk shows state and takes decisions. Everything it cannot do itself is one of four subcommands, and **the desk always names the next one on screen** — the operator never has to remember which is which. | Invocation | What you do | | --- | --- | | `/kelly-jobhunt setup` | Create or adopt the Busabase Folder and three Bases, then read them back | | `/kelly-jobhunt profile` | Take the user's resume or raw notes, extract a structured profile, ask which job channels to search, and build a typeset PDF resume | | `/kelly-jobhunt research` | Find target companies and their contact addresses, draft one email each, import them | | `/kelly-jobhunt send` | Put the user's own SMTP credentials in the Busabase Vault, rehearse the transport, then send what they approved | | `/kelly-jobhunt` (no argument) | Open the desk and report where things stand | Run them in that order the first time. Afterwards `research` is the one that repeats. `setup` is optional in the sense that the desk provisions lazily on first use, but running it first turns "why is this empty" into one command with an answer. The first app run has two separate gates before that command loop begins: 1. connect Busabase and explicitly select the target Space when the accoun