Skip to content

Commit 8074791

Browse files
committed
docs(design): what the sandbox measured for the #630 batch
1 parent 238a738 commit 8074791

1 file changed

Lines changed: 31 additions & 0 deletions

File tree

.agents/docs/2026-09-13-630-what-a-framework-still-hits-in-the-engine.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -880,3 +880,34 @@ The design's two refusals were withdrawn on review before landing: a graph
880880
that imports `std` on an Apple cross target without a package builds as it
881881
did yesterday and is reported once (§5.3), and a payload without a builtins
882882
archive is reported once rather than refused (§5.3, item 7).
883+
884+
## 14. What the sandbox measured
885+
886+
Run on 2026-09-14 in `xlings subos use v630 --sandbox`, with both tools set to
887+
the CN mirror, against mcpp 2026.9.13.2 installed from the published index
888+
(`xlings install mcpp@2026.9.13.2`, six minutes after the bump merged) and
889+
the packages resolved from the index by version:
890+
891+
| section | claim | reading |
892+
|---|---|---|
893+
| 1 | `llvm.libcxx = "22.1.8.1"` on Linux over glibc: the report names the C++ layer as the graph's, `ldd` lists no libc++, the program prints `1-2-3` | ok, ok, ok |
894+
| 2 | `min_api_level` under `--strict` on a non-Android row prints no `unsupported key` | ok |
895+
| 3 | one identity, two git revisions: the override is reported, both revisions are named, the library is compiled against the root's revision | ok, ok, ok |
896+
| 4 | a path host tool: first build 41; an edit without a version bump reaches the consumer (42); the reversal reaches it (41) | ok, ok, ok |
897+
| 5 | `mcpp emit xpkg` with `cfg(linux)`: the linux block names the tool, the other two do not, no warning | ok, ok, ok |
898+
899+
14 claims, 14 ok, 0 skipped. The first run reported two failures that were
900+
the script's own: it read the override warning by its diagnostic domain,
901+
which a warning does not render, and its section 4 wrote the tool's source
902+
to a relative path after changing directory, so the edit never happened. Both
903+
are the same shape as the CI assertions corrected in §13, and the record
904+
keeps them because a verification that fails for its own reasons reads
905+
exactly like one that found a defect.
906+
907+
The release: mcpp-community/mcpp v2026.9.13.2 (release run 34764806249,
908+
four platforms, `publish-ecosystem` green after the macOS archive was mirrored
909+
by `gtc` locally and the eight GitCode assets compared byte for byte),
910+
openxlings/xim-pkgindex#836, mcpplibs/mcpp-index #408, #409, #410, #411,
911+
mcpp-community/mcpp-plugins#22 (0.9.2; its macOS CI launched the bundle with
912+
the resource under `Contents/Resources/` and ran the iOS simulator row over
913+
the two packages). The workspace bootstrap pin moved to 2026.9.13.2.

0 commit comments

Comments
 (0)