star adopts the output convention: the shared root, and extension commands as commands - #783

The plan landed with status in-progress because the worktree script was rewritten while it was being run.
A plan that has not been reviewed is a draft; it moves to chartered on review.

Refs #743

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

…lings

Reviewed 2026-09-02. star is the code generator every make target runs through, so the plan carries the
last-known-good process the Makefile documents: build/star.lkg taken before the first edit (done, from
1aaba0f, then `star self install`), retired after the tree builds from source, make regenerate no diff,
make install. Phase 1 is complete.

Checking the install found three collisions with the shared root the survey missed: star registers
version and self itself, and its config group comes from two Starlark extensions. RootConfig gains
post-install and post-uninstall hooks so star's extension install survives the move.

Three rulings, one rule -- the shared route on all four programs, a program's own additions attached
beside it:
  config: the shared set on all four; star's show and sync attach beneath.
  man: the shared `man` is the one route; star's docs man and docs markdown go; docs starlark stays.
  usage text: never on an error, not even a bad flag or an unknown subcommand -- cobra's dump is not
    context-aware; SilenceUsage: true on the shared root, once, for all four programs.

Taking the install also exposed #780, its own worktree.

Refs #743

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

The 2026-09-02 ruling from #743, recorded where configuration is designed: devlore-test, lore, star and
writ carry the same `config` command, the shared root's, and star's show and sync attach beneath it. The
spec gains a "command surface" section stating the ruling, the two sources star's config reads today, and
that `self install` produces each program's default config (#780). The 441 plan gains the status row, the
observation that the surface is uniform before the model beneath it is, and one open question: do show and
sync join the shared set.

Refs #441, #743

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

Nothing imported it: main.go imports cmd/internal/cli, and star's root bound no output flags from either
package. The two comments that named it are corrected. The renderTable it carried had already been promoted
to pkg/result.TableFormatter in #740 phase 4.

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

Refs #743

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

…rulings

The CLI design said star bound its own cmd/star/cli.AddOutputFlags; nothing imported the copy, and star's
root bound no output flags at all. Section 15 still analyzed writ reconcile's one-bool bridge as a live
defect two paragraphs after its own table said writ had none; #774 removed the bridge on 2026-08-31, and the
passage is now history with what pins it. Section 7's domain-rendering example, lore list --format manifest,
went with #779. Sections 2, 9 and 12 and decisions 7-9 now carry the 2026-09-02 rulings:
the shared root's commands are one set on the four programs with a program's additions attached beneath;
no usage text follows any error; man is the one route to man pages. star-extensions.md listed a
cmd/star/cli/selfinstall.go that never existed. The status doc and the 740 epic plan record lore's three
phase-4 boxes as landed in #779 and star's deletion as landed in phase 2. The config status doc gains the
command-surface row, the show/sync question, and the two-source discrepancy; the phase-8 implementation plan's
star-unification item records that the command surface was ruled ahead of it and what the fold adds beneath.

Refs #740, #743, #441

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

…mmands

The hand-built root goes: cli.NewRootCmd supplies the common set, --dry-run and --silent, and config, man,
self and version. star wraps the shared pre-run to copy --dry-run into starruntime.DryRun, refresh its flag
map and point the runtime's status at the one narrator. RootConfig gains post-install and post-uninstall
hooks so star's extension install survives the move; the shared root sets SilenceUsage, so no program prints
the usage block after an error; schema.StarDefaultConfig seeds config.d/star.yaml like the other three.

Three Starlark extension commands bound flags the common set owns. The loader now refuses a reserved name.
A script's return value is its result: Command.Run returns it as JSON-shaped Go and the leaf emits it through
the pipeline. generate takes the provider's package as its one operand -- the files land inside it, so
--source, --output, --write and --gen all go, and --dry-run is the preview; the 30 Makefile recipes follow.
validate returns its report and --format goes with its markdown printers. extract writes both artifacts
and --format goes. Extension commands register in name order, so setup no longer appears twice by chance.

The LKG is retired in this commit's gates: build from source, regenerate with no diff, test, install.

#743 phase 3; the plan's Phase 3 is complete.

Refs #743

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

… stub fails

The two Starlark print handlers narrate through cli.Note, as lore's does, so --silent gates a script's
print() with everything else. docs starlark returns its guide as a result and emits it through the pipeline;
whether a prose result should default to value is logged on #740. The three key leaves, unimplemented until
ADR-040, fail with an error that says so rather than printing a note and exiting 0 -- the plan had classed
them as narration, and the checklist's rule against stubs that report success overrides that.

No fmt.Print or os.Stdout remains in cmd/star outside tests.

#743 phase 4; the plan's Phase 4 is complete.

Refs #743

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

The opposite of hermetic is ambient: a runtime that takes its context from what surrounds it. "Non-hermetic"
named an absence. Eleven lines in six files -- the scripting runtime's banner and its comment, the execution
runtime's note and comment, two test names, the method-classification table, and two plan documents -- now
say ambient, and 2.4-hermeticity-guarantees.md defines the pair once beside hermetic.

#743 phase 5; every phase of the plan is complete.

Refs #743

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