Organize fork changes into concise release notes
Document rev 5 installation and changes since rev 4 and rev 2
docs: explain changes since rev 2 and current fork builds
Add 'What the fork fixes' — the five changes, in plain language The build page says how to build and install the fork, but nothing said what the fork is actually for. This is the one-page answer: the five changes as a table with their PRs, the caveats that matter more than the changelog (auto- resume is unverified against a real restart, and the updater will offer an upstream release that silently undoes all five), and a pointer to the build page.
Add the fork build-and-use guide Covers building from swaplabs/main, the app-identity question (a fork build installs over an existing Orca and its updater points at upstream releases), and an example prompt an engineer can hand to an agent. Home becomes an index pointing at it.
Initial Home page