docs: reword the Macroplan definition to be less flat

Lead with the promise-vs-reality tension ("keeps the receipts")
instead of the limp "learning-oriented record of what we committed
to deliver".

CONTEXT.md

@@ -1,11 +1,11 @@
 # Macroplan
 
-A **Macroplan** is a week-granular view of the features we've committed to deliver — a simpler cousin of a Gantt chart whose purpose is not just scheduling but *learning* from how our estimates held up over time.
+A **Macroplan** is a week-by-week plan that keeps the receipts: what we promised to deliver, when it actually landed, and what the gap taught us — a simpler cousin of a Gantt chart whose purpose is not just scheduling but *learning*.
 
 ## Language
 
 **Macroplan**:
-A week-granular plan of the **Features** we've committed to deliver, read as a record of how estimates held against reality.
+A week-by-week plan that keeps the receipts on the **Features** we promised: when each actually landed, and what the gap taught us.
 _Avoid_: Gantt, roadmap, timeline
 
 **Feature**:

README.md

@@ -1,6 +1,6 @@
 # Macroplan
 
-A week-granular, **learning-oriented** view of the features a team has committed to deliver — a simpler cousin of a Gantt chart whose point is not just scheduling but learning from *how our estimates held up over time*.
+A week-by-week plan that keeps the receipts on what a team promised to deliver — a simpler cousin of a Gantt chart whose point is not just scheduling but learning from *how our estimates held up over time*.
 
 Each feature reads left-to-right as a story: where it started, what we first promised, every time it slipped, and when it actually shipped — judged honestly against the **first** estimate, never a moved goalpost.