LLL Scheduled Publish Readiness Review / 予約公開の準備点検

FAQ

Does this predict publication? The report flags observable gaps before publication. Publish guards, policy and host rejection are outside its scope. / 予約前に見える欠けを列挙します。公開ガード・方針・本体が公開時に拒否する条件は対象外です。

When should I use this? Before a busy release, check references and translated versions in future reservations. / 公開予定が集中するとき、予約記事の参照先や翻訳版を事前に確認できます。

Why are relation-bound reference fields "not checked"? The plugin API returns an entry's own data; entries linked through a relation are not returned. The report shows how many scheduled entries sit in collections that have such fields. Reference fields stored as plain ids are checked by exact id. / リレーションで結んだ記事はプラグインAPIが返しません。そのような項目を持つコレクションの予約記事の数を表示します。id を平文で持つ参照項目は完全一致で確認します。

Which times are shown? The host stores UTC. A second column adds the offset you choose; the site's own time zone is not available to plugins. / 保存は協定世界時。2列目に選んだオフセットを併記します（サイトの時刻帯はプラグインから読めません）。

What is not covered? Published entries that carry a scheduled change (counted, not checked: the host returns the live version), hidden collections, passed schedules (counted only), images/files/objects in required fields (not judged). / 公開済みで予約された変更を持つ記事（件数のみ）、非表示コレクション、過ぎた予約（件数のみ）、必須の画像・ファイル・オブジェクトの判定は対象外です。

Why PARTIAL? It reads up to 200 scheduled entries per collection, 60 list calls, 300 reference lookups and 200 translation-group reads. Past a limit or on a failed read the result is marked partial: an entry that is not listed is not shown to be fine. / 上限や読取失敗で部分結果になります。載っていない記事が問題なしとは言えません。

Security

LLL Inc. / MIT / contact@lx3.cafe. Version 0.1.0.

Capabilities: content:read and schema:read only. One POST admin route requiring plugins:manage and a signed-in caller. No network, hooks, cron, storage, settings or writes of any kind; it never schedules, unschedules or publishes. The report contains collection names, ids, slugs, locales, titles (up to 200 characters, shown up to 80), times and field names; field values other than the title are not shown. Output is plain text in a code block; control characters are removed and spreadsheet-formula prefixes neutralised. The report is not stored by the plugin; copies in the browser are outside plugin control.

Limits: 200 scheduled entries per collection, 60 list calls, 300 single-entry reads for reference targets, 200 translation-group reads, 150 finding rows, 48 KiB report; beyond these the result is marked partial or cut.

Report issues privately with version and a redacted reproduction. Do not send tokens or private exports.

Changelog

0.1.0

• First release: read-only list of facts about future scheduled entries (empty required fields, missing slug where the host needs one, reference targets that are drafts or scheduled later, other-language versions that are drafts or scheduled later, far-away or crowded times). Not a publish verdict; nothing is changed.

Installation / 導入

Install from the EmDash Registry, then open Admin → Scheduled Publish Readiness, choose a language, a time offset and optionally one collection, and press "Check scheduled entries". Requires permission to manage plugins. Capabilities: content:read, schema:read. No network access.

Registry から導入し、管理画面の「Scheduled Publish Readiness」で言語・時刻のオフセット・（必要なら）コレクションを選び「予約記事を点検」を押します。プラグイン管理権限が必要です。権限は content:read / schema:read。外部通信なし。