Tags

Tags give the ability to mark specific points in history as being important

  • v0.4.0

    f4a40a3b · Merge feat/backup-unsafe-live-volumes-flag (v0.4 — backup unsafe-live-volumes flag) · 
    ncz v0.4.0

backup --unsafe-live-volumes flag (v0.3 charter parked follow-up)

Operator-facing change:
- 'ncz backup create' gains --unsafe-live-volumes flag. With this flag,
  Podman volumes are exported live without first stopping the owning
  systemd unit. Faster, but risks capturing volumes mid-write. The
  default path quiesces the unit before export and restarts it after.

Library API change (breaking — semver minor bump):
- BackupAction::Create variant gains required unsafe_live_volumes field
- BackupCreateReport, BackupVerifyReport, BackupRestoreReport gain
  unsafe_live_volumes field
- BackupManifest gains unsafe_live_volumes field with #[serde(default)]
  for forward-compat with v0.3.0 archives during deserialization
- All five public types gain #[non_exhaustive] for forward-compat with
  future additive fields
- pub fn manifest() in state::backup retains 2-arg signature as wrapper;
  pub fn manifest_with_options() new for 3-arg path
- pub fn create() in cmd::backup retains 5-arg signature as wrapper;
  pub fn create_with_unsafe_live_volumes() new for 6-arg path

Provenance:
- Archives created with --unsafe-live-volumes are durably tagged in
  BackupManifest, surfaced via verify/restore reports (JSON + text),
  and restore() emits stderr warning when an unsafe archive is being
  restored.

Adversarial-reviewed under PRIMARY DIRECTIVE #4 (Codex review at every
gate): 5 rounds of fix-pass iteration before approve. Built and smoked
on TYPHON x86_64 Linux (rust 1.95.0): 271 unit + 2 integration tests
passing, fmt + clippy -D warnings clean.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

  • v0.3.0

    e564c5bb · chore(ncz): bump version 0.3.0-alpha.3 → 0.3.0 for v0.3.0 final release · 
    ncz v0.3.0

v0.3 charter complete: sessions + backup + cron slice trio.

Slices (all merged to main, all approve-verdict at HEAD):
- sessions {list,show,export,prune}
- backup {create,verify,restore}
- cron {list,add,...}

Each slice survived 4 rounds of adversarial-review iteration before
merging. 267+1 tests on main, fmt+clippy -D-warnings clean.

Adversarial-reviewed under PRIMARY DIRECTIVE #4 (Codex review at
every gate). Built + smoked on ULTRA arm64 Linux Podman.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

  • v0.3.1

    1126b400 · Merge zterm-v0.3.1 (closes Chunk E + F-1/F-3/F-4 delighters) · 
    zterm v0.3.1 - Paradox 4.5/dBASE V TUI + delighters

Closes Chunk E (E-3/E-4/E-7) and adds F-1/F-3/F-4 delighters on top
of the v0.3.0 turbo-vision-4-rust UX foundation.

What is in v0.3.1 (vs v0.3.0):

E-3 finish - all slash commands wired to real CommandHandler
  (workspace, session, theme, model, providers, mcp, memory, help)
E-4 - token usage in status line (TurnChunk::Usage), saturating_add
  to avoid overflow on hostile backend usage payloads
E-7 - braille-dot spinner with 80ms tick during in-flight turns
F-1 - LLM-generated connect-splash sequence on workspace activation,
  cached per-workspace at ~/.zterm/cache/, 24h TTL, fallback to
  local-generated banner
F-3 - welcome-back easter egg on Nth launch (5/10/25/...), randomized
  period-accurate quotes (Turbo Pascal, WordStar, Paradox, dBASE,
  QEMM, Procomm Plus), counter at ~/.zterm/state.toml
F-4 - configurable beep-on-error toggle via /theme beep on|off
  (off by default, respects terminal bell)

Adversarial-review fixes also in this release:
- agent.rs: saturating_add for token math (avoids overflow on
  malformed/hostile backend usage data)
- tui/mod.rs: fail-closed on AppConfig::load errors in workspace
  probe (prior code collapsed any load error to has_multi_workspace
  = false and could enter legacy zeroclaw pairing path with bearer
  token write to wrong backend)

Quality gates:
- cargo fmt --check         clean
- cargo clippy -D warnings  clean
- cargo test focused        cli::tui::tv_ui 37 tests + cli::agent 3 tests pass
  (full --all-targets blocked by macOS sandbox, focused suites cover
  the changed surface)

Adversarial-review (codex-companion gpt-5.5): approve, 0 findings.

Author: Jason Perlow <jperlow@gmail.com>

  • v0.2.0

    123d0e84 · style(ncz): apply cargo fmt to round-2 test blocks · 
    ncz v0.2.0 — credential / provider / model / MCP surface

Adds operator-facing config commands on top of the v0.1.0 device-management
surface. Two adversarial-review rounds; final verdict approve at 123d0e8.

Commands added:
- ncz api {add,remove,list,set}     — /etc/nclawzero/agent-env management
- ncz providers {add,remove,show}   — /etc/nclawzero/providers.d/*.json
- ncz models {list,status,discover} — provider catalog + live /v1/models
- ncz mcp {list,add,remove,show}    — /etc/nclawzero/mcp.d/*.json

Quality gates:
- cargo fmt --check          ✅ clean
- cargo clippy -D warnings   ✅ 0 warnings
- cargo test --all-targets   ✅ 212 unit + 1 CLI integration

Adversarial-review (codex-companion gpt-5.5):
- round 1: 2 findings (HIGH legacy env quote handling, MEDIUM MCP user-flag)
  fixed at 47cde59
- round 2: 2 findings (HIGH parse-error propagation, MEDIUM URL userinfo bypass)
  fixed at 123d0e8
- final: approve, 0 findings — ship verdict

Author: Jason Perlow <jperlow@gmail.com>