**The operations console moves to `/newsroom/`, which is where the editor says every admin action
belongs.** Eleven pages — the console index, mail, board, bridges, team, agent activity, design
review, guidance and documents, plus the six guidance documents — left `/backoffice/`. Their
builders went with them: `build/backoffice.py` and its three siblings are now `build/newsroom.py`,
`newsroom_bridges.py`, `newsroom_design.py`, `newsroom_team.py`. The navigation label a reader sees
changed from **Back office (EN)** to **Newsroom (EN)**.

**The interviews page became a console page rather than moving as-is.** It had been built with the
newspaper's chrome and simply relocated, and **gate 19 caught that immediately**: any page in the
console namespace must declare `lang="en"` and carry the notice saying this is not the publication.
The gate was right and the page was wrong — it is about how this newsroom works, not about what it
found, which is the same test that put the other eleven there. It is now `/newsroom/interviews.html`,
built by the console's own shell, in the console's rail under Reference.

**What is left under `/admin/`, and why each thing is still there.** The question was asked
directly, so here is the whole of it:

| What | Why it has not moved |
|---|---|
| `admin/review/index.html` | **Gate 13** permits unapproved delivery items to be shown with their state on `/entregas/`, `/redacao/` and `/admin/` only. One line in `build/gates.py` adds `/newsroom/`. Deny-listed. |
| `admin/versions.html` | **`admin/build/validate.js` reads this exact path** to check the release table has one row for the current version. Deny-listed. |
| `admin/build/version.txt` | Same file, line 54, same problem. It is also read by CI and by `before_push.py`. |
| `admin/build/validate.js`, `render.mjs` | The toolchain, not an admin action on the site. It can stay; moving it means editing CI and the deny-listed file that names itself. |

So `/admin/` survives on **three lines in two files that no agent here may edit** — and that is the
design working, not failing. An agent that can edit the gate that stops it has no gate. Issue 008
carries the exact changes; none of them was worked around by reaching for Bash, which would be the
same edit under another name.

**The browser gate earned its keep again.** The interview prompts rendered as `<pre>` blocks with
no wrapping rule — `.bo-pre` was a class I invented and never styled — and the page came out 937px
wide in a 390px viewport. No other gate looks at width. A prompt that needs sideways scrolling on a
phone is a prompt nobody copies on a phone, and copying is the entire point of that page.

*Old release notes that linked into `/backoffice/` were repointed, because the site gate requires
every link to resolve. Their prose was left alone: a note saying a page was at `/backoffice/…` in
March was true in March, and rewriting the record to match today would be the one edit this
repository never makes.*