build: scaffold versioning, docs and the packaging pipeline

Adds the layer that makes this a distributable product rather than three
directories:

  VERSION      one sl0ppi version for the whole monorepo
  FORKS.md     what each component is based on, and how to rebase the fork
  Makefile     build / vendor / stage / package, plus dev-box helpers
  packaging/   fetch pinned payloads, assemble an install tree, install it
  docs/        architecture, the rename plan, the roadmap

The self-contained runtime question is settled and verified: pi upstream builds
its own release binary with `bun build --compile`, and a vendored bun runs the
vendored pi dist unmodified, so the tarball carries bun + pi and needs no system
node, npm or rust on the target machine.

packaging/install.sh does a per-user install under ~/.local, never clobbers an
existing config (writes .new alongside, or backs up under --force-config), and
warns loudly when a stock zellij is present -- because until docs/rename.md is
implemented the binary is still zellij underneath and would collide with it.

0 files changed, 0 insertions, 0 deletions