5.0 KiB
EXT-2 STDIO SDK terminal component — accepted, 2026-11-01
Final corrected full component: 4 groups PASS, actual CLI 0; owned HTTP/STDIO cleanup and selected source/runtime hashes unchanged. This is installed-SDK component evidence with an explicitly synthetic remote HTTP server and synthetic in-memory applied/pending receipts. It does not execute the product top-level mcp-stdio.ts, measure the current full authorized catalogue, prove real mutations or activate the candidate in production.
The exact immutable raw acceptance has SHA-256 30df089477373fb491f316d69082b585b3a3a3fc4f9b1c319903407bd3535c2e; executed fixture SHA eec8eda0e66f1cf7f72b983c234645cdb9659602b77305d80b8dc652c706abd7. Scope/assets receipt records all13 selected hashes, independently rechecked while saving these docs. Candidate patch remains staged, SHA d276341b3bf62aca0e0c495b1b73164de8fcf08286d2c91f89f52f71a5d249f5; product/source/package/dist were not changed by this component.
Accepted groups:
- Real installed SDK legacy/modern STDIO discovery over owned JSON/LF streams, local schema rejection, local bridge serverInfo metadata and1,200,000-character ID. Synthetic one-tool ordinary catalogue JSON was416/571 bytes, long-ID JSON1,200,407/1,200,562 bytes; schemas matched. The existing HTTP1MiB ID rule and safe-arithmetic overflow checks remained intact. Legacy output notification passed unchanged.
- Four overlaps (legacy/modern × applied/pending): one held remote synthetic receipt and independent oversized local SDK discovery use the same local ID. The SDK-only discovery is bounded; the original receipt object reaches the wire unchanged with exactly one serialization, one remote synthetic effect and no replay. These are synthetic ledger effects, not real RouterOS/DB mutations.
- Explicitly pin modern before claimless notifications; preserve malformed/batch-line handling and readiness via supported
tools/list. A400,000-byte malformed-UTF8 raw ID decodes to an encoded ID of1,200,002 bytes and remains compatible. A genuine entry-owned oversized unsupported-revision error is bounded before factory/callback invocation. - Lost upstream async context still passes the original synthetic receipt/one serialization. During local cancellation, the actual public callback signal is observed aborted before releasing the remote hold. The synthetic remote effect occurs once, remains pending, and no response for the cancelled request is emitted. Genuine modern
pingreturns -32601; supportedtools/listsucceeds afterwards without another callback or effect. No remote cancellation outcome is invented.
The guard preserves STDIO's existing10MiB raw input buffer. The actual local identity yields122-byte modern stamp and conservative encoded-ID bound31,457,282 bytes. The derived maximum pre-callback terminal JSON/line allowances are32,506,013/32,506,014 bytes; the actual per-message allowance uses that message's encoded ID. This is codec/ID arithmetic, not a global RAM reservation or a changed HTTP/Flow cap. Protected or unknown-correlation messages pass before new shape checks/stringification; notifications and unsupported paths are outside a complete-line bound. Whole stream, global heap, external clients/Inspector and full EXT-2 remain open.
Static evidence: complete backend four-file compiler-host overlay923 roots/2248 source files/0 errors; scoped4-target lint0, syntax0, apply-check0, TMP compile0; four existing meaningful Flow tests passed against the candidate pure codec and actual compiled B1/delivery dependencies. No product build or PG run was performed. The first inert unit import attempt failed before assertions; its fixture import binding was corrected and the refusal retained.
History preserves both actual refused full runs with exact executed hashes, completed groups and successful cleanup. The first lacked a strong abort-observation barrier and failed in the final readiness assertions; no product defect was established. The second proved actual abort/no cancelled reply/no limiter decision, then failed the incorrect assumption that pinned-modern supports ping. The separate group4-only diagnostic confirmed -32601 and supported discovery readiness, CLI0; it explicitly does not claim full-component acceptance. The final full4 run independently covers the corrected modern pin and all strict identity/cancellation checks.
Current full authorized HTTP catalogue → actual top-level STDIO bridge → local schema conversion/metadata and real child-process lifecycle remains a separate activation gate owned by root. No historical363/schema/byte assumption is accepted for that gate. Only these docs were written after the final run; no additional code, processes, tests, clients or runner preparation followed root's preservation-only instruction. Remaining work is7 directions / approximately33 packages, unchanged by this component; no parent package closes here.