v1.2.26

CottenRouter v1.2.26

This release supports the current WhiteDNS Panel installer/runtime contract and
adds a real Feed Telegram transport regression against the published binaries.

• WhiteDNS Panel 0.14.4 no longer has the historical capabilities subcommand.
  Router now checks its exact selected version and current run/init/health/export
  CLI before stopping an existing service. Older builds keep their capability
  check; the pinned 0.5.1 beta still requires explicit selection.
• Panel installs and updates select the native Linux AMD64 or ARM64 archive,
  checking archive/runtime hashes, the architecture declaration and ELF machine.
  Stable release discovery remains independent of the Router version.
• Panel's native serving zones are imported on install/update and Configure or
  Advanced saves, including zones that replace the original identity delegation.
  Database identity, account keys, quotas and per-engine limits are preserved.
  Conflicting zones restore the previous files and service state. After changing
  tunnel zones in Panel, save its Router Configure form to refresh the routes.
• TUI and English/Persian instructions now default to the current stable Panel.
  Current Panel account engines remain managed natively: Soar, Cotten and
  MasterDNS share the private DNS frontend.

Feed v0.42.0's native client and server passed signed MTProto capability discovery,
sealed-session handshakes and bidirectional multi-cell streams through the
released Router. Twelve direct/routed cases cover base32/hex query encodings and
three cell budgets, with byte-exact results against a namespace-local test DC.
No Telegram account or public Telegram endpoint is used by this regression.

Validation includes full Go and Linux race suites, vet, builds and installer
checks. Real Panel 0.14.4 passed fresh managed installation, native authenticated
account creation, zone changes, update preservation, Advanced synchronization and
injected conflict rollback in private namespaces. Systemd/release transport is
substituted; the actual Panel binary, database, generated service command and
UDP/TCP listeners run. ARM64 bundle checks do not claim native ARM64 execution.

After upgrading Router, update an existing managed Panel with:

sudo cottenrouter update --project whitedns-panel

The same command with --project thefeed updates Feed through its native wizard.
External Telegram login/API behavior and production-network connectivity remain
separate checks.

Full Changelog: v1.2.25...v1.2.26