Updated July 27, 2026
The latest published version of each public ParkviewLab open-source project, where it ships, and a summary of what each current version provides.
| Project | Latest | Released | Published to |
|---|---|---|---|
| conception-space | 0.8.6 | 2026-07-20 | GitHub Releases |
| jonobones | 0.1.5 | 2026-06-25 | npm · GHCR |
| deco-assaying | 0.3.5 | 2026-07-17 | PyPI · GHCR |
| flint-slating | 0.1.6 | 2026-06-25 | PyPI · GHCR |
| smalt-mcp | 1.3.3 | 2026-06-25 | PyPI · GHCR |
| ebony-enriching | 0.1.10 | 2026-06-25 | PyPI · GHCR |
| pensa-grex | 3.3.0 | 2026-07-27 | GitHub Releases |
| cobalt-grinding | 0.1.0 | 2026-07-02 | PyPI |
| cogrind-workshop | 0.1.0 | 2026-07-02 | PyPI |
Build and navigate 3D spaces for thinking. Hand-place and sculpt ideas. See unplanned connections.
This is a maintenance release with no user-visible changes: the workflow and script comments describing macOS signing status and the electron 43 extraction mechanism have been corrected, and an inert yauzl dependency override was removed without affecting lockfile resolution.
The macOS build is signed and notarized; the Windows and Linux builds are unsigned, so those may warn on first launch. See the install notes.
A headless, Joplin-sync-compatible knowledge daemon.
This is a maintenance release with no user-facing code changes: the REST API reference in docs/api.md has been corrected and expanded to cover all nine error codes, success status conventions, pagination flags, relationship-list parameters, the 512 MB resource upload limit, and several endpoint-specific quirks, and a stale hardcoded version in the /health example was removed. The remaining work is internal — REUSE/AGPL formalization, handbook onboarding, changelog automation, and a CI pin bump to Node 24.
npm install -g jonobones
# or
docker pull ghcr.io/parkviewlab/jonobones:latest
MCP server for source-code analysis via tree-sitter (Python/C/C++ initially, broader coverage planned).
This is a maintenance release that bumps the indirect mcp dependency from 1.27.0 to 1.28.1.
uvx deco-assaying
# or
docker pull ghcr.io/parkviewlab/deco-assaying:latest
MCP server that reads PDFs and exposes them as structured Markdown.
This is a maintenance release that bumps lagging GitHub Actions pins to their Node 24 floors, with no user-facing behavior changes.
uvx flint-slating
# or
docker pull ghcr.io/parkviewlab/flint-slating:latest
MCP wrapper around Smalt's storage surface (read / write / link / claim / search).
This is a maintenance release that bumps lagging GitHub Actions pins to their Node 24 floors, with no user-facing behavior changes.
uvx smalt-mcp
# or
docker pull ghcr.io/parkviewlab/smalt-mcp:latest
An MCP lab notebook — proposal / experiment / gap lifecycle.
This release is maintenance-only, bumping GitHub Actions pins to their verified Node 24 floors ahead of GitHub's removal of Node 20 from runners. There are no user-visible behaviour changes.
uvx ebony-enriching
# or
docker pull ghcr.io/parkviewlab/ebony-enriching:latest
Track what you're doing as project plans, drawn as an interactive map. Parallel work branches and rejoins. A local agent can edit the map with you.
This release reworks the MCP tool surface around the model's own vocabulary: reads are now strict about node kind (read_domain, read_project, read_task), writes use one id parameter name (node_id) across a shared id namespace, and several tools are renamed to match what they actually act on (delete_node, move_task, move_project, detach_project, reorder_project, open_branch below a node). The app gains two actions the tools already had, wrapping a run as a sub-project and deleting a note, and the note interface (glyph, menu items, editor, collapse/expand) is now the same on a project's close as on its opening. Two writes that could silently misshape a plan are now refused — moving a close, and splice-deleting a plan's base — and every write reports the title it ended with, so a collision-driven rename is visible to the caller.
The macOS build is signed and notarized; the Windows and Linux builds are unsigned, so those may warn on first launch. See the install notes.