Release 0.11.0: extensions UX, notes vaults, reading slots, lineage counts

.github/ISSUE_TEMPLATE/extension-submission.yml

@@ -0,0 +1,82 @@
+name: Submit a community extension
+description: Ask for your Burrow extension to be listed on the Community extensions page.
+title: "Community extension: "
+labels: ["community-extension"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Prefer a pull request? Add an `[[extension]]` entry to `extensions/community.toml` instead (see "Submit your extension" on the Extensions page of the documentation).
+
+        **The Burrow maintainers don't review, verify, audit or endorse community extensions.** We check that the entry is well-formed, add it, and the listing says it is used at the reader's own risk. Don't put an email address or other personal data in this form.
+  - type: input
+    id: name
+    attributes:
+      label: Name
+      description: The `name` in your extension.toml. Lowercase kebab-case, at most 40 characters.
+      placeholder: wordcount
+    validations:
+      required: true
+  - type: input
+    id: title
+    attributes:
+      label: Title
+      description: A short human name, at most 60 characters.
+      placeholder: Word count
+    validations:
+      required: true
+  - type: input
+    id: description
+    attributes:
+      label: Description
+      description: One line of plain text, at most 160 characters.
+      placeholder: Shows the word count and reading time of the open draft.
+    validations:
+      required: true
+  - type: input
+    id: repo
+    attributes:
+      label: Source repository
+      description: An https:// link to the public source code.
+      placeholder: https://github.com/example/burrow-ext-wordcount
+    validations:
+      required: true
+  - type: input
+    id: homepage
+    attributes:
+      label: Homepage (optional)
+      placeholder: https://example.com/wordcount
+  - type: input
+    id: author
+    attributes:
+      label: Author
+      description: Your GitHub handle, without the @. Not an email address.
+      placeholder: example
+    validations:
+      required: true
+  - type: textarea
+    id: capabilities
+    attributes:
+      label: Capabilities
+      description: Exactly what your manifest's `capabilities` asks for, one per line (or "none").
+      placeholder: |
+        items.read
+        ui
+    validations:
+      required: true
+  - type: checkboxes
+    id: platforms
+    attributes:
+      label: Platforms
+      options:
+        - label: macOS
+        - label: Windows
+  - type: checkboxes
+    id: understood
+    attributes:
+      label: Before you submit
+      options:
+        - label: I wrote this extension, or I maintain it, and its source code is public.
+          required: true
+        - label: I understand the maintainers check the entry's format only, and that the listing can be removed if it's reported as malicious or misleading.
+          required: true

.github/PULL_REQUEST_TEMPLATE/extension.md

@@ -0,0 +1,23 @@
+<!--
+Listing a community extension. This template is for a pull request that adds
+(or updates, or removes) one [[extension]] entry in extensions/community.toml.
+Open it with ?template=extension.md on the compare URL.
+-->
+
+## Extension
+
+- **Name:** <!-- e.g. wordcount -->
+- **Source:** <!-- e.g. https://github.com/example/burrow-ext-wordcount -->
+
+## Checklist
+
+- [ ] This pull request changes only `extensions/community.toml`, and only one entry.
+- [ ] The entry is in alphabetical order by `name`.
+- [ ] `name` matches the `name` in my `extension.toml`.
+- [ ] `capabilities` lists exactly what my manifest asks for.
+- [ ] `repo` links to the extension's source code, which is public.
+- [ ] `author` is my GitHub handle, and there's no email address anywhere in the entry.
+- [ ] `python3 scripts/community-extensions.py check` passes.
+- [ ] I understand that the Burrow maintainers check the entry's format only.
+      They don't review, verify, audit or endorse the extension, and the listing
+      says so. A listing can be removed if it's reported as malicious or misleading.

.github/workflows/ci.yml

@@ -97,6 +97,11 @@ jobs:
         with:
           persist-credentials: false
 
+      # The community extension list: format only (valid TOML, required
+      # fields, names, https URLs, sorted). It never fetches or runs anything.
+      - name: Check the community extension list
+        run: python3 scripts/community-extensions.py check
+
       # The pinned mdBook; fails on mdBook errors or broken links.
       - name: Build the book
         run: scripts/build-site.sh

.github/workflows/pages.yml

@@ -15,6 +15,8 @@ on:
       - "CHANGELOG.md"
       - "scripts/build-site.sh"
       - "scripts/site-linkcheck.py"
+      - "scripts/community-extensions.py"
+      - "extensions/community.toml"
       - ".github/workflows/pages.yml"
   workflow_dispatch:
 

.gitignore

@@ -11,3 +11,5 @@
 
 # The documentation site build (mdbook build site)
 /site/book/
+# Made from extensions/community.toml by scripts/build-site.sh
+/site/src/generated/community-extensions.md

CHANGELOG.md

@@ -15,6 +15,25 @@ teaches something new in the tour, set the newest entry's `version` in
 
 ## [Unreleased]
 
+## [0.11.0] - 2026-10-09
+
+### Added
+
+- **Turn an extension off.** Manage extensions (⇧⌘P › Manage extensions…) has **Turn off** for any extension that's on, whatever state it's in. It stops the extension and keeps what you allowed, so Turn on brings it back as it was. **Forget permissions** turns it off and clears what you allowed, so the next Turn on asks again. The consent sheet gains **⌘⌫ turn off**, so you can back out the moment you see what an extension asks for.
+- **Several notes folders.** markdown-notes can open any number of folders (Obsidian vaults, say). The Notes tab in the notes drawer has a chip for each folder, plus **Add folder…** and **Remove from Burrow** (which only removes the folder from Burrow and never touches your files), and remembers the folder you were in. Settings › Notes folders lists them, and you can add several at once. ⌘K's notes chip searches every folder. In the config they are `vault=` for the first and `vault-<label>=` for each one after.
+- **Reading time and Inspect**, two bundled extensions ported from Blygger Studio 0.39, both off until you turn them on. **reading-time** puts an estimated reading time at the end of each post's byline in the Stream and the Reader ("· 4 min"; hover for the word count), counted the way the studio counts. **inspect** adds a ⋯ chip to each post you read, with an Inspect sheet showing the record Burrow holds (ids, versions, references, hashes) and its JSON with the bodies left out, with Copy JSON.
+- **Extensions can add to what you read.** Two new slots in the extension protocol, behind the `reading.read` permission: a short marker at the end of each post's byline, and rows in a post's ⋯ sheet. See [Extensions](https://aneeshsathe.github.io/blygger-desktop/extensions.html).
+- **Import and export subscriptions as OPML.** Blyg › Import Subscriptions from OPML… (or Import OPML… on the Subscriptions screen) reads an export from another feed reader, lists its feeds with the ones you already follow marked, and subscribes your blyg to the ones you tick, at a steady pace, filing them in an **Imported feeds** folder in the Reader, with a summary and Retry for any that fail. Imported feeds stay out of your public blogroll. Blyg › Export Subscriptions as OPML… saves all of them. `blygger +import-opml` and `+export-opml` do the same from a terminal.
+- **Community extensions.** The docs now list extensions other people have made, from `extensions/community.toml`; submit yours with a pull request or the issue form. Burrow's maintainers don't review or vouch for them: an extension runs with your user's rights, so read its source and use it at your own risk.
+
+### Changed
+
+- **The lineage glyph shows counts.** Beside the kinds, the glyph shows how many posts a post draws on and how many known here draw on it ("2 · 3"). The ⌘J view and the action ring show the same numbers, by kind. On a blyg that runs the studio's lineage-glyph extension, Burrow uses the blyg's own counts; elsewhere it works them out from what it holds, using the same rules. Opening a post from ⌘J marks it read, as opening it from the list does.
+- **Read state needs the `reading:state` permission** (Blygger Studio 0.39 moved marking posts read and unread there). Burrow now asks for it. **After updating, sign in again once** (Burrow › Disconnect…, then Sign in with browser, and allow every permission) so read marks sync between your Macs. Until then they're kept on this Mac and wait to be sent, and everything else syncs as usual. Studios before 0.39 are unaffected.
+- **Cross-posting stays beside your work.** A cross-post run opens the browser in the usual foldable side pane, not over the whole window, and its Preview and Post sheets sit beside the page so you can see it. Fold the pane mid-run and the run carries on ("macro running · show pane" in the status bar). The pane unfolds itself before Burrow types into the page.
+- **The tour teaches what's new.** After an update, "Show me what's new" starts at the first step for that release (NEW IN 0.11.0), and the tour now walks through extensions, Turn off, notes folders, reading time and inspect, OPML import, ⌘N, ✂ Clip and cross-post, on sample data, without changing your config. It also covers what 0.10.0 added, which its tour skipped.
+- **markdown-notes no longer assumes `~/Notes`.** With no folder chosen it asks only to show messages, and the Notes tab offers **Choose a folder…**, so the consent sheet only ever names folders you picked. A config with `vault=` works as before.
+
 ## [0.10.0] - 2026-10-09
 
 ### Added

Cargo.toml

@@ -1,10 +1,10 @@
 [workspace]
 resolver = "3"
-members = ["crates/blyg-core", "crates/blyg-ai", "crates/blyg-render", "crates/blyg-ext", "crates/blyg-ext-notes", "crates/blyg-ext-crosspost", "crates/blyg-app"]
+members = ["crates/blyg-core", "crates/blyg-ai", "crates/blyg-render", "crates/blyg-ext", "crates/blyg-ext-notes", "crates/blyg-ext-crosspost", "crates/blyg-ext-reading-time", "crates/blyg-ext-inspect", "crates/blyg-app"]
 
 [workspace.package]
 edition = "2024"
-version = "0.10.0"
+version = "0.11.0"
 license = "MIT"
 description = "A fast, local-first macOS studio for Blygger blogs"
 # Placeholder repo; set it with scripts/set-repo.sh (see packaging/config.env).

crates/blyg-app/Cargo.toml

@@ -16,6 +16,9 @@ blyg-ai = { path = "../blyg-ai" }
 blyg-ext = { path = "../blyg-ext" }
 blyg-ext-notes = { path = "../blyg-ext-notes" }
 blyg-ext-crosspost = { path = "../blyg-ext-crosspost" }
+# --- reading slots --- (reading-time and inspect, `blygger +ext <name>`)
+blyg-ext-reading-time = { path = "../blyg-ext-reading-time" }
+blyg-ext-inspect = { path = "../blyg-ext-inspect" }
 # gpui-kit pins the matching GPUI snapshot (gpui-pre 0.3.6) plus gpui-base /
 # gpui-component 0.6.6. We use gpui-base's unstyled textarea and draw the rest.
 gpui-kit = { version = "=0.6.6", default-features = false }

crates/blyg-app/src/app.rs

@@ -2088,6 +2088,7 @@ impl Render for MainView {
             .children(self.render_sheet(&ui_font, &body_font, cx))
             .children(self.render_ai_overlay(&ui_font, &body_font, cx)) // --- AI ---
             .children(self.render_ext_overlay(&ui_font, cx)) // --- extensions ---
+            .children(self.render_slots_sheet(&ui_font, cx)) // --- reading slots ---
             .children(self.render_reading_sheet(cx)) // --- reading & versions ---
             .children(profile_overlay) // --- profiles ---
             .children(self.render_toast())
@@ -2659,6 +2660,7 @@ impl MainView {
             .children(screen.to_read.map(|t| div().id("to-read").child(t)))
             .children(self.render_server_notice())
             .children(self.render_ext_notice(cx)) // --- extensions ---
+            .children(self.render_macro_status(cx)) // --- browser macros ---
             .children(self.render_update_notice(cx)) // --- auto-update ---
             .children(self.render_ai_status()) // --- AI ---
             .child(
@@ -3089,12 +3091,13 @@ impl MainView {
                 let explain = match way {
                     ConnectWay::Browser => {
                         "Burrow opens your blyg's studio in your browser. Sign in there and \
-                         allow Burrow; it gets renewable access with all four permissions, \
+                         allow Burrow; it gets renewable access with every permission, \
                          kept in your macOS Keychain. Needs blygger-studio 0.28 or later."
                     }
                     ConnectWay::Token => {
                         "Make a token in your blyg's Studio → More → Client access: choose REST \
-                         API and all four permissions (read, draft, publish, manage). It lasts \
+                         API and every permission (read, draft, publish, manage, and reading:state \
+                         where offered). It lasts \
                          30 days. A server with Burrow's extensions can use its owner token \
                          here instead. Either is kept in your macOS Keychain."
                     }
@@ -3289,7 +3292,8 @@ impl MainView {
                 .absolute()
                 .top(px(TITLEBAR_H))
                 .left_0()
-                .right_0()
+                // --- browser macros --- beside the side pane, not over it
+                .right(self.macro_sheet_right().unwrap_or(px(0.)))
                 .flex()
                 .justify_center()
                 .child(