You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Notes from reviewing most of the open PRs over the last day; the detail sits on each PR. Collected here so the state of the queue is in one place. The grouping below is one way to rank it, not a decision — and two of the small ones are mine, which is worth weighing.
The i18n gate: a lint ratchet plus a checked-in English copy inventory. 13/13 green, mostly generated files.
This has to be decided
i18n direction — #494 vs #497. Both land on the same ground. #497 is only the gate (no strings move); #494 is the framework plus a zh-TW locale. They compose in that order, but #494 currently reworks English copy on the way rather than moving it — the Obsidian setting loses its "one-way, edits are never overwritten" guarantee, the mic-device explanation shrinks to five words, and progress labels like Clearing…/Saving… both become "Loading…". Details are on #494. I've closed my own #441 — it was stale and in the way — so this is a two-way choice.
#495 (Apple SystemLanguageModel as the default summariser). 13/13 green and well built. But _adopt_apple_system_default() moves existing macOS installs to apple:system on the next config load, and the Apple path summarises long meetings through a 2800-character snapshot instead of gemma-12b map-reduce. Same meeting, reprocessed, gives a thinner note with nothing saying why. That is a product decision rather than a review question.
Blocked on their authors
feat: parity across chat, notes, folders, and a local MCP server #496 (+19328) — the mock-Ollama fixture lost its fixed port, which breaks the mock contract for the whole model-free T2 lane, not just this PR. Also worth splitting: MCP server / chat / notes+folders. The MCP server itself reviewed clean.
e2e-nightly.yml has been red for at least seven consecutive nights, always the same job (T2 real-summarize), everything else green. Ollama answers /api/chat with a 500 and the job never logs the response body. Worth fixing before the next release, since a permanently red canary reports nothing. I can take that one.
Notes from reviewing most of the open PRs over the last day; the detail sits on each PR. Collected here so the state of the queue is in one place. The grouping below is one way to rank it, not a decision — and two of the small ones are mine, which is worth weighing.
Green and small
Speaker Ninstead of collapsing every remote speaker into one lane (#486). 13/13 green.This has to be decided
i18n direction — #494 vs #497. Both land on the same ground. #497 is only the gate (no strings move); #494 is the framework plus a zh-TW locale. They compose in that order, but #494 currently reworks English copy on the way rather than moving it — the Obsidian setting loses its "one-way, edits are never overwritten" guarantee, the mic-device explanation shrinks to five words, and progress labels like
Clearing…/Saving…both become "Loading…". Details are on #494. I've closed my own #441 — it was stale and in the way — so this is a two-way choice.#495 (Apple SystemLanguageModel as the default summariser). 13/13 green and well built. But
_adopt_apple_system_default()moves existing macOS installs toapple:systemon the next config load, and the Apple path summarises long meetings through a 2800-character snapshot instead of gemma-12b map-reduce. Same meeting, reprocessed, gives a thinner note with nothing saying why. That is a product decision rather than a review question.Blocked on their authors
049bad0aand deletes its tests, and the sidecar is built for macOS 26 while the app still shipsminimumSystemVersion: 14.4.0. Neither has ever run the e2e workflow — only cubic.One thing that isn't a PR
e2e-nightly.ymlhas been red for at least seven consecutive nights, always the same job (T2 real-summarize), everything else green. Ollama answers/api/chatwith a 500 and the job never logs the response body. Worth fixing before the next release, since a permanently red canary reports nothing. I can take that one.