v2.0.2194

✨ Features

• An on/off setting looks the same on every admin page, and setting up a Context Map repository is one step.
• The Context Map admin page is now a browsable corpus, not a list.
• GitLab: reply inside an existing merge-request discussion.
• GitLab connector gains discussions, labels, milestones, boards and todos.
• GitLab: label, milestone, token and comment options the connector could not reach.
• Admin pages are now checked in a real browser against a running backend.
• Every admin page is now captured as an image, and a sixth review perspective reads them.
• Every admin page now shows its own title.

🔧 Improvements

• A failed upstream call is now a distinct type rather than a convention.
• Failed connector calls carry their error type along the delegation chain, not only where the error is built.
• Failed connector calls are recognisable as failures on the paths a call actually takes.
• Error envelopes the gateway builds itself are recognisable too.
• A failing pre-commit run now answers whether the suite or the change decided it.
• A vendor moving its API documentation no longer goes unnoticed.

🐛 Fixes

• Prototype saves keep their push credential across gateway restarts.
• Clearer guidance when an upstream answers with more data than the gateway will carry.
• A failed call stays recognisable after the gateway enriches it.
• Structured body fields now advertise their real shape.
• A test that fails in two different output shapes is now recorded as one test.
• Red status text stays readable on the lighter surfaces it appears on.
• Three pieces of status text that were hard to read now aren't.
• A brand colour that would make the panel unreadable is refused at save time.
• The review ledger records the design round that shipped this week.
• A spreadsheet operation now names the tab it could not find instead of using another one.
• Text across the admin panel is checked against WCAG AA, and three places that missed it are fixed.
• A colour token now belongs to one stylesheet.
• Service discovery answers on every connected service.
• Follow-ups from an adversarial review of the evening's admin-panel work.
• The Context Map now names its type gap by what would close it.
• One kind is now one entry in the Context Map, however it was spelled.
• Gmail says when an attachment request cannot be met, instead of sending the mail without it.
• The test suite no longer inherits the machine's own gateway configuration.
• The sidebar shows one current page again, and the operations page leads with its answer.
• Spacing across the admin panel now has a scale to drift from.
• Operations that cannot be completed correctly now stop instead of doing something else.
• Forwards and moves handle awkward inputs and partial failures correctly.
• Two actions that destroy more than they looked like now warn before the dialog does.
• On the clients page, a control's weight now matches what it does.
• A failed lookup no longer answers as if it had succeeded.
• The setup-help panel keeps its distance from the list below it.
• Switching the Context Map to a different repository now writes the starter files into the new one.
• Calendar and Gmail now say when a parameter had no effect, instead of succeeding quietly.
• The dropped-parameter diagnostic no longer reports fields that are sent.
• Transient upstream failures no longer open an issue on first sight.
• The allowed-services picker on the clients page says what it is offering.
• Log queries return the line budget you asked for.
• A sync that never answers can no longer freeze its own button.
• Restores the admin panel's styling.
• The hidden attribute now hides, everywhere in the admin panel.
• "Sync now" on the Context Map page shows that it is working.
• A shared admin stylesheet drops the half of it that styled nothing.
• The setup help panel lines up with the fields it explains.
• The Context Map browser's toolbar lines up with the panes beneath it.
• The panel chrome stops overruling pages about their own buttons.
• Two repositories with the same name no longer collapse into one Context Map page.
• The admin panel stops overriding the pages it hosts.
• The Context Map page preview is bounded, and setting up a repository can be retried.
• Admin page styling moves out of the markup and into stylesheets.
• Two admin pages stop being separate documents, and the panel stops arguing with them.
• The sidebar's current entry goes back to looking as it did.
• The navigation says where you are, not just where your pointer is — and every admin page carries a name.
• Two addresses and one credential no longer sit in Redis in the clear.
• Admin pages name themselves once, and the usage toolbars line up.
• Every admin page states its own name, and actions sit where the eye looks.
• One switch component across the admin, and the date filter stays on screen.
• Every connector's API-documentation link resolves again.
• Deliberate refusals now read as warnings in the audit log.
• Read tools band their deliberate refusals like write tools do.
• Pages no longer say their own name twice, and Action Usage gets the room Data Usage has.
• Page titles now sit exactly on the box they name.
• Page titles line up with the content again, and the scanning pages get their width back.
• The browser check now verifies that a message survives a page reload, and reports its coverage accurately.
• One way for admin pages to report what happened.
• In-page messages now behave the way the dialogs they replaced did.
• Admin pages now share one content width.
• The test suite no longer reaches the network.
• Destructive maintenance actions now look destructive.
• The admin navigation on narrow screens says that it continues.
• Empty sections and expandable areas now look the same wherever they appear.
• Tightened the checks that guard the admin page captures and titles.
• The suite-cost line reports what it measures.

Full changelog: https://mcpgate.de/changelog/

Docker: docker pull mcpgate/mcpgate:2.0.2194