organization: keep the old stderr prefix on config diagnostics in both spellings

Sol's stage B review (P2): mosaic org config validate|resolve printed
'mosaic org config: ' on refusals and warnings, so a caller moving from
mosaic business validate|resolve lost the byte-level diagnostic contract
in rename design r2. Now only the usage line follows the spelling; every
other stderr line keeps 'mosaic business: '. The B2 test compares a
refusal, a warning and a system config problem unnormalized; it fails
4 of 9 on the old source.
This commit is contained in:
jason.woltje committed 2026-11-09 13:12:53 -06:00
1 parent ee7dbd2332
commit e19db4009c
5 files changed
+36 -22

No files matched your search

+4 -4
View File
@@ -263,10 +263,10 @@ scripts/mosaic org instance set <org> <instance> [--definition <def>] [--vars <f
`scripts/mosaic business validate|resolve|instances|instance|veto` is the old
spelling of these commands, with the same arguments, and it still works. Both
spellings run the same code and give the same status and stdout. The
validate/resolve stderr lines start with the spelling you used
(`mosaic org config: ` or `mosaic business: `), and a usage error prints that
spelling's usage. `scripts/mosaic org validate FILE` is a different command: it
spellings run the same code and give the same status, stdout and stderr.
Only a validate/resolve usage error differs: it prints the usage of the
spelling you used. Every other validate/resolve stderr line, refusals and
warnings included, starts `mosaic business: ` in both spellings. `scripts/mosaic org validate FILE` is a different command: it
checks a draft file by path and prints `valid`.
Reads `businesses/<business>.json` next to the system config