[P1] Canonical ~value bypasses the removal of direct-output APIs #11

Reproduced during the 2026-09-04 language review at a20753c6cff96ee86758744e227a04460234a832. Priority: P1.

~"private input sample"

This passes canonical preflight and writes a Makepad JSON log record containing the string directly to stdout. The same behavior occurs in an optimized runtime with an empty host and in the standalone CLI. The source value is also returned normally.

The grammar permits ~, and operator_to_unary maps it to Opcode::LOG. The opcode reaches handle_log, bypassing the masked std.log, print, and println members. Its formatter also uses an ordinary growing String; see the logging implementation.

Consequently, removing module members is not a complete audit of source-reachable effects. Script-visible input can enter process logs outside capability audits or a host's chosen output policy. Where stdout carries another protocol, these records can also interfere with framing. This is a logging/output boundary breach; no arbitrary filesystem, network, or secret-store access was demonstrated.

Remove ~ from the canonical workflow grammar or replace its opcode behavior with an explicitly configured, bounded host sink. Audit all admitted opcodes for direct I/O and allocation outside the VM budget. Test stdout and stderr capture as part of the no-ambient-output contract, using both direct and computed values.

Acceptance: implement the described correction, publish the resulting language contract, and add focused regression coverage including applicable capability, streaming-parser, and resource-limit cases.

Fix and executable regressions: PR #19. Workspace tests, explicit vendor suites, formatting, strict Clippy, and the Linux ARM64/RISC-V and Windows GNU compile checks pass locally. All GitHub Actions checks pass on f1e775f, including Linux tests, fuzzing, AddressSanitizer, and Miri. This issue remains open until the fix is merged.