Releases: MCamner/mq-hal
v2.0.0 — HAL Operator Platform
HAL Operator Platform — the capstone of the v1.3–v1.9 operator build.
Running mq-hal with no arguments opens one operator dashboard that reads the whole MQ stack — stack health, brain/memory, release readiness, local runtime, history, and alerts — without opening a single repo. mq-hal stays read-only: it observes, summarizes, displays, and routes; it never thinks, reviews, or stores.
Shipped in this platform release
- Stack / Brain / Release / Runtime control centers (v1.3–v1.6)
- Unified TUI dashboard with panel navigation (v1.7)
- Timeline & history with alerts (v1.8)
- Operator actions —
next/fix/open(v1.9) - HAL Operator Platform — one dashboard over the whole stack (v2.0)
release-check.sh green; stack contract gate READY at v2.0.0.
v1.2.0 — Vector-store health summary in stack-status
What's new
- Vector-store health summary added to
stack-statusoutput - MQ ecosystem repo registry integrated (
mq register) - Release JSON fields corrected
- ROADMAP updated: v1.1.0 marked Done, v1.2.0 shipped
Upgrade
pip install --upgrade mq-halv1.1.0 — mq-mcp runtime health observability
What's new
mq-mcp runtime health in stack-status
mq-hal stack-status now probes the live mq-mcp HTTP server (localhost:8765) and reports:
http_reachable— whether mq-mcp is runningtool_count— number of registered toolshas_orchestration_contract—validate_orchestration_contractpresenthas_learn_tools— learn layer tools presenthas_review_skills— review tools present
Example output when mq-mcp is running:
mq-mcp runtime
--------------
available=True path=~/mq-mcp
version=1.10.0 runtime=ok vector=ok model=configured
http=reachable tools=66 orchestration_contract=yes learn=no review_skills=yes
If mq-mcp is installed but not reachable, the recommendation suggests mq-agent mcp start.
ROADMAP sync
- Current status updated to v1.0.3
- Release map: v1.0.3 Done, v1.1.0 added
v1.0.3 — ROADMAP cleanup
ROADMAP ticked clean: 9 stale open items resolved, 2 deferred items remain (mq-mcp/vector-store infra). No code changes.
v1.0.2 — Runtime observability: env-status
What's new
mq-hal env-status — HAL environment and tool availability report with degraded-mode recommendations.
$ mq-hal env-status
HAL Environment Status
======================
Environment variables
---------------------
--- OLLAMA_URL http://localhost:11434 (default: ...)
SET EDITOR code
...
Tool availability
-----------------
[ ok ] Python 3
[ ok ] git
[ ok ] Ollama
[MISS] mq-agent
...
Recommendations
---------------
[✓] all: No degraded components detected.
Also available as mq-hal env and mq-hal env-status --json.
Sensitive env var names (containing API_KEY, SECRET, TOKEN, PASSWORD) are always shown as [REDACTED].
ROADMAP cleanup
Current statusupdated to v1.0.2model-statusandstack-statusticked off in observability layer- v1.0.1 and v1.0.2 added to release map
v1.0.1 — HAL Learn Layer
What's new
mq-hal learn — local lesson store for verified learnings from Codex, Claude, or manual work.
mq-hal learn add \
--repo mq-hal \
--source manual \
--task "version sync before release" \
--lesson "Always update README badge, CHANGELOG and docs/index.html together." \
--validation "release-check --dry-run passes"
mq-hal learn list
mq-hal learn show <id>
mq-hal learn search "version sync"
mq-hal learn summarizeStorage: ~/.mq-hal/learn/lessons.jsonl
Secret patterns (api_key:, token:, bearer, ghp_*, sk-*) are redacted to [REDACTED] before write.
Safety
- Local only — no upload, no sync
- No command execution
- No router or allowlist mutation
- No automatic promotion to
AGENTS.mdorCLAUDE.md
Docs
docs/LEARNING.md — format, safety rules, distinction from session memory.
v1.0.0 — Stable local HAL command router
mq-hal v1.0.0
First stable release of mq-hal — a local HAL-style command router for the mq ecosystem.
What's stable
- CLI command surface — 33 named commands, enforced by release-check
- Intent schema —
schemas/intent.schema.jsonv1, validated in CI - Router allowlist —
ALLOWED_INTENTS+ALLOWED_MQLAUNCH, documented inINTENT_CONTRACT.md - Repo config format —
config/repos.jsonschema documented indocs/FORMATS.md - Session memory format —
~/.mq-hal/session.jsonlJSONL schema documented indocs/FORMATS.md - Timeline output format — text and JSON formats documented in
docs/FORMATS.md - mqlaunch + mq-agent integration — boundary documented in
docs/INTEGRATION.md - Model fallback behavior — profiles in
config/models.json, deterministic fallback always available
What's included
docs/FORMATS.md— stable format declarationsdocs/TROUBLESHOOTING.md— common problems and fixes- Full safety audit: no
shell=True, intent output normalized before routing, path escape protection, executor validate_command + critic gate + dry-run default
Release gate
release-check.sh --dry-run passes. CI green. Branch protection active.
Docs
v0.15.2 — Release gate hardening
What changed
release-check.shnow checks GitHub release tag: fails if the current VERSION already has a published release, blocking accidental re-release.release-check.shsmoke tests use|| fail "..."so all failures are collected and reported together with the FAILED banner instead of silentset -eexit.tools/check-command-docs.shdynamically extracts commands frombin/mq-hal's case statement — any command added to the dispatcher without a COMMAND_SURFACE.md entry will now block release automatically.- ROADMAP v0.15.0 release gate v2 items marked complete.
Release gate
release-check.sh --dry-run passes on this commit.