Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 29 additions & 0 deletions RELEASE_EVIDENCE.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,35 @@ Latest implementation and adoption results are in the
[dogfood execution ledger](docs/DOGFOOD-EXECUTION.md). The dated snapshots below
remain historical evidence; internal pilot acceptance is separate from G0–G4.

## 0.4.3 shipment checks, 27 September 2026

Navigation refresh no longer fails on a source-suffixed file that is not valid
UTF-8:

- Such a file, for example an MPEG transport-stream video segment saved as
`.ts`, is skipped and counted as `invalidUtf8` in the refresh exclusions.
The freshness manifest skips the same files, so status stays current, and a
file that later becomes valid text makes the index stale as before. The
0.4.2 install survey refreshed 267 of 268 local checkouts; the one failure
was this case. On that checkout the fixed build indexed 1,920 files, skipped
six as `invalidUtf8` and stayed current.
- `.gitignore` and `.z1p-navigation.json` that are not valid UTF-8 still fail
the refresh.

`@forgesworn/context` is unchanged apart from its version, kept in step with
the tools package.

Local Node 24.21.0 checks from `npm ci --ignore-scripts` passed 457 tests,
independent packed-package smoke, navigation stdio smoke (now including a
skipped and counted invalid-UTF-8 source), 22 scale tests and the 10k postings
probe. Both unchanged benchmark gates passed with required-source recall 1.0:
raw evidence 37.02x, navigation 364.88x (the baseline is this repository's own
source, so the figures move with it).

Measured benefit: none shown. This restores coverage for affected checkouts
and was not measured on an executor. No token, subscription or cash saving is
claimed. Reconnect existing MCP servers after upgrading.

## 0.4.2 shipment checks, 27 September 2026

Local navigation widened so one client entry can serve every ordinary
Expand Down
4 changes: 2 additions & 2 deletions docs/GETTING-STARTED.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,8 +27,8 @@ matching core version:
mkdir context-install
cd context-install
npm init -y
npm install --ignore-scripts /absolute/path/to/forgesworn-context-0.4.2.tgz \
/absolute/path/to/forgesworn-context-tools-0.4.2.tgz
npm install --ignore-scripts /absolute/path/to/forgesworn-context-0.4.3.tgz \
/absolute/path/to/forgesworn-context-tools-0.4.3.tgz
```

For that installation, use
Expand Down
6 changes: 3 additions & 3 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

6 changes: 3 additions & 3 deletions packages/context-tools/THIRD_PARTY_NOTICES.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Third-party notices

These notices accompany `@forgesworn/context-tools@0.4.2`. The package itself is
These notices accompany `@forgesworn/context-tools@0.4.3`. The package itself is
MIT licensed, Copyright (c) 2026 TheCryptoDonkey; see `LICENSE`.

Runtime dependencies are installed separately by the package manager, not
Expand All @@ -9,9 +9,9 @@ notices below cover direct runtime dependencies; retain the licence files
from transitive dependencies as well when redistributing an installation or
bundle. Dependency versions and source links refer to this release.

## @forgesworn/context@0.4.2
## @forgesworn/context@0.4.3

Declared licence: MIT. Source package: https://www.npmjs.com/package/@forgesworn/context/v/0.4.2
Declared licence: MIT. Source package: https://www.npmjs.com/package/@forgesworn/context/v/0.4.3

```text
MIT License
Expand Down
4 changes: 2 additions & 2 deletions packages/context-tools/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@forgesworn/context-tools",
"version": "0.4.2",
"version": "0.4.3",
"description": "Local CLI and MCP tools for Z1P Core encrypted context",
"license": "MIT",
"type": "module",
Expand Down Expand Up @@ -36,7 +36,7 @@
"test": "vitest run --config vitest.config.ts"
},
"dependencies": {
"@forgesworn/context": "0.4.2",
"@forgesworn/context": "0.4.3",
"@modelcontextprotocol/sdk": "1.30.0",
"@noble/hashes": "1.8.0",
"ignore": "7.0.9",
Expand Down
2 changes: 1 addition & 1 deletion packages/context/THIRD_PARTY_NOTICES.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Third-party notices

These notices accompany `@forgesworn/context@0.4.2`. The package itself is
These notices accompany `@forgesworn/context@0.4.3`. The package itself is
MIT licensed, Copyright (c) 2026 TheCryptoDonkey; see `LICENSE`.

Runtime dependencies are installed separately by the package manager, not
Expand Down
2 changes: 1 addition & 1 deletion packages/context/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@forgesworn/context",
"version": "0.4.2",
"version": "0.4.3",
"description": "Z1P Core portable signed and encrypted context collections",
"license": "MIT",
"type": "module",
Expand Down
Loading