feat(domain): R4.2e OD-3 value cap (400,000), rescue-copy guard, 1 GiB linear ceiling, budget measurements
json_js::MAX_JSON_VALUES from the R4.2e measurements (CAP envelope 39,652 values, 612-leaf export 23,803; ~100 B of tree per value, a 16 MiB dense document 784 MiB with the cap off, 16 MiB with it); draft.restore refuses an over-budget copy as invalid; --max-memory 1 GiB proven to trap on the proofs build; cargo pdf_budget prints the value table, the Node budget suite prints the per-class cost (fresh instance, W4 asserted).
This commit is contained in:
1 parent
f8579bc19a
commit
6ee04c96c5
13 files changed
+599
-14
No files matched your search
+6
-1
@@ -3,7 +3,12 @@
|
||||
[target.wasm32-unknown-unknown]
|
||||
# The shadow stack of the browser module, set explicitly (the toolchain default is also
|
||||
# 1 MiB). packages/core-wasm/tests/panic.test.ts proves that exhausting it traps.
|
||||
rustflags = ["-C", "link-arg=-zstack-size=1048576"]
|
||||
# Linear memory ceiling (R4, OD-3 (a)): a runaway allocation traps at 1 GiB (the instance is
|
||||
# poisoned and re-created by CoreRuntime) instead of growing until the OS kills the tab. Far
|
||||
# above the needs measured in RUST.md §10 (import worst case under the value cap, the export
|
||||
# of a report at the collection caps); packages/core-wasm/tests/pdf-import.budget.test.ts
|
||||
# proves the trap on the proofs build.
|
||||
rustflags = ["-C", "link-arg=-zstack-size=1048576", "-C", "link-arg=--max-memory=1073741824"]
|
||||
|
||||
[env]
|
||||
# ts-rs writes the TypeScript types of the contracts here on `cargo test -p faunosteo-core --features ts`.
|
||||
|
||||
Reference in new issue
Block a user