2026.10.16.1: the provider port, indices in mcpp's home, upstreams, the system home, filesystems and long paths by Sunrisepeak · Pull Request #811 · mcpp-community/mcpp

platform: filesystem capabilities, measured; scaffold publication by them (#809)

Sunrisepeak

and

speak-agent

committed

f6153b0

provider: the port (mcpp.provider), the xlings adapter under src/provider/xlings, callers through mcpp.provider.select; payloads written by no one but their provider

Sunrisepeak

and

speak-agent

committed

3019e2b

provider: every path through the port; the boundary lint

Sunrisepeak

and

speak-agent

committed

c4fac21

provider: indices mcpp owns live in its home, refreshed staged; upstreams with a trust boundary; --system; windows_long_paths; the handshake

Sunrisepeak

and

speak-agent

committed

4c98ce9

provider: an owned index is read only where its owner keeps it; doctor shows the home, its upstreams, its filesystem and Windows long paths; the Windows path budget

Sunrisepeak

and

speak-agent

committed

f18b6ad

2026.10.16.1; docs: 25 the home, its indices and its store; payloads are never written (91, SPEC-006 v0.8, SPEC-001 1.6); windows_long_paths; tools follow the adapter's path

Sunrisepeak

and

speak-agent

committed

b3535d8

config: the system configuration's default target; a source scan's false positive avoided

Sunrisepeak

and

speak-agent

committed

23c0f3a

pm: a payload the provider cannot describe, or has nowhere in the index's store, is looked for in the home (legacy store); e2e: the owned index's place, stub xlings answer the handshake and stage a…

Sunrisepeak

and

speak-agent

committed

5164d16

e2e: an upstream home is linked and never written (914); the system home is maintained with --system and read by users (915); a home from before keeps working (916); a fresh home adopts its owned i…

Sunrisepeak

and

speak-agent

committed

5ed53a0

CI: a home and a project on NFSv3 (toolchain install, mcpp new, build, run, doctor); e2e: a long home on Windows (917); the isolated homes inherit the store of mcpp's indices

Sunrisepeak

and

speak-agent

committed

afb0377

config: [xlings] home refuses a home mcpp did not make, naming upstream; design record of what was implemented

Sunrisepeak

and

speak-agent

committed

5cdd8e0

xlings 2026.10.16.1 bundled and pinned everywhere (openxlings/xlings#676)

Sunrisepeak

and

speak-agent

committed

c46b82e

config: whether a home is mcpp's is asked of the provider port (indices_of); a home an earlier mcpp made (its index named mcpp-index) stays usable as [xlings] home

Sunrisepeak

and

speak-agent

committed

630aea9

pm: an installed package of mcpp's indices is looked for in every store of the home (its index's, then the provider home's)

Sunrisepeak

and

speak-agent

committed

d26c235

platform: fs_caps' alias of std::filesystem is not named fs (mcpp::platform::fs is a namespace; GCC 16 crashed reading both); e2e 32, 33 link the mcpplibs index where mcpp keeps it

Sunrisepeak

and

speak-agent

committed

2d3ebcf

toolchain: a toolchain whose C runtime cannot be installed is refused there, naming xim:glibc@<v> (no fixup remains to report it later)

Sunrisepeak

and

speak-agent

committed

4d0cdfb

toolchain: the runtime is pinned once its payload is installed, and the provider's links to it are made again then (a toolchain's loader is <registry>/abi; installing glibc alone does not make it)

Sunrisepeak

and

speak-agent

committed

478c50a

Navigation Menu

Repository navigation

2026.10.16.1: the provider port, indices in mcpp's home, upstreams, the system home, filesystems and long paths - #811

2026.10.16.1: the provider port, indices in mcpp's home, upstreams, the system home, filesystems and long paths#811
Sunrisepeak merged 17 commits into
mainfrom
release/2026.10.16.1

Commits on Oct 16, 2026

platform: filesystem capabilities, measured; scaffold publication by them (#809)

provider: the port (mcpp.provider), the xlings adapter under src/provider/xlings, callers through mcpp.provider.select; payloads written by no one but their provider

provider: every path through the port; the boundary lint

provider: indices mcpp owns live in its home, refreshed staged; upstreams with a trust boundary; --system; windows_long_paths; the handshake

provider: an owned index is read only where its owner keeps it; doctor shows the home, its upstreams, its filesystem and Windows long paths; the Windows path budget

2026.10.16.1; docs: 25 the home, its indices and its store; payloads are never written (91, SPEC-006 v0.8, SPEC-001 1.6); windows_long_paths; tools follow the adapter's path

config: the system configuration's default target; a source scan's false positive avoided

pm: a payload the provider cannot describe, or has nowhere in the index's store, is looked for in the home (legacy store); e2e: the owned index's place, stub xlings answer the handshake and stage a…

e2e: an upstream home is linked and never written (914); the system home is maintained with --system and read by users (915); a home from before keeps working (916); a fresh home adopts its owned i…

CI: a home and a project on NFSv3 (toolchain install, mcpp new, build, run, doctor); e2e: a long home on Windows (917); the isolated homes inherit the store of mcpp's indices

config: [xlings] home refuses a home mcpp did not make, naming upstream; design record of what was implemented

xlings 2026.10.16.1 bundled and pinned everywhere (openxlings/xlings#676)

config: whether a home is mcpp's is asked of the provider port (indices_of); a home an earlier mcpp made (its index named mcpp-index) stays usable as [xlings] home

pm: an installed package of mcpp's indices is looked for in every store of the home (its index's, then the provider home's)

platform: fs_caps' alias of std::filesystem is not named fs (mcpp::platform::fs is a namespace; GCC 16 crashed reading both); e2e 32, 33 link the mcpplibs index where mcpp keeps it

toolchain: a toolchain whose C runtime cannot be installed is refused there, naming xim:glibc@<v> (no fixup remains to report it later)

toolchain: the runtime is pinned once its payload is installed, and the provider's links to it are made again then (a toolchain's loader is <registry>/abi; installing glibc alone does not make it)