Skip to content

Versions and Upgrading

m4bwav edited this page Nov 21, 2026 · 1 revision

Versions

Version Date Changes
0.1.1 2026-11-21 A failed backup --restore-test sets the verdict to restore failed, adds a STOP finding first and exits 2. README gaps filled.
0.1.0 2026-11-21 First release: the skill with five references and tech.py (net, disk, backup with --restore-test, health).

Releases: https://github.com/m4bwav/techwright/releases

Upgrading

In Claude Code:

/plugin marketplace update techwright
/plugin update techwright@techwright

Restart Claude Code afterwards so the new version loads.

From 0.1.0 to 0.1.1

One behaviour changed. With a restore test that cannot find the file, 0.1.0 printed the copy-count verdict and exited 0:

verdict: gaps
copies:
  - {'copy': 'original', 'media': 'this PC', 'offsite': False}
findings:
  - Only 1 copy found; 3-2-1 needs 3.
  - All copies sit on one kind of media; add an external drive or cloud.
  - No off-site copy: fire, theft or ransomware takes everything. Add a cloud backup.
admin_needed:
restore: {'restore_test': 'fail', 'reason': 'usb/nope.txt is not a readable file in the backup'}
exit 0

0.1.1 prints verdict: restore failed, a STOP: restore test failed: ... line first under findings, and exits 2 (Commands shows the full output). A script that checks the exit code of tech.py backup now sees a failed restore. A run with no --restore-test, or with one that gives pass or differs, prints the same as before.

Clone this wiki locally