{"blyg":"0.4","id":"2n17ghxcefxgahdfxtgy9zxx4z","kind":"thread","origin":"https://blyg.blygger.org/","page":"t/2n17ghxcefxgahdfxtgy9zxx4z/","author":{"name":"Venkatesh Rao","url":"https://blyg.blygger.org/"},"created":"2026-11-14T19:25:19Z","updated":"2026-11-14T19:25:20Z","version":1,"content_md":"\n# Blygger Studio 0.58.2 to 0.59.0\n\n*3 releases of the reference client, newest first. Read each one's **Migrations** line before upgrading.*\n\n## 0.59.0: Extensions from other repositories, menu zones and editor regions\n\n*Released 2026-11-13. [v0.59.0 on GitHub](https://github.com/blygger/blygger-studio/releases/tag/v0.59.0).*\n\nThree changes for extension authors and operators, held on `main` since 0.58.1. It also\ncarries everything in 0.58.2 and 0.58.3, which were released from a branch without them.\n\n**Vendoring an extension from another repository** (#59, decision #89). An operator can\ncompile a browser-only extension published in someone else's repository into their own\nbuild: `npm run ext:add -- <https repo> <commit>` fetches exactly that commit on the\noperator's machine, checks its layout, that it has no server half, its imports and a\ntypecheck against the extension API, prints every file and a tree hash, and vendors it\nonly after a yes. `ext:update` and `ext:remove` do the rest. The source goes into the\ngitignored `extensions-vendor/` and the lock into `extensions.local.json`, so nothing\nvendored is committed and a release build never carries one; `npm run build` re-hashes\neach vendored tree and refuses one edited since. No Studio loads anything at run time,\nand there is no registry. See `docs/extension-vendoring.md`.\n\n**Menu zones** (#143). An extension page asks for a place in the main menu with\n`page.mainMenu.zone`: `top` (one page, above reading), `visible` (one page, above\ncompose; the default, and where `mainMenu: { icon }` put a page before) or `hidden`\n(More). The Studio decides: a full zone moves a page down, never up, in compiled order,\nand the page's context says what it asked for and where it landed (`menu: { asked,\nzone }`). Template: `extensions/menu-top-example`.\n\n**Editor regions** (#144). An extension can keep parts of the full editor's text out of\nits text box, for text a tool writes and the author should not edit by hand, such as\nchapter navigation. `editorRegions({ text, item })` returns ranges; the box shows the\nrest, and every edit is joined back with the regions before the draft sees it, so\nautosave, preview, counts and publish keep the whole text. Hidden each time the editor\nopens, read-only when shown, and if a join does not round-trip the edit is saved whole\nand the editor shows everything. Full editor only. Template:\n`extensions/regions-example`.\n\n**Extensions and the error log** (0.58.2's hooks, carried to the new surfaces): an\nextension page's context is built per extension, so its errors are logged under its\nname and it has `showError`.\n\nPrivate contract and SDK unchanged. Protocol version unchanged (`\"0.4\"`).\n\n**Migrations:** none. A node coming from before 0.58.0 needs `0045`.\n\n## 0.58.3: Sublists, verse and code blocks are easier to type\n\n*Released 2026-11-13. [v0.58.3 on GitHub](https://github.com/blygger/blygger-studio/releases/tag/v0.58.3).*\n\nSublists, line breaks inside a paragraph and code blocks always rendered: the Studio's\nmarkdown is CommonMark. What was missing was a way to type them in a text box.\n- **Tab and Shift+Tab** move the list item under the cursor in and out a level; with\n  several lines selected they all move, and undo takes it back. A numbered item that\n  opens a sublist is renumbered to 1, which is the only way markdown reads it as a list.\n  Off a list, or on the first item of one, Tab moves focus as usual.\n- **Shift+Enter** breaks a line without ending the paragraph, for verse or an address.\n  It types markdown's backslash line break, which you can see in the text. Inside a\n  code block it types a plain newline.\n- **The full editor's toolbar** has a button for each, and one that puts the selected\n  lines in a code block (or starts an empty one), for an iPad's keyboard, which has no\n  Tab key.\n- The syntax page has a Markdown section saying how to write each by hand.\n\nPrivate contract and SDK unchanged. Protocol version unchanged (`\"0.4\"`).\n\n**Migrations:** none. A node coming from before 0.58.0 needs `0045`.\n\n## 0.58.2: An error log you can read and send, and focus view on an iPad\n\n*Released 2026-11-13. [v0.58.2 on GitHub](https://github.com/blygger/blygger-studio/releases/tag/v0.58.2).*\n\n**The Studio keeps an error log** (Settings → Errors). An error banner can be gone\nbefore you have read it; what it said is now kept, with the time, the page you were on,\nthe item, the request that failed with its status and error code, the Studio version and\na stack. Every banner has a *details* link to its entry. Errors that never reach a\nbanner are kept too: uncaught exceptions, unhandled promise rejections, and a page that\nfailed to load. A failure repeated within a minute is one entry with a count and the\ntime it first happened.\n- **The log stays on the device.** It lives in the browser's own storage, holds the\n  latest 100 entries, and is sent nowhere. Each device has its own. It records failures,\n  not writing: no draft text, and no query strings.\n- **Export error log** hands over a dated JSON file with the entries, the Studio\n  version and the device (browser, platform, screen and window size, whether the Studio\n  was opened from the home screen, language, timezone). A phone or tablet opens the\n  share sheet; a desktop saves the file. **Copy diagnostics** puts the same as plain\n  text on the clipboard, for an issue. **Clear error log** empties it.\n- Not logged: messages to the author such as a link that does not resolve, requests the\n  Studio cancelled, and requests the browser dropped because you were leaving the page.\n- Only the browser Studio is covered. Cron, the importer and Webmention run on the\n  server with no browser attached, and their errors are in the Worker's own logs.\n\n**Extensions.** What an extension throws in a slot is logged under its name and the slot\n(the slot still renders nothing until the page reloads). An error caught by\n`context.run` is logged the same way, as well as shown. **New: `context.showError(error)`**\nshows an error the extension found for itself in the screen's error line and logs it;\npass an `Error` or a message. Existing extensions need no change. The example extension\nuses it, and `docs/extensions.md` describes it.\n\n**Focus view on an iPad closed as soon as it opened.** iPad Safari has browser\nfullscreen and leaves it when the on-screen keyboard comes up; the Studio took that for\nEscape. On an iPad and iPhone the view no longer asks for browser fullscreen, so\nSafari's toolbar stays and the view stays open.\n\n**Hiding or showing a response** could fail with \"Collection must be in 'ready' state for\nmanual sync operations\" if you left the page before the server answered: the one write\n0.58.1's fix (#142) had missed.\n\nPrivate contract and SDK unchanged. Protocol version unchanged (`\"0.4\"`).\n\n**Migrations:** none. A node coming from before 0.58.0 needs `0045`.\n\n\n\n*This announcement is drafted from the releases' sections of [`CHANGELOG.md`](https://github.com/blygger/blygger-studio/blob/main/CHANGELOG.md), which is where they are maintained. To comment, respond to this item from your own blyg.*\n","content_html":"<div class=\"blyg-tk-gen\"><h1>Blygger Studio 0.58.2 to 0.59.0</h1>\n<p><em>3 releases of the reference client, newest first. Read each one's <strong>Migrations</strong> line before upgrading.</em></p>\n<h2>0.59.0: Extensions from other repositories, menu zones and editor regions</h2>\n<p><em>Released 2026-11-13. <a href=\"https://github.com/blygger/blygger-studio/releases/tag/v0.59.0\">v0.59.0 on GitHub</a>.</em></p>\n<p>Three changes for extension authors and operators, held on <code>main</code> since 0.58.1. It also\ncarries everything in 0.58.2 and 0.58.3, which were released from a branch without them.</p>\n<p><strong>Vendoring an extension from another repository</strong> (#59, decision #89). An operator can\ncompile a browser-only extension published in someone else's repository into their own\nbuild: <code>npm run ext:add -- &lt;https repo&gt; &lt;commit&gt;</code> fetches exactly that commit on the\noperator's machine, checks its layout, that it has no server half, its imports and a\ntypecheck against the extension API, prints every file and a tree hash, and vendors it\nonly after a yes. <code>ext:update</code> and <code>ext:remove</code> do the rest. The source goes into the\ngitignored <code>extensions-vendor/</code> and the lock into <code>extensions.local.json</code>, so nothing\nvendored is committed and a release build never carries one; <code>npm run build</code> re-hashes\neach vendored tree and refuses one edited since. No Studio loads anything at run time,\nand there is no registry. See <code>docs/extension-vendoring.md</code>.</p>\n<p><strong>Menu zones</strong> (#143). An extension page asks for a place in the main menu with\n<code>page.mainMenu.zone</code>: <code>top</code> (one page, above reading), <code>visible</code> (one page, above\ncompose; the default, and where <code>mainMenu: { icon }</code> put a page before) or <code>hidden</code>\n(More). The Studio decides: a full zone moves a page down, never up, in compiled order,\nand the page's context says what it asked for and where it landed (<code>menu: { asked, zone }</code>). Template: <code>extensions/menu-top-example</code>.</p>\n<p><strong>Editor regions</strong> (#144). An extension can keep parts of the full editor's text out of\nits text box, for text a tool writes and the author should not edit by hand, such as\nchapter navigation. <code>editorRegions({ text, item })</code> returns ranges; the box shows the\nrest, and every edit is joined back with the regions before the draft sees it, so\nautosave, preview, counts and publish keep the whole text. Hidden each time the editor\nopens, read-only when shown, and if a join does not round-trip the edit is saved whole\nand the editor shows everything. Full editor only. Template:\n<code>extensions/regions-example</code>.</p>\n<p><strong>Extensions and the error log</strong> (0.58.2's hooks, carried to the new surfaces): an\nextension page's context is built per extension, so its errors are logged under its\nname and it has <code>showError</code>.</p>\n<p>Private contract and SDK unchanged. Protocol version unchanged (<code>&quot;0.4&quot;</code>).</p>\n<p><strong>Migrations:</strong> none. A node coming from before 0.58.0 needs <code>0045</code>.</p>\n<h2>0.58.3: Sublists, verse and code blocks are easier to type</h2>\n<p><em>Released 2026-11-13. <a href=\"https://github.com/blygger/blygger-studio/releases/tag/v0.58.3\">v0.58.3 on GitHub</a>.</em></p>\n<p>Sublists, line breaks inside a paragraph and code blocks always rendered: the Studio's\nmarkdown is CommonMark. What was missing was a way to type them in a text box.</p>\n<ul>\n<li><strong>Tab and Shift+Tab</strong> move the list item under the cursor in and out a level; with\nseveral lines selected they all move, and undo takes it back. A numbered item that\nopens a sublist is renumbered to 1, which is the only way markdown reads it as a list.\nOff a list, or on the first item of one, Tab moves focus as usual.</li>\n<li><strong>Shift+Enter</strong> breaks a line without ending the paragraph, for verse or an address.\nIt types markdown's backslash line break, which you can see in the text. Inside a\ncode block it types a plain newline.</li>\n<li><strong>The full editor's toolbar</strong> has a button for each, and one that puts the selected\nlines in a code block (or starts an empty one), for an iPad's keyboard, which has no\nTab key.</li>\n<li>The syntax page has a Markdown section saying how to write each by hand.</li>\n</ul>\n<p>Private contract and SDK unchanged. Protocol version unchanged (<code>&quot;0.4&quot;</code>).</p>\n<p><strong>Migrations:</strong> none. A node coming from before 0.58.0 needs <code>0045</code>.</p>\n<h2>0.58.2: An error log you can read and send, and focus view on an iPad</h2>\n<p><em>Released 2026-11-13. <a href=\"https://github.com/blygger/blygger-studio/releases/tag/v0.58.2\">v0.58.2 on GitHub</a>.</em></p>\n<p><strong>The Studio keeps an error log</strong> (Settings → Errors). An error banner can be gone\nbefore you have read it; what it said is now kept, with the time, the page you were on,\nthe item, the request that failed with its status and error code, the Studio version and\na stack. Every banner has a <em>details</em> link to its entry. Errors that never reach a\nbanner are kept too: uncaught exceptions, unhandled promise rejections, and a page that\nfailed to load. A failure repeated within a minute is one entry with a count and the\ntime it first happened.</p>\n<ul>\n<li><strong>The log stays on the device.</strong> It lives in the browser's own storage, holds the\nlatest 100 entries, and is sent nowhere. Each device has its own. It records failures,\nnot writing: no draft text, and no query strings.</li>\n<li><strong>Export error log</strong> hands over a dated JSON file with the entries, the Studio\nversion and the device (browser, platform, screen and window size, whether the Studio\nwas opened from the home screen, language, timezone). A phone or tablet opens the\nshare sheet; a desktop saves the file. <strong>Copy diagnostics</strong> puts the same as plain\ntext on the clipboard, for an issue. <strong>Clear error log</strong> empties it.</li>\n<li>Not logged: messages to the author such as a link that does not resolve, requests the\nStudio cancelled, and requests the browser dropped because you were leaving the page.</li>\n<li>Only the browser Studio is covered. Cron, the importer and Webmention run on the\nserver with no browser attached, and their errors are in the Worker's own logs.</li>\n</ul>\n<p><strong>Extensions.</strong> What an extension throws in a slot is logged under its name and the slot\n(the slot still renders nothing until the page reloads). An error caught by\n<code>context.run</code> is logged the same way, as well as shown. <strong>New: <code>context.showError(error)</code></strong>\nshows an error the extension found for itself in the screen's error line and logs it;\npass an <code>Error</code> or a message. Existing extensions need no change. The example extension\nuses it, and <code>docs/extensions.md</code> describes it.</p>\n<p><strong>Focus view on an iPad closed as soon as it opened.</strong> iPad Safari has browser\nfullscreen and leaves it when the on-screen keyboard comes up; the Studio took that for\nEscape. On an iPad and iPhone the view no longer asks for browser fullscreen, so\nSafari's toolbar stays and the view stays open.</p>\n<p><strong>Hiding or showing a response</strong> could fail with &quot;Collection must be in 'ready' state for\nmanual sync operations&quot; if you left the page before the server answered: the one write\n0.58.1's fix (#142) had missed.</p>\n<p>Private contract and SDK unchanged. Protocol version unchanged (<code>&quot;0.4&quot;</code>).</p>\n<p><strong>Migrations:</strong> none. A node coming from before 0.58.0 needs <code>0045</code>.</p>\n</div>\n<div class=\"blyg-tk-gen\"><p><em>This announcement is drafted from the releases' sections of <a href=\"https://github.com/blygger/blygger-studio/blob/main/CHANGELOG.md\"><code>CHANGELOG.md</code></a>, which is where they are maintained. To comment, respond to this item from your own blyg.</em></p>\n</div>\n","content_hash":"sha256:674251fccb2b5e6e9c03929e7aaed651bfd5204a9d957beea808d6ce3df9cb83","media":[],"transclusions":[],"generated":[{"sources":[],"model":"claude-opus-5-5"},{"sources":[],"model":"claude-opus-5-5"}],"changelog":[{"version":1,"at":"2026-11-14T19:25:20Z","note":"Studio 0.58.2 to 0.59.0 released."}]}