Authorise recurring content production

The July and August reviews both asked for authorisation to run an /improve or /article task on the TN scope. With no answer, no content was produced in two months — all traffic growth came from pages built before July.

Proposal (2026-08-18): rather than a one-off authorisation that has to be re-requested every month, give a content task the same autonomy as ctr-optimizer — autonomy: pr, one page a month, shipped as a draft PR. The PR review becomes the safeguard. That is what worked for #16216: idea to merge in a day, because it went out as a PR instead of waiting for prior agreement.

Answer (2026-08-19, Chat) : "yes" — approves the 2026-08-18 proposal: recurring content task runs with autonomy: pr, one page a month, shipped as a draft PR.