Skip to content

docs: add index README and YAML frontmatter to every doc#3

Merged
rafael5 merged 3 commits into
mainfrom
docs-discoverability-phase0
May 11, 2026
Merged

docs: add index README and YAML frontmatter to every doc#3
rafael5 merged 3 commits into
mainfrom
docs-discoverability-phase0

Conversation

@rafael5
Copy link
Copy Markdown
Contributor

@rafael5 rafael5 commented May 11, 2026

Summary

  • Adds docs/README.md indexing every document in docs/ with the shared TYPE/CONNECTION vocabulary established across the m-dev-tools org on 2026-05-11.
  • Adds YAML frontmatter (created, last_modified, revisions, doc_type) to every existing doc in docs/. Existing frontmatter is merged, not replaced.
  • Implements Phase 0 of the org-wide docs-discoverability standard. The accepted standard, vocabulary, schema, and 4-phase CI rollout plan live in m-dev-tools/.github at docs/docs-discoverability/README.md (committed via #35).

Test plan

  • Existing make check-docs-prose gate passes (docs/ is still prose-only).
  • docs/README.md lists every doc; labels use the agreed 23-type vocabulary.
  • No existing frontmatter fields lost (verified during the org-wide pass; m-stdlib module docs in particular preserve their module: / synopsis: / errors: / conformance: / etc. fields).

🤖 Generated with Claude Code

rafael5 and others added 3 commits May 11, 2026 10:14
Add docs/README.md indexing every document in docs/ with a shared
TYPE/CONNECTION vocabulary used consistently across all m-dev-tools
repos.

Add YAML frontmatter (created, last_modified, revisions, doc_type)
to every existing doc. Existing frontmatter is merged, not replaced.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Ships the machine-readable m-cli <-> m-test-engine contract decided in
docs/m-engine-implementation-plan.md so m-cli's `m doctor` and the
upcoming `m engine` subcommand family have a single, version-handshaked
surface to read from.

* dist/m-test-engine.json — protocol 1, GHCR image ref,
  bind_mount object (host=/m-work, container=/m-work, mode=rw),
  compose-first + run_args fallback per plan §1.3
* dist/m-test-engine.schema.json — JSON Schema 2020-12, additive-only
* tools/check-manifest.py — extended to validate both manifests:
  schema-shape, compose_file resolves on disk, verified_on within 90d
* dist/repo.meta.json — enrolled engine_contract in exposes;
  bumped verified_on to 2026-05-11
* README.md — new "Machine-readable contract" section pointing
  consumers at the manifest + schema + drift gate
* docs/m-engine-tracker.md — live progress tracker; locks the
  plan doc once stages move off `todo`

Notes / followups recorded in tracker narrative log:
- /m-work declared in manifest is target state; compose.yml and
  Dockerfile still bind /work — runtime cutover deferred to Phase 2
- ghcr.io image not yet published; Phase 3 covers the publish workflow

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Phase 1a's manifest declared the canonical bind mount as /m-work but
left compose.yml + Dockerfile + lifecycle.json pinned to /work. This
commit closes that drift so a `docker compose up -d` produces a
container whose runtime layout matches the published contract.

* docker/compose.yml — bind ${M_TEST_ENGINE_BIND:-/m-work}:/m-work;
  working_dir: /m-work; restart: unless-stopped (matches manifest
  run_args.restart)
* docker/Dockerfile — WORKDIR /m-work; prose updated for the shared-
  mount model
* dist/lifecycle.json — mount_point /m-work, mount_source_default
  /m-work
* dist/repo.meta.json — notes field references the new mount point
* AGENTS.md + README.md — prose reflects the host /m-work shared
  working tree (all m-* repos as siblings under one host directory,
  visible identically inside the container)

This is the runtime half of the bind-mount decision in
docs/m-engine-implementation-plan.md §1.4. The m-cli side
(DockerEngine.bind_root default + stage_routines prefix-mapping) lands
in a coordinated m-cli commit.

`make check-manifest` green; `docker compose config` validates the
compose file shape. Smoke target requires a running container (kicked
off via `m engine start` once the m-cli side lands).

Tracker (docs/m-engine-tracker.md) updated with completed Phase 2
stages 2.0 (this cutover) + 2.1/2.2/2.3/2.5/2.6 on the m-cli side
and three new followups (sudo-in-fix design, capabilities recursion,
m_cli.engine package conversion).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@rafael5 rafael5 merged commit 62d4f88 into main May 11, 2026
1 check passed
@rafael5 rafael5 deleted the docs-discoverability-phase0 branch May 11, 2026 15:57
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