Split from #74 (documentation accuracy sweep, item 1). The README output-style section claimed all user-facing output goes through internal/ui. #74 narrowed that claim to match reality rather than doing this refactor, because routing these call sites through ui is a behavior change that affects --quiet.
These call sites write plain text directly to stdout, bypassing internal/ui, so they are unstyled, uncolored, and ignore w.Quiet():
internal/cli/database.go — database delete, including its interactive confirmation prompt
internal/vaultik/info.go via v.stdoutf (internal/vaultik/vaultik.go)
internal/vaultik/snapshot_list.go — the snapshot list table
Definition of done
Each emits through internal/ui, or a deliberate exception is recorded for output that must stay machine-plain and scriptable (for example config get values and the --json documents); --quiet is honored where it should be; the README output-style section is updated to state the resulting rule exactly; tests cover the --quiet behavior of the affected commands; make check green.
model: claude-opus-4-8
Split from https://git.eeqj.de/sneak/vaultik/issues/74 (documentation accuracy sweep, item 1). The README output-style section claimed all user-facing output goes through `internal/ui`. #74 narrowed that claim to match reality rather than doing this refactor, because routing these call sites through `ui` is a behavior change that affects `--quiet`.
These call sites write plain text directly to stdout, bypassing `internal/ui`, so they are unstyled, uncolored, and ignore `w.Quiet()`:
- `internal/cli/version.go` — all of `version`
- `internal/cli/config.go` — `config init`/`get`/`set` output
- `internal/cli/database.go` — `database delete`, including its interactive confirmation prompt
- `internal/vaultik/info.go` via `v.stdoutf` (`internal/vaultik/vaultik.go`)
- `internal/vaultik/snapshot_list.go` — the `snapshot list` table
## Definition of done
Each emits through `internal/ui`, or a deliberate exception is recorded for output that must stay machine-plain and scriptable (for example `config get` values and the `--json` documents); `--quiet` is honored where it should be; the README output-style section is updated to state the resulting rule exactly; tests cover the `--quiet` behavior of the affected commands; `make check` green.
model: claude-opus-4-8
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Split from #74 (documentation accuracy sweep, item 1). The README output-style section claimed all user-facing output goes through
internal/ui. #74 narrowed that claim to match reality rather than doing this refactor, because routing these call sites throughuiis a behavior change that affects--quiet.These call sites write plain text directly to stdout, bypassing
internal/ui, so they are unstyled, uncolored, and ignorew.Quiet():internal/cli/version.go— all ofversioninternal/cli/config.go—config init/get/setoutputinternal/cli/database.go—database delete, including its interactive confirmation promptinternal/vaultik/info.goviav.stdoutf(internal/vaultik/vaultik.go)internal/vaultik/snapshot_list.go— thesnapshot listtableDefinition of done
Each emits through
internal/ui, or a deliberate exception is recorded for output that must stay machine-plain and scriptable (for exampleconfig getvalues and the--jsondocuments);--quietis honored where it should be; the README output-style section is updated to state the resulting rule exactly; tests cover the--quietbehavior of the affected commands;make checkgreen.model: claude-opus-4-8