docs: refresh landing page — add m-test-engine + m-cli-extras + Track C install flow#1
Open
rafael5 wants to merge 1 commit into
Open
docs: refresh landing page — add m-test-engine + m-cli-extras + Track C install flow#1rafael5 wants to merge 1 commit into
rafael5 wants to merge 1 commit into
Conversation
The org grew from 7 to 9 repos during the 2026-05-09 self-containment
sprint (m-test-engine added in Track A2, m-cli-extras in Track D 6b);
the landing page table didn't yet reflect either.
- New "Test engine" section describing m-test-engine (the
minimal-YDB Docker container that backs `m test` / `m coverage`).
- m-cli-extras added under "Toolchain" with its plugin model
described.
- m-cli row updated to mention `m plugins` and the entry-points
plugin system.
- m-stdlib-vscode row updated to mention the bundled manifest
snapshot landed in Tier 4.
- "Getting started" rewritten — the old flow ("clone tree-sitter-m
before m-cli; order matters") was the pre-Track-C2 path-dep
workflow. Now `uv sync --frozen` pulls the URL-pinned
tree-sitter-m wheel from the v0.1.1 GitHub Release, and
`make -C m-test-engine up` is the engine flow.
- m-cli-extras install hint added.
- Licensing summary updated for 9 repos (was 7).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
rafael5
added a commit
that referenced
this pull request
May 11, 2026
Supplements AI-discoverability-plan.md §3.4. §3.4 was authored when no repo shipped the Phase-0 contract; with tier-1 + tier-2 onboarded (6 of 9 repos as of 2026-05-10), that table is stale as a priority guide. This doc reframes priority around the actual remaining work and ranks it by *downstream dependents* — not by ease of shipping. Structure: - §2 Current-state inventory (per-repo Phase-0 contract status) - §3 Outstanding work catalogued from parent plan §7 + phase1-plan.md - §4 Dependency graph (ASCII; shows what blocks what) - §5 Priority ranking by downstream-leverage (P1-A ranks #1 with 6 downstream items; tier-3 onboarding ranks #4 despite being "easy" because it doesn't unblock anything) - §6 Recommended execution order — single-threaded sequence + which items to parallelize when bandwidth allows - §6.4 explicit "easy first" trap: ships three quick PRs, leaves nothing unblocked - §7 Concrete recommended next move: ship P1-A as a single coherent PR (cuts the longest dependency chain in front of the entire Phase 1 + 3 + 4 stack) - §8 How to keep the doc in sync (read-then-act discipline) Source files referenced (all on main): - AI-discoverability-plan.md §3.4 — original tier-based framing - phase0-plan.md — completed - phase1-plan.md — to-do, Track A-D layout matches §3-5 here Prose-only gate (make check-docs-prose) green: doc is .md under docs/.
3 tasks
rafael5
added a commit
that referenced
this pull request
May 11, 2026
Captures Phase 4 exit per phase4-plan.md §6 + §11. Mirrors phase3-evidence.md shape: one section per gate, "What this proves" roll-up, then each §11 done-criterion cited green. Verified locally (gate outputs in the evidence doc): * pytest profile/build/ — 51/51 green * make catalog — byte-idempotent regen * make validate-catalog — schema-strict OK * make handshake — 8/8 steps * make recipes-check — 4/4 clean * uvx --from git+...@v0.1.0 m-dev-tools-mcp --tool route_intent --query "parse JSON in M" → ["module:m-stdlib#STDJSON"] (the parent-plan exit criterion, end-to-end from a fresh clone) All nine §11 done-criteria cited green: 1. m-dev-tools-mcp repo public AGPL-3.0 + full Phase-0 contract (PR #1) 2. server.py exposes 3 TDD-covered tools (PR #2 — 30 dedicated cases) 3. v0.1.0 GitHub Release with 23-KB pure-Python wheel attached (Track D2) 4. tools.json carries the entry with repo_meta_url + mcp_tools_url + release_wheel_url (.github PR #27) 5. task_index.json has infra.agent_integration → tool:m-dev-tools-mcp (.github PR #27) 6. examples/claude-code/ has .mcp.json + README + smoke.sh + session.md template (PR #3) 7. This evidence file (PR — current) 8. uvx canonical round-trip green (run captured above) 9. CI green on every Phase 4 PR Phase 5 (continuous enforcement) unblocked. PyPI publishing remains deliberately deferred. Two out-of-scope follow-ups noted in the evidence doc: * validate-repo-meta.py UTF-8-decode bug on binary release-wheel exposes URLs (use --no-resolve until fixed) * 3 Phase-3-era orphan schema fixtures gitignored but still on disk; auto-classifier blocks rm
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The org grew from 7 to 9 repos during the 2026-05-09 self-containment sprint (m-test-engine added in Track A2, m-cli-extras in Track D 6b); the landing page table didn't yet reflect either, and the "Getting started" install flow still described the pre-Track-C2 sibling-checkout workflow.
Test plan
🤖 Generated with Claude Code