Initialize CMP as a C++23 module project

[helantianshen]

Summary

This PR turns the generic mcpplibs module scaffold into the initial CMP (Coroutine Machine Process) project.

• replace the inherited mcpplibs.mylib identity with package mcpplibs/cmp and module mcpplibs.cmp
• establish C++23 as the project and standalone-example baseline
• keep the root module import-only until the runtime API is designed
• update tests, examples, documentation, CI configuration, repository guidance, and .gitignore
• remove generic publishing templates and their template-only smoke checks

This PR establishes the repository identity and development baseline. It does not implement coroutine runtime functionality.

Package identity

• project: CMP — Coroutine Machine Process
• package: mcpplibs/cmp
• version: 0.1.0
• standard: C++23
• root module: mcpplibs.cmp
• future namespace: mcpplibs::cmp
• license: Apache-2.0

The C in CMP echoes the naming role of the G in the Go runtime. This is naming motivation only, not a claim of equivalent runtime behavior.

The root module currently contains only:

export module mcpplibs.cmp;

Template cleanup

templates/basic and templates/lib were generic mcpp new publishing assets inherited from the scaffold. They did not describe a CMP-specific API.

tools/template_smoke.sh rendered each publishing template, replaced scaffold placeholders, redirected the generated dependency to the current checkout, and then built and ran the generated project. Once the inherited templates were removed, the script no longer had a test subject.

examples/basic remains as an independent path-dependency consumer of mcpplibs.cmp.

Convention check

The repository layout was checked against:

• mcpplibs/template
• mcpplibs/cmdline
• mcpplibs/llmapi
• mcpplibs/imgui-m
• mcpp manifest documentation

The comparison confirmed that package naming, src/cmp.cppm, and module mcpplibs.cmp follow current mcpplibs conventions. Publishing templates, template-smoke scripts, CI layout, and lock-file policy are package-specific rather than organization-wide requirements.

mcpp search cmp returned no existing package match on 2026-08-02.

Validation

• mcpp build --cache=off
• mcpp test --cache=off — 1/1 passed
• examples/basic: mcpp run --cache=off — exit code 0
• git diff --check

CI retains separate Linux, macOS, and Windows build, test, and example-consumer workflows.

Non-goals

• task or promise types
• schedulers, timers, cancellation, async I/O, work stealing, or blocking pools
• publishing CMP to mcpp-index
• replacement mcpp new templates before a stable public API exists