{"blyg":"0.4","id":"38kgkb8nstt10rne2gz0ye2k9a","kind":"thread","origin":"https://blyg.pioneeringspirit.xyz/","page":"t/38kgkb8nstt10rne2gz0ye2k9a/","author":{"name":"PAtwater","url":"https://blyg.pioneeringspirit.xyz"},"created":"2026-11-21T04:09:28Z","updated":"2026-11-21T04:11:03Z","version":1,"content_md":"![[76kjxyfywjvkshcvagc89j94s8]]\n\nOh just seeing this and sent a pr last night. Please feel free to close that without merging or whatever is necessary. \n\nOut of curiosity what does code cleanup look like in this agentic era? Asking the bots to summarize spaghetti ness and where to refactor? Curious if there's any prompt types there. ","content_html":"<blockquote class=\"blyg-transclusion\" data-blyg-id=\"76kjxyfywjvkshcvagc89j94s8\" data-blyg-version=\"1\" data-blyg-origin=\"https://blyg.aneeshsathe.com/\">\n<blockquote class=\"blyg-transclusion\" data-blyg-id=\"6kybmed14xpazrccnkr8qwqabq\" data-blyg-version=\"1\" data-blyg-origin=\"https://blyg.pioneeringspirit.xyz/\">\n<blockquote class=\"blyg-transclusion\" data-blyg-id=\"5jpyygskg74wz0yr971w9976sd\" data-blyg-version=\"1\" data-blyg-origin=\"https://blyg.aneeshsathe.com/\">\n<p>The most exciting update to date! 🫚</p>\n\n<blockquote class=\"blyg-transclusion\" data-blyg-id=\"0enf8zg43d5rtvsr5xre4gktbd\" data-blyg-version=\"1\" data-blyg-origin=\"https://blyg.blygger.org/\" data-blyg-label=\"Blygger Studio 0.63.0: Tangling, placeholders, and links on the wire\">\n<div class=\"blyg-tk-gen\"><h1>Blygger Studio 0.63.0: Tangling, placeholders, and links on the wire</h1>\n<p><em>Released 2026-11-18, the reference client. <a href=\"https://github.com/blygger/blygger-studio/releases/tag/v0.63.0\">v0.63.0 on GitHub</a>.</em></p>\n<p><strong>Tangling</strong> (decisions #78, #100; ROADMAP row 45). Wrap a passage in <code>![[+ …]]</code> and\npublishing makes it a new item of its own, quoted back where it stood: the thread keeps\nreading the same, and the passage gains its own page, version history and feed entry. Each\nnew item is a thread. Publish shows a count first (&quot;this will create N new items&quot;) and\nasks before minting them, for the studio and for any client on the API (a publish that\nwould tangle answers <code>409 tangle-confirmation-required</code> until it sends <code>tangle: true</code>).\nNothing is minted unless every new item and the thread itself would publish; the new items\npublish first, then the thread, so the thread is the newest entry (§13.7). A tangle that\nstopped part way is finished by the next publish. Up to 10 spans per publish. The preview\nshows a span as a dashed quote; spans are inert in code, TK scopes and comments.</p>\n<p><strong>Placeholders.</strong> <code>[[+ text]]</code> inline makes a new thread for an idea not yet written and\nturns the sentence's text into a link to it, <code>[[id | text]]</code>. The new thread's text is the\nanchor text as a heading, and its working copy carries a comment naming the thread and\nthe sentence it came from (comments never publish). Placeholders share tangling's count,\ncap and confirmation.</p>\n<p><strong>Links on the wire</strong> (spec 0.4 §10.3a, decision #79; ROADMAP row 77). Every version\nrecords the items its <code>[[id]]</code> links resolve to, in text order, and item documents carry\nthem as <code>links[]</code>, each with an <code>origin</code> when it is another blyg's. Imports store them.\n<strong>A link to another blyg's item now sends it a mention</strong>; the receiver files it as <code>link</code>,\nthe last of the §15.4 relations. A <code>link</code> is a notice: it is never listed among an item's\npublic responses (§15.5). The syntax page says so beside <code>[[id]]</code>.</p>\n<p><strong>Folding</strong> (spec §13.7, eighteenth revision, decision #112). A thread's placeholders fold\nunder it as its parts do, but only when published in the same act <strong>and</strong> saying no more\nthan the link's own text. A chapter linked by a contents page published seconds later is\nits own arrival. Your own items fold by link only when the thread minted them.</p>\n<p><strong>Local patches.</strong> <code>npm run patches</code> lists the commits this install carries that upstream\ndoes not, and flags the ones that touch the wire. Settings shows &quot;This build carries N\nlocal patches&quot;. <code>npm run upgrade</code> lists them before merging and names the local commits in\nany file that conflicts. The bug template asks for the count. The developers' guide,\n<a href=\"https://blyg.blygger.org/docs/where-does-it-go.md\">Where does my change belong?</a>, says when a change should be a\npatch, a mod, an extension or a pull request.</p>\n<p>Publish takes <code>tangle</code> and answers <code>parts: [{id, version}]</code>; items carry <code>tangled_from</code>;\nversions carry <code>links_json</code>; the mention relation enum gains <code>link</code>. Private contract\n5.12.0, SDK 0.18.0. <strong>Migrations:</strong> two. <code>0047_tangled_from.sql</code> adds <code>items.tangled_from</code>;\n<code>0048_links.sql</code> adds <code>versions.links_json</code> and <code>imported_items.links_json</code>. Both recreate\ntheir tables' change triggers. Versions published before 0048 carry no <code>links[]</code> until\nthey are next published.</p>\n</div>\n<div class=\"blyg-tk-gen\"><p><em>This announcement is drafted from the release's section of <a href=\"https://github.com/blygger/blygger-studio/blob/main/CHANGELOG.md\"><code>CHANGELOG.md</code></a>, which is where it is maintained. To comment, respond to this item from your own blyg.</em></p>\n</div>\n\n</blockquote>\n\n</blockquote>\n<p>Sending a pr to burrow so we can start tangling! In case you haven't already. Excited to play more with this. Thanks again for leading this great dive into the Thicket. Been a pleasure and an honor.</p>\n\n</blockquote>\n<p>Working on this now and have also run a lot of code clean up so hold the PR because it will not match the state of the app</p>\n\n</blockquote>\n<p>Oh just seeing this and sent a pr last night. Please feel free to close that without merging or whatever is necessary.</p>\n<p>Out of curiosity what does code cleanup look like in this agentic era? Asking the bots to summarize spaghetti ness and where to refactor? Curious if there's any prompt types there.</p>\n","content_hash":"sha256:8c7781f0cb4460ddefd17be4579fbae6da171a69e82c04623b2b3726f4836d45","media":[],"transclusions":[{"id":"76kjxyfywjvkshcvagc89j94s8","version":1,"origin":"https://blyg.aneeshsathe.com/","cited":{"source":"And Yet Here We Are 🚀","author":"Aneesh Sathe","excerpt":"The most exciting update to date! 🫚 Blygger Studio 0.63.0: Tangling, placeholde…","url":"https://blyg.aneeshsathe.com/t/76kjxyfywjvkshcvagc89j94s8/","retrieved":"2026-11-21T04:11:03Z"}}],"stub_of":{"origin":"https://blyg.aneeshsathe.com/","id":"76kjxyfywjvkshcvagc89j94s8","version":1,"cited":{"source":"And Yet Here We Are 🚀","author":"Aneesh Sathe","excerpt":"The most exciting update to date! 🫚 Blygger Studio 0.63.0: Tangling, placeholde…","url":"https://blyg.aneeshsathe.com/t/76kjxyfywjvkshcvagc89j94s8/","retrieved":"2026-11-21T04:11:03Z"}},"changelog":[{"version":1,"at":"2026-11-21T04:11:03Z","note":null}]}