Changelog

All notable changes to Flying Jib are documented in this file.

The format is based on Keep a Changelog, and this project aims to follow Semantic Versioning.

[Unreleased]

Phase 3 peer communication (CLI):
- Hyperswarm/Protomux presence + chat for private worlds
- Stdin chat on host/join; /peers command
Standalone packaging:
- npm run make:standalone → single Bare executable (no system Node)
- Flying Squid postinstall patches for static plugin load
Phase 2 private world sharing (core):
- CLI: host (share), join (client tunnel)
- HyperDHT world tunnel with capability header
- fj1. invite encode/decode
- Per-world tunnel key persistence
Phase 1 Bare application scaffold:
- CLI: create, list, start, status
- lib/squid-manager.js — embedded Flying Squid, forced 127.0.0.1
- plugins/fj-bind-guard.js — loopback listen assertion
- Bare interop: bare-node-runtime, engine patches, events/readline shims
Phase 0 documentation and agent governance scaffold:
- living_docs/ — roadmap, progress, status, architecture overview, open questions, changelog
- developer_docs/ — setup, architecture, modules, protocol, build/release, testing, contributing
- user_docs/ — getting started, private/mesh worlds, invites, troubleshooting, FAQ
- agent/ — rules, workflow, security, documentation policy, coding standards, ADRs 0000–0013
Architecture decision: Local Authority + Capability Tunnel + Federated Regions
ADR-0013: Bare/Pear-only runtime; single standalone executables via bare-build; no app-level Node.js
Product name: Flying Jib

Process model: supersede Electron + Node Squid child (ADR-0004) in favor of Bare main/worker + Squid on bare-node-runtime
Release path: primary CI is hello-pear-bare / bare-build standalone + Pear OTA (not Electron Forge)

Documented invariants: no master servers; Minecraft TCP bind only on 127.0.0.1; Apache-2.0 / no AGPL hard deps
Users must not need system Node.js; no Node child for game server