Add Python to the orchestrator image?

The cms repo's own page-improvement engine, /improve, is the house tool for reworking an existing page — and Country OS cannot run it. It drives Python scripts (keyword_audit.py, improve-gate.py) and the orchestrator image is node:22-bookworm-slim with no Python at all (verified 2026-08-21).

So the new tn:content task can create pages but never improve one, which is awkward: the site's biggest wins are on pages that already exist and already rank. ctr-optimizer covers the snippet, but not a real rework.

This is the second time the missing runtime has cost something. The 08-17 audit could not reproduce the FaqAnswer bug for the same reason.

The ask. Add python3 (and pip) to the image, or decide that page reworks stay a human, interactive job. Adding it is a two-line Dockerfile change and a rebuild; the cost is a larger image and a second runtime to keep current. The payoff is that every Python tool in the cms repo becomes reachable from a scheduled run, not just this one.

Answer (2026-08-21, Chat) : "Record rejection — decision to rework the skill directly on countryos rather than using cms as the live deployment path" — no to adding python3 to the image. The direction instead is to rework the relevant skill(s) to run natively on countryos, rather than depending on cms's Python tooling as the live deployment path.