Repository navigation
Knowledge Base v0.1.6
Knowledge Base 0.1.6
The MCP transport accepts bounded JSON extension fields in request _meta, including identifiers emitted by native clients. Optional progressToken values must be strings of at most 128 characters or safe integers. The complete envelope retains its configured byte, depth and node bounds.
The packed protocol proof exercises metadata-bearing calls through all five tools. Regression coverage includes progress-token validation, aggregate envelope limits, authorization and admission across the supported request envelopes.
Current-head CI passed 1,022 application tests and 128 release checks on each Node version, plus the synthetic composition, artifact checks and authenticated protocol proof.
The four synchronized packages are @pegma/knowledge-base-contracts, @pegma/knowledge-base-core, @pegma/knowledge-base-application and @pegma/knowledge-base-mcp, all at 0.1.6. All four packages passed exact registry-byte, native signature, source-provenance and clean-consumer verification. Real-host client acceptance continues after host dependency adoption.
The original preparation archive, manifest and verification receipt are attached. The successful recovery verified four identical existing packages and uploaded zero new versions. Original package writers were attempts 1 through 4.