This resonates. I'm a non-technical founder who works closely with a dev team, and reviewing PRs on GitHub has always felt like being dropped into the middle of a conversation with no context. The "chapters" metaphor is exactly right — when I review a PR I don't need to see every file change, I need to understand the narrative: what changed, why, and in what order it makes sense to read.

Curious: do you see Stage being useful for less technical stakeholders who still need to understand what's being shipped? Or is this primarily aimed at engineer-to-engineer review?