[VyasGuru]

What

Adds docs/reports/week-2/solution.md, the Week 2 solution section covering the architecture, how each choice addresses the problem, the live migration, verification, and reported results.

Closes #13

Why

The Week 2 case analysis needs a source-backed explanation of how Magic Pocket responds to the scale, cost, performance, control, and durability problems described in #12.

This PR remains a draft while the architecture diagram in #11 is open. The text follows the same component order without taking over the diagram issue.

How to check it

Read docs/reports/week-2/solution.md and compare the architecture walk, migration timeline, and results sections with the issue checklist. Every substantive external claim has a Source Log ID.

Checklist

• Documentation-only change; code tests are not applicable
• Every external claim cites the Source Log
• No new sources are needed
• The requested report output is added
• Issue [Design] Draw the Magic Pocket architecture diagram #11 is merged and the architecture walk is checked against its final diagram

[frectrium]

@VyasGuru the architecture diagram is up in #57 (docs/design/architecture.md). Since this PR depends on it:

1. Check that your walk-through order matches section 1.4 there (blocks, Frontends, Block Index, zones and cells, buckets and volumes, Replication Table, Master, Volume Managers, OSDs, replication, erasure coding, Pocket Watch). Tell me on docs(design): add Magic Pocket and Satchel architecture diagrams #57 if you'd rather I reorder the diagram to match yours.
2. Once docs(design): add Magic Pocket and Satchel architecture diagrams #57 merges, swap the "being produced in issue [Design] Draw the Magic Pocket architecture diagram #11" link for the doc itself and take this out of draft.