B2 Files

Declare SPDX license (MIT) in manifest.

Removes the file-destruction-acknowledged pre-flight check, which made delete unusable as documented.

Because swamp does not pass method inputs to checks, the check could only read globalArgs — so it rejected --input allowFileDestruction=true BEFORE execute ever received the flag, while its own error message instructed you to pass exactly that.

The consequence was worse than a self-contradicting message. With the per-run path blocked, the only way to delete anything was to set allowFileDestruction: true permanently on the model — so a check written to prevent accidental destruction was forcing you to arm destruction for good, on a model whose delete can leave a restic repository unreadable with no error until the next restore. It failed on the safe configuration and passed on the dangerous one.

The protection is unchanged. assertDestructionAllowed inside delete and hide still refuses without the acknowledgement; it now simply sees both the method input and the global argument, as it always should have. It also covers hide, which no pre-flight check could ever guard — checks fire only for methods named create/update/delete/action.

Both halves verified against live B2: the per-run acknowledgement now reaches execute, and delete without it still refuses.

Strictly compatible. This can only turn a failing run into a working one — nobody could have depended on delete being blocked, and if you set allowFileDestruction on the model as a workaround it still works, though you can now drop it and acknowledge per run instead. No schema, instance name, method or argument changed.

The test accompanying the removed check asserted its behaviour was correct, so the suite encoded the bug rather than catching it. Its replacement asserts the property that matters — every check applying to delete must pass on a model that has not pre-authorised destruction — and was verified to fail when the check is reintroduced.

First publish of @sntxrr/b2/files — inventory and manage B2 file versions via the Native API v4.

Aggregate scan separates current bytes from the non-current versions a bucket with no hidden-version lifecycle rule pays for forever, plus sync, copy, and gated hide, delete and Object Lock updates.

Live-verified against a real account: a full fleet scan of 2,693,460 versions sized 39.49 GiB of non-current data. That run found and fixed three contract-level defects no mock test caught:

• B2 omits legalHold and fileRetention entirely on buckets without Object Lock, so a zero lock count meant "not reported" rather than "not locked" — lockFieldsAbsentCount now models absent, unreadable and readable as three distinct states.
• sync, delete and update forced a bucket-ID lookup their B2 calls never need when addressed by fileId, locking out bucket-restricted keys without listBuckets.
• copy resolved the destination bucket name after the copy had landed, stranding a completed side effect behind a failed method.

Every version-derived metric is nullable: null means "not measured", never zero. Read the truncated flag before reading any byte total — the default maxPages of 50 caps buckets past roughly 500k versions.