NanoClaw adds CLI verbs for resolving approval requests

qwibitai/nanoclaw PR #3029 is the primary source for today’s NanoClaw item: “feat: operator approval-resolution verbs for ncl (approve/reject/reject-with-reason).” ClawCharts placed NanoClaw on the assignment desk at rank #6, but the public claim comes from the inspected source cluster, not the medal.

The facts: current baseline resolves to qwibitai/nanoclaw; the observed row showed None seven-day stars, unknown active contributors, unknown commits, and 30213 total stars; GitHub reports 30213 stars, 856 open issues, default branch main, pushed_at 2026-07-12T19:32:29Z; release baseline is v2.1.17 (2026-06-17T14:51:14Z).

What changed: feat: operator approval-resolution verbs for ncl (approve/reject/reject-with-reason). The source is current to 2026-07-12T19:32:38Z. Related/context links inspected for the cluster: qwibitai/nanoclaw PR #3028 — fix: avoid duplicate replies after send_message; qwibitai/nanoclaw PR #3027 — fix(container): relocate TMPDIR off /tmp so onecli CA can't be poisoned into a root-owned dir; qwibitai/nanoclaw issue #3026 — Re-wrap nudge re-runs the model and duplicates replies when the agent already replied via send_message; qwibitai/nanoclaw PR #3025 — fix(container): raise the agent SDK's 32000 output-token cap to the m….

Why it matters: this is trust-boundary work, the sort of plumbing that determines whether agent infrastructure is observable, governable, and recoverable under operator load.

Current: repo/product baseline, releases, PRs, issues, and community/discovery search surfaces were checked. Weak community hits, duplicate package mirrors, ambiguous name collisions, and stale keyword-only matches were rejected rather than promoted.

Caveat: GitHub-source items can describe work in motion rather than shipped product behavior, so this is filed as source-inspected operator news, not a release claim.

Operator context: the primary artifact is qwibitai/nanoclaw PR #3029, titled “feat: operator approval-resolution verbs for ncl (approve/reject/reject-with-reason).” It was selected after comparing the current repo, release baseline, recently updated pull requests and issues, and the public discovery surfaces used for this edition. The claim is deliberately narrow: the source shows current project motion or, for a quiet watchlist, the absence of a stronger fresh public event. It does not turn an unmerged proposal into shipped behavior, and it does not treat the ClawCharts position as evidence for the underlying claim.

Source cluster: qwibitai/nanoclaw PR #3028: fix: avoid duplicate replies after send_message; qwibitai/nanoclaw PR #3027: fix(container): relocate TMPDIR off /tmp so onecli CA can't be poisoned into a root-owned dir; qwibitai/nanoclaw issue #3026: Re-wrap nudge re-runs the model and duplicates replies when the agent already replied via send_message; qwibitai/nanoclaw PR #3025: fix(container): raise the agent SDK's 32000 output-token cap to the m…. These links are grouped because they show the adjacent operator surface around NanoClaw, not because every item is equally important. The primary source carries the headline; supporting links provide comparison, implementation context, or evidence that the selected angle is not an isolated keyword hit. Package mirrors and generic search residue were excluded.

Operational reading: for teams evaluating NanoClaw, the useful question is whether this work changes a trust boundary, control surface, integration seam, or maintenance burden. The current evidence is enough for a watch-or-test decision, not for an unconditional rollout recommendation. Operators should inspect merge or closure state, confirm the behavior against the version they run, and keep the caveat attached until the project’s own shipped baseline catches up. That boundary is dull but useful; infrastructure tends to punish decorative certainty.

Source-inspected operator brief; ClawCharts is assignment context, not claim evidence.