B2 Lifecycle And Cost Hygiene

When to use

• The user asks why a B2 bill, bucket, prefix, or egress pattern is growing.
• The user wants lifecycle rules for old versions, hidden files, abandoned multipart uploads, or retention-aware cleanup.
• The user asks to delete stale objects, expire versions, abort uploads, or reduce storage cost.

Byte path

• Object data MUST move directly between the client or workload runner and B2 using presigned URLs, multipart upload URLs, or an external B2/S3 client.
• MUST NOT route object data through the model or MCP server. Cost hygiene uses reports, listings, metadata, lifecycle policies, and aggregate counts rather than object bodies.
• Sample only bounded metadata. Avoid dumping complete large listings into chat; summarize by bucket, prefix, age band, storage class, and owner where available.

Safety gates