LLL Image Upscale Review / 画像の拡大指定点検

What is checked? In the top-level image blocks of one saved field of a published article, the saved display width/height is compared with the saved original width/height. Images whose display size is more than 5% above the original are listed as "enlarged-candidate" with the ratio (display / original), a possible cause of a blurry look.

Is a candidate a blurry image? Not necessarily. It is a candidate. The width visitors actually get depends on the theme and CSS, which are not read, and a size may be deliberate. Nothing is measured from the image file.

"undetermined"? A display value that is not a plain positive number (a string, 0, negative, "100%", "auto"), a display size with no saved original size, or one axis enlarged while the other is shrunk. Not compared; their presence prevents an all-clear.

Images with no display size? Counted only (noDisplaySize). Gallery items carry no saved display size and are counted, not compared.

Where does the original size come from? The width/height saved on the image block, or on its asset. It is a saved value, not the real file size.

Is this an image optimizer? No. Optimizers look at file size or convert files. This compares sizes saved in the article and changes nothing.

Limits? JSON 128 KiB, 2000 blocks, 2000 image items, first 100 candidates shown (counts are complete), report 48 KiB. Drafts are rejected.

何を点検するか：公開記事の保存済み項目のトップレベルimageで、保存された表示の幅・高さを保存された元寸法と比べ、5％より超えるものを倍率つきで「拡大の候補」として一覧します。候補はぼやけの証拠ではなく、テーマCSSで実際の幅は変わります。数値でない・元寸法なし・縦横矛盾は「未判定」。画像ファイルは見ません。連絡 contact@lx3.cafe へは合成データか伏せ字の手順だけを送ってください。

Read capabilities: content:read, schema:read. No media access, no writes, KV, storage, external HTTP, cron, analytics or API keys; allowedHosts is empty. One POST route requiring content:edit_own_drafts and a signed-in caller; host ownership checks apply. Results last only for the request; the report is not stored. The report shows only numbers (sizes, ratios, block positions) and fixed labels: no URL, media id, file name, alt text, caption or any free text from the article. Errors are fixed messages and never include internal details. The runtime license for the bundled EmDash SDK code is in the package README.

Report cells and spreadsheets. The report is tab-separated plain text. A cell beginning with =, +, - or @ (after optional whitespace/control characters) gets a leading apostrophe so it is not run as a formula; cells containing tab, line break or double quote are wrapped in double quotes.

Calling the plugin route directly. The entry to review comes only from the host-attested editor context (route.ui.entry). A direct POST to the plugin API route ignores any ui/entry value in the body, query string or headers; verified in the real sandbox as another contributor (npm run test:runtime).

読取2権限のみ。メディア・通信・書き込みなし。レポートは数値（寸法・倍率・ブロック位置）と固定ラベルだけで、URL・メディアID・ファイル名・alt・本文の文字列は出しません。脆弱性は contact@lx3.cafe へ、秘密を含めず連絡してください。

0.1.0

Adds a review panel that compares the saved display width/height of each top-level image block of one saved field of a published article with its saved original size (read-only), and lists images displayed more than 5% larger than the original with the ratio, plus values that could not be compared. English/Japanese manual copy report. No content changes, no fetching, no media access, no external calls.

公開記事の保存済み項目のトップレベルimageブロックについて、保存された表示寸法を保存された元寸法と読み取り専用で比べ、5％より大きいものを倍率つきで一覧し、比べられない値も別に示す初版。英日の手動コピーレポート付き。本文変更・取得・メディア参照・外部通信なし。

Install LLL Image Upscale Review (image-upscale-review) from the official EmDash Registry once available. Requires EmDash 1.4 and a configured supported sandbox runner. The plugin asks for content:read and schema:read only (no media access, no write). Open a published, saved article and use the "Image Upscale Review / 画像の拡大指定点検" editor panel, choose one Portable Text field and a language, then press the button. After you change the article, save and publish, then review again. The report is copied by hand. No settings, free.

公式Registryから導入し、公開済みの保存記事の編集画面でパネルを開き、本文項目と言語を選んで確認します。権限は content:read / schema:read のみ（メディアは見ません・書き込みなし）。記事を直したら保存・公開のうえ再点検してください。レポート全文は手動コピーです。設定不要・無料。