…'s AI settings (#92)
**Before:** on the live site, inline code in tables splits mid-word (the
Action guide shows `messag` / `e`), code blocks draw `!=` as `≠`,
Material-only syntax shows up as text (`{ .lg .middle }`, `# (1)`), the
GitLab guide's last bullet runs into a paragraph, and the home page has
no menu on a phone. The Action guide lists 9 of the Action's 12 inputs
and describes `pr-title` as a Conventional Commits check; the App guide
says the App runs CC001–CC016 and does not mention
`body_ai_attribution`, `ai_label` or `require_verified`.
**After:**
Each image: Before on the left, After on the right.
GitHub Action, Inputs

GitLab guide: `!=` and the last bullet

Getting started, step 5

Getting started, step 6

Home page on a phone, menu opened

**What changed:**
- `assets/extra.css`: table code wraps with `overflow-wrap: break-word`
instead of Sumi's `anywhere`, which shrank the column to one character;
code blocks turn ligatures off again after Sumi's `font` shorthand on
`.sumi-prose pre` reset them. Placed away from the lines the layout PR
(#91) changes.
- `getting-started.md`, `guides/github-actions.md`: plain comments
instead of `# (1)` annotations; no `{ .lg .middle }` on the cards.
- `guides/other-ci.md`: blank line after the nested code block, so the
list continues.
- `guides/github-actions.md`: rows for `message-ai-attribution`,
`pr-body-ai-attribution` and `ai-label` (from action.yml and the Action
README); `pr-title` says what `--pr-title` checks; the `edited` tip
covers the description too.
- `guides/github-app.md`: CC001–CC017 plus CC501; new sections
"AI-written pull requests" and "Verified commits", taken from the App
README.
- `configuration.md`: a "Top level" table (`inherit_from`, `warn`),
`body_ai_attribution` and `ai_label` under `[pull_request]`, a `[jira]`
table, and a note on `require_verified` under `[commit]`. The App-only
rows sit outside the sections `docs_sync_test` compares with the CLI.
- `example.md`: a "Checking a pull request title" recipe (output from
2.22.0), and the skipped-check warning points at `--pr-title`.
- `index.md`, `overrides/landing.html`, `stylesheets/landing.css`: the
home page sets `layout: docs`, so Sumi keeps its menu button, and
renders the sidebar as the phone drawer; it stays hidden above 920px.
The desktop home page is unchanged (pixel diff only in the animated
demo).
**How:** `mkdocs build --strict` is clean and `python -m pytest tests/
-q` passes (18) against commit-check 2.22.0. A Playwright scan of all 31
pages found 32 table code spans broken mid-word on the live site at
1280px, and 0 on this build at 1280px and 390px.
Before:
extra.csscaps the page at 1220px, the width carried over from the Material theme. Sumi's own frame is 1480px. The 1220px cap left the article 632px wide at every screen size, with wide empty margins on a large monitor. Measured across the 31 docs pages:On macOS the scrollbar only shows while you scroll, so a cut-off line looks like the whole line.
After:
Same 31 pages measured after the change:
On a phone, the 3 to 6 column tables (rule index, comparisons) still scroll sideways. That is the usual trade-off for a table that is wider than the screen, so this PR leaves them as they are.
/migration/ at 2560px:
MCP client tabs at 1440px and on a phone:
A long CI line on the GitLab/Bitbucket page at 1440px and on a phone:
How: only
docs/assets/extra.csschanges.mkdocs build --strictis clean, andpython -m pytest tests/ -qgives 18 passed. The table above comes from loading every docs page in Chromium at 1440, 2560, 390 and 320px and counting elements whose content is wider than their scroll box. The screenshots were added and removed in two commits on this branch, so a squash merge leaves no images behind.Summary by CodeRabbit