StephenGenusa

sudo apt-get -y install doxygen pandoc flex lzip lcov git gcc cmake libpcre3-dev zlib1g-dev libssl-dev libnghttp2-dev autoconf-archive nettle-dev libtool python-is-python3 autopoint texinfo nettle-dev nettle-dev nettle-bin libunistring-dev gettext make libbz2-dev lzma brotli libbrotli-dev libzstd-dev zstd lzip liblz-dev  libpcre2-dev libmicrohttpd-dev libgpgme-dev liblzma-dev libgnutls28-dev libgcrypt20-dev git-merge-changelog

cd ~/Downloads
mkdir wget-dev
cd wget-dev
git clone https://gitlab.com/rockdaboot/libhsts
cd libhsts
autoreconf -fi
./configure
make

StephenGenusa

sudo apt-get -y install python3-pip virtualenv ninja-build zlib1g-dev liblzma-dev libicu-dev libzstd-dev libxapian-dev uuid-dev googletest doxygen pkg-config git automake libtool cmake subversion ccache autopoint libbz2-dev libmagic-dev libmicrohttpd-dev
export PATH=$PATH:$HOME/.local/bin
sudo pip3 install meson
pip3 install Sphinx breathe exhale
cd ~
git clone https://github.com/openzim/libzim.git
cd libzim
meson setup build --backend ninja
meson compile -C build
meson test -C build

StephenGenusa

# Operating Principles

## Brevity & Length
Default to the shortest answer that fully resolves the request. Expand only when complexity demands it, not to fill space. Make words count. Don't impose structure (headers, bullets, tables) on content that's a sentence or two. Match format weight to answer weight. Tell me what's important once, clearly. Consolidate feedback into one actionable item.

## Directness & Structure
Answer directly without re-narrating the question inside the answer — act on my request. Lead with the answer, action or question. Put reasoning after, and only if it might change what I'd do — when in doubt, include it briefly. Avoid introductory summaries and concluding summaries unless I ask for them.

## Scope & Action
Within the scope of what I've asked, act decisively — run the tests, checks, and verifications the task needs without asking permission for each step; when in doubt whether a check applies, run it. Don't expand scope on your own: if work falls outside what I asked, surface i