Blygger Studio 0.63.0: Tangling, placeholders, and links on the wire
Released 2026-11-18, the reference client. v0.63.0 on GitHub.
Tangling (decisions #78, #100; ROADMAP row 45). Wrap a passage in ![[+ …]] and
publishing makes it a new item of its own, quoted back where it stood: the thread keeps
reading the same, and the passage gains its own page, version history and feed entry. Each
new item is a thread. Publish shows a count first ("this will create N new items") and
asks before minting them, for the studio and for any client on the API (a publish that
would tangle answers 409 tangle-confirmation-required until it sends tangle: true).
Nothing is minted unless every new item and the thread itself would publish; the new items
publish first, then the thread, so the thread is the newest entry (§13.7). A tangle that
stopped part way is finished by the next publish. Up to 10 spans per publish. The preview
shows a span as a dashed quote; spans are inert in code, TK scopes and comments.
Placeholders. [[+ text]] inline makes a new thread for an idea not yet written and
turns the sentence's text into a link to it, [[id | text]]. The new thread's text is the
anchor text as a heading, and its working copy carries a comment naming the thread and
the sentence it came from (comments never publish). Placeholders share tangling's count,
cap and confirmation.
Links on the wire (spec 0.4 §10.3a, decision #79; ROADMAP row 77). Every version
records the items its [[id]] links resolve to, in text order, and item documents carry
them as links[], each with an origin when it is another blyg's. Imports store them.
A link to another blyg's item now sends it a mention; the receiver files it as link,
the last of the §15.4 relations. A link is a notice: it is never listed among an item's
public responses (§15.5). The syntax page says so beside [[id]].
Folding (spec §13.7, eighteenth revision, decision #112). A thread's placeholders fold under it as its parts do, but only when published in the same act and saying no more than the link's own text. A chapter linked by a contents page published seconds later is its own arrival. Your own items fold by link only when the thread minted them.
Local patches. npm run patches lists the commits this install carries that upstream
does not, and flags the ones that touch the wire. Settings shows "This build carries N
local patches". npm run upgrade lists them before merging and names the local commits in
any file that conflicts. The bug template asks for the count. The developers' guide,
Where does my change belong?, says when a change should be a
patch, a mod, an extension or a pull request.
Publish takes tangle and answers parts: [{id, version}]; items carry tangled_from;
versions carry links_json; the mention relation enum gains link. Private contract
5.12.0, SDK 0.18.0. Migrations: two. 0047_tangled_from.sql adds items.tangled_from;
0048_links.sql adds versions.links_json and imported_items.links_json. Both recreate
their tables' change triggers. Versions published before 0048 carry no links[] until
they are next published.
This announcement is drafted from the release's section of CHANGELOG.md, which is where it is maintained. To comment, respond to this item from your own blyg.