v1.4.0 — clearer first steps and storage budget checks

FailTrace 1.4.0 makes the first investigation easier to understand and adds a storage budget check for retained evidence.

• Check accumulated artifacts with failtrace artifacts --max-bytes 1073741824 --json, or Core's inventoryArtifacts({ maxBytes }). A complete inventory exits 0 within budget or 1 over budget; incomplete evidence exits 2. This is a read-only check and does not delete files or impose a write quota.
• Start with a shorter README, a task-based documentation index, and an original animated demo showing failure capture, input reduction and patch verification.
• Keep installation examples, documentation links and demo assets consistent with an offline CI check.

The CLI and all seven MCP tools retain the existing debugging workflows. No runtime dependencies were added.

npx --yes failtrace@1.4.0 demo
npx --yes failtrace@1.4.0 mcp --cwd "/absolute/path/to/your/project"

See the changelog and storage guide. The attached archive and checksum identify the exact release package.