chore(history): rehost archived m-tools design docs under .github/docs/history/#17
Merged
Merged
Conversation
…s/history/ The m-tools repo on GitHub is archived. Three design documents in it are still load-bearing — they're the *why* behind the m-dev-tools ecosystem's shape (Go/Rust/Python toolchain analogy that drove m-cli's CLI ergonomics, Tier-1 strategy that scoped the first m-cli release, phased remediation roadmap that produced both m-cli and m-stdlib). Routing agents at a repo we no longer maintain — and one GitHub could prune at any time — is brittle. Resolution per AI-discoverability-plan.md §8 non-goal #4 ("rehost its docs in .github/docs/history/ or drop them from tools.json"): rehost, not drop. Changes: - docs/history/ — verbatim copies of three preserved docs: - gap-analysis-and-remediation-strategy.md - m-tool-gap-analysis.md - m-tooling-tier1.md Plus a README.md documenting the provenance policy and the explicit exclusion of implementation.md + ydb-dev-tools-gap-analysis.md. Each preserved doc carries a single `> Archived snapshot.` banner after the H1 citing upstream commit 16fe3f7 (2026-04-27). - profile/tools.json: dropped the `m-tools` entry (was `status: archived`, no manifest by design); build-catalog's archived-carryover no longer triggers for it since the prior tools.json doesn't list it. - profile/task_index.json: retargeted the three `history` category intents from `tool:m-tools` to typed-ID `doc:m-dev-tools#<filename>` and the new in-org doc URLs. - profile/README.md, docs/AI-discoverability-plan.md, docs/AI-discoverability-guide.md: cross-references retargeted at the in-org paths. Equivalent to the original chore/rehost-archived-m-tools-docs work (PR #14), rebuilt on top of post-P1-A/P1-D state. PR #14 conflicted heavily on profile/tools.json because it was authored against pre-P1-A baseline. Verification: - make check-docs-prose ✓ (docs/history/ holds only .md prose) - make validate-catalog ✓ (tools.json + task_index.json strict-validate) - make catalog ✓ (regen is byte-idempotent; m-tools stays gone) - 26/26 pytest in profile/build/ - make phase0-smoke PASS
rafael5
added a commit
that referenced
this pull request
May 11, 2026
Phase 3 launch state captured. Both upstream blockers from §0 closed: - Phase 1 (org routing layer) CLOSED 2026-05-10 — A/B/C/D all merged (PRs #10/#11/#12/#16); make catalog + make validate-catalog green in CI; make catalog byte-idempotent against origin/main. - Phase 2 (tier-2 + tier-3 manifests) CLOSED 2026-05-10 — all 3 tier-2 + all 3 tier-3 repos onboarded same day; tools.json carries 9 manifest-bearing entries; m-tools archived holdout rehosted under docs/history/ via PR #17. §0 status column refreshed; verification commands inlined so any future session can re-confirm the launch state without spelunking git history. Recipe 7's MCP-server soft-dep noted as Phase-4 follow-up but not gating. Pure documentation change; no plan-structure edits beyond §0. Tracks A → B+C+D → E and stage matrices unchanged.
5 tasks
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
Equivalent to PR #14, rebuilt against post-P1-A/P1-D `main`. PR #14 was authored on the pre-P1-A `tools.json` shape and produced unresolvable conflicts when rebased. Same content; same intent; same files. Closing #14 in favor of this one.
Why
The `m-tools` repo is archived on GitHub. Three design documents in it are load-bearing for AI agents trying to understand the m-dev-tools ecosystem:
Routing agents to a repo we no longer maintain — and one GitHub could prune at any time — is brittle. Per `AI-discoverability-plan.md` §8 non-goal #4 ("rehost its docs in .github/docs/history/ or drop them from tools.json"): rehost, not drop.
Changes
Verification (all green)
Test plan