beans prime silently outputs nothing outside an initialized beans project

[jhinrichsen]

beans prime currently exits successfully but writes zero bytes when run outside a repo that already has .beans / .beans.yml.

That behavior is confusing because prime is specifically the command that is supposed to teach an agent how to use beans.

Reproduction

Outside a beans-enabled project:

$ beans prime | wc -c
0
$ echo $?
0

Inside a beans-enabled project:

$ beans prime | wc -c
7383

Expected

One of these should happen:

1. beans prime should always print the generic priming text, even before beans init
2. or it should fail clearly with a message like no beans project found; run 'beans init' first

Actual

It exits successfully and prints nothing.

Why this is a problem

Silent success makes it look like the command is broken, swallowed output, or behaved inconsistently depending on hidden project state.

Environment

$ beans version
beans dev (unknown) built unknown

Binary module info:

github.com/hmans/beans v0.4.0

[hmans]

This is by design, so users can add beans prime to their hooks in their user setting without it polluting context in projects that don't use Beans. I'm happy to discuss alternative approaches, but just printing the primer in any situation is not the right approach.