GeezerVison

… interfaces for build programs; layer suppliers may not require one another in a circle

…g of the payload's host side reaches a row whose C library a platform describes

…ayload or uses llvm-rc; a quoted toolchain header is the toolchain's

…; the rows' systems are words of the language; a platform-served row names the platform as its remedy

…olds beside its C library; its headers, libraries and std module stand where the payload's would

…repository, so its edges to sibling members hold

…tatic links and checks a static program

A program for another system was handed to the host's ldd (exit 127). Its
closure is now read from the file: a library this build produced travels
beside it, every other name is the target system's. `--mode static` sets
force_static and checks the file, so a dynamic program is never packed under
the `-static` name; a row whose C library a platform describes supports a
full static link.

…; docs/04 states per-target object variants

The words are given to ld.lld only; a platform with driver = "compiler" now
receives a warning that names [platform.build] ldflags. docs/04 states the
per-target object variants and per-program entry objects instead of the
retired compile-once sentence.

…lvm on every host; the unserved-target remedy names a spelling the parser accepts

The mingw-llvm provider names xim:mingw-w64-sysroot (the target side of
llvm-mingw: MinGW-w64 on UCRT, libc++, libunwind, compiler-rt) for
x86_64-windows-gnu and the new aarch64-windows-gnu row, below the gcc payload
where that exists. A base package on a MinGW row is the driver's sysroot with
the run-times its layers state; its compiler runtime is read from the
directory the base names (compiler-runtime-dir), and a static link takes its
archives. A provider's sysroot package is the base statement of last resort.
The unserved-target diagnosis names [toolchain] <host> = { path, prefix }
instead of [target.X] toolchain = "<path>" (mcpp#913).

…ilds that compile it (mcpp#902)

A [scan_overrides] glob whose files exist and take no part in this build -- a
feature that is off, a ! rule of a [target.<selector>.build] -- is no longer
refused; a glob that matches no file of the package still is.

…686-openkal) are registered intent

Planned rows: a request is refused as planned rather than as an unknown
target, and an explicit [target.<row>] toolchain opts in early. No payload of
the index targets them, and openkal's 32-bit class is a design discussion.

…C-013 v1.7, SPEC-014 v2.2, SPEC-016 v1.1; MCPP_KERNEL_ABI_INTERFACES and layer-cycle in docs/30 and docs/50

…1), foreign ELF closure and the static check (docs/10), defined rows, served FreeBSD rows and link.flags (docs/35); en and zh

…he documents that state them; design record 2026-11-10 (cross-platform ecosystem, fourth version)

…ers, [build] states them, the package root is the sysroot; a provider's sysroot is its identity's base

The [base] table (an architecture-keyed roots map, include-dirs, libs by link
form, compiler-runtime-dir) is replaced by the manifest vocabulary every layer
supplier uses: include_dirs, ldflags, std-module*, and one new [build] key,
compiler_runtime_dir (-resource-dir for clang, -B for gcc). One base package is
the sysroot of one identity; a platform's provider takes sysroot as a package
or { path }, ahead of the platform's own. The mingw-llvm provider names
xim:mingw-w64-sysroot@20261104-1.

…t, the rows snapshot; freebsd is a platform name

… limit

…ames no hosts exists where the platform's runner does

CI on #916: a carrier for windows-aarch64 was built now that aarch64-windows-gnu
is a row, over the mingw-llvm base beneath openkal-windows (an x86_64
implementation). The provider's sysroot, an engine default, is no longer a
statement when the graph supplies the system, as the row's toolchain
convention already is not; and a carrier that names no hosts is built only
where the platform's runner exists (runner.hosts), so --systems all leaves the
others out with the reason.

…ase records, metrics and bounds; SPEC-017 (mcpp#917)

The runner's side of the test protocol, for any framework that implements it:
- test-parts: --cases names the parts [test] split runs a program as (parts),
  and each part's record names its program (part_of);
- test-case-stream: the report is read while the program runs (P5.1), and a
  case record states each case's beginning and end before the program's record;
- test-metrics: the cases' kind, tags, metrics and bounds and the program's
  usage reach the records, and the run kept under target/mtest carries them
  with each case's start and its failures' expected and actual values (P6,
  P10.2, P12), so a Bench case's measurements reach mtest analyze trend.
The --list main keeps its meaning. SPEC-017 states the runner, the protocol it
reads, the records and the store, framework-neutral.

…n function

step13_windows_resources stays within the 400-line function limit.

…oot is stated wherever no cfg is trusted

The base statement was memoised when first asked, before the dependency graph
was loaded, so a provider's base did not yield to a graph that supplies the C
library (x86_64-windows-gnu over openkal on hosts the mingw-llvm provider
serves). The compile side stated a paired provider's sysroot only when a cfg
was bypassed; the Windows llvm payload has no cfg, so aarch64-windows-gnu found
no libc++ headers there. The link side already stated it unconditionally.

…ows; e2e 1063 runs in the wine job

…es the MSVC ABI it asks for

A dependency is installed under the home's install turn (registry/.install.lock,
re-entered for the package's own dependencies); a process that waited for the
turn looks for the package again before installing it. A second process was
told the install succeeded while the first was still placing the package, and
stopped with "install path missing after fetch" (two e2e workers fetching one
package into one home).

e2e 182: llvm alone is not a request for the MSVC ABI now that clang pairs with
the MinGW-w64 payload and compiles against it on a host without a cfg; the
project writes x86_64-windows-msvc as its target.

…s; the mingw-llvm provider names mingw-w64-sysroot 20261104-2 (mcpp:c-abi=ucrt)

The c-abi layer of a base package was reported by the package's name
(mingw-w64-sysroot); it is the C library its provides states. Revision 2 of the
MinGW-w64 base states ucrt, the name mcpp's vocabulary gives the Windows C
library and the one the MinGW-w64 payload answers, so that one requirement
(compat.glfw's Win32 backend) is met by either. The design records I1 in that
form, and the defects CI exposed.

…ot dropped

base_statement_text points into the memo; an answer that was not kept left it
pointing at another target's statement or at none. The engine tier's answer is
kept and marked provisional, and asked again once the dependency graph is
loaded.

-stdlib= rode the toolchain words every C and assembly command shares, so a C
unit of a paired target drew clang's unused-argument warning, an error under
-Werror. paired_stdlib_flag() is appended to the C++ flags and to the module
scan; the std module build asks for it as before.

…oked for in

The error "install path missing after fetch" now lists each version directory
the lookup tried, in its order, so that a provider that placed the payload
elsewhere is seen at once. e2e 15 prints the output of a failing mcpp test.

A home whose [xlings] home names an existing registry wrote its own index directory and store into that registry's configuration. The e2e homes under a temporary directory did, and later builds over the shared registry were sent to a store deleted with its home ("install path missing after fetch" on Windows and macOS). Such a home now records no place of its own there; e2e 1067 fails before and passes after.

The test named openkal-linux; on Windows and macOS the pinned os brings the 0.24 family's implementation of that system instead.

…vironments, borrowed registries

…he fast path; state only work done

- The build directory's lock is dropped once the tests are built, and each invocation reports into its own protocol directory, test-protocol/<pid>-<start>/, removed when it ends and swept when its process is gone (#915). e2e 1068 runs a build and a second test beside a running one; it fails before and passes after.
- The programs a test finds as MCPP_BIN_<NAME> are built by try_fast_build when no override applies, which now hands back the recorded programs.
- The packages are no longer announced before the build; Phase A's report names a package when one of its steps runs, and a test's Compiling line is written when the bulk pass ran a step of its own.
- The test graph is written to test.ninja (set on the three test plans).

…one command

BuildPlan::graphFile names the file the backend writes and drives (-f). test.ninja shares the directory's objects, .ninja_log and .ninja_deps with build.ninja, so an output both graphs name with different commands is rebuilt rather than reused. The dyndep rule's text no longer depends on the plan: $module_map carries its own leading separator, and obj/main.cpp.ddi.dd was rescanned on every switch between mcpp build and mcpp test because its command differed by a space. The e2e that read the test graph from build.ninja read test.ninja.

…form 0.25.0

openkal-platform 0.25.0 (mcpp-index#751) groups openkal 0.25.0, openkal-image 0.5.5, openkal-musl 0.29.0 and the implementations of the 0.25 family; its mcpp floor is 2026.11.9.1.

…released build directory, platform 0.25.0

A full mcpp test writes test-plan.json beside test.ninja (every test of the package: its program, its own sources, its protocol or the objects that state it, its guide; the runtime directories and the tool directory; [test] split and store) and a build-cache entry for the test graph (selection @test). The next mcpp test admits that entry through admit_recorded_build, which now takes the graph it replays, asks that the discovered tests are the recorded ones, that nothing under tests/ is newer than the graph and that ninja has nothing to do for the selected tests, and runs them from the record; the environment, the arguments after -- and the programs' places are joined at run time. A workspace's root package matches its own record (selection and group '.') on both fast paths. e2e 1069 fails before and passes after; on a workspace of 1,500 sources one program's unchanged tests went from 5.8 s to 0.13 s.

…915)

The issue's shape: the test runs mcpp build in its project with the test's environment. Measured for T9 on 2026.11.9.1 and 2026.11.10.1, with gcc and with an llvm workspace: the test's environment (the subos's bin first on PATH, its library variables, MTEST_*) leaves the configuration's fingerprint as it is; the rebuilds the issue saw were the test graph written over build.ninja and the lock held through the run.

…sessions, check details, a case's output

docs/specs/test.md is the mcpp test spec: SPEC-017 v1, the mtest protocol's normative text (P1-P12 kept) and the [test] keys, as base capabilities B1-B6 and optional ones O1-O9; test-runner.md is folded into it. B5: --no-run records carry each program's launch. B6: an entry target's test-capabilities and test-session, reported by --guide. O3: failure source and fatal, case checks, in records and the store. O8: a case's output from the program's output events, or from a program that ran that case alone; the output of several cases is not divided by arrival, which a buffered stream does not allow (measured). Features test-launch-records, test-frameworks, test-checks, test-output. e2e 1070 fails before and passes after.

…nd 1069 on every host

The Windows launcher and the single-file launcher pinned mcpplibs.os 0.4.1, of the openkal 0.24 family, which the built-in platform 0.25.0 refuses (cross/mingw-cross, e2e 988); 0.4.4 ranges over the 0.24 and 0.25 families. e2e 1068 bounds its commands without timeout(1), which macOS lacks; e2e 1069 asserts that no dev-dependency is resolved, since the programs' build plans on hosts where mcpp build plans each time (macOS).

override = true on a root's dependency or in [workspace.dependencies] answers every request for the package in the graph its table governs ([dependencies]: build and tests; [dev-dependencies]: tests; [build-dependencies]: build programs). A replaced request that does not already admit the override is named once (Overrode); mcpp.lock marks the package and --locked reads the marker; an override of a platform version group's member is taken with a warning; a library's override is ignored and said to be. A refusal of two irreconcilable versions names the overriding line; a library's exact pin of a package every consumer shares (a target-side layer, a kernel ABI) is noted to its users and refused by mcpp publish. src/build/prepare/overrides.cpp holds the steps. e2e 1071 fails before and passes after.

An entry target that states them is not warned of an unsupported key.

…inked

flags.cppm reads the triple of the directory the payload's libc++.a was found in; another architecture or system marks MechanismInput::foreignCxxArchives, and resolve() links no C++ runtime there and states that the row's is a package's (mcpp:c++-abi). Measured on aarch64-freebsd-musl from a Linux host: ld.lld: libc++.a(algorithm.cpp.o) is incompatible. The OpenKal conformance suite now takes openkal-llvm-runtime there (openkal-freebsd).

…ild, why flags, one interface edit)

bench/tests/engine.cpp times the mcpp under test (MCPP) on a small module
fixture; each cost enters the mtest store as a metric with its samples. The
engine comparisons remain the standard set run by hand.

.github/versions.env pins mtest (MTEST_VERSION, MTEST_SHA256); the composite
action mtest installs it and exports MTEST, and e2e-mtest takes it from there.
test-report merges the stores mcpp test kept in a job, writes the job's
Markdown report into its summary and uploads the store; the unit jobs of the
three hosts and the Linux bench run use it. Each e2e shard writes its report,
run_all.sh groups the shards by the workflow run, and ci.yml's test-report job
renders one report over every job (mtest ci report).

…pplement

…utside the repository

…ude nothing provides is the script's own

- system_include_dirs reads a cross gcc's own <root>/<triple>-w64-mingw32/include when no payload is paired: under the mingw provider, a script's "winres.h" was taken for a file of the project that no action produces, and the build failed in ninja (e2e 1058, the cross gcc case).
- A quoted include found in no directory is an input only when a build action writes it; otherwise the script's preprocessing decides (#if __has_include) and the resource compiler names a missing one with the script and line (e2e 1072).
- docs/04 (en, zh) and CHANGELOG.

…tation record