{"blyg":"0.4","id":"1v1h3zm5h0nd0prdtxk8d1tz62","kind":"thread","origin":"https://blyg.blygger.org/","page":"t/1v1h3zm5h0nd0prdtxk8d1tz62/","author":{"name":"Venkatesh Rao","url":"https://blyg.blygger.org/"},"created":"2026-11-08T02:53:08Z","updated":"2026-11-08T02:53:09Z","version":1,"content_md":"\n# Blygger Studio 0.57.0 to 0.58.0\n\n*2 releases of the reference client, newest first. Read each one's **Migrations** line before upgrading.*\n\n## 0.58.0: Changelogs you can read, and an order that ignores the noise\n\n*Released 2026-11-07. [v0.58.0 on GitHub](https://github.com/blygger/blygger-studio/releases/tag/v0.58.0).*\n\n**Changelog display** (#140, decision #95). Settings → Feed → changelog chooses, for your\nown item pages and separately for blyg items in your reader, what to show of an item's\nchangelog: the latest note (the default, as before), the full history of notes newest\nfirst, or an AI summary of them. A summary is written from the notes only, never from\nthe text of earlier versions, so it cannot reveal what the author left unpinned. It is\nlabelled with the model's name and stays in your studio, never in the item document or\nthe feed. Each summary is written once per version and kept: on your pages, in the\nbackground on a version's first view, with the full history shown meanwhile; in your\nreader, only when you open an item. Settings → AI → changelog summaries takes your\ninstructions for how summaries should read.\n\n**Summarize the history to date** (#140). The editor's note card has a new checkbox, off\neach time: a drafted note then covers every version so far, ending with this one, up to\n400 characters, under the same rule as any note against quoting unpinned text. The note\nbecomes the start of that version's feed title.\n\n**The pace-layered order** (#141, RFC-3, decision #97). A version republished unchanged,\nor with an edit of a few characters, no longer climbs. A thread published together with\nthe fragments it names, within 15 minutes, is one publication: it takes one place in the\norder, with the fragments beneath the thread. A withdrawn thread's fragments stand on\ntheir own. The order's fixtures now live in blygger-spec (`conformance/feeds/`), where\nother clients can check against them.\n\nPrivate contract **5.8.0** (additive: `POST /changelog-summary`, `history` on\n`draftNote`, three settings); SDK **0.14.0**. Protocol version unchanged (`\"0.4\"`).\n\n**Migrations:** `0045` (`changelog_summaries`). Apply it before deploying.\n\n## 0.57.0: Writing a book on the studio\n\n*Released 2026-11-07. [v0.57.0 on GitHub](https://github.com/blygger/blygger-studio/releases/tag/v0.57.0).*\n\nMost of this release was asked for while writing a book on the studio (the blykker\npilot, *New Nature*).\n\n**Comments to self** (#131). In a working copy, `/* … */` holds a note for you:\ninline or over several lines, kept across saves and publishes, and left out of\neverything public: the page, feeds, item documents, history and quotes. A `TK`\nscope inside one can be generated as usual. Editing only a comment is not an\nunpublished change. An unclosed `/*`, or a `*/` on its own, blocks publish rather\nthan risk showing the note. In code they are literal; elsewhere `\\/*` and `\\*/` write\nthe characters. **Existing text can change meaning:** a working copy that already has\n`/*` outside code will either refuse to publish with a reason or, if a `*/` follows,\ndrop the text between them at its next publish or quote refresh. The preview shows\nthis first, and already-published versions don't change. Discarding changes or\nrestoring a version removes comments, and the confirm dialog says so.\n\n**Focus view** (#126). A full-screen writing view in the full editor: the icon at the\nright of the editor's head line, or ⌘⇧↩ / Ctrl+Shift+Enter; Esc leaves. It has\ntypewriter scrolling, controls that fade while you type, the counts in a corner, and a\n**preview** tab (⌘⌥↩ / Ctrl+Alt+Enter). Text, caret, scroll and undo history all\nsurvive the switch, and autosave keeps running.\n\n**Word count while writing** (#125). The `word-count` extension now also shows its\ncount beside the character count, in the composer and the full editor, through a\nnew general `draftCounter` extension slot. Like the character count, it leaves comments\nto self out.\n\n**Extension pages can sit in the main menu** (#133). `page.mainMenu: { icon }` links an\nextension page from the main menu, above compose, instead of from More. Browser only.\n\n**A quote's label is shown to readers** (#136, ROADMAP row 79, decision #81). A labelled\ndirective, `![[id | text]]`, bakes `data-blyg-label` on its blockquote. Public pages,\nthe reader and fork flattening use it as the attribution link's text. What the link\nsaid before stays beside it, so a label never hides whose quote it is and is never\nshown as the quoted item's title. Unlabelled quotes bake byte-identically. The reader\nconformance suite goes from 74 to 79 passing.\n\n**Single-node deploys** (#138). A self-host whose `wrangler.private.jsonc` has no\n`env` block (one target, `\"env\": \"\"`) now passes `npm test` and `deploy:all`'s\ncross-check. The pinned-`account_id` guard still applies.\n\nPrivate contract, SDK and protocol version unchanged (`\"0.4\"`).\n\n**Migrations:** none.\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.57.0 to 0.58.0</h1>\n<p><em>2 releases of the reference client, newest first. Read each one's <strong>Migrations</strong> line before upgrading.</em></p>\n<h2>0.58.0: Changelogs you can read, and an order that ignores the noise</h2>\n<p><em>Released 2026-11-07. <a href=\"https://github.com/blygger/blygger-studio/releases/tag/v0.58.0\">v0.58.0 on GitHub</a>.</em></p>\n<p><strong>Changelog display</strong> (#140, decision #95). Settings → Feed → changelog chooses, for your\nown item pages and separately for blyg items in your reader, what to show of an item's\nchangelog: the latest note (the default, as before), the full history of notes newest\nfirst, or an AI summary of them. A summary is written from the notes only, never from\nthe text of earlier versions, so it cannot reveal what the author left unpinned. It is\nlabelled with the model's name and stays in your studio, never in the item document or\nthe feed. Each summary is written once per version and kept: on your pages, in the\nbackground on a version's first view, with the full history shown meanwhile; in your\nreader, only when you open an item. Settings → AI → changelog summaries takes your\ninstructions for how summaries should read.</p>\n<p><strong>Summarize the history to date</strong> (#140). The editor's note card has a new checkbox, off\neach time: a drafted note then covers every version so far, ending with this one, up to\n400 characters, under the same rule as any note against quoting unpinned text. The note\nbecomes the start of that version's feed title.</p>\n<p><strong>The pace-layered order</strong> (#141, RFC-3, decision #97). A version republished unchanged,\nor with an edit of a few characters, no longer climbs. A thread published together with\nthe fragments it names, within 15 minutes, is one publication: it takes one place in the\norder, with the fragments beneath the thread. A withdrawn thread's fragments stand on\ntheir own. The order's fixtures now live in blygger-spec (<code>conformance/feeds/</code>), where\nother clients can check against them.</p>\n<p>Private contract <strong>5.8.0</strong> (additive: <code>POST /changelog-summary</code>, <code>history</code> on\n<code>draftNote</code>, three settings); SDK <strong>0.14.0</strong>. Protocol version unchanged (<code>&quot;0.4&quot;</code>).</p>\n<p><strong>Migrations:</strong> <code>0045</code> (<code>changelog_summaries</code>). Apply it before deploying.</p>\n<h2>0.57.0: Writing a book on the studio</h2>\n<p><em>Released 2026-11-07. <a href=\"https://github.com/blygger/blygger-studio/releases/tag/v0.57.0\">v0.57.0 on GitHub</a>.</em></p>\n<p>Most of this release was asked for while writing a book on the studio (the blykker\npilot, <em>New Nature</em>).</p>\n<p><strong>Comments to self</strong> (#131). In a working copy, <code>/* … */</code> holds a note for you:\ninline or over several lines, kept across saves and publishes, and left out of\neverything public: the page, feeds, item documents, history and quotes. A <code>TK</code>\nscope inside one can be generated as usual. Editing only a comment is not an\nunpublished change. An unclosed <code>/*</code>, or a <code>*/</code> on its own, blocks publish rather\nthan risk showing the note. In code they are literal; elsewhere <code>\\/*</code> and <code>\\*/</code> write\nthe characters. <strong>Existing text can change meaning:</strong> a working copy that already has\n<code>/*</code> outside code will either refuse to publish with a reason or, if a <code>*/</code> follows,\ndrop the text between them at its next publish or quote refresh. The preview shows\nthis first, and already-published versions don't change. Discarding changes or\nrestoring a version removes comments, and the confirm dialog says so.</p>\n<p><strong>Focus view</strong> (#126). A full-screen writing view in the full editor: the icon at the\nright of the editor's head line, or ⌘⇧↩ / Ctrl+Shift+Enter; Esc leaves. It has\ntypewriter scrolling, controls that fade while you type, the counts in a corner, and a\n<strong>preview</strong> tab (⌘⌥↩ / Ctrl+Alt+Enter). Text, caret, scroll and undo history all\nsurvive the switch, and autosave keeps running.</p>\n<p><strong>Word count while writing</strong> (#125). The <code>word-count</code> extension now also shows its\ncount beside the character count, in the composer and the full editor, through a\nnew general <code>draftCounter</code> extension slot. Like the character count, it leaves comments\nto self out.</p>\n<p><strong>Extension pages can sit in the main menu</strong> (#133). <code>page.mainMenu: { icon }</code> links an\nextension page from the main menu, above compose, instead of from More. Browser only.</p>\n<p><strong>A quote's label is shown to readers</strong> (#136, ROADMAP row 79, decision #81). A labelled\ndirective, <code>![[id | text]]</code>, bakes <code>data-blyg-label</code> on its blockquote. Public pages,\nthe reader and fork flattening use it as the attribution link's text. What the link\nsaid before stays beside it, so a label never hides whose quote it is and is never\nshown as the quoted item's title. Unlabelled quotes bake byte-identically. The reader\nconformance suite goes from 74 to 79 passing.</p>\n<p><strong>Single-node deploys</strong> (#138). A self-host whose <code>wrangler.private.jsonc</code> has no\n<code>env</code> block (one target, <code>&quot;env&quot;: &quot;&quot;</code>) now passes <code>npm test</code> and <code>deploy:all</code>'s\ncross-check. The pinned-<code>account_id</code> guard still applies.</p>\n<p>Private contract, SDK and protocol version unchanged (<code>&quot;0.4&quot;</code>).</p>\n<p><strong>Migrations:</strong> none.</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:18787ed303e6fb5ed553cedea6ad600b4c6cf743a0fbf014b3ef799536a57500","media":[],"transclusions":[],"generated":[{"sources":[],"model":"claude-opus-5-5"},{"sources":[],"model":"claude-opus-5-5"}],"changelog":[{"version":1,"at":"2026-11-08T02:53:09Z","note":"Studio 0.57.0 to 0.58.0 released."}]}