Route direct-stdout command output through internal/ui (closes #149)

version, info, remote info, config, and database delete wrote plain text straight to stdout, so they were unstyled and ignored --quiet. Output is now governed by internal/ui in two buckets. Status lines and confirmations (config init, config set, the database delete prompt) go through the ui message methods and are silenced by --quiet. The data a command exists to produce is written plain -- the version/info/remote-info reports, the snapshot list table, config get values, and the --json documents -- and is never suppressed, since a script depends on it and a marker would corrupt a table or document. The database delete confirmation prompt is always shown. Pure-cli commands reach ui through a small commandUI helper.

Model: opus-4-8

internal/vaultik/snapshot_list.go

@@ -114,9 +114,15 @@ func (v *Vaultik) ListSnapshots(jsonOutput bool) error {
 		return encoder.Encode(snapshots)
 	}
 
-	err = v.printSnapshotTable(snapshots)
-	if err != nil {
-		return err
+	// The table is the output this command exists to produce, so it is
+	// written plain (markers would corrupt the columns) to the UI writer's
+	// stdout; --quiet silences it. Reconciliation notes below go through
+	// the UI methods, so their warnings still emit under --quiet.
+	if !v.UI.Quiet() {
+		err = v.printSnapshotTable(snapshots)
+		if err != nil {
+			return err
+		}
 	}
 
 	if remoteErr == nil {