Tags: KernAIO/shell

chore(release): reach the newest compatible @kernhq packages

Advanced by the nightly release so the images carry the modules published since the last one.

chore(release): reach the newest compatible @kernhq packages

Advanced by the nightly release so the images carry the modules published since the last one.

chore(release): reach the newest compatible @kernhq packages

Advanced by the nightly release so the images carry the modules published since the last one.

chore(release): reach the newest compatible @kernhq packages

Advanced by the nightly release so the images carry the modules published since the last one.

chore(deps): refresh the lockfile for the reached ranges

module-mail is ^0.5.0 rather than ^0.5.1 for now: npm's CDN still
serves the abbreviated document from before 0.5.1 was published, so
pnpm cannot resolve it, and 0.5.1 only moved a devDependency. The range
reaches 0.5.1 the moment the registry does; the nightly reach will
record it.

chore(release): reach the newest compatible @kernhq packages

Advanced by the nightly release so the images carry the modules published since the last one.

chore(release): reach the newest compatible @kernhq packages

Advanced by the nightly release so the images carry the modules published since the last one.

chore(i18n): delete 223 message keys nothing references

Leftovers of the extract-module-messages migration: module strings moved
into their own bundles and @kernhq/ui's common.* namespace, the shell's
flat copies stayed. Audited by word-boundary grep across every Kern repo,
including dynamic access and named imports; tracker_issues_count stays
(plurals.test.ts imports it by name).

check-i18n.mjs now also counts named imports from a paraglide messages
module — that blind spot reported the one key still in use as deletable.

test: pick the blank page in quire's new template chooser

test: pick the blank page in quire's new template chooser