Logic-Loom v0.1.0-alpha.7

Logic-Loom v0.1.0-alpha.7

Seventh alpha — the "packaged builds actually run the pipelines" cut.
If you installed alpha.5 or alpha.6 and the Zotero pipeline died the moment
you clicked Run, this is the release that fixes it.

Fixed: the Zotero pipeline failed in every packaged build

Running any zsum pipeline stage from an installed Logic-Loom failed
immediately with:

logic-loom-api: error: unrecognized arguments: -m logic_loom_api._zsum_launcher cards

Cause. The sidecar spawns the zsum CLI through its own runtime as
<sys.executable> -m logic_loom_api._zsum_launcher <stage>. In a packaged
build sys.executable is the frozen logic-loom-api binary, not a Python
interpreter — PyInstaller's bootloader implements no -m, so it forwarded
-m … straight to the sidecar's own argument parser, which rejected it.

Why it escaped earlier releases. Development runs are unaffected: there
sys.executable is the uv-managed .venv/bin/python, which has a real -m.
The bug only ever existed in packaged builds, which is exactly where it went
unexercised.

Fix. Bundled modules are now addressed through a runtime-aware helper —
-m in development, and a hidden --run-module re-entry flag when frozen,
dispatched via runpy before argument parsing. This mirrors the
--install-runtime-pkg escape hatch the sidecar already used for the same
class of problem.

The identical latent bug in the NotebookLM node-generation dispatch is
fixed by the same change; it had been carrying a known follow-up marker since
issue #103.

If you saved Settings on alpha.5 or alpha.6

zsum_python_cmd is persistable from the Settings page, so a packaged build
that saved settings before this release has a permanently dead command stored
in ~/.config/logic-loom/config.toml. Logic-Loom now detects that specific
stale value on load and drops it so the working default is regenerated — no
manual edit required. A custom command pointing at a real external
interpreter is left untouched.

Also in this release

• Local installer (local_install_and_clean.sh) — one command to sync the
  sibling repos, refresh vendored sources, build, install to /Applications,
  and clean up build artifacts.
• Vendoring: zotero-summarizer converted from a git subtree to a
  content-copy; AKMS refreshed to 7e07ace, MechDSL to edc4310.
• Test reliability: a debounce test that raced a fixed sleep against a
  50 ms timer is now poll-based, ending intermittent CI failures that moved
  between Linux and Windows.
• Documentation: packaging and GitNexus reference content moved into
  lazy-loaded skills.

No UI or API surface changed in this release.

Platform availability

Built by the public build-binaries.yml workflow on real macOS, Linux, and
Windows runners.

• macOS Apple Silicon — .dmg
• Linux x86_64 — .deb and .AppImage
• Windows x86_64 — .msi and NSIS .exe installer

Asset names are unchanged from alpha.6 (Tauri defaults, e.g.
Logic-Loom_0.1.0_aarch64.dmg). A single SHA256SUMS.txt manifest covering
every asset ships alongside the binaries.

Verifying downloads

shasum -a 256 -c SHA256SUMS.txt

Logic-Loom v0.1.0-alpha.6

Logic-Loom v0.1.0-alpha.6

Sixth alpha — a release-plumbing cut, not a feature cut. The app is
functionally identical to v0.1.0-alpha.5; what changed is how releases are
built and published. Binaries now come from a dedicated public build pipeline
under a two-repo release model.

There are no application, backend, or UI changes since v0.1.0-alpha.5. If
you are already on alpha.5, upgrading gets you the same app from the new
distribution path — install it only to confirm the new pipeline's artifacts.

Two-repo release model

Releases are now a single version tag pushed to two repos, each reacting to it
differently:

• SOSOVSKI/Logic-Loom (private source) — .github/workflows/release.yml
  now cuts a source-only GitHub Release (…-source.{tar.gz,zip} +
  SHA256SUMS). It no longer builds binaries.
• CEmM2/Logic-Loom-releases (public) — .github/workflows/build-binaries.yml
  checks out the private source at the tag via a PAT, builds the
  macOS/Linux/Windows bundles on real runners, and attaches them (plus
  SHA256SUMS.txt) to the public Release for that tag.

scripts/release.sh was rewritten to orchestrate this: it pushes the tag to
both repos, idempotently, source first. See the "Releases" section of the
README.md for the full flow and flags.

Platform availability

Multi-platform, now built by the public build-binaries.yml workflow on real
macOS, Linux, and Windows runners.

• macOS Apple Silicon — .dmg
• Linux x86_64 — .deb and .AppImage
• Windows x86_64 — .msi and NSIS .exe installer

A single SHA256SUMS.txt manifest covering every asset ships alongside the
binaries.

Heads-up: asset filenames changed

The new pipeline publishes Tauri's default artifact names rather than the older
hand-normalized scheme. If you script downloads, update your expected names:

Platform	alpha.6 asset
macOS (Apple Silicon)	Logic-Loom_0.1.0_aarch64.dmg
Linux (AppImage)	Logic-Loom_0.1.0_amd64.AppImage
Linux (deb)	Logic-Loom_0.1.0_amd64.deb
Windows (NSIS)	Logic-Loom_0.1.0_x64-setup.exe
Windows (MSI)	Logic-Loom_0.1.0_x64_en-US.msi

(Previously: Logic-Loom-0.1.0-alpha.5-<platform>.<ext>.)

Verifying downloads

shasum -a 256 -c SHA256SUMS.txt

Logic-Loom v0.1.0-alpha.5

Logic-Loom v0.1.0-alpha.5

Fifth alpha — the app now ships curated knowledge and ready-to-run
starter batches. A gated, versioned library of established nodes is
bundled and surfaced in-app, and a promotion path turns reviewed drafts into
shippable Tier-A content.

Builds on v0.1.0-alpha.4 with two coordinated capabilities: bundled
starter batches (Part 1) and a curated established-node library (Part 2),
plus the draft→established promotion tooling that connects them.

Platform availability

Multi-platform, built by the GitHub Actions release.yml workflow on real
macOS, Linux, and Windows runners.

• macOS Apple Silicon — .dmg
• Linux x86_64 — .deb and .AppImage
• Windows x86_64 — .msi and NSIS .exe installer

Per-platform SHA-256 manifests ship alongside the binaries as SHA256SUMS files.

What's new since v0.1.0-alpha.4

Curated established-node library (Tier A)

The app now ships a read-only, versioned library of established knowledge
nodes, gated mechanically so nothing unvetted can leak in:

• Curated nodes live in a source tree with a frozen frontmatter contract and a
  PROVENANCE.toml sidecar (who verified it, when, version, source).
• A build guard refuses to bundle anything lacking status: established,
  so the shipped library is authoritative by construction — never by discipline.
• At runtime the library is unioned into the graph as a read-only second
  source with provenance and tier stamped onto every node.
• The UI distinguishes Established vs Draft/Generated with badges, offers a
  report-an-error path on established nodes, and a copy-to-my-vault
  action so you can fork an established node into your own editable workspace.

Library version 1.0 ships in this release (5 verified nodes across
computational-mechanics and numerical-methods).

Bundled starter batches (Tier B)

First-run seeding now drops a starter-batch seed pack into your AKMS
workspace so the Batches tab is useful immediately, framed clearly as
draft/generated (Tier-B) content that is your own to run and edit — visually
never co-mingled with the shipped Tier-A library.

Draft→established promotion path

A new scripts/promote_node.py closes the loop from a reviewed draft to
shippable Tier-A content: it validates a node against the real schema, stamps
status: established, records provenance in the sidecar, and files the node
into the curated tree — all-or-nothing and non-destructive, with the build
guard as the mechanical backstop. A PROMOTION_CHECKLIST.md documents the
human-review gate that defines "established".

Under the hood

• Node discovery in the curated tree is now identity-based (a file is a node
  only if its frontmatter carries an id), so documentation living beside the
  nodes never mis-registers.
• Security hardening on the copy-to-vault path (resolved-path containment,
  O_NOFOLLOW, and a dir_fd capability guard) from an adversarial review.
• The cross-repo tracker (dev/STATUS.md) records both shipped capabilities and
  the established-library versioning + bump procedure.

Verifying downloads

shasum -a 256 -c SHA256SUMS.txt

Logic-Loom v0.1.0-alpha.3

Logic-Loom v0.1.0-alpha.3

Third alpha — the Research Assistant learns, LLM-backed modes turn on, and
MechDSL joins the app as a Taichi-free FEM code generator.

Builds on v0.1.0-alpha.2 with a full Learn workflow, host-driven LLM
learning modes, and a new MechDSL computational-mechanics bridge — plus a
large zotero-summarizer upgrade.

Re-cut (2026-06-17): binaries rebuilt from master after merging the
vendored-package refresh — akms-learn advanced to current AKMS main (the
real-graph-audit lesson fixes) and mechdsl-core to MechDSL 0.2.0. No
app-feature changes versus the original alpha.3 cut.

Platform availability

Multi-platform, built by the GitHub Actions release.yml workflow on real
macOS, Linux, and Windows runners.

• macOS Apple Silicon — .dmg
• Linux x86_64 — .deb and .AppImage
• Windows x86_64 — .msi and NSIS .exe installer

Per-platform SHA-256 manifests ship alongside the binaries as SHA256SUMS files.

What's new since v0.1.0-alpha.2

Research Assistant — Learn tab

A new Learn tab compiles AKMS knowledge into learning artifacts (outlines,
anthologies, notebooks, assessments) through the bundled akms-learn engine.
The UI is capability-driven: available modes and exporters are advertised by the
backend, and unavailable or planned modes render disabled instead of failing on
submit. Includes mode-specific forms, Pass B preview panels, artifact history
with an open-export-folder action, a domain-pack status card, a "Send to Learn"
handoff from the Graph view, and a Learning Source Review Bundle export.

LLM-backed learning modes

Modes that need a language model (e.g. expanded/adaptive generation) now turn on
when the host application supplies an LLM provider — the provider is injected
into each learning request, and the mode catalog reflects real host availability
so a provider-less install degrades gracefully.

MechDSL — computational-mechanics bridge

A new MechDSL mode compiles % mechanics LaTeX problem statements into FEM
solver code and transpiles algorithm boxes, with an Overview / Compile /
Artifacts UI. It ships without the Taichi runtime: the emit and transpile
paths are Taichi-free, so the capability is available out of the box and only
the optional on-device verification path would require the extra. This keeps
the bundled engine lightweight.

Vendored dependency upgrades

• zotero-summarizer: large upstream merge adding the NotebookLM pipeline
  (zsum nlm) as an LLM backend for card/digest generation, and section-aware
  PDF extraction (extraction.mode: sections) using TOC/heading detection.
• akms-learn vendored at current AKMS main — LLM provider seam plus the
  real-graph-audit lesson fixes (section heading matching, assessment
  references, and section-based pitfalls).
• MechDSL (mechdsl-core + algo2code) vendored at 0.2.0 to back the
  MechDSL bridge.

Desktop

• Light / dark / system theme toggle.
• Translucent Logic-Loom backdrop behind every route.

Verifying downloads

shasum -a 256 -c SHA256SUMS.txt

Logic-Loom v0.1.0-alpha.2

Logic-Loom v0.1.0-alpha.2

Second alpha — usability fixes, AKMS bundling, and the start of the
Research Assistant surface.

Builds on v0.1.0-alpha.1 with a hardened landing experience, working
batch/runs/prompt flows, and the AKMS Claude assets actually packaged
into the sidecar.

Platform availability

First multi-platform Logic-Loom release. Artifacts are produced by the
GitHub Actions release.yml workflow on real macOS, Linux, and Windows
runners.

• macOS Apple Silicon — .dmg
• Linux x86_64 — .deb and .AppImage
• Windows x86_64 — .msi and NSIS .exe installer

Per-platform SHA-256 manifests ship alongside the binaries as
SHA256SUMS files.

What's new since v0.1.0-alpha.1

Landing and navigation

• Logic-Loom landing page with the full banner, three mode tiles
  (Zsum / AKMS / Assistant), and a watermark behind the action grid.
• Top bar gets a clickable LogicLoom home link plus a top-level
  Settings entry that opens a unified settings page with a Zsum /
  AKMS / Assistant sidebar.
• /zsum index now shows a proper Overview (replacing the legacy
  picker/pipeline button list).
• All "Phase N placeholder" panes replaced with real content:
  Zsum Overview, Zsum Collections (collection picker + filterable
  paper table with per-paper digest state), Zsum Runs (full RunsPage),
  AKMS Overview, Assistant Runs.

Vault and markdown

• Tailwind Typography plugin wired up — markdown previews finally
  render bullets, headings, code blocks, and tables.
• Tauri opener plugin wired into the AKMS Claude Assets pane so the
  Edit / Open folder / Show default buttons actually open the file
  or folder in the system handler (falls back to clipboard when
  running in the browser dev preview).

AKMS

• AKMS Claude assets are now bundled in the wheel via
  scripts/sync_akms_claude_assets.py. Install + materialize-runtime
  • reset endpoints succeed instead of returning 500 / "failed to
    fetch".
• New AKMS workspace section in Settings → AKMS surfaces the path
  that holds batches.json, prompt-library/, claude-runtime/,
  and run history. Set it once; everything follows.
• "View in Graph" preserves the ?node= query param across the
  legacy redirect, and the graph view shows a "Regenerate graph"
  button when the cached graph predates a new node.
• AKMS Batches gets + Add, Archive, and Delete buttons; the
  detail header sums them all up. Sources tab is read-only and points
  the user at Assistant → Batches for curation.

Prompts and schemas

• All 14 canonical prompt slots ship with bundled defaults. The
  prompt store now reads both .logicloom.json wrappers and raw
  .md files so Assistant prompts (literature survey, paper intro,
  related work, proposal ideas, method comparison, annotated
  bibliography) load out of the box.
• New decoupled JSON schemas: PromptSchema is a separate entity
  with full CRUD (/api/prompts/schemas), and PromptVariant now
  carries an output_schema_id field. Variants can be paired with
  any schema without rewriting prose.
• paper_card_v1 JSON schema ships bundled and is linked to the
  default zsum.paper_card variant.
• Prompt Library page: schema selector dropdown in the variant
  editor + a new SchemaManager panel with create / edit / delete.
• Delete button for user variants in the Prompt Library.
• Empty / whitespace-only variants now fail validation with a clear
  "content is empty — variant must have a body" message.

Assistant

• Assistant Batches Sources tab gets a Zotero library picker:
  collection dropdown + citekey/venue filter + per-row checkboxes,
  with a separate collapsed <details> section for manual entry.
• Related Papers panel pins the Find related papers (N seeds)
  button to a sticky header with a yellow hint when seeds are
  missing.
• RelatedPaperService.find_similar and the broader
  PaperDiscoveryService.search now tolerate per-provider failures:
  if Semantic Scholar 429s, OpenAlex results still come through.
  Both failing surfaces the first error.
• Workflows → "Run with this workflow" carries ?workflow_id= and
  respects the current mode (assistant vs akms), and the receiving
  BatchesPage auto-opens the run dialog with the workflow
  pre-selected.
• Batch settings, prompt-profile selectors, and the Run dialog all
  use real dropdowns populated from /api/prompts/profiles and
  /api/workflows instead of free-text inputs.

Operations

• New pnpm sync:akms-assets, pnpm sync:zsum-prompts,
  pnpm sync:thirdparty scripts. The three sidecar:build:*
  scripts run sync:thirdparty first so packaged sidecars always
  include the latest vendored content.
• Clearer 400 messages when bundled AKMS resources aren't present in
  a build (previously: opaque 500).

Still required

• Zotero
• Better BibTeX export
• access to local PDFs
• a configured LLM backend or provider CLI, such as:
  • Ollama / LM Studio / OpenAI-compatible server
  • Claude CLI
  • Codex CLI
  • Gemini CLI

Install notes

macOS

Unsigned alpha — Gatekeeper may warn the app is from an unidentified
developer.

1. Right-click Logic-Loom.app
2. Click Open
3. Confirm Open

If Gatekeeper still blocks it, advanced users can run:

xattr -dr com.apple.quarantine /Applications/Logic-Loom.app

Windows

Unsigned alpha — Windows SmartScreen may warn. Click More info → Run
anyway. The MSI and NSIS .exe produce equivalent installs; pick
whichever your environment prefers.

Linux

.deb for Debian/Ubuntu (sudo apt install ./Logic-Loom_<ver>_amd64.deb).
.AppImage for distro-agnostic single-file launch (chmod +x then run).

Known issues

• First-run setup still requires manual path selection.
• Public-pool Semantic Scholar rate limits surface quickly when
  exploring discovery; configure an API key under Settings →
  Assistant for steady use.
• QMD-backed vault search requires registering the vault as a QMD
  collection first; the ripgrep backend is the default and works
  out of the box.
• The bundled graph cache may lag the live nodes vault — use the
  Regenerate graph button when "View in Graph" reports an unknown
  node.

Checksums

Per-platform SHA256SUMS files are produced inline by the release
workflow and attached alongside the binaries on this GitHub Release.

Logic-Loom v0.1.0-alpha.1

Logic-Loom v0.1.0-alpha.1

Draft release notes for the first public macOS alpha.

First alpha release for friends, colleagues, and early testers.

Platform availability

• macOS Apple Silicon only
• Release asset: Logic-Loom-0.1.0-alpha.1-macOS-arm64.dmg
• Windows and Linux builds are not attached to this tag

Included in this alpha

• Logic-Loom desktop app
• React/Tauri frontend
• Bundled logic-loom-api Python sidecar
• Bundled zotero-summarizer package
• Bundled Python runtime and runtime dependencies required by the sidecar

Still required

• Zotero
• Better BibTeX export
• access to local PDFs
• a configured LLM backend or provider CLI, such as:
  • Ollama / LM Studio / OpenAI-compatible server
  • Claude CLI
  • Codex CLI
  • Gemini CLI

AKMS status

Logic-Loom includes AKMS integration points, but AKMS-specific workflows remain optional and release-dependent.

Depending on the exact asset you download and your local setup:

• AKMS tabs may be gated
• graph features may require a readable AKMS source vault
• batch/node workflows may still rely on AKMS-specific resources outside the base alpha path

Install notes

macOS

Because this is an alpha build, macOS may warn that the app is from an unidentified developer.

Try:

1. Right-click Logic-Loom.app
2. Click Open
3. Confirm Open

If macOS still blocks it, advanced users can run:

xattr -dr com.apple.quarantine /Applications/Logic-Loom.app

Known issues

• First-run setup may still require manual path selection.
• Some settings and terminology remain closer to the underlying research tooling than to a polished end-user installer.
• External provider CLIs/services still need to be installed and authenticated separately.
• This tag is macOS Apple Silicon only.

Checksums

Attach checksums/v0.1.0-alpha.1/SHA256SUMS.txt to the GitHub Release assets.

If you also want a single-file checksum alongside the manifest, use:

• checksums/v0.1.0-alpha.1/Logic-Loom-0.1.0-alpha.1-macOS-arm64.dmg.sha256.txt