Skip to content

Logic-Loom v0.2.1

A patch release. No Logic-Loom feature changes — this refreshes the vendored AKMS toolchain from 7e07ace to f32d81f and moves the akms / akms-failure-memory git pins from 72494ac to the same commit, so the bundled agent assets and the failure-memory package are current for the first time since v0.1.0-alpha.7.

Why this exists

The two mechanisms Logic-Loom uses to consume AKMS had drifted apart and both were stale. The vendored content copy behind the bundled .claude assets sat 125 commits behind AKMS; the git pin behind the installed packages sat 16 commits behind. A v0.2.0 binary therefore shipped agent assets from July.

Bundled agent assets refreshed and expanded

The curated whitelist (packaging/akms_claude_assets.toml) now picks up AKMS's published agent surface rather than only its internal .claude/ tree, which matters because that directory is stripped from every published AKMS copy and was a fragile source to depend on.

Newly bundled:

  • skills/akms — the core AKMS loop: compile a graph, resolve exact task context, generate role-scoped loadouts, feed outcomes back.
  • skills/deepwiki-nodes — generate domain knowledge nodes from a DeepWiki-indexed repository, the code-sourced sibling of node-gen.
  • skills/akms-spec-check — audit an AKMS implementation against the frozen v2 conformance invariants.
  • hooks/ — two PreToolUse guards: global vault read-only, frozen-schema warning.
  • docs/akms/spec/invariants.md — a normative, checkable subset of the frozen v2 spec with stable INV-* ids.

The existing node-gen skill, digest-refiner, akms-spec-reviewer, and node-gen-invoker assets are refreshed to their current upstream versions. That picks up an upstream fix worth naming: akms-spec-reviewer and akms-spec-check had been pointing at Packages/AKMS/dev/design_docs/, a path that does not exist, so any "clean" spec audit they produced had read no specification at all.

akms-failure-memory 0.1.0 → 0.3.0

  • Preflight no longer enforces artifact identity. It previously ran on every operation and hard-failed on the AKMS version string, a digest over seventeen AKMS source files, and the repo2md checkout's version/commit/cleanliness — with no escape hatch. It now blocks only on an incompatible AKMS schema version or a repo2md that cannot be invoked, and reports everything else as advisories.
  • The provider fingerprint no longer tracks AKMS source bytes. That digest meant any comment or docstring edit upstream changed every fingerprint and marked prior publications stale.

Both reduce spurious failures in ordinary development without weakening the checks that catch real incompatibility.

Known issues

Backend E2E (windows-latest) still exits 1 after the suite passes (821 passed, 6 skipped, then KeyboardInterrupt at threading.py:355). Non-daemon ThreadPoolExecutor workers outlive the run at interpreter shutdown. No test fails and product behaviour is unaffected; recorded as lesson L001 in this repo's .failure-memory/ ledger. Unchanged from v0.2.0.

Everything since v0.2.0

  • Vendored AKMS content copy: 7e07ace → f32d81f
  • akms and akms-failure-memory git pins: 72494ac → f32d81f
  • Five new whitelist sections, sourced from AKMS's published root paths
  • scripts/sync_akms_claude_assets.py gained hooks / docs section groups — they were absent from SECTION_GROUPS, so such sections would have silently no-op'd rather than failing; covered by a new regression test
  • Consumer-contract pack pin moved to 90ad2801… across all three sites that carry it, with the divergence from AKMS's v1 integration lock documented where the pins live

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

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

Verifying downloads

shasum -a 256 -c SHA256SUMS.txt