Repository navigation
Releases
Knowledge Base v0.1.8
Adds optional observations for exact test-report review and bounded staff-authorized published-article comparisons used by support learning. Existing five MCP operations and their three scopes are unchanged.
All four 0.1.8 packages passed exact registry-byte, signature, signed-source provenance and clean public-consumer verification. Upgrade contracts, core, application and MCP together.
The original prepared archive, manifest and registry-verification receipt are retained below. Publication attempts 1 through 4 each stopped at bounded registry visibility. Attempt 5 uploaded zero packages, verified four identical versions and passed the separate registry-consumer job. The original source, signed tag and prepared artifact stayed unchanged throughout recovery.
Background comparison uses existing authoring authority, actual publication approval checks and bounded repeated cursor cycles. It returns current approved article content for private and bot-only audiences without granting an ambient customer permission. Comparisons are point-in-time bounded observations, not atomic global snapshots. Optional structural observation ports preserve legacy integrations.
Host adoption, native-client acceptance and customer rollout continue separately.
Knowledge Base v0.1.7
Adds canonical receipts to staff-authorized test-report views for linking confirmed KB test reports with support workflows.
All four 0.1.7 packages passed exact registry-byte, signature, signed-source provenance and clean public-consumer verification. Upgrade contracts, core, application and MCP together.
The original prepared archive, manifest and registry-verification receipt are retained below. Publication attempts 1 through 4 each stopped at bounded registry visibility. Attempt 5 uploaded zero packages, verified four identical versions and passed the separate registry-consumer job. The original source, signed tag and prepared artifact stayed unchanged throughout recovery.
Staff/status/query reads close their ledger observations after awaited report and authority checks. Existing owner-bound verifier behavior and the five MCP authoring operations retain their three scopes.
Host adoption, native-client acceptance and customer rollout continue separately.
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.
Knowledge Base 0.1.5
Knowledge Base 0.1.5
All four synchronized Knowledge Base packages are published and verified at 0.1.5.
This patch groups independent answering reads while retaining current authority, publication and approved-evidence checks. Posting reads retain configured work limits, including early refusal under a lowered entry budget. It establishes no universal backend query or CPU guarantee.
Signed tag v0.1.5 binds source 6dae20df. Both Node 22/24 release lanes passed 991 runtime tests and 128 release regressions, with zero skips. Publication run 42821672972 finished with all six jobs successful. Recovery retained original source, manifest and tarballs; all four failed publisher attempts remain recorded, and the final publisher skipped four already-identical packages.
Strict workflow verification and an independent retained check passed: exact original registry and installed bytes/dependencies, genuine npm 11.18 signatures/Sigstore verification, certificate/source/workflow/tag/original-writer bindings and clean public imports plus factory/MCP metadata checks. These checks do not admit actual host reports or certify a real client.
Permanent evidence: original Actions ZIP, original manifest, verification receipt. Verify ZIP SHA-256 b87b16c0b6badb38dface2eb7e2c60a84eca6c0c0c70f83fb4b9432ee9546e41 before extraction, then manifest SHA-256 61739de9c3f1d65a481ec96a297cab63f6576787fdd4e01fbd4cea627b12d22d.
Host dependency adoption, existing-login/Admin consent, actual Codex/Claude Code/hosted Grok Bot/T3 Code flows, provider/privacy controls, full workflows and supervised pilots remain separate acceptance gates.
Knowledge Base v0.1.4
Add governed operation-local authoring observations, body-free evidence-report queries, prepared read waves and bounded resumable repair. Final disclosure rechecks the current report/ledger state and original restricted principal.
All four 0.1.4 packages are qualified against the exact signed-source preparation. Node 22 and 24 each passed 935 runtime tests and 128 release tests with zero skips, plus all required format, type, composition, artifact and authenticated-agent protocol checks. The full PR review, code/security review and CodeQL gates passed before merge.
Release run 42576167664 finished successfully on attempt 5. The four package writes originated in attempts 1–4; their original provenance invocations were cryptographically authenticated. Final recovery verified zero new publications and four identical existing packages. Original validation and preparation executions were retained across retries.
Independent retained verification confirmed the original archives, genuine npm 11.18.0 signature/Sigstore checks, certificate/source identities, exact writer invocations and public package imports with synthetic MemoryStore composition. Host rollout, durable backend acceptance and actual client runs continue separately.
Retained assets:
knowledge-base-v0.1.4-artifact-13654629912.zip: original Actions artifact, SHA2567709befd52d64989bfd620b072f51b913fe563777d4b68f08806e5f61edac46d.knowledge-base-v0.1.4-verification.json: public verification summary and qualification limits, SHA2564f96cd0a0a6b1f10ed83e7adffdde80dd7941adf771986b1c07c860f4a1f5605.
v0.1.3
Knowledge Base 0.1.3 adds shared local-agent test reports, staff confirmation, and report-aware API/MCP operations. The five agent tools and three agent scopes remain unchanged.
Reviewed source: 8b4c25aa6a40f0c56be97f07e3b7b5ac6136a99b, signed annotated tag v0.1.3.
Release run 42533473529 completed successfully on attempt 5. Both original Node 22 and 24 gates passed 675 runtime tests across 16 files and 128 release checks, with zero skips. Failed-job recovery reused the original prepared artifact throughout; no artifact was rebuilt or repacked.
All four registry packages passed exact-byte/dependency checks, genuine npm signature and Sigstore verification, certificate and source/workflow/tag policy checks, and public-package consumer checks. Authenticated original publishing attempts are contracts 1, core 2, application 3, and MCP 4. Each original publisher encountered delayed public registry visibility; the final recovery found all four existing versions identical.
Original prepared artifact: 13638542884, SHA-256 25a4f95e7d5f9722f3b8ece3e20cf6bd35c5d6618abfa52d218319236b449464. The attached ZIP preserves those exact original bytes. The attached verification summary records package digests and original invocation identities; it is informational rather than a standalone cryptographic proof.
Consumer checks use synthetic ports and MemoryStore. Actual host activation, real client compatibility, and durable deployment acceptance remain separate gates.
Knowledge Base 0.1.2
Adds optional atomic private source references to direct application draft creation and updates. Content and its current provenance commit together, with current source-read authorization on initial calls and retries. Existing requests that omit references retain their previous identity and provenance behavior. HTTP/MCP authoring scopes remain limited to draft and evidence operations.
Historical legal source snapshots retain their exact verification rules; stricter opaque-reference checks apply to new writes. This release supplies the KB prerequisite for Support Desk resolution learning, not the completed learning workflow or either website integration.
Verified trusted release: all four packages are on npm at latest=0.1.2; bootstrap remains 0.1.0. The protected signed v0.1.2 tag identifies main commit 004044b. Source was reviewed in PR #9.
Validation:
- Node 22 and 24 each passed 439 runtime and 128 release tests with zero skips, plus composition, four-package checks, and authenticated SDK proof.
- Workflow 42436081951, final attempt 5, passed exact registry-byte, signature/provenance, and clean-consumer verification for all four packages at 2026-11-08 03:39:55 UTC.
- Every recovery used the original prepared artifact 13599399407. Already published versions were skipped only after identical-byte verification; no repacking or replacement occurred.
- Artifact archive SHA-256: c5ad819773292ef100a97a8f30e9c639b4ce5fca96c901a5873f8da6364f8609.
- Independently recorded manifest SHA-256: a7369297302182645c5157cd997c2ded0c3698c3e142efcff23866337cb51b33.
Release source: PR #9. No host activation, actual-client acceptance, or pilot gate is closed by this component release.
Knowledge Base 0.1.1
Knowledge Base 0.1.1 synchronizes the four contracts, core, application, and optional MCP packages for trusted publication.
The authenticated protocol proof composes four packed KB artifacts with exact registry @pegma/agent-access@0.1.1. The reviewed source records manual-bootstrap receipts, the verified Agent Access artifact and provenance, pin maintenance, and source-reader documentation links.
Publication is verified. The trusted Publish workflow completed its separate unprivileged registry, signature, provenance, and clean-consumer checks for all four packages on 2026-11-07 at 23:35:31 UTC. Each package's latest tag is 0.1.1; bootstrap remains 0.1.0.
Existing-login/Admin consent, requested client applications, both real hosts, and supervised pilots retain their separate acceptance gates. The manual 0.1.0 bootstrap has no OIDC provenance.