feat(rfc-cm): baseline P0-P3 compute machine, stdlib and resource slices

Implements the first vertical slices of RFC-CM-0001/0002 on top of a113d89:

- P1: opaque Memory regions (64 KiB pages, budgets, grow-only), byte
  read/write, Memory-index place assignment, wire/host-boundary rejection.
- CM-A04/A05: value-semantics List/Map/Text/Table primitives and the
  recoverable Result map convention.
- CM-A06: opaque Resource handles, resource.open/read/write/close, stdout
  write, granted project-file read and buffered write, strict fail-closed.
- CM-A07 Compat-A: explicit .mq.md format/utf8/io chain matching builtin
  print for the covered value types; builtin remains default.
- P2 fixtures: allocators, list/tree/graph/hash, integer codecs, UTF-8
  encode/decode, CSV/JSON subsets, table filter/sort/join, bytecode VM.
- ADRs 0022-0027, spec updates, evidence reports and 68 semantic goldens.

Gate: cargo fmt --check, clippy -D warnings, 407 tests passed.
This commit is contained in:
cflmy committed 2026-11-20 21:16:54 +08:00
1 parent a113d89496
commit 92bfbf2568
127 files changed
+11351 -141

No files matched your search

+15 -3
View File
@@ -1,7 +1,9 @@
# Marqdo Value Wire Format v1
Status: **frozen for M0.5**. Changes require an ADR, a `wire_version` bump and
cross-ABI compatibility tests.
Status: **frozen for M0.5; extended by ADR-0022 (non-transferable `Memory`)**.
Changes require an ADR, a `wire_version` bump and cross-ABI compatibility
tests. Adding a rejected tag is not a version bump; accepting a new value shape
is.
Canonical implementation: `crates/marqdo-value/src/wire.rs`
(`to_wire`, `from_wire`, `from_wire_with_limits`, `WireLimits`, `WireError`).
@@ -14,12 +16,20 @@ documented in [`foreign.md`](foreign.md) and implemented in
## 1. Why a typed wire format
JSON has one numeric type. Marqdo has arbitrary-precision `Int`, IEEE-754
`Float` (including `NaN` and both infinities) and 13 distinct runtime value
`Float` (including `NaN` and both infinities) and 15 distinct runtime value
types (`crates/marqdo-value/src/value.rs`). Encoding an `Int` as a JSON number
would silently lose digits above 2^53 and would make `Int(1)` and
`Float(1.0)` indistinguishable after a round trip. The wire format is
therefore **fully type-tagged** and is not plain JSON.
Addressable `Memory` and host `Resource` handles are deliberately **not
transferable**. `to_wire` emits
`{"type":"memory"}` only so that an accidental transfer is visible; decoding
that tag is always `WireError::Invalid`, and the host boundary rejects any
argument containing a live handle before an ABI call. Copying bytes requires an
explicit standard-library snapshot to a managed value, not serializing a
handle (ADR-0022).
The rules that follow from this:
1. Every value is a JSON **object** with a mandatory `"type"` string.
@@ -81,6 +91,8 @@ The table is normative and mirrors `encode`/`decode` in
| `Code` | `{"type":"code","language":"python","source":"...","content_hash":"<sha256 hex>"}` plus optional `"unit"` and `"span"` | `language` and `content_hash` default to `""` on decode when absent; `source` is required. |
| `FunctionRef` | `{"type":"function_ref","module":"index.mq.md","name":"main"}` | Both fields required strings. |
| `PluginHandle` | `{"type":"plugin_handle","plugin":"demo.solver","export":"solver.add","id":1}` | `id` must be a non-negative JSON integer (`as_u64`). |
| `Memory` | `{"type":"memory"}` | **Never decodable.** No handle, address or bytes are encoded; a round trip is intentionally impossible (`wire::tests::memory_handles_are_not_transferable`). |
| `Resource` | `{"type":"resource"}` | **Never decodable.** Host-private stream handle; `from_wire` rejects the tag (`resource_handles_are_not_transferable`, ADR-0025). |
Optional fields (`unit`, `span`, `display`, `language`, `content_hash`) are
emitted only when present on the value. Encoders always emit `display` for