Lanes 1 to 4: the shared root conforms - #890

Closes #795.
Closes #794.
Closes #828.
Closes #884.

Lanes 1 to 4 of #887, the schedule that closes the command line epic. Closes feature #832. Plan: docs/plans/fix/795-shared-root-conformance.md.

Summary

• Lane 1, The shared version command renders text; -o yaml prints Version: lines instead of a result #795. version printed five lines with fmt.Fprintf, so --output yaml and --output json printed the same five lines on every program. It returns a VersionReport through cli.Emit now. --short keeps both spellings.
• Lane 2, The no-direct-stdout walk misses writers that are stdout by another name: cmd.OutOrStdout() #794. The no-direct-stdout walk never considered cmd.OutOrStdout(), which is stdout under another name, so three writ repo sites reached stdout outside the pipeline while the walk stayed green. The walk reports it everywhere but cli.Emit, the one caller; repo add, remove and list emit RepoRegistration records carrying the layer, its root and its state.
• Lane 3, --silent does not suppress the ambient-runtime banner; two stderr lines survive it #828. --silent was still an unparsed string while star loaded its extensions and its runtime reported the module surface. The shared root reads --silent from the raw arguments and installs the narrator before construction, so every program is covered; star's runtime spec carries that narrator rather than defaulting to its own over stderr. --silent does not suppress the ambient-runtime banner; two stderr lines survive it #828's second half, the banner as a DEBUG diagnostic, waits on A diagnostics API for provider developers #507 as that issue states.
• Lane 4, The suite's exit codes are the sysexits set: §9 says 0/1/2, the constants have five gaps, and every failure exits 1 #884. Three sources gave three answers. The constants are now the thirteen Declare-BashScript defines, cli.ExitCode maps cobra's refusals to EX_USAGE, a value --output does not accept is one of them, star exits through cli.ExitCode, and §9 states the table and the mapping rule.

Two things found while working, both recorded

• I broke make build in lane 1: its version-stamp check reads writ version --short, which became json. The Makefile asks for --output value, which is how a scalar reaches a consumer raw (§7). The plan's Files table names the Makefile with the reason.
• TestRepo_BareInvocation_Lists was passing for the wrong reason: it matched layer names inside the help text, so it stayed green after The workflow group on the shared root, groups that take no action, and cmd/internal #885 removed the bare listing. It now asserts what The workflow group on the shared root, groups that take no action, and cmd/internal #885 ruled, that a group prints help.

Test plan

Unit and package tests, make check's gate:

• make vet lint shell-lint complexity verify-ldflags clean; star lint go ./... clean; frontmatter valid; make regenerate produced no diff
• make test green in every package but cmd/internal/lorepackage, which clones the registry over the network and cannot pass on an aircraft connection (TestRegistry_SyncIntegration fails instead of skipping without a network, and its escape hatch calls t.Fatalf where it means t.Skip #888). The commit script asserted that it is the only failure rather than tolerating any.

Installed and exercised on darwin/arm64, build v0.1.0-dev.20260912173102-1-g25fa079c:

• version --output json parses on writ, lore, star and devlore-test; yaml, table, list, csv and value render; none prints nothing
• repo list --output table and --output json report the three registered layers with their roots; --filter state=registered --jq '.[].layer' reaches them
• star --silent version writes 0 bytes to stderr; without the flag, 413
• a bad flag, an unknown command and a bad --output exit 64 on writ, lore and star; config get nosuchkey exits 65; success exits 0

Installed and exercised on linux/arm64, danoble-ud24-1.local, from a bundle of the same build:

• every one of the four checks above, same results
• writ self install on a machine with no prior devlore presence

Convergence, run by the owner:

• writ upgrade → [writ] [✔] Nothing to regenerate.

Not run:

• make test-race and make test-scenario, for the same network reason as TestRegistry_SyncIntegration fails instead of skipping without a network, and its escape hatch calls t.Fatalf where it means t.Skip #888. CI runs both here.

Found on the remote and filed, not this pull request's work

writ self install on a fresh machine creates empty layers/base, team and personal, repo list reads them as registrations, and repo add clones the repository and then refuses, leaving an orphan. Appended as evidence to #840 and #792, which are feature #463's.

Time

Computed by the algorithm of noblefactor-ops#188 at merge.