Document expected disk usage growth and pruning behavior for long-running nodes

[autumn-wheezy]

Overview

Operators running base/node over long periods may see disk usage grow steadily, but the repository documentation does not clearly explain expected disk growth patterns, pruning behavior, or storage requirements over time.

Problem Description

Without clear guidance, node operators may:

• underestimate disk requirements for long-running nodes
• be unsure whether disk growth is expected or indicates a misconfiguration
• not know when pruning occurs or how it affects storage usage
• struggle to plan infrastructure capacity correctly

This can lead to unnecessary troubleshooting or unexpected outages due to full disks.

Expected Behavior

• Operators should understand expected disk usage growth.
• Pruning behavior and its impact on storage should be documented.
• Storage planning should be easier and more predictable.

Steps to Reproduce

1. Run base/node continuously for an extended period.
2. Monitor disk usage over time.
3. Observe steady growth without clear documentation explaining expected behavior.

Proposed Solution

• Add a documentation section describing:
  • expected disk usage growth over time
  • which components consume the most disk space
  • whether and when pruning occurs
  • recommended disk sizing for common setups
• Include notes on how configuration choices may affect storage usage.