8.1.0 — See what a document task changed, and more examples to try

A snapshot as of 8.1.0 (released 2026-10-01). It will go stale as the app moves on — that is expected, and the living reference is the guide each section links to.

Nothing to configure. Everything here is in Blueprints’ document tasks.

New features

See each document against its original

When a document task finishes, its screen shows, under the report, each document the build kept an original of (.blueprint/originals/) compared with the file now (#2793), so what changed can be read in place, with the sentences around it.
A review answered 「直し方の案まで作る」 writes a proposed copy beside each document (<name>.proposed<ext>); those are compared with their documents too (#2795).
The comparison follows the app’s theme, light and custom themes included (#2797).

Carry on with 「文書を整える」 (polish)

Polish can work through the findings adopt shelved (#2781): answer 「棚上げした指摘も直す」 to 「棚上げした指摘も直しますか」.
The finished screen of 「文書のフォルダに chaff を入れる」 (adopt) offers polish on the same places (#2783).
The finished screen of 「用語をそろえる」 (glossary) offers polish on the same documents (#2765).

Tasks look further

Polish reads specifications and READMEs for what their readers need (#2779).
「文書を確かめる」 (verify) checks unit price × quantity and tax, not only totals (#2763).

Examples to try without documents of your own

The new-build form’s examples gain:

「規程を規程として整える」 — a regulation (#2755)
「英語のブログ記事を整える」 — an English blog post; the document stays in English, the report comes back in your language (#2773)
「出張旅費規程の改定を比べる」 — a regulation revision (#2757)
「検討報告を部長向けに要約する」 — a report summarised for a named reader (#2759)
「見積書を確かめる」 — an estimate (#2761)
「ネットショップの利用規約を読み解く」 — terms of service (#2767)
「休暇の規程と手引きに尋ねる」 — asking two documents that disagree (#2769)

What looks different

The new-build form shows one example per task, and the rest open with 「ほかの例を見る」 (#2785) — the examples had pushed the task choice far down.
Document tasks are listed most-used first (#2787).
Polish’s report puts the questions for the writer right after what was polished (#2789).
「規約をつくる」 (style) starts its language and strictness questions on the usual answers (#2771).

Under the hood

When glossary creates chaff.yaml for documents of different kinds, it gives each its own genre (#2775), so a policy’s guide is no longer measured as a policy.
Polish no longer reports a missing STYLE.md when only chaff.yaml is needed (#2777).
The document tasks run chaffjs 0.17 (#2791).

Nothing here needs doing.