v1.3.0

pdd hatch --no-cwd adopts a pet with nothing bound to it yet, to bind a folder to later — the core already allowed an unbound pet, only the CLI insisted on one up front. A folderless pet answers to no agent source, and a bug that invented a placeholder source id to keep such a pet visible could let a stray agent event drive it into a false "Working" state; that placeholder is gone, so an unbound pet now correctly answers to nothing. Also clarifies what each pet context menu action does.