The output convention is enforced: the shared root owns the common set, and the checkers hold it - #788

…ild gets the terminal

Two tree checkers and two source walks in cmd/internal/cli, each shown red on a fixture: no command
shadows a flag it inherits, by long name or shorthand -- cobra calls the first an override and says
nothing, and panics on the second the first time the command runs; neither is protection, this is
(ruled 2026-09-03) -- none binds a reserved output flag, and every subcommand inherits the four; a root's
set is the shared root's, by usage text; no in-scope package writes to stdout without the sink; nothing
outside cmd/internal/cli imports pkg/result. The checker reads raw flag sets, because cobra's merged
views are what panics. ReservedOutputFlagNames moves here from star, which imports it.

RunInteractive is the seam: an editor or pager the user drives gets the three streams there and nowhere
else, and with no terminal it refuses naming the alternative. config edit and man call it. §10 of the
design records the interaction model ruled 2026-09-03: data children are captured, always; a graph never
needs a TTY; an interactive command asks one question at a time, records every answer into its artifact,
and runs the same unattended.

Invariant 1 over the real tree is COMMITTED RED, by design (776-output-enforcement.md, Requirement 4).
TestNoDirectStdout_InScope reports thirteen writes, all in the shared package itself:

  cmd/internal/cli/config.go:109  fmt.Println   config get
  cmd/internal/cli/config.go:366  fmt.Println   config validate
  cmd/internal/cli/config.go:390  fmt.Println   config validate
  cmd/internal/cli/config.go:392  fmt.Printf    config validate
  cmd/internal/cli/config.go:397  fmt.Printf    config validate
  cmd/internal/cli/config.go:413  fmt.Println   config schema
  cmd/internal/cli/config.go:419  fmt.Println   config path
  cmd/internal/cli/config.go:421  fmt.Println   config path
  cmd/internal/cli/config.go:510  fmt.Printf    config list
  cmd/internal/cli/man.go:171     fmt.Printf    man --install
  cmd/internal/cli/man.go:172     fmt.Println   man --install
  cmd/internal/cli/man.go:173     fmt.Printf    man --install
  cmd/internal/cli/selfinstall.go:188  fmt.Print  the self install prompt

Phase 2 turns it green. #776 phase 1; the plan's Phase 1 is complete.

Refs #776

Claude-Session: https://claude.ai/code/session_01SqQVFZz7AdiLZkGoAcUqRW

…nd the shared commands keep it

NewRootCmd registers the four flags once and owns their options per root; cli.Emit is the one render path,
for the shared config commands and every program alike; addOutputFlags is unexported so no program can
forget it or call it twice. lore, star and writ drop their call, their variable and their emitResult.
devlore-test moves onto the shared root (#757): its run command renders through cli.Emit, its own --store
resolution and its local --dry-run go because the root does both, and its help wraps at COLUMNS=70 like the
other three. The environment prefix maps - to _, so DEVLORE_TEST_* keeps working.

config get, list, path, schema and validate emit results, so -o json works on each; validate's result is a
report {path, present, valid, warnings}; man's install notes and the self install prompt narrate on
stderr. TestNoDirectStdout_InScope, committed red one commit ago on those thirteen sites, is green.

The checker that refuses every shadow of an inherited flag found four on its first run over the tree:
lore onboard --verbose and star devlore test run --dry-run duplicated the root's and now read it; star
devlore model build --model is --base-model and star lint go --config is --golangci-config, because each
meant something else. Star's loader now refuses any flag that shadows a root flag. Every program's root
test calls the shared checkers; writ and devlore-test gain the root test they lacked.

#776 phase 2; the plan's Phase 2 is complete.

Refs #776, #757

Claude-Session: https://claude.ai/code/session_01SqQVFZz7AdiLZkGoAcUqRW

--view table renders one table per epic in the tree's order: ID, Issue, Title, Status (a check when closed)
and a Comment carrying the kind, the parent feature, severity and priority, and any classification fault;
--view tree is the report as it was, and the default. --by thread sections the report by the four threads
in execution order and defaults the state to all; --by epic, the default, is every epic or the one --epic
names; the two are orthogonal. --output markdown|json is the reduced set of
the output convention: markdown for a person, json for the rows every view is built from. A WIP label, if
one is ever used, travels in the comment.

Closes #786

Claude-Session: https://claude.ai/code/session_01SqQVFZz7AdiLZkGoAcUqRW

…e epic's plan complete

Section 14 of the CLI design names the test behind each invariant; the status document's enforcement box
is ticked, the last of the epic's convention boxes. The 740 plan's goals, its Phase 3 writ boxes -- landed
by #774 and unticked since -- and its Phase 5 are ticked, and its status is complete. make docs runs in
this commit's gates. devlore-docs generates lore's and writ's pages only, filed as #787.

#776 phase 3; every phase of the plan is complete.

Refs #776, #740

Claude-Session: https://claude.ai/code/session_01SqQVFZz7AdiLZkGoAcUqRW