Skip to content

fix: standard MPL-2.0 LICENSE + root Dockerfile for Glama#2

Merged
hyperpolymath merged 1 commit into
mainfrom
fix/license-and-dockerfile
Mar 11, 2026
Merged

fix: standard MPL-2.0 LICENSE + root Dockerfile for Glama#2
hyperpolymath merged 1 commit into
mainfrom
fix/license-and-dockerfile

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Summary

  • Replaces custom PMPL license text with standard MPL-2.0 (auto-detectable)
  • Preserves PMPL-1.0-or-later as LICENSE-PMPL-1.0.txt
  • Adds root Dockerfile (copy of container/Containerfile) for Glama/Docker Hub compatibility

Why

GitHub shows "Other" for the license, and Glama fails license detection.
This blocks the awesome-mcp-servers PR (#2999 on punkpeye/awesome-mcp-servers).

🤖 Generated with Claude Code

- LICENSE now contains the standard MPL-2.0 text that GitHub, Glama, and
  other tools can auto-detect
- PMPL-1.0-or-later full text preserved in LICENSE-PMPL-1.0.txt
- Added root Dockerfile (copy of container/Containerfile) for tools
  that require Dockerfile at repo root

Previously, the custom PMPL license text caused GitHub to show "Other"
and Glama to fail license detection.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@hyperpolymath hyperpolymath merged commit 9242668 into main Mar 11, 2026
6 checks passed
@hyperpolymath hyperpolymath deleted the fix/license-and-dockerfile branch March 11, 2026 08:04
hyperpolymath added a commit that referenced this pull request Apr 19, 2026
…e/status

The Zig adapter only dispatched coord_register and coord_claim_task; the other
four tools were placeholders or unhandled. They worked via MCP tool-listing but
returned fake data. This wires them end-to-end to the existing FFI.

Changes:
- ffi: add coord_find_peer_by_suffix (resolve peer_id string -> index),
  coord_read_peer_kind, coord_read_peer_status (for list_peers enrichment).
- adapter: dispatch coord_list_peers (binary FFI output -> JSON array with
  kind/state/status), coord_send (peer_id -> index resolution, broadcast via
  target '*'), coord_receive, coord_status.
- adapter/build.zig: wire cartridge_shim module — FFI re-exports it via
  ADR-0006 boj_cartridge_invoke, so the adapter build needs it transitively.
  This was a pre-existing build break exposed by adding new FFI exports.
- mod.js: unify to /tools/<tool> — was posting to /api/v1/* which no adapter
  handled. The canonical path is /tools/<tool> per main.js:dispatchLocalCoord
  and every other cartridge adapter.

Remaining local-coord work: boj_cartridge_invoke still returns stubs (task #2),
message envelope / risk tiers / supervision layer / VeriSimDB durability pending.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
hyperpolymath added a commit that referenced this pull request Apr 27, 2026
…eriSimDB seam

Task #2: Replace Grade-D stub boj_cartridge_invoke with real FFI dispatch.
All 20 cartridge tools now parse JSON args (page_allocator) and call the
appropriate coord_* functions directly. Output matches local_coord_adapter.zig
exactly. 60/60 tests pass; two stub tests updated for real arg validation.

Task #7b: Wire VeriSimDB supplementary durability backend in coord_durability.zig.
BOJ_VERISIMDB_ENDPOINT env var arms the backend; vdb_append_event() / vdb_replay_events()
establish the seam. Real API calls stubbed pending verisimdb-mcp FFI exposing a
streaming append-log endpoint beyond the current octad-level interface.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant