When a dog process exits with an error it must emit ONE uniform line naming itself, the verb, the URI it was acting on, and the ok64 error code — e.g. sniff: get file://<store>?/beagle#<sha>: KEEPNONE. Today error exits are cryptic and contextless (Error: SNIFFFAIL, Error: BEDOGEXIT, bro: cannot open difff: FILENONE), so the user can't tell which dog failed, on what, doing which verb. This is the general form of BE-002. See Verbs.
The error-exit surface is inconsistent and drops the context a user needs.
MAIN wrapper prints a bare Error: <CODE> with no dog name, no verb, no URI — be difff cascades to Error: BEDOGEXIT / Error: NONE telling you nothing.bro: cannot open difff: FILENONE (no verb/URI, raw code, leaks the dog name the user never typed), sniff: object not found: hex=… keep_err=KEEPNONE (verbose, bespoke), Error: SUBSPARSE (no context at all). Each dog rolls its own.KEEPNONE, SUBSPARSE, GRAFFAIL, POSTCFLCT with no operand context.)
None. The pieces already exist: every dog knows its name (argv[0]), its verb (the parsed cli verb), and its URI/operand (the cli at-URI or the failing operand); ok64 codes already decode to names via ok64str/ron60. They just aren't composed into one line.
One uniform error-exit line, single-sourced, across every dog (be, sniff, keeper, graf, spot, bro, woof, mark, dog).
<dog>: <verb> <uri>: <CODE> — <dog> = argv[0] basename, <verb> = the cli verb (or the projector/scheme for verbless), <uri> = the cli at-URI / failing operand, <CODE> = ok64str(code). Empty fields are elided gracefully (<dog>: <CODE> when no verb/URI).MAIN calls with its cli context — either a PRO.h MAIN hook the dog populates (name/verb/uri) so the wrapper's bare Error: <CODE> becomes the rich line, or a dog/-level DOGFail(cli*, code) every dog's entry funnels through. Format identical everywhere.cannot open, sniff's object not found, the *.dbg chains) into the uniform line, keeping at most one extra detail line where it genuinely helps (e.g. the resolved fs path) — never instead of the uniform line.BEDOGEXIT: the spawn layer (BERun) should relay the child's already-printed line and surface the child's code, not just its exit byte.be difff, be get ?<missing>, a forced KEEPNONE) and assert stderr carries dog + verb + uri + decoded code in the one-line format.
(pending — needs the ruling deferred to from BE-006: single-source the line in the PRO.h MAIN hook each dog populates, vs a dog/-level DOGFail(cli*, code) funnel, vs root-be-only printing with children silenced.)
(audit 2026-07-07: nothing landed — dog/abc/PRO.h:384 still prints the bare Error: <CODE>; no DOGFail/reporter exists anywhere under beagle/; bespoke prints persist, e.g. keeper/WIRECLI.c:87.)
DOGFail(cli*,code) vs
root-be only) — blocks everything below; same ruling closes BE-006.
<dog>: <verb> <uri>: <CODE> (empty fieldselided) at the chosen seam; wire every dog's MAIN exit through it.
cannot open, sniff object-not-found,
keeper/WIRECLI.c:87 unreachable) — one detail line max, never a substitute.
BERun/BEReap (BE.cli.c:393/428) surface the child's line,
not a parent BEDOGEXIT re-print (the BE-006 stacked-error collapse).
be difff, be get ?<missing>, forced KEEPNONE → exactly onestderr line in the uniform format.
same pending ruling).
(pending)