docs(chapter-37): make the README a guide to the whole fork
Chapter: 37 - Reader scaffolding. Plain-English map: Rewrite the README so it explains the fork's thesis, the open-source bets, the full change index, and the way to read this branch's commits as chapters. Why it matters: The branch changes a lot: repo shape, security, CI, Docker, workflows, tests, and docs. A less technical reader needs a map before they walk the history. Principle: Documentation should explain why the work exists, not only how to run it. Precedent borrowed: The fork report itself: repeated community patterns around security, self-hosting, provider choice, workflow portability, database integrity, and testing. Upstream base: willchen96/mike@d39f580. Original local commit: d598c70.
| Repository | amal66/mike |
|---|---|
| Author | Amal <mamalanand3@gmail.com> |
| Authored | |
| Committed | |
| Parents | d2406f43 |
| Stats | 1 file changed , +239 , -50 |
| Part of | Make the README a guide to the fork |
Capture this commit into my fork
Download a Markdown prompt that tells Claude how to port this
exact commit into your working tree. Run it via
claude -p < capture-commit-213ee269.md
from inside the repo you want the change in.